OPNsense Forum
Archive => 20.7 Legacy Series => Topic started by: Rasense on January 01, 2021, 06:44:58 pm
-
Hi all, I am new here and was wondering if any of you could help before I try another firewall.
I have an Intel atom E3845 device that came with pfsense on a 8gb cf card +2gb of ram. I have a 200mb virgin media connection and was suffering from random disconnects. I tried upgrading pfsense to a development version 2.5 hoping that this would fix my issue, but instead it killed my install, after sourcing a serial cable I reinstalled the system with opnsense hoping that this would fix my issue. But sadly after spending an hour setting up 25 static ip addresses for all my devices and opening ports for our Nintendo game consoles I am facing exactly the same issue now.
I want to throw in the towel with BSD and look at untangle or openwrt but wanted to give it one more last try by contacting this forum to see if I am missing something.
Let me explain my network setup (lan ip addresses set to 10.4.4.1 range)
Virgin media hub3 in modem mode >> opnsense igb0 (wan) igb3(lan) >>> linksys velop mesh wifi in bridge mode
If I take out the opnsense router and set the VM hub into router mode it all works fine apart from the speed that goes up and down. To me this means that either the Opnsense router is doing something funky or the VM hub is being silly.
What do you guys think I should do? And which log files should I start checking?
Evrytime the internet goes down I see this in system/log files/general
usr/local/etc/rc.newwanip: On (IP address: 10.4.4.1) (interface: LAN[lan]) (real interface: igb3).
usr/local/etc/rc.newwanip: IPv4 renewal is starting on 'igb3'
usr/local/etc/rc.linkup: Hotplug event detected for LAN(lan) but ignoring since interface is configured with static IP (10.4.4.1)
kernel igb3: link state changed to UP
usr/local/etc/rc.linkup: Hotplug event detected for LAN(lan) but ignoring since interface is configured with static IP (10.4.4.1)
kernel igb3: link state changed to DOWN
-
Are you using Unbound?
-
Hi, yes I haven’t changed anything so it’s on by default. Do you recommend it to be switched off ? And if so why ?
On the positive side since last night 7pm-ish I haven’t seen any connection drops. Maybe it’s fixed itself ?
-
The 20.7.7 version of Unbound (1.12.x) had a bug that causes the Unbound DNS service to crash repeatedly (Apparently only for some users) there is a patch released by unbound that seems to resolve the issue.
Patch command: pkg add -f https://pkg.opnsense.org/FreeBSD:12:amd64/20.7/misc/unbound-1.13.0_1.txz
Honestly, I am not sure this is your issue, but this patch is so minor it should only help.
Edit(s): Fix finger wandering issues
-
Why I asked about Unbound is that there might be a challenge with DHCP that results in Unbound restart, and while that is happening there is NO DNS resolution working. Now if one uses Unbound without blocking lists this might not be an issue - but with a few blocking lists active it can take 40 seconds before Unbound responds.
Also link up/down will restart Unbound - just like above when DHCP sometimes is active. And as above, Unbound restart means no DNS resolution.
I think this will be addressed in 21.1 or so, and there does not seem to be to many people running into this (except me since well never mind).
Anyway, Unbound might be a bit of a challenge - that is why I mention this.
-
Thank you both, good to see active members here . Gives me encouragement to keep trying opnsense :-)
I will try the patch later and let you know what happened.
As this morning dhcp started to play up and down again, I have disabled unbound .. let’s see if this helps for now
-
Ok I have taken the Opnsense firewall out :-( . Last night I disabled unbound, I thought if unbound is the issue and I disable it this would surely fix the problem. Nope nope and nope. After many restarts of Opnsense , my mesh network nodes and the Virgin media hub 3, This problem is not going away. It will randomly work for a couple hours without any issues and then start dropping or renewing the lan IP address .. I soo want this to work but have no clue how to.
Currently running Virgin media hub in modem mode connected to Linksys Velop mesh in router mode.. all running perfect, but I have no control over my network now :-( .
Also @MBfromOK i tried the advised patch by you
but get the following error - pkg: https://pkg.opnsense.org/FreeBSD:12:amd64/20.7/misc/unbound-1.13.0_1.txz: Not Found
-
This version of unbound 1.12.x has a bug that’s the reason behind the crash of the unbound DNS service. But only some users are facing this problem, not everyone. The good news is that there is a patch released by unbound that seems to resolve this problem. You should try it here allspeedtest (https://www.allspeedtest.com/) it will be helpful for you.
Another reason behind this can be your router. If you are using an old router, you should change it. Because old routers are not strong enough to handle the internet signals and that’s why you feel that everything’s disturbed. Change your router or use a wifi booster to increase the coverage area at your place. Both of these solutions will help you a lot.