Yes, you are correct. A static config won't take the interface down so it
won't flush the routes.
On Apr 3, 2012 5:28 PM, "Mike Connors" wrote:
> >
> > > > It shouldn't be in a "running" state unless there is physical
> > > connectivity
> > > > and packets are flowing across the interface.
> > >
>
> > > It shouldn't be in a "running" state unless there is physical
> > connectivity
> > > and packets are flowing across the interface.
> >
> >The eth0 interface is not RUNNING, but the routes are there and so is
> > the
> > constipation.
> >
> Actually you are wrong on this point. As you s
On Tue, 3 Apr 2012, Larry Brigman wrote:
> Actually you are wrong on this point. As you stated earlier today, once
> you 'ifconfig eth0 down' things worked. If that was truely the case then
> the interface was up but without a carrier. The routes would remain
> intact as the kernel doesn't know
On Tue, Apr 3, 2012 at 1:33 PM, Rich Shepard wrote:
> On Tue, 3 Apr 2012, Mike Connors wrote:
>
> > I cannot get my eth0 to go in / out of the "running" state by running
> ifup
> > / ifdown, although it works with the loopback interface.
>
>On Slackware, using 'ifconfig eth0 up|down' I can.
>
On Tue, 3 Apr 2012, Mike Connors wrote:
> I cannot get my eth0 to go in / out of the "running" state by running ifup
> / ifdown, although it works with the loopback interface.
On Slackware, using 'ifconfig eth0 up|down' I can.
> Also, two default routes on the same network and I have no probl
On Tue, 3 Apr 2012, Rich Shepard wrote:
> Now, what I'd like from you networking gurus is a script I can put in
> rc.local to test if wlan0 is RUNNING. And, if it is, to take down eth0.
> This way eth0 is taken out of the stack when the system boots and dhcpcd
> sees a WAP, but otherwise it is t
>
> Running 'ifconfig -a' showed routes for both eth0 and wlan0, but only the
> latter was RUNNING. So, as root, I ran 'ifconfig eth0 down' to remove the
> routes and ... voila! That was the problem.
>
> Now, what I'd like from you networking gurus is a script I can put in
> rc.local to test
On Mon, 2 Apr 2012, Russell Johnson wrote:
> Nothing would be going out eth0, since it's not connected to anything,
> and, as per Rich's message, it's not in a running state. As I recall, the
> IPs Rich reported are in two different subnets, so, in theory, the IP
> stack should try both routes, if
