Topics

1

23.1 Legacy Series / Android -- some apps load very slowly after upgrade to 23.1

« on: April 07, 2023, 12:28:20 am »

Following upgrading to 23.1, some apps running on two Android devices started loading very slowly.
Android devices:  Samsung Tablet, Pixel 5a phone
Slow apps:
-- loading an Excel file from OneDrive -- this can take several >>minutes<< unless I am running NordVPN on the tablet, in which case loading is immediate, as it was before upgrade to 23.1.  File size is 240k.
-- Starting Google Drive and loading a file -- not quite as slow as Excel File, but it can take up to a minute for Google Drive to display the directory, then another extended wait to load a pdf or word file.  Not a problem with the VPN running.
-- Running Wunderground weather app on either the tablet or the phone.  The app starts immediately, but takes an extended time to load any information.  Again, not a problem when running the VPN.  Also, not a problem for the phone when connected the the cellular network, not the LAN with the opnsense router.
Other devices on the network include Linux desktop running  Ubuntu 22.04, Windows 10 laptops, iphone, ipad.  None of these other devices are having similar problems.
Opnsense configuration:
OPNsense 23.1.5_4-amd64
Intel(R) Atom(TM) CPU E3845 @ 1.91GHz (4 cores, 4 threads)
Unbound DNS
I did not operate any of the intermediate versions of 23.1, but went directly to 23.1.5_4 release.
Is there something funky about how Android does DNS that causes a problematic interaction with Opnsense?
Thanks in advance for any help.

2

General Discussion / WAN DHCP client doesn't renew/relaod after power down

« on: November 03, 2021, 07:03:01 pm »

I recently had a failure of my UPS (battery died) during a storm event that resulted in repeated cycling of line power.  During the event, I lost internet connectivity and thought it was ISP's problem -- OPNsense was up and showing an IPv6 address on the WAN interface, but no IPv4.  After many hours of no internet, I investigated and found that going to Interfaces>Overview>WAN->reload resulted in a valid IPV4 address on the WAN interface and restored internet connectivity.
Again making an incorrect assumption, I figured that some problem associated with repeated power outages had resulted in a rare state that would not be repeated.  WRONG.  I cycled the power again, after doing a clean shutdown of OPNsense, as I replaced the battery in the UPS, and once again, no IPV4 address on the WAN interface and no internet connectivity after restart.  As before, going to the Interfaces>Overview>WAN->reload step restored the WAN interface to full operation.
As I have been running on a UPS for quite a while, I had not previously experienced the power cycling fault.  I have, however, done numerous reboots associated with updating OPNsense, which has not resulted in loss of WAN connectivity.
OPNsense 21.7.4-amd64
FreeBSD 12.1-RELEASE-p20-HBSD
OpenSSL 1.1.1l 24 Aug 2021
Intel(R) Atom(TM) CPU E3845 @ 1.91GHz (4 cores)

Browsing for similar problems, I see that others have experienced sim

Browsing for similar problems, I see that others have experienced similar problems associated with earlier major releases of OPNsense.  Is this still an outstanding issue?  Any ETA for a fix?  Or is there something in settings that I should change?
Thanks in advance for help/advice.
John K.ilar problems associated with earlier major releases of OPNsense.  Is this still an outstanding issue?  Any ETA for a fix?  Or is there something in settings that I should change?
Thanks in advance for help/advice.
John K.

3

21.1 Legacy Series / Failed, no signature found

« on: February 12, 2021, 08:12:55 pm »

I am trying to upgrade from  20.7.8_4-amd64 to 21.1 through the web gui interface. I have repeatedly gotten the following response:
 ***GOT REQUEST TO UPGRADE: maj***
Fetching packages-21.1-OpenSSL-amd64.tar: .............................. failed, no signature found
***DONE***
I tried this with the source set to LeaseWeb in DC and NYC*BUG, with the same result.

CPU: Intel(R) Atom(TM) CPU E3845 @ 1.91GHz (4 cores)

Suggestions?

Thank you.

4

20.7 Legacy Series / Ubuntu 16.04 DNS problems after 20.7.8_4-amd64 update

« on: February 02, 2021, 10:28:38 pm »

Shortly after final 20.7.8_4 update, my Ubuntu 16.04 workstation started having problems resolving domain names.  I have other Ubuntu 18.04 machines, windows machines, and android and ios machines, none of which seem to be having issues.  Attempting to look at the problem with Wireshark, I see messages of the type "standard query response 0xxxxx No such name [A or AAAA] [hostname]...." which are returned by OPNsense on DNS queries from the Ubuntu 16.04 machine, also returned by Google DNS servers 8.8.4.4 and 8.8.8.8.
Is this correct behavior?  It would seem that the flaw would be on the Ubuntu machine, since the rest of the network appears to be running properly, but I haven't changed any settings there.
If I reset the connection from the Ubuntu machine using Network Manager, DNS recovers but only for a very short time, and then stops working again.
Any debugging help would be much appreciated.

5

20.7 Legacy Series / opnsense 2.7 won't reboot

« on: October 02, 2020, 10:20:10 pm »

Opnsense 2.7.2 freezes on reboot, initiated from web interface.  Recovers after waiting ~15 minutes and cycling power.
Upgraded to 2.7.3, upgrade appears to complete successfully, with reboot initiated, but system does not reboot.  Again wait 15 minutes and cycle power, and system comes back up quickly with 2.7.3 apparently successfully installed. 

Subsequently log onto system with ssh and issue "shutdown -r now", and system shuts down cleanly and comes back up quickly.

Would appreciate any suggestions about what the problem may be.  I would like to be able to keep the system firmware/software up  to date, but it makes me nervous when the install does not proceed smoothly.