/default.ipxe... Connection timed out | fog_1.0.1 | Ubuntu 14.04 LTS | Winxp32 Vbox Client
-
[quote=“PaganLinuxGeek, post: 42706, member: 2226”]I noticed today that the last line shown on the vbox console has the WRONG ip address. (It’s showing tftp://192.168.1.1/default.ipxe…
Now I’ve set dnsmasq.conf to use .116 What would cause the clients to default to the .1 ip instead? is there another file somewhere that undionly.kpxe is referencing?[/quote]Simple question but, in your install log, you answered no for using FOG as a dhcp server. Have you covered DHCP options 66 & 67, made sure they are correct?
[url]http://fogproject.org/wiki/index.php/FOGUserGuide#DHCP_Settings[/url]
-
the line in the ipxe embeded script that loads default.ipxe is [CODE]chain tftp://${next-server}/default.ipxe[/CODE] i’m not sure how it could both load the undionly.kpxe file and get the location of the default.ipxe file wrong
-
I cannot modify those options in the router my ISP provided. That is why I am using dnsmasq
I tried installing the svn suggested over my existing fog install. The “devel” version I guess shows the server IP…
I’m trying to understand why it’s pulling the router’s IP instead of what dnsmasq is sending…[CODE][root@jezebelle tftp]# cat /etc/dnsmasq.conf
tftp-root=/tftpboot
#enable-tftp
dhcp-option=vendor:PXEClient,6,2b
dhcp-no-override
dhcp-range=192.168.1.107,proxy
#port=0
log-dhcp
dhcp-boot=undionly.kpxe,192.168.1.107
dhcp-option=17,/images
dhcp-option=pxe,66,192.168.1.107
pxe-prompt=“Press F8 for boot menu”, 9
pxe-service=X86PC,“iPXE Boot (Newer for Secure Boots)”, undionly
pxe-service=X86PC,“PXE Boot (Older machines)”, pxelinux
pxe-service=X86PC,“Boot from local hard disk”, 0
#interface=eno1,enp7s0,enp4s0,lo
[/CODE][CODE][root@jezebelle tftp]# ifconfig
eno1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.116 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 fe80::922b:34ff:fed4:e03 prefixlen 64 scopeid 0x20<link>
ether 90:2b:34:d4:0e:03 txqueuelen 1000 (Ethernet)
RX packets 2713 bytes 207258 (202.4 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 40 bytes 9597 (9.3 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 20 memory 0xf7600000-f7620000enp4s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.115 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 fe80::6a05:caff:fe0a:5e3 prefixlen 64 scopeid 0x20<link>
ether 68:05:ca:0a:05:e3 txqueuelen 1000 (Ethernet)
RX packets 2704 bytes 205402 (200.5 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 35 bytes 9194 (8.9 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 16 memory 0xf74c0000-f74e0000enp7s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.107 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 fe80::922b:34ff:fed4:df3 prefixlen 64 scopeid 0x20<link>
ether 90:2b:34:d4:0d:f3 txqueuelen 1000 (Ethernet)
RX packets 441929 bytes 66602075 (63.5 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1299172 bytes 1874321485 (1.7 GiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 18lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 0 (Local Loopback)
RX packets 76552 bytes 1155843438 (1.0 GiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 76552 bytes 1155843438 (1.0 GiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0virbr0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 192.168.122.1 netmask 255.255.255.0 broadcast 192.168.122.255
ether 6e:1a:c0:4e:a2:a6 txqueuelen 0 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
[/CODE] -
If it helps any, this is the router/modem they provided as much as I hate this device I am forced to use it
[url]http://docs.technicolor.com/data/files/cm/DMS-CTC-20130228-0000.pdf[/url] -
As you’re using dnsmasq, have you made a link or copy of the “bootfile” on the /tftpboot as undionly.0
-
Yes I did
undionly.0 -
Just kicking around ideas…
Turn DHCP off for that device you have, and install FOG with DHCP turned on… see what happens…
-
Already considered that. It’s not an option on this device.
I have a raspberry PI running on the home lan that could handle dhcp as it’s always on. -
[quote=“PaganLinuxGeek, post: 42774, member: 2226”]Already considered that. It’s not an option on this device.
I have a raspberry PI running on the home lan that could handle dhcp as it’s always on.[/quote]Install FOG with DHCP anyways, then disconnect from that modem/router thing. Use a cross over cable to connect directly to the target machine.
