Bug #4403
closedIp autosuggestion doesn't work
Description
Foreman 1.4 running on RHEL 6.1 with a smart proxy running DNS, DHCP and TFTP services on RHEL 6.5
Running foreman proxy with DEBUG flag activated in settings.yml
When creating a new host, in the network form, select domain and after that subnet, the IP autosuggestion feature doesn't work. Apparently the proxy things that all the addresses in the range are busy but they aren't.
Output example at /var/log/foreman-proxy/proxy.log:
I, [2014-02-20T14:04:33.251753 #7693] INFO -- : Found a pingable IP address which does not have a Proxy::DHCP record
D, [2014-02-20T14:04:33.251873 #7693] DEBUG -- : Searching for free ip - pinging 172.20.13.252
I, [2014-02-20T14:04:33.252834 #7693] INFO -- : Found a pingable IP address which does not have a Proxy::DHCP record
D, [2014-02-20T14:04:33.253045 #7693] DEBUG -- : Searching for free ip - pinging 172.20.13.253
I, [2014-02-20T14:04:33.253961 #7693] INFO -- : Found a pingable IP address which does not have a Proxy::DHCP record
W, [2014-02-20T14:04:33.254088 #7693] WARN -- : No free IPs at 172.20.13.0/255.255.255.0
(END)
For the whole log see attached file.
Files
Updated by Ohad Levy over 10 years ago
according to the logs, you have something responding to tcp or icmp pings.
can you verify yourself? (try tcpping to port 7).
Updated by Xavier Naveira over 10 years ago
Ok so I pinged a free address with:
hping3 -S -p 7 172.120.13.125
and got
len=46 ip=172.20.13.125 ttl=255 id=18743 sport=7 flags=RA seq=0 win=0 rtt=0.5 ms
len=46 ip=172.20.13.125 ttl=255 id=32053 sport=7 flags=RA seq=1 win=0 rtt=0.4 ms
len=46 ip=172.20.13.125 ttl=255 id=44593 sport=7 flags=RA seq=2 win=0 rtt=0.5 ms
if I use icmp I get nothing
hping3 -1 172.120.13.125
It seems that our network configuration is faking the tcp response in some way... I'll checl with the network engineer, is there a workaround from your part?
Updated by Xavier Naveira over 10 years ago
We have configured the firewall to let echo requests pass through with an explicit rule and now seems to be working.
We get suggested only addresses ended with and odd number as the last byte though (11,13,15...) Is this the expected behaviour?
Updated by Dominic Cleal over 10 years ago
- Translation missing: en.field_release deleted (
2)
Updated by Ohad Levy about 10 years ago
- Status changed from New to Feedback
can you confirm this now works as expected? thanks!
Updated by Anonymous over 7 years ago
- Status changed from Feedback to Resolved
no further reaction, seems fixed, closing.