Posts made by Wayne Workman

You did try recursively changing permissions on /tftpboot ?

I have plans on making such videos… but I haven’t done it yet…

You can expect them in the coming weeks. I’ll put them into the WiKi when their up on YouTube.

Really?

So… You don’t see “Full Registration” on the menu at all? Can you take a video of what happens after you select that option?

[quote=“rgomez, post: 45012, member: 28841”]It’s working now. I can’t explain why this happens, but I’ve searched a lot in this forum and on another thread an user explained something related wiht NIC not being properly shutdown by Intel, so… What i’ve done in all NUCs is boot an LiveOS (Ubuntu for eg.) and after that restart to Network boot and it’s working. Already done 20 NUCs everything works, except Full Host Register (didn’t spent many time seing why)[/quote]

If you can, a screen shot or picture of the errors during full host registration would be helpful.

Also,

Check back here from time to time, it’s highly likely that other members can smash this problem pretty quickly.

It could be that those are for .32, both were last modified in 2011…

I’ve also just searched the forums quickly without any hits for “iso” or “ISO”

I personally have never put an ISO into the FOG boot menu, but I plan to… I’m currently putting together a Fedora 21 core server (no GUI) and I’m going to probably put FOG on it today, simply for the purposes of learning more about it and helping here on the forums.

In the mean time, you might find these helpful:
[url]http://www.tecmint.com/installing-windows-7-over-pxe-network-boot-in-centos/[/url]
[url]http://www.howtogeek.com/61263/how-to-network-boot-pxe-the-ubuntu-livecd/[/url]

Also, if you figure it out, please let us know what you did… The WiKi pages on this need updated.

What version/revision of FOG?
What’s the Linux distro and version?

Also, take a look at this: [url]http://fogproject.org/wiki/index.php/Include_any_ISO_in_the_FOG_Bootmenu[/url]

From just glancing through that WiKi page, I would THINK that you’re ISO is in the wrong spot.

Although this WiKi page is about Parted Magic, it might help you figure this out:
[url]http://fogproject.org/wiki/index.php/Include_Parted_Magic[/url]

Let us know, we’re here to help.

Well, the idea is to have a laptop with FOG installed, and go out with a cross-over cable to deploy & capture images. However, I want the client registration info and images I capture to sync with the primary server once the laptop is brought back online later…

I think I’m just going to have to try it out and see…

Tom is working on the problem. I think it’s best to hold off till he can code a fix.

Just found an Awesome article, I’m posting all of what I found because I’d hate for the resource to go away…
SITE: [url]http://www.syslinux.org/archives/2014-January/021404.html[/url]

Going to try this out next week!

-----------------------------------------------------------------------Content-----------------------------------------------------------------------

[syslinux] Windows Server DHCP + UEFI recipe

Alexandre Blanchetteblanalex at gmail.com
Wed Jan 15 03:45:05 PST 2014

A small how-to for encapsulating option 210 inside option 43 on Windows
DHCP servers would be welcome then

And as far as UEFI x86 system go, one would simply have to create another
vendor class with the value PXEClient:Arch:00006

On Wed, Jan 15, 2014 at 12:05 AM, Gene Cumm <[URL=‘http://www.zytor.com/mailman/listinfo/syslinux’]gene.cumm at gmail.com[/URL]> wrote:

I’ve found a way to support PXE booting both UEFI and BIOS architecturesvwith Windows Server DHCP.

This method uses a feature introduced in WinServer 2012: DHCP policies.
First, in the the DHCP console, at the IPv4 root of the server, create a vendor class named PXEClient (UEFI x64) with the following value: PXEClient:Arch:00007 Then create your configuration for your BIOS clients in your scope or as global settings as usual by setting options 66 (IP or hostname of your > TFTP > > host) and 67 (pxelinux.0). For the UEFI clients, you must then create a policy. In the condition > page > > of the wizard, add a condition with the following settings: > > Criteria: Vendor Class > > Operator: Equals > > Value: PXEClient (UEFI x64) > > Tick Append wildcard(*) > > > > Do not configure an IP address range for the policy. > > > > Finally configure options 66 (TFTP server) and 67 (syslinux.efi). You > must > > separate TFTP servers for your BIOS and UEFI clients because Microsoft > DHCP > > server does not send option 210 (path prefix). Microsoft DHCP servers > will > > only send options listed in the Parameter Request List in the > DHCPDISCOVER > > packet. > > > > One could make a cleaner setup by creating a BIOS PXEClient vendor class > > and putting their options within a policy too. >> I haven’t tried WS2012 yet but PXELINUX will parse DHCP option 43 > (vendor-specific information) nicely and I have encapsulated 210 > inside 43 successfully (can’t recall if I tried WS2008R2 and/or > ISC-DHCPd but I did at least one). >> The one oddball missing from your recipe is the UEFI x86 systems that > are not 64 bit. They are rare but exist. >> – > -Gene > _______________________________________________ > Syslinux mailing list > Submissions to [URL=‘http://www.zytor.com/mailman/listinfo/syslinux’]Syslinux at zytor.com[/URL] > Unsubscribe or set options at: > [url]http://www.zytor.com/mailman/listinfo/syslinux[/url] > Please do not send private replies to mailing list traffic. >>

–
Alexandre Blanchette <[URL=‘http://www.zytor.com/mailman/listinfo/syslinux’]blanalex at gmail.com[/URL]>

Still researching this… This thread is likely to get very jumbled up as I do this.

Tech Net article: Introduction to DHCP policies:
[url]https://technet.microsoft.com/en-us/library/dn425039.aspx[/url]

Tom is working on this, I think…

See here:
[url]http://fogproject.org/forum/threads/svn-3192-hangs.12685/[/url]

I had this idea… it’s sort of out there but here goes…

Is it possible to have a always-on Master storage node tied to another storage node within the same LAN?

And if so, say that other storage node was a laptop… that went “offline” from time to time…

When it came back online, would it sync any images I uploaded? Would it sync the database?

What sort of communications do Master storage nodes and other storage nodes need to fully function?

Any way to turn the web GUI on for a non-master storage node? Would things still sync if I did?

How are you running DHCP? What is it on?

Also, can you try making this file?

[CODE]/etc/xinetd.d/tftp[/CODE]

[CODE]service tftp
{
protocol = udp
port = 69
socket_type = dgram
wait = yes
user = nobody
server = /usr/sbin/in.tftpd
server_args = -s /tftpboot
disable = no
}[/CODE]

restart the service
[CODE]sudo service xinetd restart[/CODE]

Test tftp

Create a file named test.txt with some content in /tftpboot path of the tftp server
[CODE]sudo echo “Is my TFTP service working?” > /tftpboot/test.txt[/CODE]

On some other system follow the following steps.

[CODE]tftp x.x.x.x
tftp> get test.txt
//Sent 159 bytes in 0.0 seconds
tftp> quit
cat test.txt[/CODE]

----FOR FUTURE REFERENCE----

Some Hyper-V screen shots for one of our servers that is running FOG…

Bear in mind, I configured a static IP for the FOG server via the Fedora 21 OS.

In case the image hosting breaks, images are [U][URL=‘https://mega.co.nz/#!d4dhxQpK!-gyAjUY_bRJ4D4Uo-mAaSG1MAsvkVkywR6kePxBIBZc’]located right here[/URL][/U].

NIC Overview
[IMG]http://s10.postimg.org/fu5oos6fd/NIC_overview.png[/IMG]

NIC 2
[IMG]http://s7.postimg.org/8ce5q3dnv/NIC2.png[/IMG]

Hyper-V virtual adapter
[IMG]http://s10.postimg.org/pisdcw4jt/Hyper_V_virtual_adapter.png[/IMG]

Hyper-V virtual adapter IPv4 properties
[IMG]http://s23.postimg.org/71n5syxsb/Hyper_V_Virtual_Adapter_ip4.png[/IMG]

Hyper-V virtual adapter - IPv6 properties
[IMG]http://s10.postimg.org/fv1w6gsnd/Hyper_V_Virtual_Adapter_ipv6_properties.png[/IMG]

Virtual Switch - Overview
[IMG]http://s21.postimg.org/3viul08yf/Virtual_Switch_Overview.png[/IMG]

Virtual Switch - Extensions
[IMG]http://s28.postimg.org/urj4bvykt/Virtual_Switch_Extensions.png[/IMG]

Virtual Switch - MAC address range
[IMG]http://s11.postimg.org/z0zvoujnn/Virtual_Switch_Mac_Address_Range.png[/IMG]

FOG NIC - Overview
[IMG]http://s17.postimg.org/dshdq4omn/FOG_NIC_Overview.png[/IMG]

FOG NIC - Hardware Acceleration
[IMG]http://s12.postimg.org/t2orzls7h/FOG_NIC_Hardware_Acceleration.png[/IMG]

FOG NIC - Fail Over
[IMG]http://s7.postimg.org/vliubq57v/FOG_NIC_Fail_over.png[/IMG]

FOG NIC - Advanced Features
[IMG]http://s21.postimg.org/4vrizohnb/FOG_NIC_Advanced_Features.png[/IMG]

Some Hyper-V screen shots for one of our servers that is running FOG…

Bear in mind, I configured a static IP for the FOG server via the Fedora 21 OS.

NIC Overview
[IMG]http://s10.postimg.org/fu5oos6fd/NIC_overview.png[/IMG]

NIC 2
[IMG]http://s7.postimg.org/8ce5q3dnv/NIC2.png[/IMG]

Hyper-V virtual adapter
[IMG]http://s10.postimg.org/pisdcw4jt/Hyper_V_virtual_adapter.png[/IMG]

Hyper-V virtual adapter IPv4 properties
[IMG]http://s23.postimg.org/71n5syxsb/Hyper_V_Virtual_Adapter_ip4.png[/IMG]

Hyper-V virtual adapter - IPv6 properties
[IMG]http://s10.postimg.org/fv1w6gsnd/Hyper_V_Virtual_Adapter_ipv6_properties.png[/IMG]

Virtual Switch - Overview
[IMG]http://s21.postimg.org/3viul08yf/Virtual_Switch_Overview.png[/IMG]

Virtual Switch - Extensions
[IMG]http://s28.postimg.org/urj4bvykt/Virtual_Switch_Extensions.png[/IMG]

Virtual Switch - MAC address range
[IMG]http://s11.postimg.org/z0zvoujnn/Virtual_Switch_Mac_Address_Range.png[/IMG]

FOG NIC - Overview
[IMG]http://s17.postimg.org/dshdq4omn/FOG_NIC_Overview.png[/IMG]

FOG NIC - Hardware Acceleration
[IMG]http://s12.postimg.org/t2orzls7h/FOG_NIC_Hardware_Acceleration.png[/IMG]

FOG NIC - Fail Over
[IMG]http://s7.postimg.org/vliubq57v/FOG_NIC_Fail_over.png[/IMG]

FOG NIC - Advanced Features
[IMG]http://s21.postimg.org/4vrizohnb/FOG_NIC_Advanced_Features.png[/IMG]

huh…

Please do us a favor… please…

[B]Keep your working snapshot[/B]

And update FOG by like 10 revisions at a time… test each one with MemTest, perhaps.
So, 2920 then 2930, then 2940… find out where it breaks…

Then revert to your working snapshot… and take the last range you used and update one at a time… Figure out EXACTLY where it breaks. This will allow the developers to fix this issue for you and everyone else.

[quote=“Kyle Nash, post: 44926, member: 29243”]chmod 777 on /tftpboot… didn’t do the trick.[/quote]

I’d like to add that [CODE]chmod 777 /tftpboot[/CODE] will only change permissions on the /tftpboot folder, not the files in it!

Use the recursive flag for everything in a directory to inherit the permissions you assign…

[CODE]chmod -R 777 /tftpboot[/CODE]

If that doesn’t work, try this… I’ve read in some posts on the net that TFTP won’t work for remote users unless the files it’s giving are READ ONLY for everyone else… Because this is TFTP’s [U]only[/U] security… I know many give the folder 777 permissions, but this is just pure curiosity… and can be changed back easily.

[CODE]chmod -R 444 /tftpboot[/CODE]

In addition to what Uncle Frank said, the next server / filename is DHCP options 066 and 067… if that helps…

I would highly recommend building the pcap file as he said (if you don’t have luck with the other ideas), this guy has solved more issues by dredging through pcap files than you would think…