Re: My DHCP Discover do not have Option12 Host Name set ?

From: TreeBoy (debian-user_at_petethetree.co.uk)
Date: 04/20/05

  • Next message: stephanepechard: "Re: nvidia 7174 glx troubles help" 
    To: debian-user@lists.debian.org
Date: Wed, 20 Apr 2005 11:21:23 +0100

    On Wednesday 20 Apr 2005 10:13, Jean-Louis Crouzet wrote:
    > Hi all,
    >
    > any one could shed some light here thanks in advance. I'm trying to
    > understand why my SMC Barricade DHCP Client Log never see my Debian's
    > Machine name but XP ones...
    >
    > Using customized Kernel 2.6.8-15 machine on a LAN behind a SMC Barricade
    > 74004WBRA , during startup I compared the DHCP sequences content and
    > find out that Option 12: Host Name = "Always set up with XP" but not
    > with Debian!
    >
    > I think that I might have a DHCP issue as I compared the two DHCP
    > sequences (one with XP from scratch and one with Debian under same
    > conditions, scratch meant Power ON and Boot)
    >
    > On XP side just for DHCP the first attempt is the Request with Option
    > 12: Host Name = "Already set up with XP". See details hereafter
    > extracted from Ethereal Capture
    >
    > Bootstrap Protocol
    > Message type: Boot Request (1)
    > Hardware type: Ethernet
    > Hardware address length: 6
    > Hops: 0
    > Transaction ID: 0x04cba1a1
    > Seconds elapsed: 0
    > Bootp flags: 0x0000 (Unicast)
    > 0... .... .... .... = Broadcast flag: Unicast
    > .000 0000 0000 0000 = Reserved flags: 0x0000
    > Client IP address: 0.0.0.0 (0.0.0.0)
    > Your (client) IP address: 0.0.0.0 (0.0.0.0)
    > Next server IP address: 0.0.0.0 (0.0.0.0)
    > Relay agent IP address: 0.0.0.0 (0.0.0.0)
    > Client MAC address: 00:50:70:a4:0c:8a (Chaintec_a4:0c:8a)
    > Server host name not given
    > Boot file name not given
    > Magic cookie: (OK)
    > Option 53: DHCP Message Type = DHCP Discover
    > Option 116: DHCP Auto-Configuration (1 bytes)
    > Option 61: Client identifier
    > Hardware type: Ethernet
    > Client MAC address: 00:50:70:a4:0c:8a (Chaintec_a4:0c:8a)
    > Option 12: Host Name = "Melodie_Nelson"
    > Option 60: Vendor class identifier = "MSFT 5.0"
    > Option 55: Parameter Request List
    > 1 = Subnet Mask
    > 15 = Domain Name
    > 3 = Router
    > 6 = Domain Name Server
    > 44 = NetBIOS over TCP/IP Name Server
    > 46 = NetBIOS over TCP/IP Node Type
    > 47 = NetBIOS over TCP/IP Scope
    > 31 = Perform Router Discover
    > 33 = Static Route
    > Unknown Option Code: 249
    > 43 = Vendor-Specific Information
    > End Option
    > Padding
    >
    > While with Debian this option 12 is empty, see herafter:
    >
    > Bootstrap Protocol
    > Message type: Boot Request (1)
    > Hardware type: Ethernet
    > Hardware address length: 6
    > Hops: 0
    > Transaction ID: 0xc86e1461
    > Seconds elapsed: 0
    > Bootp flags: 0x0000 (Unicast)
    > 0... .... .... .... = Broadcast flag: Unicast
    > .000 0000 0000 0000 = Reserved flags: 0x0000
    > Client IP address: 0.0.0.0 (0.0.0.0)
    > Your (client) IP address: 0.0.0.0 (0.0.0.0)
    > Next server IP address: 0.0.0.0 (0.0.0.0)
    > Relay agent IP address: 0.0.0.0 (0.0.0.0)
    > Client MAC address: 00:80:c7:11:94:e3 (Xircom_11:94:e3)
    > Server host name not given
    > Boot file name not given
    > Magic cookie: (OK)
    > Option 53: DHCP Message Type = DHCP Discover
    > Option 55: Parameter Request List
    > 1 = Subnet Mask
    > 28 = Broadcast Address
    > 2 = Time Offset
    > 3 = Router
    > 15 = Domain Name
    > 6 = Domain Name Server
    > 12 = Host Name
    >
    > So within my SMC Barricade DHCP Client Log I never see my Debian's
    > Machine name...
    >
    > Any advise?
    >
    > JL

    (Oops - forgot to reply to mailing list!)
    Hi there.

    Have you set your host name in /etc/dhclient.conf ?

    Uncomment the "send host-name" line (the first real line) and set your host
    name there.

    The reason it is not sent is because more secure DHCP servers specify your
    host name based on your machine's hardware network address (otherwise known
    as your MAC address).

    Regards,
    TreeBoy 

    -- 
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
  • Next message: stephanepechard: "Re: nvidia 7174 glx troubles help"

    Relevant Pages

    • Broadband - strange error message
      ... Just got broadbanded with my Iyonix and all seems to be working ok, ... A choice of floppy boot, ... and 'use DHCP' I also have it configured to give out DHCP addresses ... Under Host names: ...
      (comp.sys.acorn.networking)
    • Re: Working on howl port
      ... software needs to work as if it has no control over network allocation, ... the host does not have knowledge of what IPv4 Link- ... these modifications reduce the reliability of the DHCP service. ... is not sufficient reason to unconfigure a valid DHCP ...
      (freebsd-net)
    • DHCP and network Boot floppy IP problems
      ... I have sniffed the subnet while trying to receive a DHCP address with each ... I have a boot floppy that I used for about 6 weeks quite heavily during ... Last week we switched our subnets DHCP server from the NT domain (Windows ...
      (microsoft.public.windows.server.networking)
    • Re: booting a sun diskless, remotely?
      ... > know we had a helper on the IOS side for at least one or two protocols. ... across n subnets by just specifying some IP addresses in the boot command? ... It does PXE stuff which is basically DHCP + TFTP. ... > The hardest part of it all was to set up the DHCP server with the ...
      (comp.unix.solaris)
    • Re: wireless network works in suse 10, but not suse 10.1
      ... I have a Dell Inspiron 8600 laptop and with suse 10, ... Suse 10.1 finds the hardware correctly (both ... because I'm only interested in getting my wireless ... IP address assigned using DHCP ...
      (alt.os.linux.suse)