From 16ad01567ae95111a5dc3b44ff842bebab454f35 Mon Sep 17 00:00:00 2001 From: ReignBock <51061876+ReignBock@users.noreply.github.com> Date: Mon, 24 Aug 2020 08:42:31 -0500 Subject: [PATCH 1/4] Update README.md Updated README to include notice for user of Netgate hardware of the absence of ng_etf module. --- README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/README.md b/README.md index 79f5429..1ac98df 100644 --- a/README.md +++ b/README.md @@ -68,6 +68,8 @@ But enough talk. Now for the fun part! At this time there is a bug in pFsense 2.4.5 and [ng_etf module is only included in pFsense 2.4.5 _amd64 build_]( https://redmine.pfsense.org/issues/10463). Should be fixed in 2.4.5-p1. +PFSense Builds for Netgate hardware may not include ng_etf (Confimred on SG4860-Desktop 2.4.5-p1). Confirm ng_etf exists before continuing and look at [Before-pfSense-2.4.5 branch](https://github.com/MonkWho/pfatt/blob/Before-pfSense-2.4.5/README.md) for gudiance if it doesn't exist. + If you are running pfSense on anything other than amd64 architecture you should compile your own version of ng_etf. Look at [Before-pfSense-2.4.5 branch](https://github.com/MonkWho/pfatt/blob/Before-pfSense-2.4.5/README.md) for some guidance on compiling and running your own ng_etf. If you only have two NICs, you can buy this cheap USB 100Mbps NIC [from Amazon](https://www.amazon.com/gp/product/B00007IFED) as your third. It has the Asix AX88772 chipset, which is supported in FreeBSD with the [axe](https://www.freebsd.org/cgi/man.cgi?query=axe&sektion=4) driver. I've confirmed it works in my setup. The driver was already loaded and I didn't have to install or configure anything to get it working. Also, don't worry about the poor performance of USB or 100Mbps NICs. This third NIC will only send/recieve a few packets periodicaly to authenticate your Router Gateway. The rest of your traffic will utilize your other (and much faster) NICs. -- 2.45.2 From fa0b0f956bf9f2f05c447b8fb2f997f144783431 Mon Sep 17 00:00:00 2001 From: Andrew Massey Date: Wed, 23 Sep 2020 09:27:47 -0500 Subject: [PATCH 2/4] Update README.md Edits to IPv6 Instructions - Edit Prefix Delegation Range to be blank - Add Prefix Delegation Size instruction - Add line about configuring DHCPv6 Server & RA for each interface. --- README.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 4f9aa90..b6a1f01 100644 --- a/README.md +++ b/README.md @@ -156,12 +156,15 @@ If you have additional LAN interfaces repeat these steps for each interface exce 1. Go to _Services > DHCPv6 Server & RA_ 1. Enable DHCPv6 server on interface LAN 1. Configure a range of ::0001 to ::ffff:ffff:ffff:fffe -1. Configure a **Prefix Delegation Range** to _64_ +1. Leave **Prefix Delegation Range** _blank_. +1. Configure a **Prefix Delegation Size** to _64_ 1. Save 1. Go to the _Router Advertisements_ tab 1. Configure **Router mode** as _Stateless DHCP_ 1. Save +If you have additional LAN interfaces repeat these steps for each interface. + That's it! Now your clients should be receiving public IPv6 addresses via DHCP6. # Troubleshooting -- 2.45.2 From 408dd2367fd958e81d52095e0d25f2aae88519c0 Mon Sep 17 00:00:00 2001 From: Andrew Massey Date: Wed, 23 Sep 2020 09:29:24 -0500 Subject: [PATCH 3/4] Update README.md typo --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index b6a1f01..48d325f 100644 --- a/README.md +++ b/README.md @@ -157,7 +157,7 @@ If you have additional LAN interfaces repeat these steps for each interface exce 1. Enable DHCPv6 server on interface LAN 1. Configure a range of ::0001 to ::ffff:ffff:ffff:fffe 1. Leave **Prefix Delegation Range** _blank_. -1. Configure a **Prefix Delegation Size** to _64_ +1. Configure **Prefix Delegation Size** to _64_ 1. Save 1. Go to the _Router Advertisements_ tab 1. Configure **Router mode** as _Stateless DHCP_ -- 2.45.2 From 21d4a59b95145def16a87bcd4efe5fb1218f84e8 Mon Sep 17 00:00:00 2001 From: Andrew Massey Date: Thu, 24 Sep 2020 07:38:21 -0500 Subject: [PATCH 4/4] Update README.md Add line in IPv6 WAN configuration steps to enable "Request only an IPv6 prefix" so that the firewall itself can access the IPv6 internet. --- README.md | 1 + 1 file changed, 1 insertion(+) diff --git a/README.md b/README.md index 48d325f..5f9fd8c 100644 --- a/README.md +++ b/README.md @@ -136,6 +136,7 @@ This setup assumes you have a fairly recent version of pfSense. I'm using 2.4.5. 1. Go to _Interfaces > WAN_ 1. Enable **IPv6 Configuration Type** as _DHCP6_ 1. Scroll to _DCHP6 Client Configuration_ +1. Enable **Request only an IPv6 prefix** 1. Enable **DHCPv6 Prefix Delegation size** as _60_ 1. Enable _Send IPv6 prefix hint_ 1. Enable _Do not wait for a RA_ -- 2.45.2