[ale] Interenet connection
James P. Kinney III
jkinney at localnetsolutions.com
Thu Feb 20 17:49:14 EST 2003
Drew,
It looks like you may have multiple problems all at once.
1. When you did the traceroute to computer1, did you call it "computer1"
or did you put in it's IP address?
2. If you put in it's name, computer1, does the machine you are doing
this on have that name and IP address in its /etc/hosts file?
3. If the hosts file does NOT have an entry for the machine named
computer1, what is the DNS server that machine is using?
4. What does your /etc/resolv.conf have to use as a DNS server?
5. Does the gateway machine allow DNS traffic to pass to the inside
network. In other words, does port 53 UDP pass? check it with :
"/sbin/iptables -L -v | grep udp"
6. Does the gateway machine allow traffic at all to pass? Check it with
"cat /proc/sys/net/ipv4/ip_forward" It should be a "1" not a "0".
7. If none of this works, turn of the bond0 device (ifconfig bond0 down)
and retry the connection attempts.
On Thu, 2003-02-20 at 14:56, Geoffrey wrote:
> It appears to me that:
>
> 1. Your gateway is not properly set up.
> 2. You're not getting to your DNS, which would be caused by #1.
>
> My gateway machine is on an internal lan separated by a dmz. My gateway
> ip is 172.16.255.220. The gateway for that machine is 172.16.10.215.
> That gateway is connected to my dsl line. Here is the beginning of my
> traceroute:
>
> /usr/sbin/traceroute www.google.com
> traceroute to www.google.com (216.239.39.101), 30 hops max, 40 byte packets
> 1 b.home.edu (172.16.255.220) 3.905 ms 4.888 ms 5.859 ms
> 2 a.dmz.edu (172.16.10.215) 50.971 ms 60.442 ms 61.323 ms
> .
> .
>
> So you see my machine goes to 172.16.255.220 which then goes to
> 172.16.10.215 and so on.
>
>
> ChangingLINKS.com wrote:
> > 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
> >>
> >>
> >
> >
--
James P. Kinney III \Changing the mobile computing world/
CEO & Director of Engineering \ one Linux user /
Local Net Solutions,LLC \ at a time. /
770-493-8244 \.___________________________./
http://www.localnetsolutions.com
GPG ID: 829C6CA7 James P. Kinney III (M.S. Physics) <jkinney at localnetsolutions.com>
Fingerprint = 3C9E 6366 54FC A3FE BA4D 0659 6190 ADC3 829C 6CA7
This is a digitally signed message part
More information about the Ale
mailing list