Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
(ASCEND) DHCP Spoofing/P75 Address Robbing
I sent the following message to one of our VIPs in response to a
problem he was having bringing his laptop computer home from the
office. He has a routing/NAT using/DHCP spoofing P75 at home.
I wondered if anyone else had ever seen this issue...
---
Bob,
I was able to replicate your IP conflict message when taking a laptop
that had been issued an IP address by the LAN based DHCP server and
putting that on the home network with a Pipeline 75. The error
message on my laptop is "The system has detected a conflict for
155.64.36.239 with 00:C0:7B:71:6E:1A".
It turns out that 00:C0:7B:71:6E:1A is the mac address of the
pipeline. I ran show arp on the Pipeline and sure enough - the only
entry was 155.64.36.236 associated with 00:C0:7B:71:6E:1A on ie0. The
Pipeline had appropriated the IP address associated the laptop's nic
(!). After running winipcfg and releasing the address and rebooting
the laptop, everything came up ok (of course we already knew it
would). Unfortunately just clicking "renew" would not work because by
that point Win95 had shut down IP on the ethernet interface.
It looks like a bug with DHCP spoofing on the Pipeline. I upgraded
the code on a Pipeline to the latest version to see if perhaps the
issue had been addressed in the intervening months since we first
rolled out the routed Pipelines. But it was to no avail.
The best advice I can give at this point is to release the IP address
using winipcfg right before shutting down for the day. That should
allow you to get up on the first try when you put the laptop on the
home network. Meanwhile I have alerted Ascend of the bug and I'm
reiterating the point in this message.
++ Ascend Users Mailing List ++
To unsubscribe: send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd: <http://www.nealis.net/ascend/faq>