Recent posts

#1
General Discussion / Re: Periodic NIC issues (?) wi...
Last post by BrandyWine - Today at 05:47:40 PM
Quote from: fornax on Today at 02:05:14 AMFirst time for everything, I guess... yesterday I had an issue that was only resolved after bouncing the WAN interface instead of LAN like every other time. In a fit of frustration I reinstalled the OS today

And you are running latest NVM for the 226's ?
#2
Are you building this for a specific car/team, or is this a service to all car/teams?

You said no 5GLTE, so how then do you reach utoob?

It's a racetrack, are there any local stipulations where you can increase wifi Tx power? How does Indy or NASCAR do in-car video? Wifi is cheap, but perhaps comes with it's own problems due to Tx power limits.

From my view, all the camera feeds should land in a 2x2 video mixer, one that allows you to show (choose) 1, 2, 3, or 4 video feeds at once, basically allowing you to have 4 video feeds in one HD screen (car, drone, cam1, pit), from there it connects (outputs hdmi) to a live-stream gateway that encodes direct to utoob live, same encoder gateways can live stream to multiple platforms at the same time. The encoders do usually support 5g-wifi and ethernet-wired, so some choices there.

As for multi-wan, sure, OPNsense can do that via policy-based routing. You default route based on source subnet. 10.10.10.0/24 DFG WAN1, 10.10.11.0/24 DFG WAN2, 10.10.12.0/24 DFG WAN3, etc. This also implies that you have three distinct connections or ISP's for internet access.

To do that, I would use a device that has at least 6 gig ifaces, 3 for WAN and 3 for LAN, then just match them, like LAN1-WAN1, LAN2-WAN2, LAN3-WAN3.

Having the fw in there allows you to control the data flows. Duly noted the single point of failures.

#3
26.7 Series / Re: Auto detection of WAN port...
Last post by Karla - Today at 05:41:52 PM
The setup is at follows.

Fritzbox 7530 -> OPNsense (at Lan) -> Fritzbox 4040.

The IP adress of Fritzbox 7530 is 192.168.178.1 with DHCP and DNS server.

Actually I am using OPNsense 26.7.

OPNsense runs on physical hardware - not VM.
#4
General Discussion / Re: ARP MAC resolution problem...
Last post by vpx23 - Today at 05:40:57 PM
Just adding two observations:

  • Even when adding the MAC address of the cable router to "Interfaces: Neighbors: Static Assignments" it doesn't get recognized, the re0 interface must be physically unresponsive.
  • When doing a packet capture in "Interfaces: Diagnostics: Packet Capture" on re0 [WAN] the gateway is back in 1-2 seconds, it seems to reset the interface. In the packet capture you can immediately see the "Request who-has IP:A tell IP:B; Reply IP:A is at MAC:A" packets.

Lately I'm getting this initially mentioned problem every day because I added an external power switch to the power socket because the power switch on the PSU started to get fried up (crackling sound when turned on). Therefore the NIC now isn't really powerless, you can even notice how the power LED of the OPNsense box flashes on again for 2-3 seconds after I switched off the power switch on the power socket.

I really think I'm gonna replace this adapter with an Intel one because I'm getting tired of rebooting OPNsense or doing a packet capture to get the gateway up again.

This good old Intel i210 would be the cheapest option: https://www.inter-tech.de/produktdetails-198/ST-729_EN.html
#5
German - Deutsch / Re: Warum wird ein Client gebl...
Last post by patient0 - Today at 05:18:04 PM
Zeig doch mal den Logeintrag für den Client der erfolgreich eine IPv4 bekommt im gleichen VLAN, scheint für mich grad unwahrscheinlich.

Welche OPNsense Version setzt Du ein? Welchen DHCP Server setzt Du ein, DNSmasq oder KEA DHCP? Und ist bei dem DHCP Server 'Firewall rules' (KEA) oder 'DHCP register firewall rules' (DNSmasq) gesetzt?
#6
General Discussion / Re: Rules under version 27
Last post by Monviech (Cedrik) - Today at 05:03:57 PM
Yes the legacy rules are visible and they work.

Thats the reason they are visible in the new Rules GUI.

They cannot be edited, but they have a command that redirects you to the migration assistant.

Even if you dont have the legacy firewall rules, you can always migrate.

Nothing is broken.

What I cannot deny though is that it might be confusing for some users. But it cannot be easily fixed. Visibility of all rules is more important, and an automatic migration too sensitive cause some rules might not be valid anymore (The migration assistant and the import validate this and warn)
#7
General Discussion / Re: Rules under version 27
Last post by mooh - Today at 05:01:43 PM
When it tried it, the legacy rules were visible in the new rules UI and they worked, at least as far as I could test it in a small test setup. I realised only after a while that I couldn't modify them.
#8
German - Deutsch / Re: Warum wird ein Client gebl...
Last post by AlexanderB - Today at 04:21:33 PM
Ich habe hier leider immer noch keine Lösung gefunden, was mich ziemlich nervt, da ich das System ja auch verwenden will.
Hat denn keiner eine Idee?

Warum greift die erste globale Regel im last match Verfahren? Wieso blockt diese mir jeglichen Verkehr, obwohl ich bereits zum testen eine Regel erstellt habe, die sämtlichen Verkehr freigibt?
#9
26.7 Series / Re: Auto detection of WAN port...
Last post by patient0 - Today at 04:04:30 PM
Would please provide more information? Where on the Fritzbox do you connect the OPNsense box, LAN or DMZ? Is OPNsense WAN usually getting a Fritzbox LAN address (192.168.178.xx ?). Do you set a static WAN to get it working? Have you changed anything on the Fritzbox? What OPNsense version are you using? OPNsense as a VM or a physical device?
#10
General Discussion / Re: Rules under version 27
Last post by Monviech (Cedrik) - Today at 03:04:38 PM
The legacy rules are not imported as new rules.

The new rules just displays the legacy rules via this command:

configctl filter list non_mvc_rules
Each legacy rule will have a link button, and if you press it you either open the exact rule when the legacy firewall plugin is installed, or it opens the migration assistant if the legacy firewall plugin is missing.