Charles; I thought it was just me, but you're absolutely correct - M$ seems to have taken ping ability away from all of their websites. But until I completed stopped (rather than disable - used "#chkconfig --level 12345 iptables off"), I wasn't able to get past the leaf. Once I ran this command and rebooted, I was able to ping past the LEAF to the i-net, and using Mozilla, able to browse using ip rather than name.
I'm now going to apply your suggestion concerning placing the Comcast name servers in /etc/resolv.conf. Thanks again, Earl ----- Original Message ----- From: "Charles Steinkuehler" <[EMAIL PROTECTED]> To: "Earl Wilson" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Thursday, February 12, 2004 10:35 AM Subject: Re: [leaf-user] routing issue with Dachstein > Earl Wilson wrote: > <snip> > > Thanks for the network diagram...I figured that's how you had things > setup, but it's nice to verify. > > > I thought I had turned the > > firewall off on the rh box during a previous re-install, but with your > > suggestions, I got the following: > > > > [EMAIL PROTECTED] etc]# ipchains -nvL > > ipchains: Incompatible with this kernel > > [EMAIL PROTECTED] etc]# iptables -nvL > > Chain INPUT (policy ACCEPT 53612 packets, 4819K bytes) > > pkts bytes target prot opt in out source > > destination > > > > Chain FORWARD (policy ACCEPT 0 packets, 0 bytes) > > pkts bytes target prot opt in out source > > destination > > > > Chain OUTPUT (policy ACCEPT 51850 packets, 4379K bytes) > > pkts bytes target prot opt in out source > > destination > > This *IS* a disabled firewall. No rules, and a default policy of ACCEPT > will let everything through. > > > As far as the routing table on the rh box, it seems that the LEAF is > > listed as the default GW: > > > > [EMAIL PROTECTED] etc]# ip route show > > 192.168.1.0/24 dev eth1 scope link > > 192.168.0.0/24 dev eth0 scope link > > 127.0.0.0/8 dev lo scope link > > default via 192.168.1.254 dev eth1 > > [EMAIL PROTECTED] etc]# route > > Kernel IP routing table > > Destination Gateway Genmask Flags Metric Ref Use > > Iface > > 192.168.1.0 * 255.255.255.0 U 0 0 0 > > eth1 > > 192.168.0.0 * 255.255.255.0 U 0 0 0 > > eth0 > > 127.0.0.0 * 255.0.0.0 U 0 0 > > 0 lo > > default firewall 0.0.0.0 UG 0 0 > > 0 eth1 > > This all looks OK. Your LEAF Firewall is the default route for the > RedHat box, and there are proper entries for both networks directly > connected to the RH box. > > Going through your original message again, I notice: > > REDHAT TO I-NET ATTEMPT: > > [EMAIL PROTECTED] etc]# ping www.msn.com > > ping: unknown host www.msn.com > > [EMAIL PROTECTED] etc]# ping 207.68.173.244 <-------------(WWW.MSN.COM) > > PING 207.68.173.244 (207.68.173.244) 56(84) bytes of data. > > --- 207.68.173.244 ping statistics --- > > 3 packets transmitted, 0 received, 100% packet loss, time 1999ms > > I now think your problem is trying to ping www.msn.com, which doesn't > reply to pings for me either (and my internet connection is working!). > You should try google, instead: > > [EMAIL PROTECTED] network-scripts]# ping www.msn.com > PING www.msn.com (207.68.171.244) from 10.34.1.21 : 56(84) bytes of > data. > > --- www.msn.com ping statistics --- > 5 packets transmitted, 0 received, 100% loss, time 4017ms > > [EMAIL PROTECTED] network-scripts]# ping www.google.com > PING www.google.akadns.net (216.239.39.147) from 10.34.1.21 : 56(84) > bytes of data. > 64 bytes from 216.239.39.147: icmp_seq=1 ttl=247 time=96.1 ms > 64 bytes from 216.239.39.147: icmp_seq=2 ttl=247 time=99.5 ms > 64 bytes from 216.239.39.147: icmp_seq=3 ttl=247 time=184 ms > 64 bytes from 216.239.39.147: icmp_seq=4 ttl=247 time=242 ms > > --- www.google.akadns.net ping statistics --- > 4 packets transmitted, 4 received, 0% loss, time 3029ms > rtt min/avg/max/mdev = 96.186/155.764/242.570/61.424 ms > > At this point, I suspect you *DO* have access to the internet from your > RH box, but with DNS broken, it doesn't actually seem like it's working, > and for testing you managed to pick an IP that doesn't reply to pings. > > Try pinging some other IP addresses from the RH box (and verify they > respond by trying to ping from your working windows boxen as well). If > you can ping anything out on the internet, the RH box and firewall are > setup correctly for network connectivity, so you'll just need to fix > domain resolution, probably by adding your ISP's name servers to > /etc/resolv.conf. > > -- > Charles Steinkuehler > [EMAIL PROTECTED] > ------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click ------------------------------------------------------------------------ leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
