Ranjan Koirala wrote:
>
> Hi jan,
> I did exactly the same as you mentioned. Now all the outside packets are
> routed towards the proxy interface which is sl0. But now I still having
> some problems.
> When I try to browse from my client computer: 192.168.51.3 (eth0:0) The
> request goes to the servre, 192.168.51.1 which dials to my favourite ISP, I
> get connected but I can't even ping to the outside world from the client
> computer. I can ping the PPP local IP address on my server, I mean the
> dynamic IP address given to me by my ISP, from the client but not even the
> remote IP from the ISP.
This may sound like something too obvious, but do you have masquerading
set up? I initially didn't ask, because with your references to eth0:0,
it sounded like it was a virtual client machine, rather than a physical
one, but I'm starting to think that it wouldn't matter. If your ISP
sees an address of 192.168.x.x, it's going to drop it to the bit bucket.
That's why you use that range (that is, so that you don't accidentally
use an IP address someone else may have registered, causing an
IP-routing black hole.
My IP masquerading configuration line is
ipfwadm -F -a masquerade -W ppp0 -S 192.168.0.0/16 -D 0.0.0.0/0
I think you will need to either change the ppp0 to sl0, or make certain
you take down masquerading every time you lose your connection. (I
believe that using sl0 would always work, but give you a performance hit
on outbound traffic. Using ppp0 wouldn't give you that hit, but
requires a more exacting configuration. It's been quite a while since
I've set it up, though, so I can't remember for certain that's true, and
I can't remember what that more exacting configuration is.)
Ed
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
