> Stop right here. If you didn't compile IPDIVERT in the kernel,
> the hooks aren't in the tcp/ip stack and you're screwed.
>
> Figuring out a way to fix this is on my TODO list, though I don't
> have any ideas that don't cost a performance hit for non-DIVERT
> users.
The LEASE stuff has a simil
On Sun, Oct 22, 2000 at 09:52:03PM +0200, Leif Neland wrote:
> I want to install ipfw and natd to a machine working as isdn-router, which I
> lost the kernel config for
> I connect to the world via userland-ppp and isdnd.
>
> I don't have any ipfw or divert compiled in the kernel, but I can load
> On Sun, 22 Oct 2000, Nimrod Mesika wrote:
>
> >> Or can I use ppp's nat together with ipfw?
> >
> >I see no reason why you can't. In fact, it will probably be more
> >efficient as you will not need two user processes (ppp and natd).
>
I tried, I can. (I should just have tried instead of asking
On Sun, 22 Oct 2000, Nimrod Mesika wrote:
>> Or can I use ppp's nat together with ipfw?
>
>I see no reason why you can't. In fact, it will probably be more
>efficient as you will not need two user processes (ppp and natd).
Furthermore, I don't see why ipfw gains you anything over ppp filters.
Ju
On Sun, Oct 22, 2000 at 09:52:03PM +0200, Leif Neland wrote:
> But the command
> "ipfw add divert natd all from any to any via tun0 "
> fails:
> 0 divert 8668 ip from any to any via tun0
> ipfw: setsockopt(IP_FW_ADD): Invalid argument
I don't know about a kernel module, but when ipfw is compi