Default.IPXE-no such file or directory (2e008081)
-
@TOXYKILLER Here’s what I find for one of your IP’s (if this is you then cool, but still a bit on the “whoa wait a minute” side)
Source: whois.arin.net IP Address: 11.101.149.115 Name: DODIIS Handle: NET-11-0-0-0-1 Registration Date: 1/19/84 Range: 11.0.0.0-11.255.255.255 Org: DoD Network Information Center Org Handle: DNIC Address: 3990 E. Broad Street City: Columbus State/Province: OH Postal Code: 43218 Country: United States
What does this mean?
Well DoD own’s the IP Space in its entirety of 11.X.X.X (Including 11.101.X.X).
-
@Tom-Elliott
We unfortunately do not have comfort of static IPs (it can be added via exception but it’s really hard through the bureaucracy process and providing business justification for this)FOG add is now 11.101.128.138 (was changed by DHCP during weekend)
Some of these picture are no longer valid.
What are we using now is this 11.101.0.0/16 network.I install fog on latest ubuntu and what a i have done was this https://forums.fogproject.org/topic/7727/building-usb-booting-fos-image/4?page=2 .
After this process task what was necessary for host registration. Registration was completed fine then i assign to this host created image and i schedule task for capturing image from host.
During this appeared this last issue. “/images/dev permission denied”
Nothing else was done on server. -
@Tom-Elliott said in Default.IPXE-no such file or directory (2e008081):
I feel I need to inform (not trying to question your ability at all) that 11.x.x.x is public. There are only 3 private address spaces. Unless you have your router/network completely airgapped for the public address spaces, this can cause potential issues. Especially if your organization owns the 11.x.x.x IP space as you’re exposing your entire network with this.
You should be using the Private address spaces for your imaging and storage. (192.168.x.x Class C CIDR/24, 172.16.x.x Class B CIDR/16, and/or 10.x.x.x Class A CIDR/8) As this will not open potential holes and security issues within your organization as well as prevent serious issues even if all worked properly.We are not using private add on our site. Only public IPs. Our company should own whole this network 11.0.0.0/8.
-
@TOXYKILLER you work with DOD Network Information Center?
-
@Tom-Elliott
Nope, I don’t work with DOD.We are using PAT for add. translation. This add. what was mentioned are not public. Sorry for little misunderstanding. -
@TOXYKILLER as long as we know the network is privately spaced and not going to cause issues, that is fine.
Then I would suggest asking your network team to give your fog server a reserved IP address. This is similar to a static IP but you wouldn’t have to keep jumping thru loops to get your server to operate, as it seems your dhcp lease times are very short. The reserved ip still resides with the dhcp server and you wouldn’t have to make any changes to the network configuration on the server for this to work.
Once you have a stationary fog server ip, I think we can get your machine up and running.
-
@george1421
/opt/fog directory exist but first mention is missing.
But it can be added manually right (/images directory) ? -
@Tom-Elliott
I have this in my plans but in this state is only testing version(will be never approved exception in this state). We must first test some process and if will be OK then we will request for exemptions for static IP. -
@TOXYKILLER If you rerun the fog installer script it should recreate things properly. if you use the wiki instructions and the git method you should just need to change to /root/fogproject/bin and run
./installfog.sh
If it prompts you for the the answers again then the installer didn’t complete the first time. Watch for errors. -
@george1421
I try it to install several times but i have same issue with missing files(i try github version too).I also try re run install on existing FOG server but same results .Can you please advise most stable or more less problematic linux distribution ?Fog-install.txt