Thread: Very strange PXE boot problem with ipconfig

dear all

i'm stuck on building site in snow , need help!

i'm having trouble debugging strange pxe booting problem: comes down behaviour of "ipconfig" inside live cd boot initrd filesystem. know documentation or source file /bin/ipconfig inside initrd.lz on live cd?

it's failing (silent hanging) when have udp broadcasts on network: when disconnect broadcasting item, boots fine. terribly confusing.

file /bin/ipconfig inside /casper/initrd.lz on 10.04.3 desktop livecd iso.

29f52987aad59fbb6c31838695913f73 bin/ipconfig
d169011c359121f3a75085f47ea0e90b /exports/ubuntu-10.04.3-desktop-i386/casper/initrd.lz
f63028da38308d917cd1460e14fb8540 /cdroms/ubuntu-10.04.3-desktop-i386.iso

or pointers or workarounds. i'm suspecting dhcp or similar, not sure @ all.

jonathan

hi

appears klibc utils version of ipconfig.

not sure of versions, main page appears be: http://packages.debian.org//klibc-utils

inside source page, there readme:

code:

bootp/dhcp client klibc ---------------------------  usage:  ipconfig [-c proto] [-d interface] [-i identifier]      [-n] [-p port] [-t timeout] [interface ...]  -c proto    use proto configuration protocol         interfaces, unless overridden specific interfaces. -d interface    either name of interface, or long spec. -i identifier    dhcp vendor class identifier.  default         "linux ipconfig". -n        nothing - print configuration         performed. -p port        send bootp/dhcp broadcasts port, port - 1. -t timeout    give on unconfigured interfaces after timeout secs.  can configure multiple interfaces passing multiple interface specs on command line, or using special interface name "all".  if you're autoconfiguring interfaces, ipconfig wait until either such interfaces have been configured, or timeout passes.  proto can 1 of following, selects autoconfiguration protocol use:  not specified    use protocols (the default) dhcp        use bootp , dhcp bootp        use bootp rarp        use rarp (not supported) none        no autoconfiguration - either static config, or none @  interface spec can either short form, name of interface (eth0 or whatever), or long form.  long form consists of 7 elements, separated colons:  <client-ip>:<server-ip>:<gw-ip>:<netmask>:<hostname>:<device>:<autoconf>    <client-ip>    ip address of client. if empty, address                 either determined rarp/bootp/dhcp. protocol                 used de- pends on <autoconf> parameter. if                 parameter not empty, autoconf used.    <server-ip>   ip address of nfs server. if rarp used                 determine client address , parameter not                 empty replies specified server                 accepted. use different rarp , nfs server,                 specify rarp server here (or leave blank), ,                 specify nfs server in `nfsroot' parameter                 (see above). if entry blank address of                 server used answered rarp/bootp/dhcp                 request.    <gw-ip>       ip address of gateway if server on different                 subnet. if entry empty no gateway used ,                 server assumed on local network, unless                 value has been received bootp/dhcp.    <netmask>     netmask local network interface. if empty,                 netmask derived client ip address assuming                 classful addressing, unless overridden in bootp/dhcp reply.    <hostname>    name of client. if empty, client ip address                 used in ascii notation, or value received                 bootp/dhcp.    <device>      name of network device use. if empty,                 devices used rarp/bootp/dhcp requests, ,                 first 1 receive reply on configured. if                 have 1 device, can safely leave blank.    <autoconf>    method use autoconfiguration. if either                 'rarp', 'bootp', or 'dhcp' specified protocol                 used.  if value 'both', 'all' or empty,                 protocols used.  'off', 'static' or 'none' means                 no autoconfiguration.  ip addresses , netmasks must either absent (defaulting zero) or presented in dotted-quad notation.  interface spec can prefixed either "ip=", "nfsaddrs=", both of ignored.  these (along ugliness of long form) present compatibility in-kernel ipconfig code 2.4 , earlier kernels.  here few examples of valid ipconfig command lines.  enable loopback interface:     ipconfig 127.0.0.1:::::lo:none  try configure eth0 using bootp 30 seconds:     ipconfig -t 30 -c bootp eth0  configure eth0 , eth1 using dhcp or bootp, , eth2 statically:     ipconfig -c eth0 eth1 192.168.1.1:::::eth2:none  --  russell's original readme, , still true:  code in main.c yucky imho.  needs cleaning.  -- russell king (2002/10/22) bryan o'sullivan (2003/04/29)

did experiments , it's dhcp or bootp failing.

i've worked around horribly moment using static configuration

code:

#ipconfig -c bootp ${device} /tmp/net-${device}.conf | tee /netboot.config     ipconfig -c bootp 192.168.1.64:192.168.1.32:255.255.255.0:::${device}:none /tmp/net-${device}.conf | tee /netboot.config

more later when can find solutions.

kind regards,
jonathan

Forum The Ubuntu Forum Community Ubuntu Specialised Support Ubuntu Servers, Cloud and Juju Server Platforms [ubuntu] Very strange PXE boot problem with ipconfig

Ubuntu