The possible locations for the problems are:
Linux box is not routing properly.
The cisco router is not routing properly. It needs the following
statements to work
ip route x.x.x.190 255.255.255.128 x.x.x.253
ip route 0.0.0.0 0.0.0.0 ip of ISP
ISP has missconfigured its end
The easiest way to test is to do a traceroute from the client.
david
On Tue, 9 Jan 2001, Peter Peltonen wrote:
> Here we go again...
>
> I've finally got my ISP to configure the CISCO router. They made "a
> a static route for xxx.xx.xxx.128/25 and configured xxx.xx.xxx.253 as a
> forwarding router". The network looks like this at the moment:
>
>
> ISP
> |
> |
> HDSL
> |
> |
> CISCO
> eth0 ip xxx.xx.xxx.254, mask /??
> |
> |
> eth0 ip xxx.xx.xxx.253, mask /30
> LINUX gw xxx.xx.xxx.254
> eth1 ip xxx.xx.xxx.190, mask /25
> |
> |
> eth0 ip xxx.xx.xxx.129, mask /25
> CLIENT gw xxx.xx.xxx.190
>
>
> But no go. Still the same situation: client can ping linux and vice versa,
> but client cannot ping the outside world.
>
> Could it be possible that my ISP still keeps the CISCO with mask /25 and
> that is why my routing fails?
>
> Maybe I should search for information with tcpdump but I've never used it
> before -- could someone give me instructions what to do with it and what to
> look for?
>
>
> Cheers,
> Peter
>
>
>
> _______________________________________________
> 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
