On Fri, Jun 7, 2013 at 2:57 AM, Geert Stappers <stappers at stappers.nl> wrote:> Op 2013-06-07 om 09:35 schreef Geert Stappers: > > Op 2013-06-06 om 14:42 schreef H. Peter Anvin: > > > > > > Sounds like it's losing lots of packets. > > > > > > > The tcpdump[1] shows strang HTTP traffic at the end. > > It is TCP to port 80, but that is all. There is no HTTP GET request. > > > > Another surprising thing was that there are many TFTP file transfers. > > I have expect HTTP transfers. > > > > The answers might be in the DHCP OFFER which says "server name > 'dhcp209'", > > but no DHCP option 209. > > > > I would like to see the dhcp server configuration file. >ddns-update-style none; log-facility local7; deny unknown-clients; non-authoritative; option subnet-mask 255.255.255.0; default-lease-time 600; max-lease-time 7200; option ip-forwarding false; # No IP forwarding option mask-supplier false; # Don't respond to ICMP Mask req server-name "dhcp209"; next-server 192.168.0.100; subnet 192.168.0.0 netmask 255.255.255.0 { range 192.168.0.1 192.168.0.88; option routers 192.168.0.100; } host rhelclient { next-server 192.168.0.100; filename "linux-install/lpxelinux.0"; server-name "dhcp209"; hardware ethernet 08:00:27:E7:34:E9; fixed-address 192.168.0.88; } The dhcp server has two network interfaces. Eth0 -public, Eth1-Private. Eth1 is 192.168.0.100 and dhcpd is tied only to Eth1. I just realized the /etc/hosts has dhcp209 pointed to Eth0's IP address. Hope now this is not a major issue. Everything has been always like this on tftp/dhcp server. Thanks.> > > > And I do like to read in the discussion order ( reply below the text ) > > > > > > Oops, [1] is http://rosa.stappers.nl/ff/tcp_w.pcap > > Groeten > Geert Stappers > -- > Leven en laten leven > _______________________________________________ > Syslinux mailing list > Submissions to Syslinux at zytor.com > Unsubscribe or set options at: > http://www.zytor.com/mailman/listinfo/syslinux > Please do not send private replies to mailing list traffic. > >-- upen, emerge -uD life (Upgrade Life with dependencies)
Op 2013-06-07 om 06:18 schreef upen:> On Fri, Jun 7, 2013 at 2:57 AM, Geert Stappers wrote: > > Op 2013-06-07 om 09:35 schreef Geert Stappers: > > > Op 2013-06-06 om 14:42 schreef H. Peter Anvin: > > > > > > The tcpdump[1] shows strang HTTP traffic at the end. > > > It is TCP to port 80, but that is all. There is no HTTP GET request. > > > > > > Another surprising thing was that there are many TFTP file transfers. > > > I have expect HTTP transfers. > > > > > > The answers might be in the DHCP OFFER which says "server name > > 'dhcp209'", > > > but no DHCP option 209. > > > > > > I would like to see the dhcp server configuration file. > > > > ddns-update-style none; > log-facility local7; > deny unknown-clients; > non-authoritative; > option subnet-mask 255.255.255.0; > default-lease-time 600; > max-lease-time 7200; > option ip-forwarding false; # No IP forwarding > option mask-supplier false; # Don't respond to ICMP Mask req > server-name "dhcp209";Acknowledge> next-server 192.168.0.100; > > subnet 192.168.0.0 netmask 255.255.255.0 { > range 192.168.0.1 192.168.0.88; > option routers 192.168.0.100; > } > > host rhelclient { > next-server 192.168.0.100; > filename "linux-install/lpxelinux.0"; > server-name "dhcp209";That seems strange to me ( sorry, right now, I have no time to elaborate my gut feeling about 'server-name "dhcp209"' in "host rhelclient {}" )> hardware ethernet 08:00:27:E7:34:E9; > fixed-address 192.168.0.88; > } > > The dhcp server has two network interfaces. Eth0 -public, Eth1-Private. > Eth1 is 192.168.0.100 and dhcpd is tied only to Eth1. > I just realized the /etc/hosts has dhcp209 pointed to Eth0's IP address. > Hope now this is not a major issue. Everything has been always like this on > tftp/dhcp server.That dhcpd config "works", what is missing is "shift to HTTP". The (speed) advantage of HTTP over TFTP is that HTTP "streams", where TFTP does "go, stop, go, stop, go, stop". What is needed is 'dhcp option 209' See http://www.syslinux.org/wiki/index.php/PXELINUX#Can_I_send_information_to_PXELINUX_via_special_options_in_the_DHCP_response.3F for a clue. Yes, this terse answer is the best I can offer now. Groeten Geert Stappers -- Leven en laten leven
On Fri, Jun 7, 2013 at 9:29 AM, Geert Stappers <stappers at stappers.nl> wrote:> Op 2013-06-07 om 06:18 schreef upen: > > On Fri, Jun 7, 2013 at 2:57 AM, Geert Stappers wrote: > > > Op 2013-06-07 om 09:35 schreef Geert Stappers: > > > > Op 2013-06-06 om 14:42 schreef H. Peter Anvin: > > > > > > > > The tcpdump[1] shows strang HTTP traffic at the end. > > > > It is TCP to port 80, but that is all. There is no HTTP GET request. > > > > > > > > Another surprising thing was that there are many TFTP file transfers. > > > > I have expect HTTP transfers. > > > > > > > > The answers might be in the DHCP OFFER which says "server name > > > 'dhcp209'", > > > > but no DHCP option 209. > > > > > > > > I would like to see the dhcp server configuration file. > > > > > > > ddns-update-style none; > > log-facility local7; > > deny unknown-clients; > > non-authoritative; > > option subnet-mask 255.255.255.0; > > default-lease-time 600; > > max-lease-time 7200; > > option ip-forwarding false; # No IP forwarding > > option mask-supplier false; # Don't respond to ICMP Mask req > > server-name "dhcp209"; > > Acknowledge > > > > next-server 192.168.0.100; > > > > subnet 192.168.0.0 netmask 255.255.255.0 { > > range 192.168.0.1 192.168.0.88; > > option routers 192.168.0.100; > > } > > > > host rhelclient { > > next-server 192.168.0.100; > > filename "linux-install/lpxelinux.0"; > > server-name "dhcp209"; > > That seems strange to me ( sorry, right now, I have no time to elaborate > my gut feeling about 'server-name "dhcp209"' in "host rhelclient {}" ) > > > > hardware ethernet 08:00:27:E7:34:E9; > > fixed-address 192.168.0.88; > > } > > > > The dhcp server has two network interfaces. Eth0 -public, Eth1-Private. > > Eth1 is 192.168.0.100 and dhcpd is tied only to Eth1. > > I just realized the /etc/hosts has dhcp209 pointed to Eth0's IP address. > > Hope now this is not a major issue. Everything has been always like this > on > > tftp/dhcp server. > > That dhcpd config "works", what is missing is "shift to HTTP". > > The (speed) advantage of HTTP over TFTP is that HTTP "streams", > where TFTP does "go, stop, go, stop, go, stop". > > What is needed is 'dhcp option 209' > > See > http://www.syslinux.org/wiki/index.php/PXELINUX#Can_I_send_information_to_PXELINUX_via_special_options_in_the_DHCP_response.3F > for a clue. Yes, this terse answer is the best I can offer now. > >How does this look? #ddns-update-style ad-hoc; ddns-update-style none; log-facility local7; deny unknown-clients; non-authoritative; #option domain-name "example.com"; #option domain-name-servers ns1.example.com; option subnet-mask 255.255.255.0; default-lease-time 600; max-lease-time 7200; #allow bootp; #allow booting; option ip-forwarding false; # No IP forwarding option mask-supplier false; # Don't respond to ICMP Mask req server-name "dhcp209l"; next-server 192.168.0.100; option space pxelinux; option pxelinux.magic code 208 = string; option pxelinux.configfile code 209 = text; option pxelinux.pathprefix code 210 = text; option pxelinux.reboottime code 211 = unsigned integer 32; subnet 192.168.0.0 netmask 255.255.255.0 { range 192.168.0.1 192.168.0.88; option routers 192.168.0.100; } host rhelclient { next-server 192.168.0.100; option pxelinux.configfile "linux-install/pxelinux.cfg/default"; filename "linux-install/lpxelinux.0"; server-name "dhcp209l"; # next-server 216.47.150.91; hardware ethernet 08:00:27:E7:34:E9; fixed-address 192.168.0.88; I was able to stop and start dhcpd fine, with above configuration in dhcpd.conf. I changed server-name to dhcp209l and updated /etc/hosts with new host entry of this name with ip of eth1.> > Groeten > Geert Stappers > -- > Leven en laten leven > _______________________________________________ > Syslinux mailing list > Submissions to Syslinux at zytor.com > Unsubscribe or set options at: > http://www.zytor.com/mailman/listinfo/syslinux > Please do not send private replies to mailing list traffic. > >-- upen, emerge -uD life (Upgrade Life with dependencies)