Dhclient: connection closed. kernel: arpresolve: can't allocate llinfo for …
2.0-RC1 (amd64) built on Sat May 7 23:04:11 EDT 2011
I've got small problem. Once in a week my dhcp wan fails. I do not know reason why is happends, but there is a strange thing.
When it happends i must restart router and it is working, but i can bring interface back for work by changing it's type from "DHCP" to "None". Same thing when i make any changes in "DHCP" type inteface and apply changes - then connection is lost and i've to change type to "None" or reboot router.
Maybe someone can tell me what is wrong in my configuration or where to look for a problem.
I can do some debuging every sunday for few hours.
Log file attached.
You still have/see this?
I have similar "problem" I believe mine is related to an unstable WAN contention, my ISP (cable) got quality, performance and other issues that often result in my cable modem "freezes" whereafter it reboots it self, unfortunately I can no longer see the log files in the modem as the ISP removed that option after a firmware update :( but I have noticed that when this happens I am given a new IP address which apparently pfSense do not see/detect (same with other FWs).
Please take packet traces on this with full data to see what is happening.
Please can you confirm that I should use the option [Diagnostics: Packet Capture] with Level of Detail set to full. For how long shall I run the capture?
I added a switch between my Cable Modem and pfSense with mirroring between the two ports, added a laptop with wireshark.
Less than second between the pfSense sends out an ICMP to the gateway, and from the wireshark I see results like "Host Administratively prohibited", in some cases while in others a positive reply is received. I assume a ping less than a second is not real good.
I do not have this problem for a month.
Currently I am using version 2.0-RC2 (amd64) built on Wed Jun 10 2011 8:04:53 p.m. EDT, "and I do not have any problems with it.
In the logs I got: "dhclient: RENEW, dhclient: Creating resolv.conf"
It seems to me that it was repaired with the bug: "http://redmine.pfsense.org/issues/1508"
Thanks for replying!
Yes - it looks very much the same as in bug #1508 as mentioned by you.
I use version 2.0-RC2 (i386) built on Mon Jun 13 14:50:12 EDT 2011 and I assume i386 and amd64 on the should be same - or?
Could you give me the full path to where you get the different log, for error tracking I am very much a newbie.
2.0-RC3 (i386) built on Mon Jul 4 16:48:37 EDT 2011
and seeing this issue, but only every other day or so. need to figure out how to gather traffic when the issue is it's a lot of traffic!