Update eFa-4.0.2-13 resolv.conf

Bugs in eFa 4
Post Reply
henk
Posts: 457
Joined: 14 Dec 2015 22:16
Location: Netherlands
Contact:

Update eFa-4.0.2-13 resolv.conf

Post by henk » 19 Apr 2020 08:51

I use Static DHCP on my LAN interface(s). The eFa DNS servers are defined in the -Pfsense- DHCP server entry for eFa.
Any NetworkManager, with default configuration, in efa will pick up these DHCP settings just fine.

After the upgrade to eFa-4.0.2-13.eFa.el7.x86_64.rpm I did reboot efa. After the reboot I noticed an issue with Unbound.
As I do not reboot to often I'm not sure the update was responsible.

A quick search found that in /etc/resolv.conf the nameserver (nameserver 127.0.0.1) was missing.

I restored the standard behaviour for NetworkManager by commenting the dns=none line

Code: Select all

/etc/NetworkManager/NetworkManager.conf

Code: Select all

[main]
#dns=none
I think an eFa-configure option "Use Networkmanager to manage resolv.conf (Y/N)" could solve this issue.

When N is selected, do not set dns=none in NetworkManager.conf

User avatar
shawniverson
Posts: 3087
Joined: 13 Jan 2014 23:30
Location: Indianapolis, Indiana USA
Contact:

Re: Update eFa-4.0.2-13 resolv.conf

Post by shawniverson » 19 Apr 2020 14:33

Sounds like a reasonable way to approach this.
Version eFa 4.0.2 now available!

User avatar
shawniverson
Posts: 3087
Joined: 13 Jan 2014 23:30
Location: Indianapolis, Indiana USA
Contact:

Re: Update eFa-4.0.2-13 resolv.conf

Post by shawniverson » 19 Apr 2020 14:33

Version eFa 4.0.2 now available!

User avatar
shawniverson
Posts: 3087
Joined: 13 Jan 2014 23:30
Location: Indianapolis, Indiana USA
Contact:

Re: Update eFa-4.0.2-13 resolv.conf

Post by shawniverson » 19 Apr 2020 14:34

Just a heads up there's a -14 in the pipe, be prepared to comment this line again. I have pulled it from future updates and will replace it with a menu option.
Version eFa 4.0.2 now available!

warlord
Posts: 19
Joined: 16 May 2019 21:21

Re: Update eFa-4.0.2-13 resolv.conf

Post by warlord » 28 Apr 2020 16:06

I've still got eFa running outside my production environment so I only noticed this issue today after it hit on April 13th when it updated to -12.
I concur that commenting out dns=none fixes the problem for me. I use local-caching nameservers for my network and have all my devices point at those. This change first set it to 127.0.0.1 (which is wrong) and then after reboot it was empty (which was also wrong).
I also concur a menu item would be nice. But having the system change its configuration during an automated update seems like a poor UX to me.
Had this been a production system I would have noticed sooner, but I also might have lost mail if DNS broke during an update overnight.

jamerson
Posts: 152
Joined: 19 Aug 2017 18:57
Location: kaaskop

Re: Update eFa-4.0.2-13 resolv.conf

Post by jamerson » 04 May 2020 16:26

i beleive i am on the same boat, my box keeps having issues with oubound,i thought it was ipv6 but good catch Henk " dank je wel"
i'll give it a try and check it.
Version eFa 4.0.0 RC1 now available in testing repo. Come join us in advancing eFa!

Post Reply