search for: dhcpoffer

...s. Scenario: ipconfig sends a DHCP_DISCOVER, server A answers with a DHCP_OFFER, server B answers with a DHCP_OFFER, ipconfig sends a DHCP_REQUEST for server A, ipconfig accepts the DHCP_OFFER from server B instead of DHCP_ACK from server A. <== BUG The reason for this was that in dhcp_parse(), DHCPOFFER and DHCPACK returned the same value (=1). So I had to modify the return values, and I thought it would be better to return the constants DHCPOFFER, DHCPACK etc instead of 1,2,3... I tried to keep the changes as minimal as possible. I'm not experienced with the diff program, so please excuse th...

...----------------------------------------------- tail -n1 -f </var/log/syslog | egrep -i "dhcpd|dnsmasq-dhcp" Sep 13 05:11:25 host dhcpd: DHCPDISCOVER from 52:54:00:72:f0:e2 via virbr0 Sep 13 05:11:25 host dhcpd: DHCPDISCOVER from 52:54:00:2a:e0:a6 via virbr1 Sep 13 05:11:26 host dhcpd: DHCPOFFER on 192.168.122.194 to 52:54:00:72:f0:e2 via virbr0 Sep 13 05:11:26 host dhcpd: DHCPOFFER on 192.168.100.107 to 52:54:00:2a:e0:a6 via virbr1 Sep 13 05:11:27 host dhcpd: DHCPREQUEST for 192.168.122.194 (192.168.122.1) from 52:54:00:72:f0:e2 via virbr0 Sep 13 05:11:27 host dhcpd: DHCPACK on 192.168.12...

...tos with xm create -c mynewdomu. Everything seems fine and the installer tries to get an IP. When I look at /var/log/messages in the Dom0 I see the DHCP-requests of the new machine: Sep 26 17:35:53 data-domain0 dhcpd: DHCPDISCOVER from 00:16:3e:aa:bb:dd via eth0 Sep 26 17:35:53 data-domain0 dhcpd: DHCPOFFER on 10.1.0.144 to 00:16:3e:aa:bb:dd via eth0 Sep 26 17:36:03 data-domain0 dhcpd: DHCPDISCOVER from 00:16:3e:aa:bb:dd via eth0 Sep 26 17:36:03 data-domain0 dhcpd: DHCPOFFER on 10.1.0..144 to 00:16:3e:aa:bb:dd via eth0 Sep 26 17:36:12 data-domain0 dhcpd: DHCPDISCOVER from 00:16:3e:aa:bb:dd via eth0 Se...

...perfectly with Parallels for Linux). The directions (from hell): http://www.virtualbox.org/download/UserManual.pdf I am trying to set up a "host interface" network between my XP guest and my Linux host. Three problems: 1) "br0" does not resolve with my DHCP server: "No DHCPOFFERS received" 2) Virtual Box will not start, unless I switch to no network or NAT network 3) eth1 will not communicate with the Internet after restarting the network daemon to try to bet an address for br0 Following the directions on page 62 for Fedora Core in the users manual do not work (...

...200, irq 5, addr 00:16:3E:22:D8:C2 100Mbps half-duplex Searching for server (DHCP)....No IP address .No IP address .No IP address and it is stuck here. dhcp server is working fine for already installed guests (from iso) and when started with -d I get: DHCPDISCOVER from 00:16:3e:22:d8:c2 via dom0 DHCPOFFER on 192.168.1.16 to 00:16:3e:22:d8:c2 via dom0 DHCPDISCOVER from 00:16:3e:22:d8:c2 via dom0 DHCPOFFER on 192.168.1.16 to 00:16:3e:22:d8:c2 via dom0 DHCPDISCOVER from 00:16:3e:22:d8:c2 via dom0 DHCPOFFER on 192.168.1.16 to 00:16:3e:22:d8:c2 via dom0 DHCPDISCOVER from 00:16:3e:22:d8:c2 via dom0 snoop...

...othing is changed the differing result is just achieved by trying another install, as i said its rather random. Any thoughts? thanks ** section of log i see when i have install issue ** Apr 16 14:25:53 cobbler dhcpd: DHCPDISCOVER from 00:0c:29:16:f8:b5 via eth0 Apr 16 14:25:53 cobbler dhcpd: DHCPOFFER on 192.168.12.190 to 00:0c:29:16:f8:b5 via eth0 Apr 16 14:25:53 cobbler dhcpd: DHCPDISCOVER from 00:0c:29:16:f8:b5 via eth0 Apr 16 14:25:53 cobbler dhcpd: DHCPOFFER on 192.168.12.190 to 00:0c:29:16:f8:b5 via eth0 Apr 16 14:25:53 cobbler dhcpd: DHCPREQUEST for 192.168.12.212 (192.168.12.117) from...

...3) Reboot the node - PXE boot fails for all next attempts. We see that a server gets DHCP requests and answers them, but a node doesn't response with DHCP ack. The typical DHCP log is: Jan 5 09:14:34 shoffner dhcpd: DHCPDISCOVER from 00:30:48:7e:24:a6 via eth1 Jan 5 09:14:34 shoffner dhcpd: DHCPOFFER on 10.1.5.2 to 00:30:48:7e:24:a6 via eth1 Jan 5 09:14:36 shoffner dhcpd: DHCPDISCOVER from 00:30:48:7e:24:a6 via eth1 Jan 5 09:14:36 shoffner dhcpd: DHCPOFFER on 10.1.5.2 to 00:30:48:7e:24:a6 via eth1 Jan 5 09:14:40 shoffner dhcpd: DHCPDISCOVER from 00:30:48:7e:24:a6 via eth1 Jan 5 09:14:40 s...

...red. <snip/> > > Guess what the filter setting was? ;) > > > > tcpdump -ni eth0.230 -s0 -w hp380g9_efi_pxe.pcap ether src c4:34:6b:b7:1b:cc or ether dst c4:34:6b:b7:1b:cc > > > > So the DHCPACK packet should have been captured... But it wasn't, neither the DHCPOFFER ... > The following has a simplification and then a specialized filter to > grab BOOTP/DHCP frames with the MAC in question. > > (ether host c4:34:6b:b7:1b:cc) or ( ( udp port 67 or udp port 68) and (udp[36:4] = 0xc4346bb7 ) and (udp[40:2] = 0x1bcc)) > > Beyond this, it feel...

...en I try to start the diskless machine (Intel Undi, PXE-2.0 build 082), it says "DHCP....". Then it says: PXE023: No boot device received. On the server, I get the following messages: Sep 24 15:51:35 master dhcpd: DHCPDISCOVER from 00:0c:76:e7:7b:e2 via eth1 Sep 24 15:51:36 master dhcpd: DHCPOFFER on 10.0.0.150 to 00:0c:76:e7:7b:e2 via eth1 Sep 24 15:51:37 master dhcpd: DHCPDISCOVER from 00:0c:76:e7:7b:e2 via eth1 Sep 24 15:51:37 master dhcpd: DHCPOFFER on 10.0.0.150 to 00:0c:76:e7:7b:e2 via eth1 Sep 24 15:51:41 master dhcpd: DHCPDISCOVER from 00:0c:76:e7:7b:e2 via eth1 Sep 24 15:51:41 maste...

...HDD video recorder CoCoon. The client not return client host name. In this case, dhcpd server assumed the client host name is (none). Therefor dhcpd output log described below. > Jan 7 10:49:24 on-o dhcpd: DHCPDISCOVER from 08:00:46:33:55:77 ((none)) via eth0 > Jan 7 10:49:25 on-o dhcpd: DHCPOFFER on 192.168.1.4 to 08:00:46:33:55:77 ((none)) via eth0 > Jan 7 10:49:25 on-o dhcpd: DHCPREQUEST for 192.168.1.4 (192.168.1.1) from 08:00:46:33:55:77 ((none)) via eth0 > Jan 7 10:49:25 on-o dhcpd: DHCPACK on 192.168.1.4 to 08:00:46:33:55:77 ((none)) via eth0 But /etc/ignore.d.server/dhcp fil...

...>>> Guess what the filter setting was? ;) >>> >>> tcpdump -ni eth0.230 -s0 -w hp380g9_efi_pxe.pcap ether src c4:34:6b:b7:1b:cc or ether dst c4:34:6b:b7:1b:cc >>> >>> So the DHCPACK packet should have been captured... > But it wasn't, neither the DHCPOFFER ... > > > >> The following has a simplification and then a specialized filter to >> grab BOOTP/DHCP frames with the MAC in question. >> >> (ether host c4:34:6b:b7:1b:cc) or ( ( udp port 67 or udp port 68) and (udp[36:4] = 0xc4346bb7 ) and (udp[40:2] = 0x1bcc)) >...

...P information for eth0... Determining host name and domain... Sending request for IP information for eth0... Determining host name and domain... And there it hangs. On the 6.3 host: Feb 8 08:28:55 penfold dhcpd: DHCPDISCOVER from 52:54:00:5a:a7:48 via br0 Feb 8 08:28:56 penfold dhcpd: DHCPOFFER on 10.0.0.205 to 52:54:00:5a:a7:48 via br0 Feb 8 08:28:56 penfold dhcpd: DHCPREQUEST for 10.0.0.205 (10.0.0.134) from 52:54:00:5a:a7:48 via br0 Feb 8 08:28:56 penfold dhcpd: DHCPACK on 10.0.0.205 to 52:54:00:5a:a7:48 via br0 Feb 8 08:28:56 penfold dhcpd: DHCPDISCOVER from 52:54:00:5a:a7:48...

...) with bind_dlz on bind 9.9.10 (from source too). My OS is Debian Jessie x64 8.8 netinst. I use https://wiki.samba.org/index.php/Configure_DHCP_to_update_DNS_records_with_BIND9 article for dynamic dhcp updates on dns zones. DHCP is working but dns updates not: i have this messages on my syslog then dhcpoffer: May 17 14:24:35 ad1 dhcpd: DHCPRELEASE of 10.10.1.0 from ea:d6:54:12:48:54 (test-pc) via eth0 (found) May 17 14:25:17 ad1 dhcpd: DHCPDISCOVER from ea:d6:54:12:48:54 via eth0 May 17 14:25:18 ad1 dhcpd: DHCPOFFER on 10.10.1.0 to ea:d6:54:12:48:54 (test-pc) via eth0 May 17 14:25:18 ad1 dhcpd: Commi...

...le to configure the address via DHCP. > > The last message is: > IP-Config: eth0 hardware address d4:85:64:5e:c0:f8 mtu 1500 DHCP RARP > > On my DHCP server (dhcp3-server 3.1.1-6+lenny4) logs I see in loop > > dhcpd: DHCPDISCOVER from d4:85:64:5e:c0:f8 via eth1 > dhcpd: DHCPOFFER on 10.150.15.172 to d4:85:64:5e:c0:f8 via eth1 > dhcpd: DHCPDISCOVER from d4:85:64:5e:c0:f8 via eth1 > dhcpd: DHCPOFFER on 10.150.15.172 to d4:85:64:5e:c0:f8 via eth1 > dhcpd: DHCPDISCOVER from d4:85:64:5e:c0:f8 via eth1 > dhcpd: DHCPOFFER on 10.150.15.172 to d4:85:64:5e:c0:f8 via e...

...here is the problem, ipconfig accepts any offered addresses, even those that don't have the filename option. So the clients may get their ip from the wrong dhcp server (e.g. the adsl router) and fail to boot. What I'm asking for is a command line option, that forces ipconfig to ignore all DHCPOFFERs that do not have a filename option, so that it only accepts ip addresses from ltsp servers. Kind regards, Alkis Georgopoulos IP-Config: eth0 complete (from 128.131.48.127): address: 128.131.48.177 broadcast: 128.131.48.255 netmask: 255.255.255.0 gateway: 128.131.48.1 dns0 : 128.130...

...rver kernel: device eth1 entered promiscuous mode Aug 16 16:26:42 pxeserver kernel: device eth1 left promiscuous mode Aug 16 16:26:47 pxeserver kernel: device eth1 entered promiscuous mode Aug 16 16:27:10 pxeserver dhcpd: DHCPDISCOVER from 00:02:b3:15:5b:3b via eth1 Aug 16 16:27:10 pxeserver dhcpd: DHCPOFFER on 192.168.2.21 to 00:02:b3:15:5b:3b via eth1 Aug 16 16:27:11 pxeserver dhcpd: DHCPDISCOVER from 00:02:b3:15:5b:3b via eth1 Aug 16 16:27:11 pxeserver dhcpd: DHCPOFFER on 192.168.2.21 to 00:02:b3:15:5b:3b via eth1 Aug 16 16:27:13 pxeserver dhcpd: DHCPDISCOVER from 00:02:b3:15:5b:3b via eth1 Aug 16 1...

...92.168.100.139 --dhcp-leasefile=/var/lib/libvirt/dnsmasq/vlan2.leases --dhcp-lease-max=11 --dhcp-no-override --log-queries --log-facilities=/path_to_my_file/my_file tailf /path_to_my_file/my_file obtaining the following output: dnsmasq-dhcp[]: DHCPDISCOVER(port2) 52:94:00:02:a7:1e dnsmasq-dhcp[]: DHCPOFFER(port2) 192.168.100.129 52:94:00:02:a7:1e ... dnsmasq-dhcp[]: DHCPDISCOVER(port2) 52:94:00:02:a7:1e dnsmasq-dhcp[]: DHCPOFFER(port2) 192.168.100.129 52:94:00:02:a7:1e ... Now I have a different problem: none DHCP Offer is sent by port2. Do someone know why does it happen and what to do about it? T...

...ennet0 to 255.255.255.255 port 67 interval 11 DHCPDISCOVER on xennet0 to 255.255.255.255 port 67 interval 14 DHCPDISCOVER on xennet0 to 255.255.255.255 port 67 interval 10 DHCPDISCOVER on xennet0 to 255.255.255.255 port 67 interval 13 DHCPDISCOVER on xennet0 to 255.255.255.255 port 67 interval 4 No DHCPOFFERS received. No working leases in persistent database - sleeping. # # ifconfig xennet0 10.42.42.227 # ifconfig xennet0 10.42.42.227 255.255.255.0 # route add default 10.42.42.1 add net default: gateway 10.42.42.1 # ping 10.42.42.1 PING 10.42.42.1 (10.42.42.1): 56 data bytes ^C ----10.42.42.1 PING Sta...

...fig/dhcp_proto.c index d4f2c09..82cd1ed 100644 --- a/usr/kinit/ipconfig/dhcp_proto.c +++ b/usr/kinit/ipconfig/dhcp_proto.c @@ -72,7 +72,7 @@ static struct iovec dhcp_request_iov[] = { /* * Parse a DHCP response packet * Returns: - * 0 = Not handled + * 0 = Unexpected packet, not parsed * 2 = DHCPOFFER (from dhcp_proto.h) * 5 = DHCPACK * 6 = DHCPNACK @@ -128,8 +128,8 @@ static int dhcp_parse(struct netdev *dev, struct bootp_hdr *hdr, /* * Receive and parse a DHCP packet * Returns: - *-1 = Error in packet_recv - * 0 = Not handled + *-1 = Error in packet_recv, try again later + * 0 = Unexp...

Dear Centos-Virt: This is actually a second request for help on the same issue. I finally got to try what several months ago was replayed to me and no joy was to be had. I am afraid the original thread got stale and also had extra, unnecessary data in it. Guest=XP Pro, SP2 Host=CentOS5; # uname -r; 2.6.18-8.1.15.el5 VirtualBox-1.5.0_24069_rhel5-2.i586.rpm