nm-applet should change state

[ajmal_82]

i have ethernet eth0 card and connected to wired lan connection through dhcp.
although my card is not detected by ubuntu i installed modules using modprobe
now the real problem is nm applet on taskbar/desktop doesnot reflect the change in
connection state .i.e its now connected.its serious to most users from windows
environment also it doesnt notify about changes in network like if new server detected,
failed,new shared lan pcs found,took too long to connect etc.
i have reprorted bug about my card i.e silan ethernet card.please reply soon

[Basilio Kublik (sourcercito)]

Thanks for taking the time to report this bug and helping to make Ubuntu better. Could you please add the /var/log/syslog to your bug report as an attachment? Also you can submit more information for it by looking to https://wiki.ubuntu.com/DebuggingNetworkManager , Thanks in advance.

[wvengen (wvengen)]

If I understand you correctly, you're proposing more detailed status information in nm-applet? It may indeed be a useful to have the reason of network failure in the tooltip, if such is on-spot enough in most cases and not confusing. You already can view network connection status for some information from nm-applet's context menu.

If you'd like to propose enhancements, please explain them in more detail. I have no idea how windows behaves on this. What means 'new server detected'? If it's that the dhcp lease expired and it got a new one from a different server, it may indeed be good to show a notification (someone trying to spoof, for example). But what should the user do in that case? Should we warn the user that it may be spoofed? I have no idea how often this would occur legitimately. You see that just copying ideas from another operating system is not fruitful in itself, taking ideas and applying them to make the user more informed and more at ease that brings progress is.
It may also be useful to have a difference in status for 'server denied request' and 'didn't get a response', I don't think we have that now (your mention of 'failed' and 'took too long').

Please remember that network-manager is relatively young and still progressing much each release. It may just need some time to be fully feature-loaded. If you'd like developers to pick up on your idea, please write them down in more detail: what exactly do you miss, and why, and what do you think it should be like. There's no guarantee that it'll be implemented right away, but that's the way to get attention.

Thank your for your suggestions, we need input from people like you to make ubuntu better.

[wvengen (wvengen)]

Sorry, I forgot one thing (which Basilio correctly asked information, whoops): does your connection work at all with network-manager, do you see a difference when the cable is plugged in or not (different icon for connected / not connected)? If not, you really need to supply the technical info asked for.

[ajmal_82 (ajmal-82)]

apparently my connection works and its only problem with network manager applet,so i tried thi and works(shows me status)
on taskbar>>right click add applet>>network speed applet.
so i dont know whats wrong with Nm but it should surely needs correction with errors
also it doesnt show status when manually connected interface or when i put static or dhcp address that it didnt assign at first.by default it says roaming mode for my card that i changed to dhcp.

[wvengen (wvengen)]

Does it help to switch to roaming mode? That basically is dhcp managed by network-manager.
To help us understand the problem, please follow comment #1 if possible.

[ajmal_82 (ajmal-82)]

iam using netspeed applet it shows both speed and status of network.but them main network monitor applet doesnt even say network detected or connected to my ethernet device eth0.I have set my connection to DHCP and got network ip.i will submit the varlog next time.no roaming mode as iam using lan on home desktop pc.

[Jayson Rowe (jayson.rowe)]

Since it's been a very long time since any additional info was added to this bug, I'm just checking to see if this is still an issue, and find out what additional work should be done on this bug.

[Charlie Kravetz (cjkgeek)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!