Messages

To close the loop on this: After switching out the Realtek interface for an Intel interface, all of my problems have dissolved. If anyone comes across this and is pondering trying a Realtek adapter because "it can't be that bad", well, it can :)

Thank you all for your time and attention on this!

However, I suppose TrueNAS ends up creating a virtual MAC for this connection internally and no longer uses the physical MAC.

Yes, and this generated MAC will change at every reboot at least for TrueNAS CORE (FreeBSD). Don't know about Linux.

But if it is TrueNAS CORE you can do something to fix it - go to System > Tunables and add a tunable following the screen shot:



The bridge should now have the same MAC address as the physical member interface on every reboot.

This is helpful, thank you! I am on Scale so I'll have to do some digging to make sure this applies, but this may help ultimately.

I'm considering putting this Realtek NIC into my TrueNAS system after I get the Intel NIC set up into my Opnsense box later today. I'm guessing that the ideal setup for this would be to revert my TrueNAS system to the physical NIC, then apply a Bridge interface attached to the secondary NIC for my VMs?

Back on topic, though - after some fiddling and reboots, I haven't seen the same ARP error regarding the TrueNAS system trying to take the gateway IP. I will have to continue to test things to see if my two work laptops are still having issues, however. As of this morning, I still needed to trigger IPv6 off and apply the change to the LAN interface to get it to connect. I'm still waiting on the Intel NIC to arrive later tonight.

I currently only have one NIC in my TrueNAS box but I followed the instructions from this video to set up a static IP and bridge for the single NIC: https://www.youtube.com/watch?v=uPkoeWUfiHU
So basically assigning a static IP on the physical interface, then removing said IP, creating a bridge, and assigning that static IP as an Alias on the bridge so the static IP remains. However, I suppose TrueNAS ends up creating a virtual MAC for this connection internally and no longer uses the physical MAC. This is the only Alias I have set up for the device. The two VMs I have running have already grabbed new, unique IPs from the DHCP range, which I then created reservations for in Opnsense.

This was before Opnsense - and it has worked so far, more or less. Are there any alternate resources one might suggest for a better way to set this up?

I assume you're not setting the static IP of these machines to the LAN IP.
It's weird enough that one machine would claim it. 2 of them???
You might want to double check your DHCP config.
The first MAC indicates an ASRock machine. The second one seems unknown.

No, definitely not. So the first MAC is the actual MAC of the ASRock motherboard running my TrueNAS system, the second is the generated MAC from the static IP I created when I made a virtual bridge within TrueNAS that I created with the static IP, so that VMs can grab their own IP. I can't see a clear reason why it would be trying to grab the gateway IP.

I've ordered an Intel NIC that is coming today, so we'll see if that helps iron out what is going on.

So I looked more into that IP issue.
It is my TrueNAS box, which has a static IP set on the box itself, as well as a reservation in OPNsense. It also moved from one MAC to another at one point, but again I'm not sure what the timeframe is on this - I was messing with that device a week or so ago, so it could have been related to that.

Code Select Expand

arp: a8:a1:59:65:5d:68 is using my IP address 192.168.1.1 on re0!
arp: a8:a1:59:65:5d:68 is using my IP address 192.168.1.1 on re0!
arp: 192.168.1.44 moved from a8:a1:59:65:5d:68 to 22:9e:2e:da:d3:2d on re0
tailscale0: link state changed to DOWN
tun0: link state changed to UP
tun0: changing name to 'tailscale0'
tailscale0: link state changed to DOWN
tun0: link state changed to UP
tun0: changing name to 'tailscale0'
re0: link state changed to DOWN
vlan01: link state changed to DOWN
re0: link state changed to UP
vlan01: link state changed to UP
arp: 22:9e:2e:da:d3:2d is using my IP address 192.168.1.1 on re0!
arp: 22:9e:2e:da:d3:2d is using my IP address 192.168.1.1 on re0!
arp: 22:9e:2e:da:d3:2d is using my IP address 192.168.1.1 on re0!
arp: 22:9e:2e:da:d3:2d is using my IP address 192.168.1.1 on re0!
arp: 22:9e:2e:da:d3:2d is using my IP address 192.168.1.1 on re0!
arp: 22:9e:2e:da:d3:2d is using my IP address 192.168.1.1 on re0!

I was just able to observe one of the devices failing to connect to the internet, then after removing DHCPv6 and applying, observing it reconnect, there doesn't seem to be anything different in dmesg. I installed the vendor driver when I was installing OPNsense initially but it didn't show in the Plugins section, so I just ran it there to be sure and it looks like it was indeed installed. I may at this point just find an Intel based NIC and go from there.

A few entries where the LAN goes down then back up, and some items that say different MAC addresses are "using my IP at 192.168.1.1", one of which is my Tuenas box which is hardwired, another doesn't show up in my leases.

None of these have timestamps, though, so I'm not sure when they happened in relation to the errors. I'll have to wait a bit until they drop off the connection and I can pull dmesg immediately after. I'll keep looking through to see if anything sticks out, though. Appreciate the direction!

I can still access the local network, they just won't connect to the internet, even though every other device on the LAN works no problem, connected the exact same way.

It would be odd that only these two devices have problems due to the NIC, but it's only about $20-30 to find out I suppose.

Hello,
I'm pretty new to OPNsense and just trying to wrap my head around more networking information, so bare with me.

I recently switched to OPNsense from a Netgear router that was having some issues. I have things pretty well dialed in without doing anything fancy at this point, but there is one thorn in my side.

All of my devices connect without issue to the network (mostly over Wifi on a dedicated AP) except for two HP work laptops. After a lot of trial an error, I thought I narrowed down the problem to IPv6, after I turned it on for the LAN interface (I have admin to one of these laptops, but not the other - so I can't disable on the adapter, though this didn't make a difference on the one). However, after one day without issues, they returned the next day: I can connect to the Wifi, but only with local network access, no internet. What REALLY fixes this, temporarily, is making some kind of minor change to the LAN interface, saving, and applying the change. Whether this is turning IPv6 on or off, or even changing IPv4 from Static IPv4 to DHCP (which fails due to a DHCP server running message) and back to Static IPv4, so ultimately making no change at all.

Has anyone run into this? Does anyone have any advice on what to look for? I'm not sure what kind of setup info would be best to share, so let me know what may be helpful to share here, or to look into.

Thanks in advance to anyone who can help me tackle this!

Edit: Here are some basics:
Version: 25.1.3
Network setup:
WAN: PPPoE (CenturyLink Fiber) over motherboard's onboard Intel LAN
LAN: Static IPv4 over Realtek PCIe Ethernet adapter
I have a managed switch plugged into this, with a TP-Link AP connected, as well as a handful of other hardwired devices.

You'll advertise exit node from Opnsense, approve on tailscale, then from your client outside of the network, connect to tailscale and use the Opnsense exit node.

I believe the two settings shown are asking if you want to run the client as an exit node and subnet router, which is not necessary or wanted.

I'm having a similar problem except that I can reach my Opnsense router and the switch everything else is connected to, but I cannot reach what is on the other side of the switch.

That said, from my research I believe you need to advertise exit node and then connect to your exit node on the client side.