[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: IPv6-capable pfinet
From: |
Stefan Siegl |
Subject: |
Re: IPv6-capable pfinet |
Date: |
Mon, 8 Oct 2007 22:38:17 +0200 |
User-agent: |
Mutt/1.5.13 (2006-08-11) |
Hi Thomas!
On Mon, Oct 08, 2007 at 08:31:15PM +0200, Thomas Schwinge wrote:
> [...] Have pfinet include the IPv6 code by default, but
> only activate the IPv6 engine if IPv6 services are actually needed, i.e.,
> if they are requested by the pfinet translator setting. The increase in
> the pfinet translator's executable size does not matter in my opinion.
You're right that it doesn't make much sense to enable the IPv6 protocol
bits, if /servers/socket/26 is not bound. I've now patched pfinet to
to do late (on demand) initialization of the engine, however we now need
to manually care for the protocol <-> device link (see new
pfinet_activate_ipv6 function).
Now you can even first start pfinet (passivly), bound to
/servers/socket/2 only, and then activate the IPv6 engine using:
fsysopts /servers/socket/2 -6 /servers/socket/26 -a ...
It even works the other way round, but IPv6-only (currently) doesn't
make much sense, since DNS is usually configured to happen over IPv4.
cheers,
stesie
ipv6-late-activation.diff
Description: Text Data