What is the difference between 'networking restart' and 'ifup ethx'
Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
What is the difference between 'networking restart' and 'ifup ethx'
Hi,
I had a D-Link 802.11g router and it connected to Internet. Other computers at my home can connected to Internet through an Ubuntu 8.04 Server squid3 box via the D-Link router. But, there is a headache :
If the D-Link router restart, for go Internet again I must execute '/etc/init.d/networking restart'. At same time, the squid3 daemon workings fine.
I don't know what's the exact problem at there and need any advice and help.
Re: What is the difference between 'networking restart' and 'ifup ethx'
When your wireless router gets restarted/power cycled, the connections on your computer also gets broken. By doing a "/etc/init.d/networking restart" you are basically re-establishing the wireless connections.
Your squid daemon will be accepting connections, but as long as the squid cannot access internet it wont be able to serve the clients.
Yes, You are right suga_rray. But why is it now establishing the connection automatically? I don't know much about the Ubuntu 8.04, but if HolyJoe requires a automatic reconnect, he/she may run a cron job every minute checking the availablity of the router.
ping -c 3 192.168.0.1 -w 3 ; if [ $? != 0 ] ; then /etc/init.d/networking restart ; fi
Yes, You are right suga_rray. But why is it now establishing the connection automatically? I don't know much about the Ubuntu 8.04, but if HolyJoe requires a automatic reconnect, he/she may run a cron job every minute checking the availablity of the router.
ping -c 3 192.168.0.1 -w 3 ; if [ $? != 0 ] ; then /etc/init.d/networking restart ; fi
192.168.0.1 is the router IP address.
Hope this helps
Thanks.
Yes, I want to establish the Internet connection automatically. I can receive the replies from ping to the router, but I cannot connect to Internet and I must execute '/etc/init.d/networking restart' (does not need to restart the squid3)
What's wrong?
When your wireless router gets restarted/power cycled, the connections on your computer also gets broken. By doing a "/etc/init.d/networking restart" you are basically re-establishing the wireless connections.
Your squid daemon will be accepting connections, but as long as the squid cannot access internet it wont be able to serve the clients.
I guess this is what is happening with you.
Thanks.
Yes, But how can I establish the Internet connection automatically.
You shouldn't need to - I reset my (home) router regularly. Ubuntu desktop, not Server mind you.
The only time I've needed to issue a network restart is when the driver hasn't loaded successfully. Always at startup, not later on though.
You shouldn't need to - I reset my (home) router regularly. Ubuntu desktop, not Server mind you.
The only time I've needed to issue a network restart is when the driver hasn't loaded successfully. Always at startup, not later on though.
Hi, syg00,
Thank you for your reply.
I don't like execute '/etc/init.d/networking restart' all the time after the router restart/power cycled too May be I should let my problem more clear, make some examples to emulate the situation:
$sudo ifdown eth0 #eth0 is the public NIC of my Ubuntu 8.04 Server
$sudo ifup eth0
after above commands has been executed, I can receive ping replies from the router except other outside URL such as www.ubuntu.com.
Need your help to find the key of the headache, thank you.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.