Request to change the default network interface (Mint & Ubuntu)

[Sebastian Roth]

@mitnotromney Thanks for reporting this. This is not you doing something wrong but our installer running into an unexpected situation. Moving this topic to bug reports.

Please help us fix this quickly. Run the following commands on your system and post output here:

ip -4 route show
ip -4 link

Thanks!

[mitnotromney]

@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.

[Sebastian Roth]

@mitnotromney Sorry forgot to say, can you please run those commands as root.

[mitnotromney]

@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.

[Sebastian Roth]

@mitnotromney Sorry to say this but so far this doesn’t make much sense to me. Not saying that it cannot be but I just can’t get my head around how the installer would produce such an output.

So first lets start by posting the install logs. Go back to the folder where you ran the installer from. Find two log files in the subdirectory .../fogproject/bin/error_logs/ and upload those in the forums.

Thanks for mentioning pi-hole. From what I have seen so far this shouldn’t cause this but I wouldn’t bet on it!

Second, macvtap0 sounds a bit like you are using some kind of virtualization. FOG has been used in many environments like VMware, Hyper-V, Xen, VirtualBox, KVM and probably others. So I don’t think this is a problem in general. But I am wondering if you can describe your setup a bit more in detail so we get the whole picture.

[mitnotromney]

@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.

[Sebastian Roth]

@mitnotromney Wow, didn’t expect that! I have no idea how a switch would be able to cause this! Anyhow, marking solved until we hear different from you or anyone else.

Thanks for the update!

[cromag]

I too am having the same issue. Choosing defaults or No results in an endless loop of the FOG installer asking if you want to change the default network interface. The only way to get around it is to choose yes and then type in the interface manually.

Would you like to change the default network interface from enp1s0 wlp2s0?
If you are not sure, select No. [y/N] Y
What network interface would you like to use? enp1s0
Fog.1.5.7 running on an ubuntu distro variant. Have had it happen on two different distros. Zorin and Peppermint.

default via 10.10.128.1 dev enp1s0 proto dhcp metric 100 
10.10.128.0/24 dev enp1s0 proto kernel scope link src 10.10.128.87 metric 100 
169.254.0.0/16 dev enp1s0 scope link metric 1000

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: enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
    link/ether 00:ce:39:cf:2c:53 brd ff:ff:ff:ff:ff:ff
3: wlp2s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DORMANT group default qlen 1000
    link/ether f4:d1:08:6f:f4:5a brd ff:ff:ff:ff:ff:ff

[Tom Elliott]

The OP really sounds like the switch was of Power Saving type. Meaning the port was powered off during a small part of the process. It could be anything else too I suppose, but this really seems to fit description.

[cromag]

@cromag I suppose it could be a setup issue. My setup is a bit different that the original OP. Let me switch some stuff around. I am running the “server” from a port on my work phone so that might have something to do with it. Let me see if hard wiring it directly to a switch fixes the issue.

[cromag]

@Tom-Elliott changing the setup and plugging directly into a 24 port cisco switch had no effect. I can work around it, I just thought maybe it was a bug in the installer.

[Sebastian Roth]

@cromag Do you get the same Device "macvtap0@" does not exist. error message?

[cromag]

@Sebastian-Roth I get No errors. It just endless loops to the same question over and over again until you manually type in the adapter.

[Sebastian Roth]

@cromag Thanks for bringing this topic up again. Indeed there was an issue in the scripts. I just pushed a fix to dev-branch. Should be fine in the next release.

Though I still have no idea where the macvtap0@ thing came from reported in the first place.