| 1 |
On Saturday 18 Oct 2014 16:38:52 Alec Ten Harmsel wrote: |
| 2 |
> On 10/18/2014 04:06 AM, Mick wrote: |
| 3 |
|
| 4 |
> > What do the router logs say? |
| 5 |
> |
| 6 |
> DD-WRT is not very informative. It only has system-type stuff in |
| 7 |
> /var/log/messages, nothing LAN-related. |
| 8 |
|
| 9 |
As James suggested, if you have SSH or telnet access to the router run arp to |
| 10 |
see what the arp tables include. Also ping the server from the router to see |
| 11 |
if you get any responses. I expect that these will not reveal anything |
| 12 |
untoward, but it is best to follow a process of elimination a step at a time. |
| 13 |
|
| 14 |
|
| 15 |
> > Have you captured any packets on both ends and in between? |
| 16 |
> |
| 17 |
> Capturing packets on my desktop shows strange behavior. When I ping my |
| 18 |
> server (kwopper), my desktop (greenbeast) starts generating a bunch of |
| 19 |
> ARPs, none of which get answered. |
| 20 |
|
| 21 |
Only to state the obvious, that this is not the expected behaviour. Are you |
| 22 |
sure that the server firewall isn't configured to only allow connections from |
| 23 |
your laptop and/or drop arp packets to avoid arp attacks? What happens when |
| 24 |
you disable the firewall? |
| 25 |
|
| 26 |
|
| 27 |
> When my laptop pings kwopper, the |
| 28 |
> first ARP is answered instantly and the pings succeed. Pinging from |
| 29 |
> kwopper is the same; instantly finds and connects to my laptop, but my |
| 30 |
> desktop does not see any ARPs or ICMPs from kwopper. |
| 31 |
|
| 32 |
Using arpscan and arping between desktop and server you should be able to find |
| 33 |
out what is happening, but I suspect something to do with the server |
| 34 |
configuration. |
| 35 |
|
| 36 |
-- |
| 37 |
Regards, |
| 38 |
Mick |
Archives