> They are wrong because there is no way for network traffic from the > devices on the LAN to make it to the interface enp2s0. Or, if they do > make it there, then there is something else seriously wrong. >
tcpdump -i enp2s0 arp will tell you if the arps are being generated from something on the wire side. If there's not much traffic then clear the arp entry and ping the IP address to generate traffic. | heimdali ~ # route -n > | Kernel IP Routentabelle > | Ziel Router Genmask Flags Metric Ref Use > Iface > | 0.0.0.0 192.168.75.1 0.0.0.0 UG 4005 0 0 > ppp0 > | 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 > lo > | 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 > br_dmz > | 192.168.3.0 0.0.0.0 255.255.255.0 U 0 0 0 > enp1s0 > | 192.168.3.80 0.0.0.0 255.255.255.255 UH 0 0 0 > enp1s0 > | 192.168.3.81 0.0.0.0 255.255.255.255 UH 0 0 0 > enp1s0 > | 192.168.75.1 0.0.0.0 255.255.255.255 UH 0 0 0 > ppp0 > | heimdali ~ # > `---- > > What it the purpose of the static host routes? The connected 192.168.3.0/24 route will take care of those hosts, so they shouldn't be required. What are enp1s0 and enp2s0 connected to? Same hub or same vlan on the switch? If so they will both see all the layer 2 broadcast traffic from each subnet.
