The server is running just fine now. It has imaged a few computers, but it was still never able to be seen by that laptop, so I just built an image from scratch for it so that I could get it to the teacher that needed it. At this point I think there is something wrong with the switch in this room (rather old 3com switch). I am getting the superintendent to buy new switches, but one thing at a time (because of the price tag).

[quote=“Eze84d, post: 44616, member: 28734”]Tom Elliott thank you very much for your help.

Of course I’m using translate.google.com to translate what I mean to, so maybe there are some inconsistencies in language.

My original language is Spanish, I’m from Argentina, and to be honest, in English, very little to no …

Thanks again for your support !!![/quote]

i highly recommend that you post the original text as well as the translation.
the automatic translation is far from perfect, and some people on the forum will be able to understand your message in your native language.

Here is exactly what we used to test the connections:
root@fogVM:/images/DellOptiplex3020syspreptest# udp-sender --file /opt/fog/log/multicast.log --ttl 32 --mcast-data-address 239.168.1.1 --min-receivers 2
Udp-sender 20120424
Using full duplex mode
UDP sender for /opt/fog/log/multicast.log at 172.28.2.21 on eth0
Broadcasting control to 224.0.0.1
New connection from 172.28.16.36 (#0) 00000009
Ready. Press any key to start sending data.
New connection from 172.28.16.49 (#1) 00000009
Ready. Press any key to start sending data.
Starting transfer: 00000009
bytes= 2 200 re-xmits=0000001 ( 50.0%) slice=0112 - 0
Transfer complete.
Disconnecting #0 (172.28.16.36)
Disconnecting #1 (172.28.16.49)

Here is the one for the image:
root@fogVM:/images/DellOptiplex3020syspreptest# gunzip -c “/images/DellOptiplex3020syspreptest/d1p1.img” | /usr/local/sbin/udp-sender --min-receivers 2 --mcast-data-address 239.168.1.1 --portbase 9000 --interface 172.28.2.21 --full-duplex --ttl 32
Udp-sender 20120424
UDP sender for (stdin) at 172.28.2.21 on eth0
Broadcasting control to 224.0.0.1
New connection from 172.28.16.36 (#0) 00000009
Ready. Press any key to start sending data.
New connection from 172.28.16.49 (#1) 00000009
Ready. Press any key to start sending data.
Starting transfer: 00000009
Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=6696
Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=6696
Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=6696
Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=6696

It’s always wanted to grab all the MAC Addresses. That’s exactly what its purpose is.

First things first, what version of FOG?

Second, what OS are you running on?

Third, is the drive really only 1.5GB? <-- You’ll be lucky if you can fit one image on it.

Thanks!

The wol function still doesn’t works with the SVN 3178 with proxy enable.
My server works well now, whithout the proxy filed.
In which cases I’ll need to filed the proxy filed ?

Last question, I don’t understand your sentence :“but don’t have a viable way to test it myself.”
I my case I just have to put an IP adress in the field “[SIZE=13px][FONT=Ubuntu][COLOR=#555555]FOG_PROXY_IP”[COLOR=#000000] and the WOL function don’t work anymore on all computers on the same subnet of my server. I asume that you can try it on evry installation ? Or it’s just in my case ??[/COLOR][/COLOR][/FONT][/SIZE]

It’s not a router.

It’s a router, switch, DHCP, DNS, Access point Combination device…

and real world organizations with over 10 clients don’t use such limited consumer grade devices within their core network infrastructure. They would use an enterprise level solution (like Cisco Small Business devices, or server 2008, 2012.) that allows configuring 066 and 067.

What I recommend for you is not necessarily what I’d recommend for others.

Matthew,

thank you for this idea. I already switched to a more reliable solution. I might try Fog in the future again with firewall turned off.

Got it working?? I just found this (again) where someone had if working already months ago: [url]http://fogproject.org/forum/threads/fog-pxe-boot-with-usb-to-ethernet-adapter.10352/page-3#post-40799[/url]

I’ve been trying to figure out exactly what you are Uncle Frank. I don’t think it’s specific to the kernel, but rather how iPXE is opening the connection, and it’s just not releasing the openness of the connection when the code links.

I am very sorry, please ignore my second question. Must’ve been late or something… I got things mixed up (still one of the new guys in the dev team). Partclone is perfectly fine.

Somehow this sounds like it could be a similar issue to the one that got me started to engage in this forum. See here: [url]http://fogproject.org/forum/threads/kernel-temporarily-loosing-partition-information-when-running-partprobe.12276/[/url]

Please run an upload debug task (Client -> Basic Tasks -> Upload Debug) and pay close attention to unusual things on the screen. Probably best to take pictures so that we can have a look if and where things go wrong.

Check the following header file in the ipxe source directory: ipxe/src/config/general.h

You’ll see some lines with ‘define’ there. Some have ‘//’ at the beginning which means that those options are not being compiled into the ipxe binary! Remove those two slashes in front of PARAM_CMD (and possible some other options too):

[CODE]…
#define AUTOBOOT_CMD /* Automatic booting /
#define NVO_CMD / Non-volatile option storage commands /
#define CONFIG_CMD / Option configuration console /
#define IFMGMT_CMD / Interface management commands /
//#define IWMGMT_CMD / Wireless interface management commands /
//#define FCMGMT_CMD / Fibre Channel management commands /
#define ROUTE_CMD / Routing table management commands /
#define IMAGE_CMD / Image management commands /
#define DHCP_CMD / DHCP management commands /
#define SANBOOT_CMD / SAN boot commands /
#define MENU_CMD / Menu commands /
#define LOGIN_CMD / Login command /
#define SYNC_CMD / Sync command /
#define NSLOOKUP_CMD / DNS resolving command /
#define TIME_CMD / Time commands /
#define DIGEST_CMD / Image crypto digest commands /
#define LOTEST_CMD / Loopback testing commands /
#define VLAN_CMD / VLAN commands /
#define PXE_CMD / PXE commands /
#define REBOOT_CMD / Reboot command /
#define POWEROFF_CMD / Power off command /
#define IMAGE_TRUST_CMD / Image trust management commands /
#define PCI_CMD / PCI commands /
#define PARAM_CMD / Form parameter commands /
#define NEIGHBOUR_CMD / Neighbour management commands /
#define PING_CMD / Ping command /
#define CONSOLE_CMD / Console command /
#define IPSTAT_CMD / IP statistics commands /
//#define PROFSTAT_CMD / Profiling commands */
…
[/CODE]
Then compile again, copy the new binary to /tftpboot, check file permissions and boot up the client…

[quote=“sourceminer, post: 44591, member: 29126”]Sounds good Tom, I was hesitant to use the Development build for obvious reasons. For the record 1.2.0 is the version I downloaded from the Sourceforge link on the home page: [url]http://sourceforge.net/projects/freeghost/files/latest/download[/url]

I will attempt to use the latest development build located here:
[url]http://www.fogproject.org/wiki/index.php/SVN[/url][/quote]

If it wasn’t for the development versions, FOG wouldn’t work in my environment.

[quote=“Wayne Workman, post: 44570, member: 28155”]Which is where DHCP classes and DHCP policies must come into play…
Still working on this… I haven’t looked into it for a good while (spring break, woot!).

But, when I do (and get it working), I plan on writing some very through documentation for the WiKi that is specific to ProxyDHCP and Windows Server 2012 DHCP.[/quote]

User Classes are great and the way to handle many things, especially the handing out of files to UEFI systems vs. Legacy systems.

i am currently testing what i suspect to not be working

You must also be sure that FTP is actually running on the FOG server.

[CODE]sudo service vsftpd restart[/CODE]

If it’s not configured right, it should give some errors which will help.

This could also be firewall related, potentially.

Blocking or non-blocking, shouldn’t matter. I believe, for now the method is a blocking mechanism, but in Carsten’s particular case, the OUI file cannot be downloaded, hence the issue he’s running into.

That fixed it. Thanks Tom.

I thought that switching back and forth might be a problem. UEFI is still a bit of a mystery to me. I removed it completely from the boot sequence and options, but it doesn’t seem to matter. I’m not even sure what I need to do to eliminate UEFI from the process. When I get time, I’ll need to research that myself. At this point, I think it’ll be easier to just interrupt the boot sequence and select the pxe boot when I need to image a machine. Thanks for the help!