#8410 closed bug (fixed)
NetworkStatus too noisy
Reported by: | bbjimmy | Owned by: | anevilyak |
---|---|---|---|
Priority: | normal | Milestone: | R1 |
Component: | Servers/net_server | Version: | R1/Development |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | All |
Description
The NetworkStatus utility gives farr too many notifications using a wireless connection.
using hrev43878
Using my eeepc connecting to my home network, ( the router is about 6 feet away) NetworkStatus keeps interrupting my work with notices that the connection has been established. It seems that the network dhcp is re-assigning the ip, but it is always the same ip. This is not unusual for wireless networks. In this case the notice is not of any value as the fact that the network has re-established the same connection does not have any affect on my ability to use the connection.
Attachments (1)
Change History (12)
comment:1 by , 13 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
Version: | R1/alpha3 → R1/Development |
comment:2 by , 13 years ago
comment:4 by , 13 years ago
Maybe this is not a NetworkStatus issue, but a wireless networling issue.
comment:5 by , 13 years ago
For some reason your adapter changes speed from 10Mbit to 100Mbit very often
/dev/net/atheroswifi/0: media change, media 0x8300af quality 1000 speed 10000000 /dev/net/atheroswifi/0: media change, media 0x8300b0 quality 1000 speed 1000000000
It could also be a problem with atheroswifi driver.
comment:6 by , 13 years ago
There is a bug in src/servers/net/AutoconfigLooper.cpp, in AutoconfigLooper::MessageReceived() : a new DHCP configuration is done each time the link status is reported as active. It should be done *only* when it become active, by comparing with previous state.
comment:7 by , 13 years ago
Component: | Applications/NetworkStatus → Servers/net_server |
---|
comment:8 by , 13 years ago
Owner: | changed from | to
---|---|
Status: | assigned → in-progress |
comment:9 by , 13 years ago
Thanks for the hint phoudoin! bbjimmy, please check if hrev44001 does any better for you.
comment:10 by , 13 years ago
Resolution: | → fixed |
---|---|
Status: | in-progress → closed |
Closing ticket. Please reopen if the problem persists.
comment:11 by , 13 years ago
Sorry it took so long to test, but yes indeed this seems to have resolved the issue.
eeehh. I could see this... I wasn't taking into account *tiny* dhcp lease renewal times (which really isn't normal however, you may want to make your dhcp leases a wee bit longer)