| 1 |
> They are wrong because there is no way for network traffic from the |
| 2 |
> devices on the LAN to make it to the interface enp2s0. Or, if they do |
| 3 |
> make it there, then there is something else seriously wrong. |
| 4 |
> |
| 5 |
|
| 6 |
tcpdump -i enp2s0 arp |
| 7 |
|
| 8 |
will tell you if the arps are being generated from something on the wire |
| 9 |
side. If there's not much traffic then clear the arp entry and ping the IP |
| 10 |
address to generate traffic. |
| 11 |
|
| 12 |
|
| 13 |
| heimdali ~ # route -n |
| 14 |
> | Kernel IP Routentabelle |
| 15 |
> | Ziel Router Genmask Flags Metric Ref Use |
| 16 |
> Iface |
| 17 |
> | 0.0.0.0 192.168.75.1 0.0.0.0 UG 4005 0 0 |
| 18 |
> ppp0 |
| 19 |
> | 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 |
| 20 |
> lo |
| 21 |
> | 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 |
| 22 |
> br_dmz |
| 23 |
> | 192.168.3.0 0.0.0.0 255.255.255.0 U 0 0 0 |
| 24 |
> enp1s0 |
| 25 |
> | 192.168.3.80 0.0.0.0 255.255.255.255 UH 0 0 0 |
| 26 |
> enp1s0 |
| 27 |
> | 192.168.3.81 0.0.0.0 255.255.255.255 UH 0 0 0 |
| 28 |
> enp1s0 |
| 29 |
> | 192.168.75.1 0.0.0.0 255.255.255.255 UH 0 0 0 |
| 30 |
> ppp0 |
| 31 |
> | heimdali ~ # |
| 32 |
> `---- |
| 33 |
> |
| 34 |
> What it the purpose of the static host routes? The connected |
| 35 |
192.168.3.0/24 route will take care of those hosts, so they shouldn't be |
| 36 |
required. |
| 37 |
|
| 38 |
What are enp1s0 and enp2s0 connected to? Same hub or same vlan on the |
| 39 |
switch? If so they will both see all the layer 2 broadcast traffic from |
| 40 |
each subnet. |
Archives