Does the box at 192.168.10.2 have 2 NIC cards? If so, is 192.168.180.1 on
the same side of the network as 192.168.10.123?
If so, then the problem is your netmask. In order for 192.168.10 to see
192.168.180, you either need to set the router box to point the route for
the 192.168.180 space back out of the 192.168.10.2 NIC, or you need to
make sure that the netmasks are something more like 255.255.0.0 for
everything on the 192.168 network.
ie:
192.168.10.123 -------- 192.168.10.2 ------- Internet
|
192.168.180.1 ---+
needs a netmask of 255.255.0.0 on both boxes or just on the 192.168.10.2
box, along with a route pointing 192.168.180.0 back out to the same
physical network.
But:
192.168.10.123 ------ 192.168.10.2/???.???.???.??? ------- 192.168.180.1
The 192.168.10.2 box needs a 192.168.180.x address where the
???.???.???.??? is, a route to the 192.168.180 network, and IP Forwarding
turned on.
On Mon, 29 Jul 2002, Furnish, Trever G wrote:
> Iptables and Ipchains are both off. Route -n config is below. Also, this
> will be fine for a day, then suddenly stop working for one address, even
> though specifying -I eth0 causes it to work.
>
> [root@enterprise root]# /sbin/route -n
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use
> Iface
> 192.168.10.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
> 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
> 0.0.0.0 192.168.10.2 0.0.0.0 UG 0 0 0 eth0
>
> That looks correct to me - I don't know where else to look to debug this.
> Maybe some tool I don't know about would show more info?
>
> -----Original Message-----
> From: Jonathan Bartlett [mailto:[EMAIL PROTECTED]]
> Sent: Sunday, July 28, 2002 4:13 PM
> To: '[EMAIL PROTECTED]'
> Cc: '[EMAIL PROTECTED]'
> Subject: Re: What could be causing this?
>
>
> Please provide the output of route -n and all firewall configs.
>
> Jon
>
> On Sun, 28 Jul 2002, Furnish, Trever G wrote:
>
> > [root@enterprise root]# ping wr-providence
> > PING hj_providence-fa0.hj-net (192.168.180.1) from 192.168.10.123 : 56(84)
> > bytes of data.
> >
> > --- hj_providence-fa0.hj-net ping statistics ---
> > 3 packets transmitted, 0 packets received, 100% packet loss
> >
> > [root@enterprise root]# ping -I eth0 wr-providence
> > PING hj_providence-fa0.hj-net (192.168.180.1) from 192.168.10.123 eth0:
> > 56(84) bytes of data.
> > 64 bytes from hj_providence.hj-int (192.168.180.1): icmp_seq=0 ttl=254
> > time=55.116 msec
> > ...
> >
> > In other words, it doesn't work without the "-I eth0". It's fine for a
> day
> > or two and then it start's behaving this way. No duplicate routes.
> > Behavior is reproducible (on this box), but has never happened on another
> > system running the same OS (rh7.2 + errata updates, kernel 2.4.9-31).
> >
> > The remote host is up the entire time.
> >
> >
> >
> > _______________________________________________
> > Redhat-list mailing list
> > [EMAIL PROTECTED]
> > https://listman.redhat.com/mailman/listinfo/redhat-list
> >
>
>
>
>
>
> _______________________________________________
> Redhat-list mailing list
> [EMAIL PROTECTED]
> https://listman.redhat.com/mailman/listinfo/redhat-list
>
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list