[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [lwip-users] ARP Request breaking Telnet traffic
From: |
Pomeroy, Marty |
Subject: |
Re: [lwip-users] ARP Request breaking Telnet traffic |
Date: |
Mon, 24 Jun 2013 09:39:30 -0400 |
>> From your trace I'd say you have the following devices in your
Network:
>> 172.16.1.7 is the lwIP device
>> 172.16.1.34 is your PC
>> 172.16.1.11 a Zyxel device (Router or similar)
Minor correction to above - that the Zyxel device starts on a different
subnet - 172.16.0.11 in Packet 16 and changes to IP 172.16.1.7 in Packet
20.
You have at least three devices claiming IP Address 172.16.1.7:
Packet 13 Src: 02:81:00:01:d4:c1 (02:81:00:01:d4:c1), This is the
original
Packet 17 Src: 02:81:00:01:d5:00 (02:81:00:01:d5:00)
Packet 20 Src: ZyxelCom_09:93:16 (00:23:f8:09:93:16),
Topology questions: do you have multiple routers active, giving out
172.16.1.7 to different devices (been there, done that!)? They may be
separated by switches which perhaps keeps them apart for a while, but
ARPS are passing through? If you completely isolate your test
topography, this problem should go away.
In any case, when duplicate IPs happen, the network becomes hopelessly
confused!
Marty
- [lwip-users] ARP Request breaking Telnet traffic, Daniel Haslimann, 2013/06/24
- Re: [lwip-users] ARP Request breaking Telnet traffic, Ueli Niederer, 2013/06/24
- Re: [lwip-users] ARP Request breaking Telnet traffic, Daniel, 2013/06/24
- Re: [lwip-users] ARP Request breaking Telnet traffic, Daniel, 2013/06/24
- Re: [lwip-users] ARP Request breaking Telnet traffic, Ueli Niederer, 2013/06/24
- Re: [lwip-users] ARP Request breaking Telnet traffic, Daniel, 2013/06/24
- [lwip-users] redefining LWIP_PLATFORM_DIAG(x), Joe Bloggs84, 2013/06/24
- Re: [lwip-users] redefining LWIP_PLATFORM_DIAG(x), Sylvain Rochet, 2013/06/24
- Re: [lwip-users] redefining LWIP_PLATFORM_DIAG(x), address@hidden, 2013/06/24