Dual NIC Setup with Internet sharing
-
Server
- FOG Version: 1.3.5
- OS: Ubuntu 16.04.2
Client
- Service Version:
- OS:
Description
I have installed Ubuntu 16.04.2 on to a machine that has 2 network cards. I also installed FOG on to this same machine. The goal is that ETH0 will be connected to the internet over a DHCP network, and ETH1 will be the Fog port that handles giving out DHCP for client machines, but gives them internet access through ETH0.
Also, when I installed the FOG Server and tried to boot a machine with PXE Boot, it receives its IP address from DHCP, but then next to TFTP it says ARP timeout and then exits the PXEBoot agent and starts loading Winblows.
-
To make it clear… I have not tried to get this ETH0 and ETH1 situation actually working yet. I’m looking for guidance on that.
I’m also looking for guidance on why PXE Boot fail and say ARP TIMEOUT.
-
Wow, you went right to 12 (on a 1 to 10 difficulty level)
I think I understand what you are wanting, but lets use FOG terms here for clarity. Let me use my words to see if I have it right.
“I have a isolated imaging network that is connected to eth1 on a dual homed host. Eth0 will connect to my business network which has access to the internet. We will install the dhcp server on our fog server for the client connected to the imaging network. Our fog server will need to act as a gateway between the imaging network and the business network so the clients (on the imaging network) can access the internet via the fog server.”
While you can do this, I have to ask the question “Is this the only option you have avaiblle?” FOG more precisely ubuntu can act as a gateway/router so its possible to do, its just not typically done with your FOG server. Can you explain a bit more about what you want to achieve by this setup over a more traditional deployment of using a hardware/software router for a router and using fog for image deployment?
-
@george1421 That pretty much summed up exactly what I’m trying to do. We are trying to isolate our image network from everything else. Currently we are using GhostCast Server, which sucks (as far as speed is concerned), but it is a part of a much larger corporate network and because of that it suffers in bandwidth consistently.
It seems that the best scenario will be to make the Ubuntu box that also houses FOG Server the same box that handles routing of internet packets through the other network card.
-
@brooksbrown Ok then turning your linux server into a router is pretty simple. You just have to turn on a linux kernel parameter to make it route between the interfaces.
The first thing you need to do is to get FOG imaging correctly. When you setup FOG did you tell it to use the eth1 as your imaging interface?
Also post your config file for the isc dhcp
/etc/dhcp/dhcpd.confYou may want to review this setup for isc dhcp server if you need to support both bios (legacy) and uefi systems: https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence
From the error, my bet is that your dhcp configuration is wrong and your dhcp option 66 doesn’t point to the IP address of your eth1 interface.
And finally turning your linux box into a router: http://www.yourownlinux.com/2013/07/how-to-configure-ubuntu-as-router.html
This is the kernel setting you need to enable in sysctl
/etc/sysctl.confnet.ipv4.conf.default.forwarding=1 net.ipv4.conf.all.forwarding=1But again lets get fog imaging correctly.
If you did not pick the proper settings during fog server install, there is a hidden file that contains the settings in/opt/fog/.fogsettingsjust review that file to ensure the settings are correct. If you need to change something make the change there and rerun the installer.
