netgraph change: will https://github.com/aus/pfatt need adjustment?

[lrosenman]

Given that I *DEPEND* on the pfatt module to authorize my ONT, will the netgraph change called out in the release notes cause me grief?

thanks (I don't dare try it as I don't want to be knocked offline).

[franco]

We simply don't load the drivers on boot, but you can put the file back if you have any issues. I don't know pfatt or what this could possibly imply.

https://github.com/opnsense/core/blob/stable/19.7/src/etc/rc.loader.d/20-netgraph


Cheers,
Franco

[lrosenman]

I wound up with having to add the file referenced as /boot/loader.conf.local and restoring my interface config to get all my vlans, et al, right.

Hopefully that survives the next major upgrade.

[harshw]

Could you provide more details? I use the pfatt script as well and I am hesitant to move to 20.1 because of this

Thanks in advance!

[pvols1979]

I was able to make the modification mentioned in this thread.  I simply created a /boot/loader.conf.local file and put the required modules in it.  I have a guide on my site to setting up the bypass using the pfatt method and I posted an update to my article regarding the changes and what is required to make it work.  Everything is working fine on my system and the local loader file should protect me against the next update.
https://geekzweb.com/2019/06/10/bypassing-arris-bgw210-700-pfsense-netgraph/

[pvols1979]

I will also contact the GitHub user who wrote the original pfatt code and let them know of the change.

[harshw]

Checked the PFATT script again and only the following modules are needed

• netgraph
• ng_ether
• ng_eiface
• ng_one2many
• ng_vlan
• ng_etf

I will try to prune the /boot/loader.conf.local file to the following and check if it still works:

Code: [Select]

netgraph_load="YES"
ng_ether_load="YES"
ng_eiface_load="YES"
ng_one2many_load="YES"
ng_vlan_load="YES"
ng_etf_load="YES"

Don't want to load modules unnecessarily if we don't need them ...

[franco]

Yes, good thinking. That's why we opted for removing most of netgraph from the system, although some PPP and NetFlow still need it but load it on demand.


Cheers,
Franco

[harshw]

Yes, good thinking. That's why we opted for removing most of netgraph from the system, although some PPP and NetFlow still need it but load it on demand.


Cheers,
Franco

I modified loader.conf.local and rebooted - after which I proceeded to do the upgrade.
So far it seems to be working ... everything came up as expected

[cwied]

99-pfatt.sh already has a line to load ng_etf, so it might make sense to just load all the other modules there too. The script uses -nq so it won't complain if they're already loaded.

Thanks for this thread. I noticed that the script would work if I invoked it by hand, but didn't know what had changed to break it during boot.

[powderwt]

I was able to make the modification mentioned in this thread.  I simply created a /boot/loader.conf.local file and put the required modules in it.  I have a guide on my site to setting up the bypass using the pfatt method and I posted an update to my article regarding the changes and what is required to make it work.  Everything is working fine on my system and the local loader file should protect me against the next update.
https://geekzweb.com/2019/06/10/bypassing-arris-bgw210-700-pfsense-netgraph/

So I'm new to opnsense, still don't have it up and running, but I had blindlessly upgraded my pfsense to which broke my.pfatt workaround due to freebsd upgrading apparently.

Curious if your method on the linked site is still working on opnsense as I had hoped to make the switch? Already installed the latest opnsense img to my machine, just need to pop in the necessary files and switch all my ONT and gateway cables and such (time is very limited however when you take the internet down in the household however 😬😬😬)