Mikkel:
Maybe you can help me interpret what I'm seeing. I'm not very good with
this stuff (yet), so I appreciate any help you can throw my way. You
mentioned something about a route not being set up. Please understand
that I did everything exactly the way as I did with my Red Hat 6.1
machine, so possibly Red Hat is no longer setting something by default
that they did before? Below are the steps you mentioned:
eth0 Link encap:Ethernet HWaddr 00:50:DA:BD:66:DD
inet addr:24.218.83.113 Bcast:24.218.83.255 Mask:255.255.252.0
UP BROADCAST RUNNING MTU:1500 Metric:1
RX packets:14947 errors:0 dropped:0 overruns:0 frame:0
TX packets:529 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
Interrupt:9 Base address:0xec00
eth1 Link encap:Ethernet HWaddr 00:50:DA:BD:88:60
inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1 errors:0 dropped:0 overruns:0 frame:0
TX packets:52 errors:0 dropped:0 overruns:0 carrier:51
collisions:0 txqueuelen:100
Interrupt:11 Base address:0xdc00
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:3924 Metric:1
RX packets:89 errors:0 dropped:0 overruns:0 frame:0
TX packets:89 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
PING 192.168.1.2 (192.168.1.2) from 192.168.1.1 : 56(84) bytes of data.
>From 192.168.1.1: Destination Host Unreachable
>From 192.168.1.1: Destination Host Unreachable
>From 192.168.1.1: Destination Host Unreachable
>From 192.168.1.1: Destination Host Unreachable
>From 192.168.1.1: Destination Host Unreachable
>From 192.168.1.1: Destination Host Unreachable
>From 192.168.1.1: Destination Host Unreachable
>From 192.168.1.1: Destination Host Unreachable
>From 192.168.1.1: Destination Host Unreachable
>From 192.168.1.1: Destination Host Unreachable
>From 192.168.1.1: Destination Host Unreachable
>From 192.168.1.1: Destination Host Unreachable
--- 192.168.1.2 ping statistics ---
13 packets transmitted, 0 packets received, +12 errors, 100% packet loss
eth0 Link encap:Ethernet HWaddr 00:50:DA:BD:66:DD
inet addr:24.218.83.113 Bcast:24.218.83.255 Mask:255.255.252.0
UP BROADCAST RUNNING MTU:1500 Metric:1
RX packets:15035 errors:0 dropped:0 overruns:0 frame:0
TX packets:542 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
Interrupt:9 Base address:0xec00
eth1 Link encap:Ethernet HWaddr 00:50:DA:BD:88:60
inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1 errors:0 dropped:0 overruns:0 frame:0
TX packets:52 errors:0 dropped:0 overruns:0 carrier:51
collisions:0 txqueuelen:100
Interrupt:11 Base address:0xdc00
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:3924 Metric:1
RX packets:102 errors:0 dropped:0 overruns:0 frame:0
TX packets:102 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
The packets do appear to be on eth0. Is this correct? I honestly don't
really understand when you mention about the route not being set up
correctly, so possibly you can reply with a short explanantion, or point
me to a resource that would help explain it? Any help is really
appreciated. Thanks.
- Mike
On Sat, 22 Apr 2000, Mikkel L. Ellertson wrote:
> At 04:05 PM 4/22/00 -0400, you wrote:
> >Afternoon Everyone:
> >
> >When I had Red Hat 6.1 installed on my machine, I had the following 4
> >lines at the end of my rc.local file:
> >
> > echo 1 > /proc/sys/net/ipv4/ip_forward
> >
> > /sbin/ipchains -F forward
> > /sbin/ipchains -P forward DENY
> > /sbin/ipchains -A forward -i eth0 -s 192.168.1.2 -j MASQ
> >
> >This allowed me to have my internal Windows machine make use of my cable
> >modem Internet connection. I just did a clean install on Red Hat 6.2, and
> >attempted to do exactly the same steps. This runs, and if I do an
> >ipchains -L forward, it shows the rule in place. However, it doesn't
> >appear to be working. Further, I noticed that I can't ping the
> >internal interface of the Windows machine from the Linux box, and vice
> >versa. Both cards work just fine if I ping them from their own
> >machines, and the connection works if I reinstall Red Hat 6.1. Anyone
> >think of a reason why it's not working or something I might be missing?
> >
> >- Mike
> >
> Is there a difference in the output of route between 6.1 and 6.2?
> It sounds like you may not have a route set up for the internal network.
> Ping would fail both ways because the Linux box would try to send the
> packets out the default route. It would send all traffic for the windows
> box out the wrong interface.
>
> A quick way to check this is to do an ifconfig, then ping the windows box,
> and another ifconfig. See what interface the transmit count goes up on.
>
> Mikkel
>
> --
> Do not meddle in the affairs of dragons,
> for you are crunchy and taste good with ketchup.
>
>
>
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
