|
Description
Renew ip address
flush DNS
Etc
Attachments
No attachments.
Duplicates
Comments
|
will_in_wi wrote on the 28 Feb 08 at 14:49
| |
Click on the network manager icon in the system tray and then click on your currently running connection. Voila, reconnect.
|
|
facundocorradini wrote on the 28 Feb 08 at 16:17
| |
That's already implemented and working.
|
|
Shosta wrote on the 28 Feb 08 at 16:54
| |
Perhaps, it needs a menu option in Network Manager, I click in the currently running connection is something very hidden.
|
|
dark wrote on the 29 Feb 08 at 00:17
| |
It sounds good and can already be done by clicking on your connection but many times people think that "repair connection" will get you connected to the internet 100% of the time when it is really an ISP or router fault.
|
|
buggin wrote on the 29 Feb 08 at 00:37
|
#!/bin/sh
sudo /etc/init.d/networking restart; sudo dhclient
one step further than clicking on the current connection again in NM
|
|
plinehan wrote on the 29 Feb 08 at 00:39
|
Maybe a "diagnose and repair" option, ala Vista, would resolve the problem 'dark' is describing. It does a fairly good job of indicating what the problem is when it can't seem to resolve the issue itself via DNS flushes, etc.
This gives an unambiguous, explicit way for users to deal with bad connections. After months of Ubuntu use I didn't realize that clicking on the icon repaired the connection.
|
|
jamessnell wrote on the 29 Feb 08 at 03:47
|
Just don't call it "repair" that promotes confusion as to what's really going on. It's stupid and breeds ignorrance. Strong feelings for me there, too many users not understanding what is meant by "repair".
The functionality _is_ important, I'd call it "Refresh Connection" or "Refresh Network Settings" - after all, that's what we're talking about. I think new Windows users won't be injured by that difference too.
Thanks!
|
|
trjonescp wrote on the 29 Feb 08 at 04:57
| |
Don't forget to flush the ARP cache
|
|
hackel wrote on the 29 Feb 08 at 05:44
| |
Why is this ever needed? I don't ever need to do this...
|
|
nyvalbanat wrote on the 29 Feb 08 at 14:34
| |
It happened several times that I booted up and the network was not connected, ie no IP address from dhcp (two Linux aspiring people at work played with vm images and had that problem in the last 2 weeks). The solution was as easy as sudo dhclient, but there was no way for them to know that. I'm sure a network "repair/refresh/whatever" icon would go a long way.
|
|
upbeat.linux wrote on the 29 Feb 08 at 16:37
|
Again this is a user comprehension issue: not wanting to take the time to learn something new or understand network troubleshooting (this is well outside the scope of an idea). Ubuntu isn't supposed to mirror Windows.
People just need to deal with the difference and educated themselves.
|
|
sketec wrote on the 29 Feb 08 at 18:12
|
@upbeat.linux : Although, I agree that people need to educate themselves, I don't think Ubuntu will ever do well 'with general audiences' if something like this is not implemented.
Something as simple as 'restart networking' when you right click the nm-aplet would not only be clear to newbies, but quick and useful for the elite. Of course, we know how to do this from command line, and you can even achieve the same effect by un-checking 'enable networking' and re-checking. Having something like 'restart networking' is more accurate wording too.
|
|
drinkypoo wrote on the 29 Feb 08 at 18:55
|
Whatever is broken on my system, I have not been changing things much (php.ini changes, pulseaudio config, but no dhclient for example) and I have tons of DHCP problems. Roaming is real trouble for me.
In fact there was even a dhclient running this last time I couldn't connect, NetworkManager had started it and not done a very good job. So I couldn't just run my own dhclient, because it would reset my adapter to an unconfigured state. I don't know whose fault this is but I haven't changed any config files for either NetworkManager or dhclient.
|
|
adelie wrote on the 29 Feb 08 at 22:04
|
my script preference:
sudo ifconfig eth0 down; sudo ifconfig eth0 up; sudo dhclient
It is amazing, imho, how often ubuntu seems to 'recognize on its own' the necessity to do this, for example, if you unplug your network cable, and plug it back in, you get the same result. However, a few time I have had my router puke on me, and the above has been the quickest k.i.s.s solution.
|
|
dan.fernandez wrote on the 1 Mar 08 at 09:04
|
"People just need to deal with the difference and educated themselves."
Educate on what? On clicking again on an already connected network so that it reconnects? This is counter-intuitive, everyone should get a hint the functionality is there. You can expect users to educate themself on "what does this button do" but not on searching for something not visible on first glare.
A "reconnect" button is NOT a hard development issue (since the functionality is already in the program: it is activating it when clicking again on the menu entry).
|
|
jojoman02 wrote on the 3 Mar 08 at 22:19
|
Perhaps a pop-up when you click a connection you are already connected to such as "Refreshing Network FOOBAR" which would do all the actions above, over time people would find out that clicking on the connection again will refresh "repair" it.
People might say this is distracting but currently there is good indication that clicking a connection refreshes it (besides minor icon changes in NM), most of those people can also live through a 1 sec message when refreshing a network, i mean seriously how often do you refresh your network? and if you do it often I'm sure you'd want a message confirming it is being refreshed.
|
|
jojoman02 wrote on the 3 Mar 08 at 22:21
| |
to clarify when i mean pop-up i'm talking about a notification message not a pop-up window or anything annoying like that. the message would go away by itself in 1 sec and should be small and in the corner coming from NM tray icon.
|
|
jsnow wrote on the 4 Mar 08 at 05:19
|
Perhaps one solution would be to have dhcp automatically request a new lease if the network cable is plugged in after being unplugged and either a) the current lease is expired (the network cable has been unplugged for a long time), or b) the dhcp server that issued the lease does not respond to an arping (the computer has been plugged into a differetn network).
That would automatically resolve two of the main situations in which I would manually restart the network.
(One of the comments above indicates that it already does something like this. If so, then please disregard my post; my one ubuntu box that uses dhcp is a bit out of date.)
|
|
vabue wrote on the 4 Mar 08 at 18:50
| |
Maybe just make custom menu point "repair connection"?
|
|
esoterikism wrote on the 5 Mar 08 at 15:04
| |
+1 Im sick of typing sudo /etc/init.d/networking restart after all these years. Though its one of the fastest things i can type :)
|
|
Eser wrote on the 14 Mar 08 at 10:01
| |
+1
|
 saivann (Moderator) wrote on the 8 May 08 at 06:32
| |
I don't see that feature implemented in Hardy? Can someone confirm if it is really implemented, and where??
|
|
Mishtal wrote on the 13 May 08 at 00:16
|
as a corollary
i personally would find it useful for there to be a "diagnose network problems" listed in the network manager options.
during my operating systems class at college, the wired internet connections built into the table seems to connect absolutely fine. i get a connection to instant messanger, websites, email, etcetera. but whenever i send any significant traffic through the pipe, the router literally ignores me until i unplug and replug the cable multiple times. restarting my system doesnt do anything, and neither does messing with the network manager via the laptop. only unplugging/replugging.
something nice and easy, to test if you have legitimate network connectivity and not pretend connectivity would be especially helpful to new users.
"why isnt my internet working?!!?"
*press diagnose network problem*
program runs
"you dont have your ethernet cable plugged in"
"for some reason i cant reach *list of well known websites*"
"your traffic is being blocked"
something that would make it easier for new users to quickly identify the problems.
this would also be useful for giving support, im sure people can see why.
as a side note.
single and/or double clicking the network manager in heron does not do anything for me. when connected or not.
|
|
saivann (Moderator) wrote on the 13 May 08 at 04:05
| |
But even before that happens, we should try to find out why this idea is marked as done, is it implemented or I should set back the status to "new"?
|
|
Mishtal wrote on the 13 May 08 at 15:51
|
currently, my local copy of Heron does not have that feature.
but i should disclaimer that by saying that my hardware configuration doesnt like Heron or its associated drivers.
|
|
saivann (Moderator) wrote on the 15 May 08 at 23:51
| |
Idea set back to "new" as the status "implemented" seems to be a mistake.
|
|
Abra_Kadabra wrote on the 27 Aug 08 at 17:32
| |
Repair doesn't work!
|
|
r0g wrote on the 30 Sep 08 at 09:17
|
I think a lot of ppl are having trouble with the NDIS wrapper in particular. My machine's wireless arbitrarily craps out after I been using it for a few hours, occasionally days. All the simple one line 'restarts' I found didn't do anything but eventually I hit on the solution of pulling NDIS out and sticking it in again. This reliably gets my wifi up and running again (although it once seemed to coincide with a system lock up so save your work first!!!)
Here's the script 'fixnet_script':
#!/bin/bash
echo Removing NDIS Wrapper from kernel
rmmod ndiswrapper
sleep 10
echo Reloading NDIS Wrapper
modprobe ndiswrapper
sleep 5
echo Bringing WLAN up
ifconfig wlan0 up
print Restarting Networking
sleep 5
/etc/init.d/networking restart
For convenience I've made another script which I've attached to an icon on my launch bar so I don't have to drop into a terminal and sudo to run it...
#!/bin/bash
echo "Attempting NDIS fix..."
gksudo fixnet_script
Naturally I'd prefer an NDIS Wrapper that could stay up as long as I can but I still find it pretty amazing that it works at all with all those hundreds and thousands of random win32 drivers!
Roger Heathcote.
|
Post your comment
|
