@george1421, Let me check shortly. And that’s where I’m feeling really lost at. Obviously, I’m doing something wrong. I feel like I’m following the install exactly but I think my network setup is making this more of an issue, that and I’m trying to pxe boot vm’s. I’m sure that’s not helping.
Posts made by mitnotromney
-
RE: PXE Boot "Initial menu has no LABEL entries!"
-
RE: PXE Boot "Initial menu has no LABEL entries!"
@Sebastian-Roth I used this link to install fog.
I’m running Fog on Ubuntu in this instance, and it’s on a physical server on it’s own VLAN. I set it up to have Fog handle DHCP. The virtual machine that screenshot is from is running on the server I mentioned in VirtualBox. Let me know any pertinent information you need and I’ll get it.
-
PXE Boot "Initial menu has no LABEL entries!"
Hey guys. I’ve been working on installing and setting up Fog at home before I deploy it at work. I’ve gotten most of my issues fixed, but now I’m landing on a new one that I can’t find documentation for.
The server goes up fine but any machine I boot to gets stuck on this:
Any thoughts?
-
RE: Request to change the default network interface (Mint & Ubuntu)
@Sebastian-Roth I think the root of my issue was my setup. I have a 5 port switch that the machine I was using to work on Fog was hooked up to. After I read your comment I went in and completely rewired my house. I’m happy to say that I was able to get Fog up and running. I’m not sure how the switch kept this from working (https://www.netgear.com/support/product/GS605.aspx), but I hooked this machine up to the router and it ran smooth.
Sorry for the pointless ticket. If you still need anything from me, I’m happy to help.
-
RE: Request to change the default network interface (Mint & Ubuntu)
@Sebastian-Roth I just ran them with sudo and got the same result:
default via 192.168.1.1 dev eno1 proto dhcp metric 100 169.254.0.0/16 dev eno1 scope link metric 1000 192.168.1.0/24 dev eno1 proto kernel scope link src 192.168.1.241 metric 100
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000 link/ether 34:17:eb:d4:6a:d2 brd ff:ff:ff:ff:ff:ff
Also, I thought I should bring this up, I use a pi-hole to handle my dhcp and dns. Not sure if that would mess with the installer, but wanted you to be aware.
-
RE: Request to change the default network interface (Mint & Ubuntu)
@Sebastian-Roth Sorry it took so long. Here’s what I got:
mit@mit-OptiPlex-9020:~$ ip -4 route show default via 192.168.1.1 dev eno1 proto dhcp metric 100 169.254.0.0/16 dev eno1 scope link metric 1000 192.168.1.0/24 dev eno1 proto kernel scope link src 192.168.1.241 metric 100
mit@mit-OptiPlex-9020:~$ ip -4 link 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000 link/ether 34:17:eb:d4:6a:d2 brd ff:ff:ff:ff:ff:ff
Let me know if I can run anything else. I’m pretty free tonight.
-
Request to change the default network interface (Mint & Ubuntu)
Hi all.
Complete noob to Fog and I’ve tried running this on my Mint Station as well as my Ubuntu station. Right after selecting normal instalattion I’m faced with this snippet:
We found the following interfaces on your system: * eno1 - 192.168.1.241/24 Device "macvtap0@" does not exist. * macvtap0@ - Would you like to change the default network interface from eno1 macvtap0@? If you are not sure, select No. [y/N]
No matter what if I select yes or no it keeps coming back up and I can’t get any further. I’ve tried hitting up Google but I’m not able to find anything. Is anyone familiar with this?