Topics

1

Web Proxy Filtering and Caching / Shaping causes dmesg to throw fq_codel_enqueue maxidx = 801 over limit

« on: December 09, 2022, 02:26:20 pm »

Hello,
where ever I search I get only a "click by click" documentation of shaping that shows how to do it for a monkey but is not explaining the why and "what if"

the kernel tells with dmesg:
fq_codel_enqueue maxidx = 801
fq_codel_enqueue over limit

Ok, and now the clicky docu is at an end
I cannot find any meaningful docu between level "the algorithm - scientific papers" and "click here and do not ask, monkey"...

Crazy things like "do not check: Enable CoDel active queue management" are totally unclear to me.
googling my warning finds nothing but guessing

I beg for a nice link to a good docu

Marc   

2

22.7 Legacy Series / 22.7.9 creates spuky network issues that require full service restart

« on: December 08, 2022, 08:47:34 pm »

Hello,
I have a virtualized opnsense with a few subnets that was running clean so far.... now I have successfully installed
OPNsense 22.7.9-amd64
FreeBSD 13.1-RELEASE-p5
upgrade... well almost successfully.

My interface vtnet1 is bound to a subnet 192.168.111.0/24 => my lan cable stuff in the house.
But after a while the clients lose the connection to the net and switch to WLAN *.*.112.0/24.

All this happens quite quietly... the DHCP clients lose their lease, if I assign a static IP I still can't ping the server in the basement. I can't reach the server from the 112 subnet either.

But the gateway on *.*.111.1 is reachable and also the interface vtnet1 is active according to ifconfig.
The WebUI looks completely normal...all services are running.

Ok, the dhcpd log never gets to the DHCPACK but I see requests coming in...and offers going out.
Ping to the server does not work

In the end i can't get anything in the WebUI.... tried:
- restart services
- de/activate interface
-Filtering rules of the firewall are on swipe for everything

Restarting OPNSense or restarting services with option 11 in SSH bring my *.*.111.0 network back up. Until it silently dies again after a while....

I come from Linux and apparently BSD is quite different... I can't find a hint in a log what dies and why.

I asked here in the german forum where to find more technical hints in BSD, unfortunately I didn't get any hints.

Now it ran for one day and then the WLAN went away.

The kernel of the host on which the OPNsense guest is running suddenly throws:
brsolnetwlan: received packet on enp8s0f1 with own address as source address (addr:d2:57:d1:5c:59:4f, vlan:1)

Shortly after that the LAN was gone...
I went to the server in the basement and restarted the Opnsense services with option 11: Tada! Works again, without reboot, without changes to the hypervisor host, without touching the cabling. The host kernel reports no more errors.
Unfortunately probably only until tomorrow...

I was tired of it now and reset the VM to the state before the upgrade 22.7.9. There it ran super stable.
Is now of course extremely annoying if you can now no longer make an upgrade without having to hear the grass grow afterwards, because the system subtly fails somewhere.
I would have liked to make a bug report but: "something wrong" uses small and I do not know BSD well enough.

Nevertheless I wanted to let you know that something does crazy things inside 22.7.9

Regards Marc

3

German - Deutsch / Nach Upgrade auf 22.7.9 ist LAN Subnetz nur kurz erreichbar

« on: December 06, 2022, 10:26:54 pm »

Hallo,
ich habe eine virtualisierte Opnsense mit ein paar Subnetzen, die bisher sauber lief... jetzt habe ich erfolgreich 
OPNsense 22.7.9-amd64
FreeBSD 13.1-RELEASE-p5
upgrade gemacht... nunja so fast erfolgreich.

Mein Interface vtnet1 ist an ein Subnetz 192.168.111.0/24 gebunden => meine Lan-Kabelzeug im Haus.
Nach einer Weile verlieren die Clients aber die Verbindung zum Netz und steigen aufs WLAN *.*.112.0/24 um.

Das alles passiert ziemlich still und leise... die DHCP clients verlieren ihren lease, vergebe ich eine statische IP kann ich den Server im Keller trotzdem nicht pingen. Ich kann den Server auch nicht vom 112er Subnetz erreichen.

Das Gateway auf *.*.111.1 ist aber erreichbar und auch das Interface vtnet1 ist aktiv laut ifconfig.
Das WebUI sieht völlig normal aus...alle Services laufen.

Ok, das dhcpd log kommt nie bis zum DHCPACK ich sehe aber Anfragen ankommen...und offers rausgehen
Ping auf den Server geht nicht

Am Ende kann ich im WebUI nichts erreichen... habe versucht:
- Services neustarten
- Interface de/aktivieren
-Filterregeln der Firewall sind für alles auf Durchzug

Ein Neustart der OPNSense oder ein Neustart der Services mit Option 11 in SSH bringen mein *.*.111.0 Netz wieder hoch. Bis es dann wieder lautlos stirbt nach ner Weile...

Ich komme von Linux und offenbar ist BSD doch recht anders... ich finde nicht einen Hinweis in einem Log was da wegstirbt und wieso.

Ideen was da Probleme machen kann und wo ich das sehen kann? Das Problem ist leider extrem diffus, damit kann man nicht in google suchen.

Gruß Marc