Had to hard code ENET adapter, now I can't update because I can't get an internet connection

[TTellez]

Working with someone from here, we got my Fog server working by hard coding the enet adapter in the server, but now when I plug it into an external network connection to try and update it, I get no internet connection.

One thought I have is to disable the network connection that is hard coded and create a new connection, but I don’t want to lose that one. In Ubuntu, is it possible to create a new connection using the same adapter, then switch back to the old connection?

Thoughts? Suggestions?

[Tom Elliott]

I might suggest looking here for some help:
https://linuxconfig.org/configuring-virtual-network-interfaces-in-linux

[TTellez]

I know this Tom. You and I worked for a good two hours to get it to work one Sunday.

[Sebastian Roth]

@TTellez Maybe start by showing us your current network config. Run ifconfig -a and cat /etc/network/interfaces as root (sudo) and post the full output as text or picture here!

[TTellez]

@Sebastian-Roth

[Tom Elliott]

@TTellez My link was to help show you how you could setup a “secondary” virtual nic that could be configured to get on the main network so you could perform the update.

[Tom Elliott]

This would leave the originally hard coded information there and available, while only altering the network you’re on so the virtual network would take over for subsequent updates/upgrades.

[TTellez]

@Tom-Elliott gotcha. Ill try it with my remedial linux skills. LOL.

[Tom Elliott]

@TTellez If you need help, we’re here to do what we can. The link should be pretty informative at least. Of course you will likely need to be in elevated permissions (sudo -i)

[TTellez]

@Tom-Elliott So I literally just
ifconfig eth0:0 123.123.22.22
then when I am done

# ifconfig eth0:0 down

And my original connection stays as is?

[Tom Elliott]

@TTellez well you would replace eth0:0 with the relevant interface name, in your case eno1:0

[TTellez]

@Tom-Elliott of course. I knew that one.
thanks

trying now.

[Tom Elliott]

@TTellez You may need to add the route for that interface as well, more than just setting the ip itself. It needs to know how to get to the endpoint of course.

I think you can do that with:

route add default gw <123.123.22.22 valid gateway> eno1:0 (not 100% on the syntax sorry)

[TTellez]

@Tom-Elliott

Still no network connection. trying the gateway addition now.

[Tom Elliott]

Once that’s done, the last part would be to look at dns (assuming you’re testing by pinging a domain name).

You would need to edit /etc/resolv.conf and add a proper dns server.

Something to the likes of making it read as:

nameserver 8.8.8.8
nameserver 4.2.2.4
nameserver <internal dns if needed>
search <domain.com if needed>

[TTellez]

None of this is working. So I will just continue to use it with the current version that is installed (1.3.5). Thanks for your help.