New FOG setup, TFTP timeout-PXE-E32
-
[quote=“haste347, post: 41989, member: 28447”]
Chain INPUT (policy ACCEPT 714K packets, 82M bytes)
pkts bytes target prot opt in out source destinationChain FORWARD (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destinationChain OUTPUT (policy ACCEPT 27794 packets, 4641K bytes)
pkts bytes target prot opt in out source destination[/quote]No iptables rules loaded and default policies set to ACCEPT. I doubt that a local firewall could be the issue.
-
didn’t see that, i’m guessing it’s a switch issue than
-
[quote=“Junkhacker, post: 42061, member: 21583”]didn’t see that, i’m guessing it’s a switch issue than[/quote]
Possibly along the lines of [url]http://fogproject.org/wiki/index.php/IPXE#What_do_I_enable_and_disable.3F[/url]
-
[quote=“Junkhacker, post: 42057, member: 21583”]have you tried Tom’s suggestion? [CODE]sudo ufw disable[/CODE][/quote]
Yes, disabling the firewall was one of the steps in the config.
I’ve got it connected through an un-managed switch for the “imaging bench” (server resides in the same room for now), which connects to the rest of the network/servers through a layer 3 switch.
I read somewhere that some switches will only pass a file with a “.0” at the end…I am wondering if that might be the case here…Any thoughts on that?
-
that’s one of the reasons Jaymes recommends DNSMASQ, i believe there are instructions on the wiki for that scenario
-
I’ve not heard about switches only passing files matching any sort of pattern (e.g. “*.0”) but you can still give it a try by renaming or linking ‘undionly.kpxe’ to ‘pxelinux.0’ (very common name).
But I have heard about layer 3 switches doing some kind of magic like not forwarding but only relaying DHCP offers…
-
Jaymes can correct me if i’m getting this wrong, but i believe he had a packet capture that showed switches changing the requested file from undionly.kpxe to undionly.0
to fix the issue, he created a symbolic link between the actual file and the requested file
ln -s /tftpboot/undionly.kpxe [FONT=Tahoma]/tftpboot/undionly.0[/FONT] -
[quote=“Junkhacker, post: 42074, member: 21583”]Jaymes can correct me if i’m getting this wrong, but i believe he had a packet capture that showed switches changing the requested file from undionly.kpxe to undionly.0
to fix the issue, he created a symbolic link between the actual file and the requested file
ln -s /tftpboot/undionly.kpxe [FONT=Tahoma]/tftpboot/undionly.0[/FONT][/quote]It is a native function of dnsmasq, not sure why, but it does append the .0 to the file name, not the switches. Just to clarify.
But the resolution was to symlink undionly.kpxe to undionly.0
and it IS part of the installation instructions on the wiki for using DNSMASQ with iPXE.
I have only tried DNSMASQ setup on Novell Netware 6.5 and a simple home network with a linksys router, I don’t have experience in other network environments.
-
ok, so i got the part about the switches changing the requested file name wrong, but i think i remember someone having problems with switches not passing along undionly.kpxe as a boot file name, i suspect because it doesn’t fit within the 8.3 parameters of the old dos days, but undionly.0 or pxelinux.0 do.
-
That was specific the novell dhcp, and a version and below of that.
The thing that sounds most likely that’s happening.
ip-helper is not setup to direct traffic back to the dhcp server to even get the options.
-
[quote=“Tom Elliott, post: 42083, member: 7271”]That was specific the novell dhcp, and a version and below of that.
The thing that sounds most likely that’s happening.
ip-helper is not setup to direct traffic back to the dhcp server to even get the options.[/quote]
To be specific Novell Netware 6.5
The only reason I know all this is because My network is sorely outdated. I had to devise a plan to still be able to use FOG and the new iPXE without altering my network because it will not accept certain values.
Matter of fact, Netware 6.5 has a VERY strict 8 character limit that even applies to groups, and usernames, it’s quite cumbersome.
-
wow, i seem to be getting a lot of details wrong today. maybe i should have taken another day off…
-
Update It was the leftover opt 67 pointing to the incorrect boot file causing the issue I was having after installing DNSMASQ.
Well, I was going through and found that I already had a link from .kpxe to .0, I made sure the permissions were the same on both files…and just for fun I decided to see what happened and I actually just pulled up the FOG menu on the workstation which I just registered.
I am now capturing my first image! I ‘think’ I may have left option 66/67 active in my DHCP server which was causing the issue.
I have been going back and forth between my landesk PXE setup and the FOG setup when a new image was needed.I will test my theory and update.
Thank you all, very much, for your help and suggestions in getting this going!
-
This post is deleted!
