BLU Discuss list archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Discuss] network issue
- Subject: [Discuss] network issue
- From: abreauj at gmail.com (John Abreau)
- Date: Fri, 14 Mar 2014 05:26:54 -0400
- In-reply-to: <08B8D88E-D033-46C3-9A5E-97169ED372C3@gmail.com>
- References: <20140313232513.GA25440@betelgeuse> <08B8D88E-D033-46C3-9A5E-97169ED372C3@gmail.com>
Just to cover all bases: You ran "ifconfig eth0 up" to bring up the Ethernet interface, and that got its ip address via dhcp, correct? This gets you the ip address, which enables you to reach other machines on the same subnet, but it does *NOT* set the default route for you. Did you set the default route by running "route add --net default gw ROUTER-ADDRESS"? On Mar 14, 2014, at 5:12 AM, John Abreau <abreauj at gmail.com> wrote: > > > On Mar 13, 2014, at 7:25 PM, dan moylan <jdm at moylan.us> wrote: > >> however, when i enter sudo ifconfig eth0 up, i get connected >> to the LAN, and can ssh into the other linux computer on the >> LAN, but can't see out -- frustrating. > > > Sounds to me like the default route is messed up. > > If you're setting it correctly on the command line, then maybe NetworkManager is noticing your changes and automatically changing them back to the wrong settings. I had a similar issue a few years ago while installing a new server where an overly aggressive NetworkManager daemon was ultimately the culprit, and I had to disable NetworkManager to get networking to function correctly. >
- References:
- [Discuss] network issue
- From: jdm at moylan.us (dan moylan)
- [Discuss] network issue
- From: abreauj at gmail.com (John Abreau)
- [Discuss] network issue
- Prev by Date: [Discuss] network issue
- Next by Date: [Discuss] network issue
- Previous by thread: [Discuss] network issue
- Next by thread: [Discuss] network issue
- Index(es):