Re: [TCLUG:8792] Multiple Ethernet Woes

To: tclug-list@mn-linux.org
Subject: Re: [TCLUG:8792] Multiple Ethernet Woes
From: Nate Carlson <natecars@infiniteloop.com>
Date: Thu, 30 Sep 1999 18:00:17 -0500 (CDT)
In-Reply-To: <199909302258.RAA18927@infinity.infiniteloop.com>
OK.. try 'route add -host 192.168.6.1 eth1 ; route add -net 192.168.6.0 gw
192.168.6.1 eth1' (if I'm remembering right, eth1 is the 3c509. If I'm
wrong, change both eth1's to eth0.) That should work, unless my memory is
not working AT ALL today.  :)

----
Nate Carlson
the infinite loop
natecars@infiniteloop.com

On Thu, 30 Sep 1999, Brian Ackermann wrote:

> route add -net 192.168.6 gw 192.168.6.1
> 
> SIOCADDRT: Invalid Argument
> 
> Looks good to me, but I'm a newbie at this....
> 
> ----------
> >From: "Brian Ackermann" <brianj@subrad.com>
> >To: tclug-list@mn-linux.org
> >Subject: Re: [TCLUG:8792] Multiple Ethernet Woes
> >Date: Thu, Sep 30, 1999, 5:54 PM
> >
> 
> > heh...I'll try it....
> >
> > ----------
> >>From: Nate Carlson <natecars@infiniteloop.com>
> >>To: tclug-list@mn-linux.org
> >>Subject: Re: [TCLUG:8792] Multiple Ethernet Woes
> >>Date: Thu, Sep 30, 1999, 5:08 PM
> >>
> >
> >> err, yeah, add the gateway that the machines on the 192.168.6 network use
> >> by default after 'gw'.. so, for example, if the isp's configured gateway
> >> is 192.168.6.1, use 'route add -net 192.168.6 gw 192.168.6.1'. Should
> >> work. And I guess the route I was having you delete doesn't exist. Ah
> >> well. Should be ok.
> >>
> >> ----
> >> Nate Carlson
> >> the infinite loop
> >> natecars@infiniteloop.com
> >>
> >> On Thu, 30 Sep 1999, Brian Ackermann wrote:
> >>
> >>> %route del 192.168.6
> >>> SIOCDELRT : No Such Process....
> >>>
> >>> %route add -net 192.168.6 gw
> >>> Usage: blah blah blah blah....
> >>>
> >>>
> >>> ----------
> >>> >From: Nate Carlson <natecars@infiniteloop.com>
> >>> >To: tclug-list@mn-linux.org
> >>> >Subject: Re: [TCLUG:8792] Multiple Ethernet Woes
> >>> >Date: Thu, Sep 30, 1999, 4:17 PM
> >>> >
> >>>
> >>> > Hmmmm....... try 'route del 192.168.6 ; route add -net 192.168.6 gw
> >>> > <gateway_for_192.168.6_network>'.. just out of curiousity.. that _might_
> >>> > work.
> >>> >
> >>> > ----
> >>> > Nate Carlson
> >>> > the infinite loop
> >>> > natecars@infiniteloop.com
> >>> >
> >>> > On Thu, 30 Sep 1999, Brian Ackermann wrote:
> >>> >
> >>> >> Here's an interesting little bit....
> >>> >>
> >>> >> After boot, if I ping the 192.168.6.48 address (the card that doesn't
> >>> work...)
> >>> >> Ping is successful....I try again...success!!! hurrah!!!
> >>> >>
> >>> >> I go to the Linux box, and ping a machine on the 192 subnet, and
> > nothing...
> >>> >>
> >>> >> I go back to the machine where the pings worked...and....nothing...
> >>> >>
> >>> >> So, it works, so long as I don't ping out with the linux box...
> >>> >>
> >>> >> We must be getting close....
> >>> >>
> >>> >> Brian
> >>> >> ----------
> >>> >> >From: "Brian Ackermann" <brianj@subrad.com>
> >>> >> >To: tclug-list@mn-linux.org
> >>> >> >Subject: Re: [TCLUG:8792] Multiple Ethernet Woes
> >>> >> >Date: Thu, Sep 30, 1999, 4:13 PM
> >>> >> >
> >>> >>
> >>> >> > I don't think so...but let me try....
> >>> >> >
> >>> >> > That would be negatory....
> >>> >> >
> >>> >> >
> >>> >> > ----------
> >>> >> >>From: Nate Carlson <natecars@infiniteloop.com>
> >>> >> >>To: tclug-list@mn-linux.org
> >>> >> >>Subject: Re: [TCLUG:8792] Multiple Ethernet Woes
> >>> >> >>Date: Thu, Sep 30, 1999, 3:58 PM
> >>> >> >>
> >>> >> >
> >>> >> >> Hmmmm... what if you do 'ifconfig eth0 down' and reconfigure eth1 to
> > the
> >>> >> >> settings eth0 was using? Will it talk then, with the second ethernet
> > card
> >>> >> >> in the machine, and just disabled?
> >>> >> >>
> >>> >> >> ----
> >>> >> >> Nate Carlson
> >>> >> >> the infinite loop
> >>> >> >> natecars@infiniteloop.com
> >>> >> >>
> >>> >> >> On Thu, 30 Sep 1999, Brian Ackermann wrote:
> >>> >> >>
> >>> >> >>> 3c509 = IRQ 10  Address 0x0300
> >>> >> >>> 3c905 = IRQ 11  Address 0xdc00
> >>> >> >>>
> >>> >> >>> Doesn't look like an IRQ problem to me...
> >>> >> >>>
> >>> >> >>> Though, /proc/interrupts was looking interesting...
> >>> >> >>> eth0 having tons of interrupts, and eth1 having zero....
> >>> >> >>>
> >>> >> >>> That says SOMETHING....
> >>> >> >>>
> >>> >> >>> Thanks for all the help guys....I appreciate this...
> >>> >> >>>
> >>> >> >>> Brian
> >>> >> >>> >
> >>> >> >>> > IRQ Conflict! (?)
> >>> >> >>> >
> >>> >> >>> > --
> >>> >> >>> >  _  _  _  _ _  ___    _ _  _  ___ _ _  __   You've Got Mail!
> >>> >> >>> > / \/ \(_)| ' // ._\  / - \(_)/ ./| ' /(__
> >>> >> >>> > \_||_/|_||_|_\\___/  \_-_/|_|\__\|_|_\ __)
> >>> >> >>> > [ Mike Hicks | http://umn.edu/~hick0088 |
> mailto:hick0088@tc.umn.edu
> > ]
> >>> >> >>> >
> >>> >> >>> >
> > ---------------------------------------------------------------------
> >>> >> >>> > To unsubscribe, e-mail: tclug-list-unsubscribe@mn-linux.org
> >>> >> >>> > For additional commands, e-mail: tclug-list-help@mn-linux.org
> >>> >> >>> >
> >>> >> >>> >
> >>> >> >>>
> >>> >> >>>
> >>> >> >>> ---------------------------------------------------------------------
> >>> >> >>> To unsubscribe, e-mail: tclug-list-unsubscribe@mn-linux.org
> >>> >> >>> For additional commands, e-mail: tclug-list-help@mn-linux.org
> >>> >> >>>
> >>> >> >>
> >>> >> >>
> >>> >> >> ---------------------------------------------------------------------
> >>> >> >> To unsubscribe, e-mail: tclug-list-unsubscribe@mn-linux.org
> >>> >> >> For additional commands, e-mail: tclug-list-help@mn-linux.org
> >>> >> >>
> >>> >> >>
> >>> >> >
> >>> >> >
> >>> >> > ---------------------------------------------------------------------
> >>> >> > To unsubscribe, e-mail: tclug-list-unsubscribe@mn-linux.org
> >>> >> > For additional commands, e-mail: tclug-list-help@mn-linux.org
> >>> >> >
> >>> >> >
> >>> >>
> >>> >>
> >>> >> ---------------------------------------------------------------------
> >>> >> To unsubscribe, e-mail: tclug-list-unsubscribe@mn-linux.org
> >>> >> For additional commands, e-mail: tclug-list-help@mn-linux.org
> >>> >>
> >>> >
> >>> >
> >>> > ---------------------------------------------------------------------
> >>> > To unsubscribe, e-mail: tclug-list-unsubscribe@mn-linux.org
> >>> > For additional commands, e-mail: tclug-list-help@mn-linux.org
> >>> >
> >>> >
> >>>
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: tclug-list-unsubscribe@mn-linux.org
> >>> For additional commands, e-mail: tclug-list-help@mn-linux.org
> >>>
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: tclug-list-unsubscribe@mn-linux.org
> >> For additional commands, e-mail: tclug-list-help@mn-linux.org
> >>
> >>
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tclug-list-unsubscribe@mn-linux.org
> > For additional commands, e-mail: tclug-list-help@mn-linux.org
> >
> > 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tclug-list-unsubscribe@mn-linux.org
> For additional commands, e-mail: tclug-list-help@mn-linux.org
>
Prev by Date: Re: [TCLUG:8792] Multiple Ethernet Woes
Next by Date: ip masquerade and packet forwarding
Prev by thread: Re: [TCLUG:8792] Multiple Ethernet Woes
Next by thread: Decoding BinHex format
Index(es):
- Date
- Thread