ASL is shipped without a dhcp relay agent, sorry. Since V5 is RPM-based, you could try to install a rpm (but that will void you support).
DHCP is a broadcast-protocol. Therefore NAT is not a solution, since broadcasts are per definition not routed. The relay agent listens on an interface and works as a "proxy" for all dhcp requests on the connected network (that means it "translates" it and forwards it to a network on another interface, resulting dhcp ack's are "retranslated").
if I try to install a dhcpxx.rpm for SuSe on Astaro, occurs a message that it needs libc.so.6(GLIBC_2.3). It seems that ASL version is 2.2.5 but SuSe has glibc versions 2.2.3 or 2.3.3.
To Astaro Team - isn't it a good idea to build in ASL a dhcp relay agent? The Cisco PIX, e.g. has one now.
if I try to install a dhcpxx.rpm for SuSe on Astaro, occurs a message that it needs libc.so.6(GLIBC_2.3). It seems that ASL version is 2.2.5 but SuSe has glibc versions 2.2.3 or 2.3.3.
To Astaro Team - isn't it a good idea to build in ASL a dhcp relay agent? The Cisco PIX, e.g. has one now.
it would be a possibility, but we intend many broadcast domains (more then 20).To install a Windows relay agent in any broadcast domain isn't a very well solution.
Hi, I have the same "problem" here. My network consists of three broadcast domains and I want to use only one DHCP-Server for all connected networks (and no additional standalone relays).
Why is there no DHCP-relay agent in ASL? Is it a security problem or does nobody need it?
