Messages

1

24.1 Legacy Series / Re: Issues after 24.1.5_2 update

« on: April 06, 2024, 09:29:10 am »

I generated new VLAN and these worked properly. So did SOME of my pre-existing VLANs though...not all of them...very weird

Anyway, during the night I gave it a thought and realised maybe it's a DNS issue. I checked the general DNS settings under the System menu and the address was completely random. I changed it to that from Cloudlfare, reboot the system and now all VLANs work, including those that did not before !

I don't really understand why certain VLANs worked initially. Some of them had a DNS server set to override the system one, so this makes sense. Then my assumption is that some clients, like my laptop, had also their own DNS setup. Hence why they were able to connect.

Hope this helps.

2

24.1 Legacy Series / Re: Issues after 24.1.5_2 update

« on: April 06, 2024, 12:22:27 am »

Creating new VLANs to replace faulty ones solved part of my problem.
Now, I cannot check software updates anymore ("Check for updates") runs but nothing happens...
Zenarmor has started but no device detected and no log, no live view...

3

24.1 Legacy Series / Re: Issues after 24.1.5_2 update

« on: April 05, 2024, 10:36:57 am »

I have been experiencing similar symptoms. Two on my VLAN don’t connect to internet anymore. Others are fine.
Weirdly enough, logs from Zenarmor plugin show no connection through these VLANs already several hours before I update Opnsense. I am now wondering if these logs maybe got corrupted as well because I have not touched any configuration in over a week and everything was working fine until I could not use my Apple TV - which is on one of the impacted VLANs - after the update yesterday…

The hot fix this morning did not change anything for me.

4

22.7 Legacy Series / Re: Firmware update does not work

« on: August 10, 2023, 07:28:50 pm »

Not sure if the issue has a similar cause, but since yesterday, I cannot perform updates and get the following message :
I struggle to understand what's going on because this weekend it prompted me to upgrade to a more recent version of Opnsense.... now it's not prompting anymore.

I am on 22.7.11_1 and would like to update to 23.1 or later if possible.

Any thoughts ?

***GOT REQUEST TO CHECK FOR UPDATES***
Currently running OPNsense 22.7.11_1 (amd64/OpenSSL) at Thu Aug 10 19:23:22 CEST 2023
Fetching changelog information, please wait... done
Updating OPNsense repository catalogue...
Fetching meta.conf: . done
Fetching packagesite.pkg: .......... done
Processing entries: .......... done
OPNsense repository update completed. 819 packages processed.
Updating SunnyValley repository catalogue...
pkg: https://updates.sunnyvalley.io/opnsense/FreeBSD:13:amd64/22.7/OpenSSL/latest/meta.txz: Not Found
repository SunnyValley has no meta file, using default settings
pkg: https://updates.sunnyvalley.io/opnsense/FreeBSD:13:amd64/22.7/OpenSSL/latest/packagesite.pkg: Not Found
pkg: https://updates.sunnyvalley.io/opnsense/FreeBSD:13:amd64/22.7/OpenSSL/latest/packagesite.txz: Not Found
Unable to update repository SunnyValley
Error updating repositories!
Checking integrity... done (0 conflicting)
Your packages are up to date.
***DONE***

Thanks in advance for your help.

5

21.7 Legacy Series / Firewall block in rule of Ethernet client

« on: January 18, 2022, 01:40:45 pm »

Hi,

I am having an issue accessing the web UI.
Thinking I may have done a mistake in my config, I decided to investigate. After some research using the command line (= connecting my Opnsense box to a keyboard, mouse and hdmi screen) I see that a rule (block in on igb1) seems to be preventing my MacBook from getting a proper DHCP IP address. The MAC thus auto-assigns a false 169.xxx IP, which in turns puts me in a different network than the Opnsense box. Reason why I cannot connect to the UI.
I decided to put the Opnsense box back to the factory default setting (I have a copy of my settings in a safe place) to start fresh. I did this in the command line.

Now, I try to connect my MacBook via Ethernet to my Opnsense box (LAN port) and still get the same firewall block when the MacBook is asking for a DHCP address. I am stuck and this is surprising since I had been connecting my box with Ethernet until now and it worked perfectly

Any ideas on how I can solve this ? I have been searching since yesterday early evening. I don’t understand why this fw rule is blocking me, I never saw it as a default rule before !

Thanks for you help

6

21.7 Legacy Series / Re: 4G fallback fails once a day

« on: January 13, 2022, 11:35:53 am »

Hi,

Thanks for your post. I have a similar setup and struggle to make it work
Would you be able to share more detail about your configuration of opnsense and the lb2120 in bridge mode , especially the point-to-point settings and link to WAN ?

I am unable to make it work. The issue you described below did not occur in my case, so that I do not know where to look anymore. You can check my post below for the full description :

https://forum.opnsense.org/index.php?topic=26316.0

Thanks for any help you could provide

7

21.7 Legacy Series / Unable to connect 4G LTE modem Netgear LB2120

« on: January 11, 2022, 11:18:09 pm »

Hi,

New with Opnsense - switching from Ubiquiti.
I use a 4G SIM as my main network connection. After browsing these forums and that from PFsense I bought a Netgear LB2120 modem which seemed to be compatible out of the box.

What I have done so far :
> Full setup and update of Opnsense (Protectli box)
> Setup Netgear LB2120 in bridge mode with ethernet on WAN port
> Create Point-to-Point device in Opnsense in PPP with parameters similar to that found on the LB2120. I selected the only Link Interface prompting on the screen /dev/cuaU0

I'm running OPNsense21.7.7-amd64 and FreeBSD12.1-RELEASE-p19-HBSD

Despite all this, I am getting errors in the logs
For instance :
"LCP: Down event
Link: DOWN event
MODEM: chat script failed
CHAT: The modem is not responding to "AT" at ModemCmd: label.
Link: reconnection attempt 1
Link: reconnection attempt 1 in 1 seconds
LCP: Down event
Link: DOWN event
MODEM: Fail to open serial port /dev/cuau0 on speed 115200
uu _lock(cuauo): device in use
LCP: LayerStart
LCP: state change Initial -> Starting
LCP: Open event"

Anyone with experience with Netgear LB2120 can help and share their config with me please ?
Could it be that I should be using another Link Interface ? I am not sure how this works to be honest...

 PS : I saw a few posts mentioning something about a non-standard TCP/IP implementation from Netgear. I admit I have not had time to try the proposed solution, I will try this later this week. https://forum.opnsense.org/index.php?topic=25727.msg123949#msg123949

Thanks in advance for your help.