All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Problem installing OS with netboot.xyz
Have a VPS where you need to set static IPv4 when you install an OS. Works fine for most ISOs but am unable to get netboot.xyz to install an OS.
I boot to netboot ISO and it will just go into a reboot loop until I select M for Manual. Asks for IP address: 123.456.789.012 Asks for Subnet Mask: 255.255.255.0. Asks for Gateway: 123.456.789.1. Asks for DNS: 8.8.8.8
At this point netboot starts up and displays a list of OSs. When I choose one it begins the install but apparently there is a problem with network so is unable to proceed.
Believe I need to enter the Network or Subnet info somewhere (123.456.789.0/24) but it's not giving me the option.
Any info or advice is appreciated.
Comments
Try this,
https://lowendspirit.com/tip-install-os-via-netboot-xyz-without-iso-support/
Which OS? On Debian you'll have to wait for DHCP to fail, then choose to manually configure the network, and enter all the details. This works for most hosts for me, but failed on ZappieHost because their gateway is outside the subnet (you may need to open a ticket and ask them for assistance in that case).
It's even easier if you use
grub-imageboot
. I've commented about this in the past on this forum, and just wrote a page on the Netboot.xyz site about how to do it: https://netboot.xyz/docs/booting/grub. Note that on most KVM VPSes, you can just press a key on boot and select iPXE, no existing OS required.In any case, that's not really relevant to this thread I don't think? OP said they can boot netboot.xyz and start the installer of some OS, they just can't complete the install.
I've experienced the same issue with netboot.xyz before.
My frank advice in this case would be to forget netboot.xyz and instead to try to get the particular ISO that you want to install. For example, if you want to install Debian, try to get a Debian ISO, and once you boot the ISO, go into "Expert install" and there's an option for static network settings.
I imagine that netboot.xyz can be made to work with static network settings, but after several tries I gave up and went directly for the ISO that I wanted to install (Debian, in my case).
How do you have a gateway outside the subnet (intentionally)? Are you sure the GW wasn't an accidental typo by provider? That's happened to me before.
That's what I thought, but somehow it actually works? My guess is the host machine has multiple IP ranges, and one gateway for it to reach the internet, and the VMs on the host all share that same gateway. As long as all traffic is routed via the host via the virtual network adapter and the host knows how to reach the gateway (could even be a static route on the host), it probably works fine?
A South African VPS I've got with ZappieHost has its IP in the
169.239.128.0/23
range, but the gateway is129.232.177.186
, and it works fine. A New Zealand VPS with the same provider has a gateway of10.0.0.1
🤔 (although they did say they have NAT VPSes on the same node)No, it would be destination unreachable. It's invalid case.
I call shenanigans. Still got the ZappieHost VM? Post the routing table. There'd need to be a static route for "You want 129.232.177.186? Send it to 169.239.128.1", which could just replace the wrong gw with the address used for static route.
I also call shenanigans, but somehow it works. It also has a
255.255.255.255
netmask which is strange to me too. Their support told me that the Debian installer doesn't like it, so they temporarily gave me an address in the129.232.177.x
range just for installation, but then once I rebooted I changed the IP and it works fine.onlink -> pretend that the nexthop is directly attached to this link, even if it does not match any interface prefix.
Interesting... I never manually set this; I just have
gateway 129.232.177.186
in the network config. I wonder if Debian automatically does that?ifupdown (0.8.7) unstable; urgency=medium
(...)
* Use the onlink option when adding a gateway route. Closes: #378506
-- Guus Sliepen <> Mon, 11 Jan 2016 22:58:44 +0100
Cool thanks @JabJab; I learned something today
Thanks for the responses. Have taken @angstrom advice and given up on netboot for this VPS, using another ISO host provides where you can just enter all the network info during setup and works no issues
Thanks, learned something new.
Why would a provider do this? Or is this some openvz shit?
My VPSes are both KVM.
Let's tag @Zappie and see - maybe they will answer
Ha thanks for the tag.
Cant speak for the issue that OP is having (to be honest I didnt fully read it sorry) but like @Daniel15 said, the debian installed (just the installer) doesnt like a fixed /32 subnet (255.255.255.255) unlike other installers like Centos for example which handle it just fine.
But once in the OS (be it Ubuntu, Debian, CentOs, Arch and yes EVEN WINDOWS) its totally ok and legitimate to have a single IP with a 255.255.255.255 mask with with a gateway that is (obviously) outside that subnet. Iin your routing table you would see
1.2.3.4
being the gateway address. As far as I know (I could be wrong) is the exact same way that (for example) OpenVZ does networking where a single IP address is added and everything is added to the single gateway.The thing I don't quite understand about this is what the network and broadcast addresses are with a
255.255.255.255
netmask. Do they just... not exist? Network, broadcast, and a host sharing the same IP seems like it shouldn't work 🤔It just meant you cant do unicast with others on the network (since the network is only you) Most PPPoE ISPs and some VPNs do the exact same thing, dishing out a single address and a routed gateway to push all your traffic from and to
Side note, this can also work with (for example) a /31 where you have 1.2.3.10/31 as the GW and 1.2.3.11/31 as the client and thats the full network.
In regards to this, it does sound very weird, if you were able to mount other (net)ISOs on your platform and give them your VPS static IP address/gateway and have them work all fine, I dont see why netboot specifically wont work 🤔 (dumb suggestions but maybe typo in the address?)
But why do this and cause problems for installers instead of just using a regular routed network? There must be a payoff worth it.
I encountered "IPv4 address and gateway not in same subnet" situation when installing Ubuntu 20 on @EvolutionHost Roubaix location (it's something similar to OVH failover IP).
This is my notes on how I solved this problem.