| 1 |
Adam Carter <adamcarter3@×××××.com> writes: |
| 2 |
|
| 3 |
>> They are wrong because there is no way for network traffic from the |
| 4 |
>> devices on the LAN to make it to the interface enp2s0. Or, if they do |
| 5 |
>> make it there, then there is something else seriously wrong. |
| 6 |
>> |
| 7 |
> |
| 8 |
> tcpdump -i enp2s0 arp |
| 9 |
> |
| 10 |
> will tell you if the arps are being generated from something on the wire |
| 11 |
> side. If there's not much traffic then clear the arp entry and ping the IP |
| 12 |
> address to generate traffic. |
| 13 |
|
| 14 |
Yes, I already tried that and didn't get any traffic listed. |
| 15 |
|
| 16 |
> | heimdali ~ # route -n |
| 17 |
>> | Kernel IP Routentabelle |
| 18 |
>> | Ziel Router Genmask Flags Metric Ref Use |
| 19 |
>> Iface |
| 20 |
>> | 0.0.0.0 192.168.75.1 0.0.0.0 UG 4005 0 0 |
| 21 |
>> ppp0 |
| 22 |
>> | 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 |
| 23 |
>> lo |
| 24 |
>> | 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 |
| 25 |
>> br_dmz |
| 26 |
>> | 192.168.3.0 0.0.0.0 255.255.255.0 U 0 0 0 |
| 27 |
>> enp1s0 |
| 28 |
>> | 192.168.3.80 0.0.0.0 255.255.255.255 UH 0 0 0 |
| 29 |
>> enp1s0 |
| 30 |
>> | 192.168.3.81 0.0.0.0 255.255.255.255 UH 0 0 0 |
| 31 |
>> enp1s0 |
| 32 |
>> | 192.168.75.1 0.0.0.0 255.255.255.255 UH 0 0 0 |
| 33 |
>> ppp0 |
| 34 |
>> | heimdali ~ # |
| 35 |
>> `---- |
| 36 |
>> |
| 37 |
>> What it the purpose of the static host routes? The connected |
| 38 |
> 192.168.3.0/24 route will take care of those hosts, so they shouldn't be |
| 39 |
> required. |
| 40 |
|
| 41 |
They shouldn't be needed. I added them manually only to see if it would |
| 42 |
make a difference. |
| 43 |
|
| 44 |
> What are enp1s0 and enp2s0 connected to? Same hub or same vlan on the |
| 45 |
> switch? If so they will both see all the layer 2 broadcast traffic from |
| 46 |
> each subnet. |
| 47 |
|
| 48 |
They are connected to different vlans on the same switch, so they don't |
| 49 |
share the same broadcast domain. The switch shows the mac addresses of |
| 50 |
the phones only in the expected vlan. |
| 51 |
|
| 52 |
|
| 53 |
Even when enp2s0 is not connected to the switch but directly to the wire |
| 54 |
the PPPoE connection comes from, the arp entries are updated. |
| 55 |
|
| 56 |
Having that said, there's one more test I can make: disconnect enp2s0 |
| 57 |
entirely and see if the arp entries still persist. |
| 58 |
|
| 59 |
|
| 60 |
As to the other reply: The firewall is IP based, and what reason and |
| 61 |
what way would any traffic have to go from a device on the LAN to an |
| 62 |
interface that is not connected to the LAN but to the internet, and on a |
| 63 |
different network than the LAN, when all IP traffic from the device to |
| 64 |
the internet is being dropped? |
| 65 |
|
| 66 |
The firewall doesn't know enp2s0 but ppp0. But still, I don't see how |
| 67 |
these arp entries could appear on enp2s0, yet they do. |
| 68 |
|
| 69 |
|
| 70 |
On a side note: I've verified that VOIP quality issues do not come from |
| 71 |
anything on the LAN (by playing music to the phones and making internal |
| 72 |
phone calls) but from the rather poor internet connection. So at least |
| 73 |
the wrong arp entries don't interfere with VOIP. |
Archives