Unified rc.firewall ipfw me/me6 issue
Willem Jan Withagen
wjw at digiware.nl
Tue Jan 19 08:28:32 UTC 2010
Luigi Rizzo wrote:
> On Sun, Jan 17, 2010 at 12:04:43PM +0100, Luigi Rizzo wrote:
>> On Sun, Jan 17, 2010 at 05:42:58PM +0900, Hajimu UMEMOTO wrote:
>>> Hi,
>>>
>>>>>>>> On Sun, 10 Jan 2010 19:52:32 +0100
>>>>>>>> Luigi Rizzo <rizzo at iet.unipi.it> said:
While we are at it, might I suggest one more "nice" thing...
For several of my projects I reduced configuring a gateway/nat/firewall to
just stuffing hostipnrs:ports into some shell variables. eg:
firewall_forward_services="192.168.10.0/24^22 192.168.10.74^873
192.168.10.74^1195 192.168.10.66^80 192.168.10.117^10000 192.168.10.67^45457
2001:4cb8:3::67^45457 192.168.10.116^sip 192.168.10.113^sip"
And I used to do that with the "std"-notation host:port.
But once I got ipv6 connected, that no longer worked. And I also found that
the ipv6 parser did some wierd stuff on other places as well.
Is it posible to fix the ipv6nr parser and have it also recognise the
versions: [a:b:c::d:e] and [a:b:c::d:e/64] (like firefox does)
Yes, I know the stanza is: put your code where your mouth is. And I've been
trying to find time to do this, and given enough days time will pop up.
But this discussion is already running and people are already breaking up
the code.
Thanx,
--WjW
More information about the freebsd-current
mailing list