I have been trying to capture reproduction information about this IP-itf lock-up over the past weeks.
This is what I gathered:
- the problem usually happens after about 6-7 days normal operation, but not always as I got one 14 days run without issues. I interrupted this one as I could not further postpone adding some functionality.
- during the problem only the IP itf is affected, the EIB over RS232 is still running fine
- tcpdump shows no single activity on the ethernet phy when pinging etc
- during last occurrence I did get a half-refreshed webserver page where the time of blockage was visible (16.31pm).
In my DSL modem log I could find a DHCP request from the EibPC at 16.28:
Fri, 29 Oct 2010 16:28:02 GMT DHCP SERVER: DHCPACK on 192.168.1.2 to 00:50:c2:79:30:9a via br0
Fri, 29 Oct 2010 16:28:02 GMT DHCP SERVER: DHCPREQUEST for 192.168.1.2 from 00:50:c2:79:30:9a via br0
which proofs that something goes wrong with the itf at lease time expiry or at least during interaction with the DHCP server.
I now switched to fixed IP and will further observe the EibPC IP itf stability.
Hope this helps to find the root cause.
Best regards, Sammy
This is what I gathered:
- the problem usually happens after about 6-7 days normal operation, but not always as I got one 14 days run without issues. I interrupted this one as I could not further postpone adding some functionality.
- during the problem only the IP itf is affected, the EIB over RS232 is still running fine
- tcpdump shows no single activity on the ethernet phy when pinging etc
- during last occurrence I did get a half-refreshed webserver page where the time of blockage was visible (16.31pm).
In my DSL modem log I could find a DHCP request from the EibPC at 16.28:
Fri, 29 Oct 2010 16:28:02 GMT DHCP SERVER: DHCPACK on 192.168.1.2 to 00:50:c2:79:30:9a via br0
Fri, 29 Oct 2010 16:28:02 GMT DHCP SERVER: DHCPREQUEST for 192.168.1.2 from 00:50:c2:79:30:9a via br0
which proofs that something goes wrong with the itf at lease time expiry or at least during interaction with the DHCP server.
I now switched to fixed IP and will further observe the EibPC IP itf stability.
Hope this helps to find the root cause.
Best regards, Sammy
Kommentar