Op 27 nov. 2019, om 11:01 heeft Andrey V. Elsukov het
volgende geschreven:
> On 26.11.2019 11:31, Marco van Tol wrote:
>> Did you find the time to look further into this?
>> If not I understand, no problem.
>>
>> Let me know if there's anything I can do to help.
>
> Hi,
>
> I'm sorry for the
On 26.11.2019 11:31, Marco van Tol wrote:
> Did you find the time to look further into this?
> If not I understand, no problem.
>
> Let me know if there's anything I can do to help.
Hi,
I'm sorry for the delay, I'll try to finish the patch at this weekend :)
--
WBR, Andrey V. Elsukov
Op 6 nov. 2019, om 16:49 heeft Marco van Tol het volgende
geschreven:
> Op 6 nov. 2019, om 16:45 heeft Andrey V. Elsukov het
> volgende geschreven:
>> On 25.10.2019 17:57, Marco van Tol wrote:
>>> This all works great in that the guests have no IPv4 any more, and in
>>> their point of view the
Op 6 nov. 2019, om 16:45 heeft Andrey V. Elsukov het
volgende geschreven:
> On 25.10.2019 17:57, Marco van Tol wrote:
>> This all works great in that the guests have no IPv4 any more, and in
>> their point of view the entire world has migrated to IPv6-only.
>>
>> Is there a way to change this
On 25.10.2019 17:57, Marco van Tol wrote:
> This all works great in that the guests have no IPv4 any more, and in
> their point of view the entire world has migrated to IPv6-only.
>
> Is there a way to change this behaviour so that traceroutes to
> synthesized addresses also report to be coming
Hi there,
I setup a NAT64 gateway on a FreeBSD 11.3-RELEASE-p3 host using the following
config:
-
#!/bin/sh
fwcmd="/sbin/ipfw"
nat64_v4="193.0.31.240/28"
nat64_pfx_v6="64:ff9b::/96"
icmp6ns=135
icmp6na=136
kldstat -q -m ipfw_nat64 || kldload ipfw_nat64
${fwcmd} -f flush
${fwcmd} nat64lsn
