Same config not working on physical machine, sendto error 64 on GW

[Knogle]

Ahoy friends, how are you doing? :)

I am currently trying to migrate my config to a physical machine due to performance issues with Proxmox. On my physical machine, I am using a lagg0 interface with different VLANs on it. VLAN 2100 is my WAN VLAN.

Everything on the LAN side works fine, but unfortunately, the WAN gateway is down, even though the interface is up and receives an IP from the ISP. However, I can't get the WAN working at all.

Even when I disable WAN monitoring, I am not able to ping remote hosts; it always says that the host is down, as in the case of pinging 8.8.8.8.

What could be wrong here? I haven't been able to figure it out yet. Thanks in advance!

On my VM this exact config works fine.

Code Select Expand

root@sin01-edge-opnsense-fw01:~ # ping 7.7.7.7
PING 7.7.7.7 (7.7.7.7): 56 data bytes
ping: sendto: Host is down
ping: sendto: Host is down
^C
--- 7.7.7.7 ping statistics ---
2 packets transmitted, 0 packets received, 100.0% packet loss
root@sin01-edge-opnsense-fw01:~ # 8.8.8.8
8.8.8.8: Command not found.
root@sin01-edge-opnsense-fw01:~ # ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes
ping: sendto: Host is down
ping: sendto: Host is down
ping: sendto: Host is down
ping: sendto: Host is down
ping: sendto: Host is down
ping: sendto: Host is down
ping: sendto: Host is down
ping: sendto: Host is down
ping: sendto: Host is down
ping: sendto: Host is down
ping: sendto: Host is down
ping: sendto: Host is down
ping: sendto: Host is down
ping: sendto: Host is down
ping: sendto: Host is down
ping: sendto: Host is down
ping: sendto: Host is down
ping: sendto: Host is down
ping: sendto: Host is down
ping: sendto: Host is down
ping: sendto: Host is down
ping: sendto: Host is down

[melhar]

I have the same issue, with WAN or LAN going down after 2-3 days.

I receive an IP, but not able to access either WAN or LAN side, nor using Ping.

If I disconnect the LAN cable and then ping like 8.8.8.8 I get traffic through.
Then connect LAN again and can also ping LAN side...

Same procedure if not able to ping LAN, but WAN works. Disconnect WAN cable, ping internal ips and connect again.

Have seen the same issue also be resolved by open gateways in GUI and just save without editing anything...

Probably a bug..?

[melhar]

An update from me here.

Found a suggestion to add the Realtek drivers available as a plugin, and use them instead of the default FreeBSD drivers. That work as a charm, and the firewall have been rock-solid now for 11 days.