Well, one pretty simple (and not always correct) fix would be to
assume that if an address has more than 1 colon, it's IPv6.
The correct fix is to generate a small flex parser.
Lars
On 2009-8-22, at 14:42, Willem Jan Withagen wrote:
Lars Eggert wrote:
The following reply was made to PR bin/117214; it has been noted by
GNATS.
From: Lars Eggert <lars.egg...@nokia.com>
To: bug-follo...@freebsd.org, fab...@wenks.ch
Cc:
Subject: Re: bin/117214: ipfw(8) fwd with IPv6 treats input as IPv4
Date: Sat, 22 Aug 2009 02:27:44 +0300
I still see this on 7.2-STABLE:
[r...@fit: ~] uname -a
FreeBSD fit.nokia.com 7.2-STABLE FreeBSD 7.2-STABLE #18: Fri Jun 26
15:43:17 EEST 2009 r...@fit.nokia.com:/usr/obj/usr/src/sys/FIT
i386
[r...@fit: ~] ipfw add 64010 fwd 2001:2060:40:1::1 ip6 from
2001:2060:40:1::123,2001:2060:40:1::124 to not
2001:0708:0040:fff2::1/64 out
64010 fwd 0.0.7.209,2060 ip6 from
2001:2060:40:1::123,2001:2060:40:1::124 to not
2001:708:40:fff2::/64 out
[r...@fit: ~] ipfw show 64010
64010 0 0 fwd 0.0.7.209,2060 ip6 from
2001:2060:40:1::123,2001:2060:40:1::124 to not
2001:708:40:fff2::/64 out
The trouble is with the :'s and the fact that parsing doen't really
take
care of multiple :'s.
What I considering is changing it in such a way that one is allowed to
specify ipv6 adresses as [a:bc::d] just like it works in firefox (and
other places)
Question then is do we use [a:bc::d]/48:53 or [a:bc::d/48]:53?
--WjW
