| 1 |
On 10/18/2014 04:06 AM, Mick wrote: |
| 2 |
> Can you give some additional information on the network topology? |
| 3 |
> |
| 4 |
> Are we talking about LAN/WAN? Same subnet? VLAN? DMZ? |
| 5 |
|
| 6 |
It's a LAN. Just a simple TP-Link router setup to do DHCP. No VLAN, no |
| 7 |
DMZ, only one subnet 192.168.0.0/24. It's at my apartment, so nothing fancy. |
| 8 |
|
| 9 |
> |
| 10 |
> Any firewall rules or special routing/bridging/etc.? |
| 11 |
|
| 12 |
Firewall is disabled on the server (CentOS) and my desktop. No special |
| 13 |
routing or bridging. |
| 14 |
|
| 15 |
> |
| 16 |
> What do the router logs say? |
| 17 |
|
| 18 |
DD-WRT is not very informative. It only has system-type stuff in |
| 19 |
/var/log/messages, nothing LAN-related. |
| 20 |
|
| 21 |
> |
| 22 |
> Have you captured any packets on both ends and in between? |
| 23 |
> |
| 24 |
> |
| 25 |
> |
| 26 |
|
| 27 |
Capturing packets on my desktop shows strange behavior. When I ping my |
| 28 |
server (kwopper), my desktop (greenbeast) starts generating a bunch of |
| 29 |
ARPs, none of which get answered. When my laptop pings kwopper, the |
| 30 |
first ARP is answered instantly and the pings succeed. Pinging from |
| 31 |
kwopper is the same; instantly finds and connects to my laptop, but my |
| 32 |
desktop does not see any ARPs or ICMPs from kwopper. |
| 33 |
|
| 34 |
I can attach Wireshark dumps if helpful. tcpdump doesn't seem to want to |
| 35 |
work on my server for some reason. |
| 36 |
|
| 37 |
Alec |
Archives