[ietf86-tech] DHCP 10.x.x.x in Tower 2 Wired

[Bjoern A. Zeeb]

Hi,

coming back to my room I got a 10.x.x.x address from DHCP.  Most
likely if I had to guess Hotel stuff, which we need to track down;
it'll be hard to "fix" this without real PVLANs.   I'll see if I can
catch a packet to find at least the tether source;  renewing the least
8 times helped to get a 130.129.12x.xxx address.   This is wired in
Tower 2 btw.   Could of course also be a private gateway in one of the
rooms.


03:03:36.802428 28:37:37:3f:e5:84 > b8:8d:12:07:b1:b0, ethertype IPv4 (0x0800), length 342: (tos 0x10, ttl 128, id 0, offset 0, flags [none], proto UDP (17), length 328)
     10.0.1.1.67 > 10.0.1.84.68: [udp sum ok] BOOTP/DHCP, Reply, length 300, xid 0x7ac94c9d, secs 4, Flags [none] (0x0000)
 	  Your-IP 10.0.1.84
 	  Client-Ethernet-Address b8:8d:12:07:b1:b0
 	  Vendor-rfc1048 Extensions
 	    Magic Cookie 0x63825363
 	    DHCP-Message Option 53, length 1: ACK
 	    Server-ID Option 54, length 4: 10.0.1.1
 	    Lease-Time Option 51, length 4: 86400
 	    Subnet-Mask Option 1, length 4: 255.255.255.0
 	    Default-Gateway Option 3, length 4: 10.0.1.1
 	    Domain-Name-Server Option 6, length 4: 10.0.1.1
 	    END Option 255, length 0
 	    PAD Option 0, length 0, occurs 26


If we can track that ethernet address down to a specific VLAN that might be
helpful.   Just to be specifc, what is 28:37:37:3f:e5:84 or where is it?

the *b1:b0 is my laptop.


/bz

-- 
Bjoern A. Zeeb                                  Charles Haddon Spurgeon:
"Friendship is one of the sweetest joys of life.  Many might have failed
   beneath the bitterness of their trial  had they not found a friend."