If Comp B can ping Comp A, and Comp A can ping ISP, it stands to reason
that Comp B can ping ISP, UNLESS Comp A is preventing it.
I looked at your firewall script from Tue, 27 Aug 2002 08:52:00, and I
see nothing that prevents Comp B from pinging ISP.
When connected to your ISP, do these and post the results:
loran:/home/clay # route -n
eric:/home/clay # route -n
loran:/home/clay # cat /proc/sys/net/ipv4/ip_forward
George
Clayton Stapleton wrote:
>
> On Saturday 07 September 2002 09:44 pm, George Toft wrote:
> > Hi Clay,
> >
> > First off, why did you put "nameserver 192.168.0.2" on comp B?
> >
> > Second, in your message dated 08/30/02 12:19, you could ping the outside
> > world. Today's message indicates you cannot. Did you change something
> > on comp A since then WRT the firewall or port-forwarding? Perform the
> > same test just to be sure:
> > eric:~ # ping -c 4 64.24.210.88
> > PING 64.24.210.88 (64.24.210.88) from 192.168.0.2 : 56(84) bytes of
> > data.
> > 64 bytes from 64.24.210.88: icmp_seq=1 ttl=255 time=0.216 ms
> > 64 bytes from 64.24.210.88: icmp_seq=2 ttl=255 time=0.193 ms
> > 64 bytes from 64.24.210.88: icmp_seq=3 ttl=255 time=0.192 ms
> > 64 bytes from 64.24.210.88: icmp_seq=4 ttl=255 time=0.197 ms
> >
> > Then follow it up with a ping -c 4 yahoo.com. It is not unusual for an
> > ISP to block ICMP (which is the protocol ping uses), so tour ping of
> > 216.126.136.250 may not really mean anything. The nslookup yahoo.com
> > worries me though.
> >
> > George
>
> Hi George
> No I do not remember changing anything in the IP-Masq test firewall or making
> any other changes in that area.
>
> Removed "nameserver 192.168.0.2" on comp B.
>
> I can ping my ISP as follows:
> clay@eric:~> ping -c 4 64.24.210.86
> PING 64.24.210.86 (64.24.210.86) from 192.168.0.2 : 56(84) bytes of data.
> 64 bytes from 64.24.210.86: icmp_seq=1 ttl=255 time=0.218 ms
> 64 bytes from 64.24.210.86: icmp_seq=2 ttl=255 time=0.189 ms
> 64 bytes from 64.24.210.86: icmp_seq=3 ttl=255 time=0.194 ms
> 64 bytes from 64.24.210.86: icmp_seq=4 ttl=255 time=0.193 ms
>
> --- 64.24.210.86 ping statistics ---
> 4 packets transmitted, 4 received, 0% loss, time 2998ms
> rtt min/avg/max/mdev = 0.189/0.198/0.218/0.018 ms
>
> When I ping "yahoo.com" the connection just hangs until I do a ctrl-alt-c.
> the same when I ping 216.126.136.250.
>
> >From comp A I can ping 216.126.136.250 as follows:
> loran:/home/clay # ping -c 4 216.126.136.250
> PING 216.126.136.250 (216.126.136.250) from 64.24.211.118 : 56(84) bytes of
> data.
> 64 bytes from 216.126.136.250: icmp_seq=1 ttl=251 time=249 ms
> 64 bytes from 216.126.136.250: icmp_seq=2 ttl=251 time=229 ms
> 64 bytes from 216.126.136.250: icmp_seq=3 ttl=251 time=229 ms
> 64 bytes from 216.126.136.250: icmp_seq=4 ttl=251 time=219 ms
>
> --- 216.126.136.250 ping statistics ---
> 4 packets transmitted, 4 received, 0% loss, time 3039ms
> rtt min/avg/max/mdev = 219.989/232.416/249.785/10.825 ms
>
> Each time I try your suggestions it seems that I get different answers.
> At a loss what to try next.
>
> TIA
> Clayton
>
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
> To subscribe, unsubscribe, or to change you mail settings:
> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
(text/plain)