[ale] Interenet connection
ChangingLINKS.com
x3 at ChangingLINKS.com
Thu Feb 20 14:32:45 EST 2003
The same thing is always says (Pinky). It's "trying to take over the world."
}$ /usr/sbin/traceroute www.google.com
traceroute: unknown host www.google.com
$ /usr/sbin/traceroute computer1
traceroute to computer1 (192.168.123.xxx), 30 hops max, 38 byte packets
1 change (192.168.123.xxx) 0.254 ms 0.209 ms 0.204 ms
Drew
On Thursday 20 February 2003 1:20 pm, Geoffrey wrote:
> What does the following return:
>
> /usr/sbin/traceroute www.google.com
>
> 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
> >>
> >>
> >
> >
>
> --
> Until later: Geoffrey esoteric at 3times25.net
>
> The latest, most widespread virus? Microsoft end user agreement.
> Think about it...
>
> _______________________________________________
> 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