Hi,
I have a strange problem and I hope someone has run into this and can
explain what the problem with my setup is.
So I have a provisioning system (192.168.10.2) that is running dhcpd and
tfp and foreman (basically an all-on-one setup) and this system can also
act as a router.
The default gateway for the network is 192.168.10.1 so I put the following
config in dhcpd.conf:
So when a system boots up it gets the dhcp information and tries to contact
the tftp server…which fails.
What makes this strange is that when I change the option routers to
192.168.10.2 then the boot succeeds and the system gets provisioned.
It almost looks like the server (a Dell r815) is using the option routers
ip to reach the tftp server and not the next-server ip as it should.
I found the reason for the problem and it has to do with the fact that
Foreman manages dhcp.
Apparently when Foreman creates the leases is adds a "supersede
server.next-server" option and as far as I can tell simply sets the ip
address of the eth0 interface there. However the tftp, dhcp, etc. services
listen only on the internal interface eth1.
The question is where can I configure the IP that Foreman will use for that
particular option?
···
On Wednesday, April 17, 2013 2:31:59 PM UTC+2, Dennis Jacobfeuerborn wrote:
>
> Hi,
> I have a strange problem and I hope someone has run into this and can
> explain what the problem with my setup is.
>
> So I have a provisioning system (192.168.10.2) that is running dhcpd and
> tfp and foreman (basically an all-on-one setup) and this system can also
> act as a router.
> The default gateway for the network is 192.168.10.1 so I put the following
> config in dhcpd.conf:
>
> option routers 192.168.10.1;
> filename "/pxelinux.0";
> next-server 192.168.10.2;
>
> So when a system boots up it gets the dhcp information and tries to
> contact the tftp server...which fails.
> What makes this strange is that when I change the option routers to
> 192.168.10.2 then the boot succeeds and the system gets provisioned.
>
> It almost looks like the server (a Dell r815) is using the option routers
> ip to reach the tftp server and not the next-server ip as it should.
>
> Is there something I'm missing here?
>
> Regards,
> Dennis
>
Hey, just shooting in the dark, but is routing in your network okay?
No typos in the netmask? I recommend to boot a machine in that network
and try to reach things both on router and on tftp server.
> I found the reason for the problem and it has to do with the fact that
> Foreman manages dhcp.
>
> Apparently when Foreman creates the leases is adds a "supersede
> server.next-server" option and as far as I can tell simply sets the ip
> address of the eth0 interface there. However the tftp, dhcp, etc. services
> listen only on the internal interface eth1.
>
> The question is where can I configure the IP that Foreman will use for
> that particular option?
you can override the value foreman sets in the proxy config (afaik,
tftp_name or something similar).
Ohad
···
On Wed, Apr 17, 2013 at 6:04 PM, Dennis Jacobfeuerborn < djacobfeuerborn@gmail.com> wrote:
On Wednesday, April 17, 2013 2:31:59 PM UTC+2, Dennis Jacobfeuerborn > wrote:
Hi,
I have a strange problem and I hope someone has run into this and can
explain what the problem with my setup is.
So I have a provisioning system (192.168.10.2) that is running dhcpd and
tfp and foreman (basically an all-on-one setup) and this system can also
act as a router.
The default gateway for the network is 192.168.10.1 so I put the
following config in dhcpd.conf:
So when a system boots up it gets the dhcp information and tries to
contact the tftp server…which fails.
What makes this strange is that when I change the option routers to
192.168.10.2 then the boot succeeds and the system gets provisioned.
It almost looks like the server (a Dell r815) is using the option routers
ip to reach the tftp server and not the next-server ip as it should.
