No subject

to have received a local ip address to use.

I think that pppd will, if not told otherwise, assign eth0's address to
ppp0 (if allowed to by the remote pppd)

The ISP ca.com.au had a setup like this a while ago - a client of mine
was able to 'assign' 192.168.1.1 to ppp0. Needless to saying nothing
worked. I suppose this is really a potential security hole by the ISP.

Garth

Jeremy Malcolm wrote:
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> 
> > I think it is because the outgoing tcp/ip packets have a
> > return address
> > of 203.25.143.101 in the header and because you are not (?) using ip
> > masquereding, your isp will route the returning packets to
> > 'backinthe.ussr.net' (203.56.15.20) and beyond.
> 
> Problem solved: I add "noipdefault" and "ipcp-accept-local" as ppp
> options, otherwise my machine presumes that its local IP address on
> the ppp0 interface is the one it usually uses, rather than the one
> that EISA has dynamically allocated.  Still not sure why this is not
> required for my other ISPs, but the main thing is that it is now
> working.
>