Hello @george1421, thank you very much for your help
Here is the ltsp.conf: ltsp.txt
I cannot reach the machine today anymore, but I will check the DHCP relay settings and deliver the requested tcpdump files tomorrow.
Hello @george1421, thank you very much for your help
Here is the ltsp.conf: ltsp.txt
I cannot reach the machine today anymore, but I will check the DHCP relay settings and deliver the requested tcpdump files tomorrow.
Hello FOG Team,
I have a problem with our FOG project dnsmasq setup and I am sorry if this has been answered before in another thread.
My setup is as follows:
Subnet 1 hosting the FOG server + proxyDHCP (Both are on the same machine).
I followed the setup exactly as described here: https://wiki.fogproject.org/wiki/index.php?title=ProxyDHCP_with_dnsmasq
Subnet 2 hosting the FOG client (MAC: 52:54:00:fb:96:27).
Palo Alto Firewall with integrated DHCP server (Same subnet as the FOG server).
I added a DHCP relay entry to forward the DHCP communication between the subnets.
Everything works fine when I move the client to the same subnet as the FOG server + proxyDHCP. I attached a tcpdump log of the working DHCP communication on the FOG server (141.5.200.57): VLAN1.txt
However, when I move the client to the other subnet, then dnsmasq seems to fail.
I can see that the DHCP discover from the client in the different subnet is arriving at the proxyDHCP server, but the proxyDHCP is not answering with an offer and I cannot figure out why.
I attached a tcpdump log of the not working DHCP communicatoin on the FOG server (141.5.200.57) (10.65.0.6 is the Gateway of the subnet that hosts the client): Privat.txt
I am new to this, but the only difference in the two files seems to be that in the failing communication an additional entry โGateway IPโ exists.
Additionally, the port of the senders incoming message seems to be 67 (10.65.0.6.67) instead of 68 (0.0.0.0.68).
Since the broadcast message seems to reach the proxyDHCP, I do not suspect a problem with the DHCP relay, however I am not sure if the mixed up port might have an influence?
Could it be a problem with the proxyDHCP that needs to be configured differently to handle broadcasts from another subnet or has problems to listen to DHCP pakets coming from port 67?
If you need more information, please let me know
Every suggestions is highly appreciated
Best,
Markus