Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - FrancoisMaymil

#1
The GUI/shell difference is worth isolating before changing more NAT rules. Your earlier results list 10.2.0.1 as the source for the shell tests, but not the exact command.

On TAC, assuming those addresses are still current, could you compare:

ping -c 3 10.1.0.11
ping -c 3 -S 10.2.0.1 10.1.0.11

and the GUI ping to the same destination with the LAN source? A capture of ICMP on the WireGuard interface of TAC and of the hub during each test would show which source is used and whether replies come back.

A separate check on the hub: wg show all allowed-ipsIn your first post, peer TAC has 172.19.0.2/24. WireGuard stores that as 172.19.0.0/24, and if several peers list the same prefix, only one peer keeps it. If the other spokes are set the same way, traffic to their tunnel addresses would all go to that one peer. That alone would not explain the GUI/shell difference, so I would start with the ping comparison.
#2
Hallo Robert,

die Meldung ,,spurious link down (PHY link up), overriding" ist eigentlich eher eine gute Nachricht. Der ure-Treiber hat einen falschen Link-down erkannt (bekanntes Polling-Problem, FreeBSD PR 252165) und hält den Link deshalb absichtlich oben. Das ist also nicht unbedingt das Flapping selbst.

Ich würde zuerst schauen, ob der Link wirklich weggeht. Im Systemlog nach ue0: link state changed to DOWN suchen und auch prüfen, ob das Gateway-Monitoring Ausfälle zeigt. Wenn nur diese eine Meldung kommt, kannst du sie eigentlich ignorieren.

Falls du mit dem Treiber das Plugin os-realtek-re meinst: das ist für PCIe-Karten mit dem re-Treiber. Beim USB-Adapter ändert dieses Plugin nichts.

Gruß
François
#3
Hallo Robert,

für ein Backup-WAN reicht USB problemlos aus. Ich würde einen Adapter mit Realtek-Chip RTL8153 (1 Gbit) oder RTL8156 (2,5 Gbit) nehmen. Die laufen unter FreeBSD mit dem ure-Treiber und sollten in OPNsense als ue0 auftauchen. Am besten beim Kauf auf den verbauten Chip achten und weniger auf die Marke.

Eine Alternative ohne zusätzliche Hardware: Falls du einen managed Switch hast, kannst du den 5G-Router auch in ein eigenes VLAN hängen und dieses VLAN über den bestehenden Port als zweites WAN nutzen.

Gruß
Thomas
#4
Before scripting this, there are two things good to know:

MAC aliases only work for devices on networks directly connected to the firewall, because OPNsense resolves them from its ARP/NDP tables. With IPv6 privacy addresses, the address currently used can change, and the alias will only catch it once it appears in the NDP table. Phones using randomized MAC addresses can also be a problem here.

If your IPv6 prefix is static, I think the most predictable solution is simply to add the IPv6 host entries next to the IPv4 ones in the same alias.

If your ISP prefix can change, have a look at the "Dynamic IPv6 Host" alias type. It combines the current prefix of the interface with a fixed host part, so you don't have to change all aliases when the prefix changes.

For doing the bulk change: in Firewall > Aliases you can export/import the aliases as JSON. So normally you can edit the export (type and content of each alias) and import it back.

I would make a config backup before, and test it first with only one alias before doing all of them.
#5
If the node shows online in the admin console, auth and the tunnel should probably be fine. The "down" status on the assigned interface is most likely just cosmetic. I would first run tailscale status and tailscale ping <other router> from the shell to confirm this.

For site-to-site between two OPNsense boxes, there are a few things that need to be correct:

Each router has to advertise its own LAN subnet in the plugin, and of course the two subnets must not overlap. Then both routes need to be approved in the admin console (Machines > Edit route settings), otherwise they will stay inactive.

Also check that "Accept routes" is enabled on both routers. If not, they will not install the subnet from the other side.

On each router, you also need a pass rule on the Tailscale interface with the remote LAN subnet as source, not only the 100.64.0.0/10 range.

If it still doesn't pass traffic, can you post the plugin settings and the output of tailscale status from both routers?