DHCP static lease for one session on a multboot client?

  • I am running pfsense 1.2.3 and I have a client PC that is a dual boot, Windows 7 and XP professional, while in Win7 I assigned a static IP through the DHCP webgui which uses the MAC address, and all is fine. However when I reboot this PC into XP and run IPCONFIG I see that is has a different IP assigned by the pfsense DHCP server. When I look in the DHCP status I only see the static IP that was assigned to the Win7 session of this client. Everything appears to work fine but how is it that IPCONFIG shows a different IP for the XP session as compared to the static Win7 session as the NIC and its MAC address are the same.  :o How does pfsense handle this? I kind of expected to see the same IP for both sessions!!!

  • Rebel Alliance Developer Netgate

    The DHCP server can't see the OS. It should be the same IP address on both if the MAC address is really the same, and both are set for DHCP.

    Are you sure the XP side isn't set with a static IP?

  • I've actually seen this behavior too, but not specific to pfsense.  Our corporate network has DHCP served by (I think) something microsoft based.  I have an atom compact I use for network tests that dual boots FreeBSD 8.1 and CentOS 5.5.  Same interface, DHCP in both cases, and they get different IP addresses.  Odd, to put it mildly.

    FreeBSD 8.1
    re0: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500
            ether 00:30:18:a3:fd:9f
            inet AAA.BBB.CCC.207 netmask 0xfffffe00 broadcast       
    CentOS 5.5
    eth0      Link encap:Ethernet  HWaddr 00:30:18:A3:FD:9F
              inet addr:AAA.BBB.CCC.205  Bcast:  Mask:  
              UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1</rxcsum,txcsum,vlan_mtu,vlan_hwtagging,vlan_hwcsum,wol_ucas<br></up,broadcast,running,simplex,multicast> 

    One thing I wonder: maybe the two clients are making the requests with different hostnames or something?  Dunno what though…

  • I'll check the XP for a static IP this evening.

Log in to reply