Messages

https://github.com/freebsd/freebsd/commits/35c027f3215c305ddf9814e895b7f4c880521eb8/sys/dev/bge
This is history of this shitty broadcom driver in FreeBSD. I don't see any vlan related commits since 12 release.

Hm, me either. I don't use bge so I cant dive deeper into it.

Deleting all vlans on this bge1 resolves issue.

20.7 with broadcom:
bge1@pci0:2:0:1:   class=0x020000 card=0x1f5b1028 chip=0x165f14e4 rev=0x00 hdr=0x00
and vlans gives you huge latencies, before FreeBSD12 (till 20.1.9_1) everything working fine.

Did you already google for known limitations?

Yes, without success :(.

Look at the blue bit in the graph at 5ms .. this is not allowed in LAN .. it mean 1 of 10 pings fails ..

On a WAN with cable or similar, ok, but internally, maybe you should replace the NIC.

This is still just an example host not directly connected to this NIC (there are many devices between this router and host on my graphs) and you should not bother with lost but with latency. And in smokeping light blue means 1 of 20 pings not 10!

No its connected thru bge1 (vlan1), there are also:
bge1: flags=8d43<UP,BROADCAST,RUNNING,PROMISC,OACTIVE,SIMPLEX,MULTICAST> metric 0 mtu 1500
bge1_vlan200: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
bge1_vlan100: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
bge1_vlan99: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
bge1_vlan50: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500

It was example host with some packet loss, I attached another one available thru bge1 without such lost (which are negligible in this problem).

Hello,

one of my routers after upgrade to 20.7 on single (it has 4port network card, problem occurs only on 1 port) broadcom 1000Base-T interfaces has huge latency, it was ~0,5ms, right now it is ~20-25ms. I already changed "VLAN Hardware Filtering" to disable with some success but it was working on 20.1.9_1 like a charm, currently not.

On attached screenshot host monitored thru this interface on 20.1.9_1 and on 20.7 after ~22:00. Please help what else can I tune to drop this latency (hardware checksum offload disabled, hardware TCP segmentation offload disabled, hardware large receive offload disabled and VLAN Hardware Filtering also disabled).

Additional info: this bge1 interface is also used to vlan tags as the only interface in this router.

Why in ipsec.conf dpdaction is always set as clear?

Code Select Expand

  dpdaction = clear

I would like to set it with one of my OPNSense routers to "restart". Is there a chance to implement GUI for that?

Why in ipsec.conf dpdaction is always set as clear?

Code Select Expand

  dpdaction = clear

I would like to set it with one of my OPNSense routers to "restart". Is there a chance to implement GUI for that?

I have OPNSense as router in location where I have 3 different networks:
192.168.1.254 as main LAN addres
10.1.10.254 as virtual ip on the same lan interface
172.28.10.254 as second virtual ip on the same lan interface
and I have reasons to have such config and don't need vlans or even can't do vlans on this network.

I replaced my old Linux router by OPNSense and almost everything is working great but I can't config DHCPv4 service to serve virtual ip networks. For example when I'm trying to add static mapping to 10.1.10.1 address on LAN, I'm getting "The IP address must lie in the LAN subnet." error.

This is insane because this is working on Linux or even windows dhcpd, and I don't see reason to block this on OPNSense. How can I add static mapings to other networks then 192.168.1.0/24?