- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- RHAS3U3 - ifconfig eth0 down/up
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-01-2004 05:19 AM
тАО12-01-2004 05:19 AM
i have the following problem with ifconfig comand:
everytime i run the command 'ifconfig eth0 down' the network goes down - fine. now i run 'ifconfig eth0 up' - the network starts up BUT from now on i don't have a functioning name resolution anymore. i can ping other systems via their ip addresses but i cannot ping them by their names anymore.
also the routing table does not have a default gateway set anymore.
doing the same with 'service network stop/start' doesn't show this behaviour....
any ideas why and how to fix this ?
thanks,
Matthias
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-01-2004 05:25 AM
тАО12-01-2004 05:25 AM
Re: RHAS3U3 - ifconfig eth0 down/up
example
ifconfig eth0 192.168.0.50 mask 255.255.255.0 up
Your subnet mask needs to be compatible with the subnet masks of the servers in /etc/resolv.conf for DNS names resolution to work right.
SEP
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-01-2004 05:41 AM
тАО12-01-2004 05:41 AM
Re: RHAS3U3 - ifconfig eth0 down/up
but didn't work for me here ????
my DNS server is located in another subnet and the default gateway is still not showing up even if i specify the netmask...and i can't specify a gateway if i see it right ...
so same behaviour as befire ...any other ideas ...
Matthias
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-01-2004 09:32 AM
тАО12-01-2004 09:32 AM
SolutionWhen you remove the interface, all the associated routing also gets removed (so any subnet routes, and if the default route is out that interface, that too!).
After you've brought the interface back up, you then need to re-add any static or default routes that previously relied upon that interface.
Short cut would be to use the 'ifdown eth0' and 'ifup eth0' routines, which take all of this into consideration. These are the commands that the 'network' service call to stop/start an interface.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-01-2004 07:08 PM
тАО12-01-2004 07:08 PM
Re: RHAS3U3 - ifconfig eth0 down/up
the reason was just a test situation where i wantet to stop networking of one system while another was using the test network for performance measuring ....
you are right, ifdown and ifup does the job perfectly instead of ifconfig eth0 down/up.
problem solved - thanks for any help to everybody !!
bye
Matthias