And you still can’t ‘tftp’ from your clients to the server?!

Dozens of different monitoring solutions für linux systems exist. Here are just a few (lightweight) suggestions: munin, cacti, mrtg… Is that what you are looking for?

Yes, those two options should suite you. Really wired, why should tftp(-client) need sudo??

See if your TFTP server ist running an listening on the correct address:
[CODE]# netstat -antup | grep tftp
udp 0 0 0.0.0.0:69 0.0.0.0:* 10149/in.tftpd[/CODE]
Check iptables firewall rules:
[CODE]# iptables -L -n -v
Chain INPUT (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination

Chain OUTPUT (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination[/CODE]
Here you see three chains. Pay close attention to INPUT and OUTPUT. ‘policy’ should be ‘ACCEPT’ and no rules defined (as you see in the output here) unless you really know how to configure linux firewall.

solved, I suppose

AFAIK it’s …mac=12:34:56:78:90:ab (colons and lowercase letters). Please correct me if I am wrong!

I am not sure if I get your setup right. Is the draytek router also setup to offer TFTP or just DHCP pointing to FOG as next-server? Which commands do you use to test TFTP???

You seem to have more than one network adapter… This is the one you propably want to make work (the second one is a wireless adapter):
[CODE]PCI 01:00.0 (1969:1062) has driver “undipci”
PCI 01:00.0 has mem 90500000 io 1000 irq 7
UNDI 0xdbb04 loading UNDI ROM 0xdbb84 to CS 964b DS 9165 for PCI 01:00.0[/CODE]
Trying to find other people having used iPXE with 1969:1062 network card didn’t show up a lot of results when searching on the web. There is just an old post from 2011: [url]http://lists.ipxe.org/pipermail/ipxe-devel/2011-November/001024.html[/url] (see the ID there and read up a couple of post before that)…

iPXE mailinglist is definitely the better place to find out about this! Would be great if you’d report back on how things turned out…

Or try Toms great tutorial on building iPXE from source and add debugging: [url]http://fogproject.org/forum/threads/build-ipxe-from-source.10152/[/url]

[CODE]make … DEBUG=dhcp,tftp,http[/CODE]

AFAIK ‘TFTP Aborted’ here just means that the client tricks the server to aquire the file size before requesting the whole file. Do you see any more TFTP traffic after this (maybe leave it for a few minutes)??

By the way, 59 is the size of the packet and NOT the error code!

For a more detailed explanation see here: [url]http://www.vercot.com/~serva/an/WindowsPXE1.html[/url] (8.7- Troubleshooting TFTP issues.)

Which version of FOG do you use?? It’s probably a good idea to use the same kernel version to match that of init_32.xz provided by FOG.
[CODE]file /var/www/fog/service/ipxe/bzImage32
… Linux kernel … version 3.15.6 …[/CODE]
This is for FOG 1.2.0 on our production server. So I would download linux-3.15.6.tar.xz… What is your version and which kernel source did you use?

From the packet dump I can see that the TFTP/FOG server receives the clients request for the file undionly.kpxe and answers back with option acknowledgement (see here for details about this: [url]https://tools.ietf.org/html/rfc2347[/url]). Normally the client is supposed to send another request then! My guess is that the server answer does not make it to the client. Can you connect a hub just in front of the client and capture packets there??

And please check out this troubleshoting guide too: [URL=‘http://www.fogproject.org/wiki/index.php/Tftp_timeout…’]http://www.fogproject.org/wiki/index.php/Tftp_timeout[/URL]

Looks promising. Seams like the client sends a request to get undionly.kpxe from the TFTP server and the server also responds (second packet). To see this clearly you should get a full packet dump. Maybe try this:
[CODE]tcpdump -i eth0 -w /tmp/tftp-debug.pcap[/CODE]
You won’t see any packets on the console then. Run the command, start your client and stop tcpdump with Ctrl-C after your client got the timeout. ZIP and upload that pcap file and I’ll have a look and see what I can see…

Do you use Windows TFTP server? Checkout this post here: [url]http://forum.ipxe.org/showthread.php?tid=7417[/url]

You’d see the difference, I am sure! The output from boot.php is only 4-5 lines if that particular client is scheduled with a task BUT is much longer if there is no task (and therefore shows the menu).

Are you sure that you are scheduling that task for the same machine that you try to access the URL from?? Maybe MAC address was changed or something like that. Please double check the clients MAC address and compare it with the one being configured for that particular client in the webinterface…

Tom reverted the whole repository back to 2996 just a few days ago as he couldn’t get to a satisfying end tracking down the performace issue. I think you’re pretty alright with 2996 at the moment!

Maybe try a different switch?!

Not wireshark but you can use tcpdump for that. For simple debugging use this:
[CODE]tcpdump -i eth0 -nn udp[/CODE]
‘udp’ is just a very simple filter so that you don’t see to much other traffic…
If you want to dig into the packet dump you’re better of writing the captured packets to a pcap file and load that on a different computer where you can use wireshark:
[CODE]tcpdump -i eth0 -w tftp-debug.pcap[/CODE]
Change ‘eth0’ to whatever interface on the FOG you use…

Probably you could also capture one image using clonezilla from that particular kind of client just to have a template of clonezilla files ready. Then swap ‘sdaX.<fstype>-ptcl-img.gz.aa’ files with those you got from fog. From what I could find out they should be in the correct format (partclone packed with gzip) already. You just need to rename them properly. Give it a try…

Hard to tell without knowing the exact steps you made. Please provide more information on how exactly you tried to build the kernel (e.g. install build environment, download kernel source, extract source, config, …)

For sure there is something wrong with the kernel source. Where did you get it from? Extracted without errors? Enough free disk space?

That file should be there! It is part of the kernel source!
[CODE]find /path/to/extracted/kernel/source/linux-3.x.y/ -name “syscall_32.tbl”
…[/CODE]

Can you see TFTP request packets on the server using wireshark??

[quote=“Junkhacker, post: 42613, member: 21583”]i really think it would be easier to create a clonezilla usb boot stick, and copy your image to it, instead of trying to rewrite the fog stuff[/quote]
You could be right there. Somehow I got drawn away by the idea of being able to make FOG do local restore… Maybe it’s just easier to use clonezilla.

Sorry, I didn’t know about FOG ignoring USB connected storage devices yet! Your screenshots show that any kind of linux would be able to use the UDM devices. Please check out this manual on how to build your custom kernel: [url]http://fogproject.org/wiki/index.php/Build_TomElliott_Kernel[/url]

You’ll find usb storage driver here: Device Drivers -> USB Support -> USB Mass Storage (mark it with <*>) and then build your kernel…