<< | Thread Index | >> ]    [ << | Date Index | >> ]

Subject: Re: A minor problem...
From: Robert Davidson <puttputt,AT,ebbs,DOT,com,DOT,au>
Date: Fri, 17 Aug 2001 13:27:30 +0200
In-reply-to: <Pine.LNX.4.31.0108171254110.569-100000@silas.datrix.co.za>

Adrian Snyman wrote:
> 
> On Fri, 17 Aug 2001 puttputt,AT,ebbs,DOT,com,DOT,au wrote:
> 
> > Adrian Snyman wrote:
> > >
> > > Maybe add the host route ..
> > >
> > > But what is the result for a traceroute to the remote eth0 interface ??
> >
> > Clarify that.  From where in the network, with what source address, to
> > which destination ?
> >
> 
> Sorry .. I think I am asleep today .. :o) ..
> 
> Within Policy Table 13 ...
> 
> Default to the cipe interface .. ??
> 

Umm I can trace to 203.34.65.1 (which is the eth0 interface on the
isp's machine) but only if I specify the source address, like this:

traceroute -n -s 203.34.65.21 203.34.65.1

.21 is one of the live ip's routed down to me via the vpn.  If I don't
specify the -s 203.34.65.21, then it gets nowhere at all, but that is
to be expected I think because I havn't put routes into that table 13
yet for the 203.34.65.x part of my ISP's network... so if I do that
and then trace to 203.34.65.1 I think it should work

[trying now]

It didn't work but I'm not all that fussed.  I'm going to change my
set up a little to fix one last issue and then there shouldn't be any
trouble at all with doing the traces and pings and all that.  Umm,
thanks for everyones help, it's been really good.

-- 
Regards,
Robert Davidson.
http://www.mlug.org.au/





<< | Thread Index | >> ]    [ << | Date Index | >> ]