[ietf86-tech] DHCP issue in tower 2

[Colin Doyle]

Glen with AMS indicated to me this evening that the wired connection in 
room 2040 didn't seem to be working. The following address was being served:

"10.0.1.165 on wired., defaultgw 10.0.1.1"

After some troubleshooting, I got it working with a static at the very 
end of the 130.129.64.0/21 range (not sure what the scope is, but I'll 
check in the morning). I wiresharked the line and discovered the rogue 
DHCP server (see attachments). I'm not certain if this address is from 
the hotel or not, but I'm guessing that since the source is ID'ed as an 
Apple, it is a genuine rogue device.

We can discuss filtering/blocking in the morning. I suspect this will 
continue to be an issue until addressed, but I'm not sure what my reach 
is in this scenario without discussing with the rest of you.

C

(the DHCP file is wireshark output)

-- 



Colin Doyle
Senior Network Engineer
CCNA, F5 ASP/ATSP, Juniper JES

Verilan Event Services, Inc.
7327 SW Barnes Rd. #215
Portland, OR 97225


Cell: 503 810-2129
cdoyle at verilan.com
www.verilan.com


This e-mail contains proprietary information and may be confidential. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution or copying of this message is strictly prohibited. If you received this message in error, please delete it immediately.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screen Shot 2013-03-10 at 11.03.59 PM.png
Type: image/png
Size: 255216 bytes
Desc: not available
Url : http://www.daedelus.com/pipermail/ietf86-tech/attachments/20130310/11ea487b/attachment-0001.png 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: DHCP
Type: application/octet-stream
Size: 992564 bytes
Desc: not available
Url : http://www.daedelus.com/pipermail/ietf86-tech/attachments/20130310/11ea487b/attachment-0001.obj