On 8/14/2014 11:27 AM, Willem Jan Withagen wrote:
> On 14-8-2014 14:46, Lee Dilkie wrote:
>> On 8/14/2014 08:08, Willem Jan Withagen wrote:
>>> I've found the notation ipnr:something rather frustrating when using
>>> ipv6 addresses. Sort of like typing a ipv6 ad
On 8/14/2014 08:08, Willem Jan Withagen wrote:
> I've found the notation ipnr:something rather frustrating when using
> ipv6 addresses. Sort of like typing a ipv6 address in a browser, the
> last :xx is always interpreted as portnumber, UNLESS you wrap it in []'s.
> compare
> 2001:4cb8:3:1::1
seriously?
you expect that kind of precise timing running in a VM?
-lee
On 11/13/2013 16:29, Ahmed Hamza wrote:
> I'm not sure if this would explain anything. But I am running DummyNet
> on a VirtualBox VM on an Ubuntu host. I have also experienced the same
> behaviour with both Frenzy (a FreeBS
there's a parsing bug with ipv6 address lists in 7, I guess it isn't
fixed yet.
I had to make separate rules for each ipv6 address.
-lee
On 9/20/2010 3:52 AM, Lars Eggert wrote:
> Hi,
>
> anyone know why this commend is failing on 8.1-STABLE?
>
> ipfw add deny all from 2001:2060:40:1::123/64,
On 4/30/2010 4:58 AM, Robert Huff wrote:
> I have been trying to get NAT working under ipfw on:
>
> FreeBSD 9.0-CURRENT #0: Fri Apr 23 11:34:17 EDT 2010 amd64
>
> and failing.
> The ipfw part works fine. I'm using:
>
> ipfw_load="YES"
> ipfw_nat_load="YES" # in-kernel ipfw nat