Routing and installation problem
-
xxx@fog-gateway:~$ sudo iptables -F
xxx@fog-gateway:~$ sudo iptables -LChain INPUT (policy ACCEPT)
target prot opt source destinationChain FORWARD (policy DROP)
target prot opt source destinationChain OUTPUT (policy ACCEPT)
target prot opt source destinationStill no go.
-
@DZKeeper That forward policy is still DROP
Lets try this one:
iptables -P FORWARD ACCEPTThat should change the forward policy to Accept and pass all data through your FOG/linux/router. -
@george1421 Done, all 3 to ACCEPT now, however, dont work.
BTW, I appreciate your time.
-
@DZKeeper OK now we can rule out forwarding (sorry about making this drawn out solving as thread discussions adds a certain amount of delay).
OK now that iptables is out of the way. From a computer on your LAB network, can you ping the business LAN interface (nic) of the FOG server from the lab network (this will test the on linux routing).
Also do the same from the business side, ping the LAB LAN network interface of your FOG server. I’ll assume from the business lan you can ping and get a response from the business LAN nic of your FOG server already.
Also from a computer on the LAB LAN computer, can you post here the output of
ipconfig /allhere? And also could you post the ip addresses of the FOG server both LAB LAN and business LAN? -
Ping No go from Lab -> business nic of FOG
Ping No go from Business -> lab nic of FOGYou assumed right.
FOG Server LAB IP: 192.168.22.99
Fog Server Business IP: 192.168.2.99PRetty hard for me to post the result of ipconfig /all from lab
-
@DZKeeper Well this is disappointing its still not working, it should be.
The reason why I wanted to see the ipconfig /all just to show that the default router for the LAB LAN is the LAB LAN nic interface of the FOG server.
Also from the business side I wanted to make sure there was a router to tell business computers about the computers beyond the FOG server. My intuition is telling me its a routing issue and not related directly to the FOG upgrade since FOG doesn’t mess with IP tables (actually one of the setup prerequisites is that you must disable the firewall all together as well as selinux).
If I had to listen to my intuition (assuming routing was working before you upgraded fog). I would almost suspect that the ip_forward setting was disabled. This command should return ( 1 ) enabled
cat /proc/sys/net/ipv4/ip_forwardYou can confirmed that the IP address of the FOG server hasn’t changed for either NIC adapters?
-
@george1421 Your last comment on “default router” made me change the option router settings in dhcpd.conf, which changed the default gateway in my lab client… boom, I can ping 8.8.8.8
Something changed my option router setting back to 192.168.2.1 instead of 192.168.22.99
-
@DZKeeper said in Routing and installation problem:
Something changed my option router setting back to 192.168.2.1 instead of 192.168.22.99
I can see/understand the fog installer “could” do this if you told FOG to configure the dhcp server for you. Running the installer would have (possibly) reset the routing options.
Since we messed with iptables, (which only would impact in memory configuration). Please reboot your FOG server to restore IP tables and clear any dynamic changes that we made. Then test again to make sure everything is back to normal. Then you can call it resolved.
-
@george1421 How should I disable this option in FOG config file ?
-
I’m confident the installer doesn’t touch iptables or firewalld. The plainrouter and router and other stuff in .fogsettings is only for configuring DHCP. I think that DHCP is messed up.
If you modify
/opt/fog/.fogsettingsand change these fields:dodhcp='Y' bldhcp='1'To:
dodhcp='N' bldhcp='0'Then the FOG installer will never again touch the DHCP configuration or DHCP service. Then you can configure
/etc/dhcp/dhcpd.confthe way it needs to be for your setup. Feel free to post this file to get help with configuring it if you need.
