search for: dhcpdiscover

...akes ages untill a VM can catch the PXE parameters. Note this output upon starting two VMs on two different subnets: ----------------------------------------------------------------------------- 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...

...nt xennet0 Internet Systems Consortium DHCP Client V3.0.3 Copyright 2004-2005 Internet Systems Consortium. All rights reserved. For info, please visit http://www.isc.org/products/DHCP Listening on BPF/xennet0/00:16:3e:77:91:30 Sending on BPF/xennet0/00:16:3e:77:91:30 Sending on Socket/fallback DHCPDISCOVER on xennet0 to 255.255.255.255 port 67 interval 4 DHCPDISCOVER on xennet0 to 255.255.255.255 port 67 interval 5 DHCPDISCOVER on xennet0 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...

...e. BIND also listens on eth0 to serve other machines. I start the install of centos 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 2...

...ere any problems with the if_re ? After upgrade RELENG_7 on my laptop NIC stopped to work:( uname -a: FreeBSD notebook.minsk.domain 7.2-PRERELEASE FreeBSD 7.2-PRERELEASE #3: Fri Apr 10 20:38:55 EEST 2009 root@notebook.minsk.domain:/usr/obj/usr/src/sys/tiger-asus-a6m i386 notebook# dhclient re0 DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 3 DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 8 DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 12 DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 7 DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 9 DHCPDISCOVER on re0 t...

...79ac84c6 Author: Mathieu Trudel-Lapierre <mathieu.trudel-lapierre at canonical.com> AuthorDate: Tue, 24 Jan 2017 10:05:12 -0500 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Wed, 2 Jan 2019 03:08:04 +0000 [klibc] ipconfig: Set broadcast when sending DHCPREQUEST and DHCPDISCOVER We need to do this, since our devices are probably not configured yet and there may be more than one device we're trying to do DHCP on on the same network. Otherwise, things might be dropped. Patch is originally from here: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1327412/comments/...

...off for TX and off for RX [ 19.978880] localhost kernel: tg3 0000:0b:00.0 eno1: EEE is disabled [ 19.980693] localhost kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eno1: link becomes ready [ 19.829468] localhost dracut-initqueue[992]: dhcp: PREINIT eno1 up [ 19.853734] localhost dhclient[1393]: DHCPDISCOVER on eno1 to 255.255.255.255 port 67 interval 6 (xid=0x4df19201) [ 26.030151] localhost dhclient[1393]: DHCPDISCOVER on eno1 to 255.255.255.255 port 67 interval 13 (xid=0x4df19201) [ 26.033472] localhost dhclient[1393]: DHCPREQUEST on eno1 to 255.255.255.255 port 67 (xid=0x4df19201) [ 26.033...

...nsole I can see: [...] [rtl8139] - ioaddr 0XC200, 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 DHCPDISCO...

...1:52:53 CentOS systemd: Reached target Network. Jun 4 01:52:53 CentOS dhclient[1140]: DHCPREQUEST on enp0s3 to 255.255.255.255 port 67 (xid=0x623c8c73) Jun 4 01:52:59 CentOS dhclient[1140]: DHCPREQUEST on enp0s3 to 255.255.255.255 port 67 (xid=0x623c8c73) Jun 4 01:53:06 CentOS dhclient[1140]: DHCPDISCOVER on enp0s3 to 255.255.255.255 port 67 interval 7 (xid=0x28b9690d) Jun 4 01:53:13 CentOS dhclient[1140]: DHCPDISCOVER on enp0s3 to 255.255.255.255 port 67 interval 17 (xid=0x28b9690d) Jun 4 01:53:24 CentOS NetworkManager[689]: <info> (enp0s3): Activation: Stage 4 of 5 (IPv6 Configure Timeou...

...GATEWAY=192.168.255.10 IPV6ADDR= IPV6PREFIX= ONBOOT=yes USERCTL=yes IPV6INIT=no PEERDNS=no BRIDGE=br0 4)# sudo /sbin/service network restart br0 failed: FAILED, unable to resolve IP address. From my /var/log/messages: dhcpd: DHCPOFFER on 192.168.255.198 to 00:30:48:78:8e:92 via eth0 dhclient: DHCPDISCOVER on br0 to 255.255.255.255 port 67 interval 7 DHCPDISCOVER from 00:30:48:78:8e:92 via eth0 dhcpd: DHCPOFFER on 192.168.255.198 to 00:30:48:78:8e:92 via eth0 dhclient: No DHCPOFFERS received. 5) #sudo VBoxAddIF vbox0 todd br0 Note: also tried it with user=root (did a VBoxDeleteIF first): no symptom...

I have the box dual booting SNV85 Dom0 and F8 Dom0. Both Dom0s utilize same ethernet interface for connection to ADSL Modem acting as DHCP Bridge (ZyXEL P660RT2). Both Dom0s obtain IP adress from ISP at boot up with no problems. 1. When i install SNV85 DomU at F8 Dom0 ( vif=['' '']) with DHCP option it gets IP adress from ISP in 1-2 min 2. When i virt-install SNV85 DomU at

...he IP being offered is sometimes 'wrong'. In the 2 examples below nothing 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:2...

...nd initrd - fine. 2) Start up the node using PXE for the first time - fine. 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 shof...

...: send_packet: Network is down Mar 9 09:03:21 localhost dhclient: receive_packet failed on eth1: Network is down Mar 9 09:03:25 localhost dhclient: DHCPREQUEST on eth1 to 255.255.255.255 port 67 Mar 9 09:03:25 localhost dhclient: send_packet: Network is down Mar 9 09:03:32 localhost dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 5 Mar 9 09:03:32 localhost dhclient: send_packet: Network is down Mar 9 09:03:37 localhost dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 10 Mar 9 09:03:37 localhost dhclient: send_packet: Network is down Mar 9 09:03:47 localhost...

...s can expire during suspend and maybe this situation is not implemented in the winbins code. I don't know if winbind "officially" support suspending. Currently I have written a systemd hook that kill winbind before suspend and restarting it after. 2) The problem appear also on "DHCPDISCOVER". I don't know why but DHCPDISCOVER make winbind react. Just after winbind try to update the "DC" list. I don't understand how winbind know what dhclient do. Maybe a bug in dhclient that close a winbind's opened socket ? But just after after DHCPDISCOVER, winbind lost n...

...RX > [ 19.978880] localhost kernel: tg3 0000:0b:00.0 eno1: EEE is disabled > [ 19.980693] localhost kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eno1: > link becomes ready > [ 19.829468] localhost dracut-initqueue[992]: dhcp: PREINIT eno1 up > [ 19.853734] localhost dhclient[1393]: DHCPDISCOVER on eno1 to > 255.255.255.255 port 67 interval 6 (xid=0x4df19201) > [ 26.030151] localhost dhclient[1393]: DHCPDISCOVER on eno1 to > 255.255.255.255 port 67 interval 13 (xid=0x4df19201) > [ 26.033472] localhost dhclient[1393]: DHCPREQUEST on eno1 to > 255.255.255.255 port 67 (xid=...

The free DHCP solution, ISC, seems to be having scaling issues (i.e. handling only about 200 DHCPDISCOVER and 20 DHCPRENEW requests), and I was wondering if anyone had any open source suggestions of solutions that could scale much better? (Ideally, I could find a free version of a solution like Nominum, but I know that's asking for much.) Anyone have any suggestions? -- Also on LinkedIn?? Feel...

...P: device wlan0 state changed normal exit -> preinit Jul 27 19:31:38 smurf3 dhclient: Listening on LPF/wlan0/c4:17:fe:bb:6a:df Jul 27 19:31:38 smurf3 dhclient: Sending on LPF/wlan0/c4:17:fe:bb:6a:df Jul 27 19:31:38 smurf3 dhclient: Sending on Socket/fallback Jul 27 19:31:38 smurf3 dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4 Jul 27 19:31:42 smurf3 dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11 Jul 27 19:31:53 smurf3 dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14 Jul 27 19:32:07 smurf3 dhclient: DHCPDISCOVER on wlan0 to 25...

...00 qdisc pfifo_fast state UP group default qlen 1000 link/ether 00:0c:29:79:d4:f2 brd ff:ff:ff:ff:ff:ff inet 192.168.1.254/24 brd 192.168.1.255 scope global eth2 valid_lft forever preferred_lft forever I also found this in the /var/log/system.log of the Sophos VM: 2015:08:29-12:04:05 sop dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 6 2015:08:29-12:04:11 sop dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 13 2015:08:29-12:04:24 sop dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 2 2015:08:29-12:04:26 sop dhclient: No DHCPOFFERS received. I have...

...>> link/ether 00:0c:29:79:d4:f2 brd ff:ff:ff:ff:ff:ff >> inet 192.168.1.254/24 brd 192.168.1.255 scope global eth2 >> valid_lft forever preferred_lft forever >> >> I also found this in the /var/log/system.log of the Sophos VM: >> 2015:08:29-12:04:05 sop dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 >> port 67 interval 6 >> 2015:08:29-12:04:11 sop dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 >> port 67 interval 13 >> 2015:08:29-12:04:24 sop dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 >> port 67 interval 2 >> 2015:08:29-1...

...ng to enable my dhcpd and pxelinux setup to use a specific config file for a booting client. I have read the pxelinux page for this (http://syslinux.zytor.com/pxe.php#special) but still seem to be encountering problems. When running the dhcpd with the '-d' debug option the daemon sees the DHCPDISCOVER from the client and then core dumps. On the client side the DHCPDISCOVER simply fails. <------------------------- DHCPDISCOVER from 00:0d:60:83:55:76 via qfe1 Segmentation Fault (core dumped) -------------------------> Without the changes advised on the aforementioned pxeli...