Messages

1

22.7 Legacy Series / Re: Connection issues after updating to 22.7.7

« on: November 24, 2022, 12:57:42 am »

So here's where Im at.  When I go to download a test file or stream something live, I watch the traffice monitor and every so often, like every 30-60 seconds the inbound traffic drops and flatlines very briefly and then comes back up again.  I'll be downloading at 60mb/s, and then it goes down to zero.  I reset opnsense to default settings and retried this test, and as best i can tell thoses issues do not happen.  So there is something in my current config that is causing this and im not really sure where to start in trying to diagnose this problem.  I hadn't changed anything in the last few months or so either, this all started after updating to 22.7.7.  Any help would be greatly appreciated, thank you.

2

22.7 Legacy Series / Connection issues after updating to 22.7.7

« on: November 23, 2022, 02:53:49 pm »

I have been getting alot of connection drops since updating to 22.7.7, now on 22.7.8.  I went to run a connection audit and get the following:

***GOT REQUEST TO AUDIT CONNECTIVITY***
Currently running OPNsense 22.7.8 (amd64/OpenSSL) at Wed Nov 23 08:47:02 EST 2022
Checking connectivity for host: mirror.wdc1.us.leaseweb.net -> 207.244.94.80
PING 207.244.94.80 (207.244.94.80): 1500 data bytes
1508 bytes from 207.244.94.80: icmp_seq=0 ttl=54 time=56.395 ms
1508 bytes from 207.244.94.80: icmp_seq=1 ttl=54 time=62.284 ms
1508 bytes from 207.244.94.80: icmp_seq=2 ttl=54 time=59.076 ms
1508 bytes from 207.244.94.80: icmp_seq=3 ttl=54 time=57.224 ms

--- 207.244.94.80 ping statistics ---
4 packets transmitted, 4 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 56.395/58.745/62.284/2.262 ms
Checking connectivity for repository (IPv4): http://mirror.wdc1.us.leaseweb.net/opnsense/FreeBSD:13:amd64/22.7
Updating OPNsense repository catalogue...
Fetching meta.conf: . done
Fetching packagesite.pkg: .......... done
Processing entries: .......... done
OPNsense repository update completed. 809 packages processed.
All repositories are up to date.
Checking connectivity for host: mirror.wdc1.us.leaseweb.net -> 2604:9a00:2010:a0b8::5
ping: UDP connect: No route to host
Checking connectivity for repository (IPv6): http://mirror.wdc1.us.leaseweb.net/opnsense/FreeBSD:13:amd64/22.7
Updating OPNsense repository catalogue...
pkg: http://mirror.wdc1.us.leaseweb.net/opnsense/FreeBSD:13:amd64/22.7/latest/meta.txz: No route to host
repository OPNsense has no meta file, using default settings
pkg: http://mirror.wdc1.us.leaseweb.net/opnsense/FreeBSD:13:amd64/22.7/latest/packagesite.pkg: No route to host
pkg: http://mirror.wdc1.us.leaseweb.net/opnsense/FreeBSD:13:amd64/22.7/latest/packagesite.txz: No route to host
Unable to update repository OPNsense
Error updating repositories!
***DONE***

My connection is fine when direct connecting to the modem, but as soon as I plug back into OPNSense the problems resume.  I was running pihole as well, fyi but that seems to have broken after this update as well so I've disabled it for the time being.  I would appreciate any insight that would help point me in the right direction to resolve this, thank you.