Re: 1841 with 3 internet connections (2xADSL, 1xbridged) help

On Apr 25, 11:44 am, Jon <j.l.robin...@xxxxxxxxx> wrote:
try specifying the interface before the next hop

ip route <site IP address> 255.255.255.255 fa 0/1 78.105.0.1

if that does not work then use ? with

ip route <site IP address> 255.255.255.255 ?

to see what the next paramet is theat the CLI parser will accept.

Hi again Merv :)

Yes, that worked, here are the results:

London(config)#ip route 83.142.25.10 255.255.255.255 fa 0/1 78.105.0.1
London(config)#^Z

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 78.105.0.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 12/15/20
ms
London#ping 83.142.25.10

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 83.142.25.10, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 12/14/16
ms

But from my workstation:

Pinging [83.142.25.10] with 32 bytes of data

Reply from 192.168.20.1: Destination net unreachable.
Reply from 192.168.20.1: Destination net unreachable.

I don't get it! From the router it's fine, but from a workstation with
the router as its gateway it isn't!

I tried a couple of traceroutes:

Tracing the route to 83.142.25.10

1 * * *
2 ge-1-1-0-64.core2.sta.lon2.coreix.net (195.66.227.58) 12 msec 16
msec 16 msec
3 ge-4-2-57.dist7b.sta.lon2.coreix.net (85.13.192.30) 12 msec 12
msec 16 msec
4 83.142.25.10 16 msec 12 msec 12 msec

London#traceroute 78.105.0.1

Type escape sequence to abort.
Tracing the route to 78-105-0-1.zone3.bethere.co.uk (78.105.0.1)

1 * * *
2 * * *
3 * * *

Would this suggest that it's not actually getting through to that
78.105.0.1 gateway via the right interface?

Again very appreciative of the help.

Jon


It looks like the ISP router ( 78-105-0-1.zone3.bethere.co.uk
(78.105.0.1)) does not respond to pings; they maybe blocking - you may
wish to ask about that

I like the name "bethere" - be there - apparently they are not ;-))

If you cannot ping from your workstation, it may mean that NAT is not
working properly and if that is the case then
the return ICMP echo replies would not make it back to your
workstation.

You are getting closer to a solution though...

You may want to repost wit you complete config (sanitized of ) course
and ask if there are any issue with the NAT portion of it.



.

Relevant Pages

  • Re: opsf over ipsec tunnel problem
    ... Type escape sequence to abort. ... Packet sent with a source address of 192.168.201.5 ... As Merv suggests lose the ospf security. ...
    (comp.dcom.sys.cisco)
  • Re: OT: Need some help, not 3000 topic
    ... Type escape sequence to abort. ... Tracing the route to mail.cepacking.com ... To join/leave the list, search archives, change list settings, * ...
    (comp.sys.hp.mpe)
  • Re: Frame relay:Long ping delay
    ... locally,it give me a long delay and remotely,the delay is half of the ... Type escape sequence to abort. ... Locall PING: ...
    (comp.dcom.sys.cisco)
  • 4500 switch first icmp packet lost?
    ... when sending a ping to a directly connected station i've the following effect: ... Type escape sequence to abort. ...
    (comp.dcom.sys.cisco)