IPFW3 and IPv6

[bycn82]

Hi Matthias,

Yes they can work together.

Regards,
Bill Yuan

On Sunday, 3 January 2016, Matthias Play <matthias_play at gmx.net> wrote:

> Hi Bill,
>
> thanks for your quick answer!
>
> An NFS daemon is running on my server machine which I use to mount DFly
> source and obj dirs on my client machines. With NFS comes mountd and rpc*
> daemons that automatically also provide their service on IPv6 ports. I did
> not find daemon flags to tell them only to use IPv4 so I would like to
> block unwanted traffic to these ports.
>
> Would it be ok to also run ip6fw alongside with ipfw3?
>
> If yes, I will set up a configuration file for ip6fw allowing all IPv4
> traffic and blocking all IPv6 traffic.
>
> Regards
> Matthias
>
> On 03.01.16 14:09, bycn82 wrote:
>
>> Hi Happy New Year Matthias,
>> not support IPv6 yet
>> but yes i want to integrate with ip6fw as well.
>> recently working on something related to voip. so did not find much time
>> for BSD.
>> Will support v6 once I remove the lock in NAT.
>>
>> Regards,
>> Bill Yuan
>> On Sunday, 3 January 2016, Matthias Play <matthias_play at gmx.net
>> <mailto:matthias_play at gmx.net>> wrote:
>>
>>     Hi,
>>
>>     Happy New Year and all the Best in 2016!
>>
>>     I set up ipfw3 to filter network traffic on a local server and want
>>     to filter all IPv6 traffic since I do not need it in my local network.
>>
>>     Is ipfw3 also filtering IPv6 traffic or only IPv4?
>>
>>     I am wondering because with the old ipfw implementation handling of
>>     both IP versions is separated into two different firewall programs,
>>     ipfw and ip6fw both being configured using distinct rc.conf variables.
>>
>>     If IPv6 filtering is not supported by ipfw3 would it be better to
>>     configure a custom kernel without the INET6 option instead of using
>>     ip6fw alongside with ipfw3?
>>
>>     Best Regards
>>     Matthias
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.dragonflybsd.org/pipermail/users/attachments/20160104/6ddf3c8d/attachment-0002.html>