[ale] Interenet connection
ChangingLINKS.com
x3 at ChangingLINKS.com
Fri Feb 21 14:40:07 EST 2003
Yes. Very much so. But now, <crying> I get great connection to my other
machines, but no "net" AND the 0.0.0.0 line is still missing from the route
-n.
On Friday 21 February 2003 1:24 pm, Geoffrey wrote:
> Were you able to get to the internet prior to the bond effort???
>
> ChangingLINKS.com wrote:
> > No dice. Still can't ping yahoo. I first had to modify the command to get
> > acceptance. Then, I added each one (and the pair of eth) per directions.
> > I tried removing the "extra bond0" but when I did, it said "network
> > unreachable" and I had to restart the network (which changed all of the
> > settings back).
> >
> > I used:
> > route add -net 192.168.123.0 gw 192.168.123.120 netmask 255.255.255.0 dev
> > bond0/eth0/eth1 to get this:
> >
> > Kernel IP routing table
> > Destination Gateway Genmask Flags Metric Ref Use
> > Iface 192.168.123.0 192.168.123.120 255.255.255.0 UG 0 0
> > 0 bond0 192.168.123.0 192.168.123.120 255.255.255.0 UG 0 0
> > 0 eth1 192.168.123.0 192.168.123.120 255.255.255.0 UG 0
> > 0 0 eth0 192.168.123.0 0.0.0.0 255.255.255.0 U 0
> > 0 0 bond0 192.168.123.0 0.0.0.0 255.255.255.0 U
> > 0 0 0 eth0 192.168.123.0 0.0.0.0 255.255.255.0 U
> > 0 0 0 eth1 127.0.0.0 0.0.0.0 255.0.0.0
> > U 0 0 0 lo
> >
> > On Thursday 20 February 2003 2:07 pm, Mike Lockhart wrote:
> >>If memory serves me correct, one of these:
> >>
> >>route add -net 192.168.123.0/(16 or 24) netmask xxx.xxx.xxx.xxx gw
> >>192.168.123.120 dev bond0
> >>or
> >>route add -net 192.168.123.0/(16 or 24) netmask xxx.xxx.xxx.xxx gw
> >>192.168.123.120 dev eth0
> >>or
> >>route add -net 192.168.123.0/(16 or 24) netmask xxx.xxx.xxx.xxx gw
> >>192.168.123.120 dev eth1
> >>or
> >>try both of the last 2 together (might help).
> >>
> >>My route skills are kinda rusty, but its pretty straight forward, I
> >>don't think your issue is DNS, although it wouldn't hurt to delete all
> >>lines in your resolv.conf file and put the following:
> >>
> >>nameserver 207.69.188.185
> >>nameserver 207.69.188.186
> >>
> >>just for testing purposes. (they're the mindspring nameserver, itchy &
> >>scratchy, which have never failed for me). See if these things help.
> >>
> >>Also, you might have somthing misconfigured in the bond0 setup, although
> >>if its working on the network and you can ping both of the IP's bound to
> >>it, its doubtful.
> >>
> >>- mike
> >>
> >>On Thu, 2003-02-20 at 14:20, ChangingLINKS.com wrote:
> >>>Still no luck with the "manual setting:"
> >>>
> >>>root]# route add default gw 192.168.123.120 metric 1
> >>>root]# /etc/init.d/network restart
> >>>Shutting down interface bond0: [ OK ]
> >>>Shutting down interface eth0: [ OK ]
> >>>Shutting down interface eth1: [ OK ]
> >>>Setting network parameters: [ OK ]
> >>>Bringing up interface lo: [ OK ]
> >>>Bringing up interface bond0: [ OK ]
> >>>Bringing up interface eth0: [ OK ]
> >>>Bringing up interface eth1: [ OK ]
> >>>[root at links root]# ping www.yahoo.com
> >>>ping: unknown host www.yahoo.com
> >>>root]#
> >>>
> >>>Traffic on the LAN is fine. Even running an NFS server. Just can't get
> >>>out. Please help.
> >>>
> >>>Drew
> >>>
> >>>On Thursday 20 February 2003 7:17 am, Joe wrote:
> >>>>"ChangingLINKS.com" <x3 at ChangingLINKS.com> writes:
> >>>>>On Wednesday 19 February 2003 3:55 pm, cfowler wrote:
> >>>>>>#1) Make sure the default gqteway is setup
> >>>>>
> >>>>>How? Ok. I was looking for a gQteway file for a while. Ok. I am
> >>>>>pretty
> >>>
> >>>sure
> >>>
> >>>>>that it is a problem with setting up the "gateway." Where do I put
> >>>>>the IP for it (tried google and man -k)?
> >>>>
> >>>>Your DHCP server should set this up. If you have to do it manually,
> >>>>do "route add default gw <IP address of gateway> metric 1"
> >>>>at the command line. IMPORTANT: the <IP address of gateway> has
> >>>>to be the address of the gateway ON YOUR LOCAL LAN, *not* the
> >>>>address of the gateway interface facing your internet.
> >>>>
> >>>>I am clue-free about the organization of Redhat's startup
> >>>>scripts (I'm a Slackware man from way back), but it's
> >>>>certainly possible to add that command to some script to
> >>>>make it happen on every boot. But again, I'd say you need
> >>>>to get DHCP working properly if you really want to resolve
> >>>>this.
> >>>>
> >>>>>>#2) Make sure resolv.conf is setup. etc/resolv.conf:
> >>>>>
> >>>>>domain domain.suffix
> >>>>>nameserver 24.93.40.62
> >>>>>nameserver 24.93.40.63
> >>>>>search domain.suffix
> >>>>
> >>>>Again, if the machine is set up to configure itself via DHCP,
> >>>>then DHCP should populate resolv.conf automagically. I
> >>>>assume the name "domain.suffix" has been changed to protect
> >>>>the innocent? (I bet it's really something like
> >>>>"austin.rr.com"?)
> >>>>
> >>>>Are you using a black-box gateway unit (like a Linksys or
> >>>>something)? Or is your gateway a PC firewall?
> >>>>
> >>>>Cheers,
> >>>>
> >>>>-- Joe
> >>>>_______________________________________________
> >>>>Ale mailing list
> >>>>Ale at ale.org
> >>>>http://www.ale.org/mailman/listinfo/ale
> >>>
> >>>--
> >>>Wishing you Happiness, Joy and Laughter,
> >>>Drew Brown
> >>>http://www.ChangingLINKS.com
> >>>_______________________________________________
> >>>Ale mailing list
> >>>Ale at ale.org
> >>>http://www.ale.org/mailman/listinfo/ale
> >>
> >>_______________________________________________
> >>Ale mailing list
> >>Ale at ale.org
> >>http://www.ale.org/mailman/listinfo/ale
--
Wishing you Happiness, Joy and Laughter,
Drew Brown
http://www.ChangingLINKS.com
_______________________________________________
Ale mailing list
Ale at ale.org
http://www.ale.org/mailman/listinfo/ale
More information about the Ale
mailing list