@NOYB:

Tangentially related

The 8 hour graph title indicates 1 minute average.  But he graph granularity is 5 minutes.  Doesn't that really make it a 5 minute average?  Average of five one minute averages.  Is that not the same as a five minute average?

Thus the title is a little misleading in that it seems to indicate the granularity of the graph.  But looking closer at the time scale reveals the graph to have a 5 minute granularity.

http://forum.pfsense.org/index.php/topic,58158.0.html

Ah that's getting closer to what I'm seeing.

Thanks, with the newer build everything is back to normal.

You already posted this in another thread. You should include this in your existing thread, rather than starting a new one.

New snapshots are up again. Should be more stable.

I believe that means that the "ID" part of the config doesnt match between local and remote.  Make sure that however the Cisco identifies itself (IP or whatever) matches what you have in your config.

Huh thats odd…
LAGG interface comes up just fine.
other interface used for pppoe aswell...
Just this NIC seems to cause problems...
Maybe driver update?

Guess it's up to Chrome/Chromium beta team to fix this one ;) Thnx
(I've submitted a feedback message in Chrome beta, so let's see…)

@Exolon:

There are two other files that may need to be updated:

/usr/local/www/index.php - Line 165
/usr/local/www/head.inc - Line 16

Both use "", which may cause an issue with the character sets, try changing the "iso-8859-1" part to "utf-8".

okay this state temporarily solved, the purpose function without manual intervention
so we need the full support for auto language change

as of now its not happening, its a cisco device on the latest firmware so i have no idea what was causing but lets wait and watch for a few days to see if it happens again, if it does then might be a bug and if not then probably dhcp relay has a bug coz as rest of the features r all disabled, thanks for the help anyways

@jimp:

Could be why, especially if the new box doesn't have a serial port or has some issue initializing it. Try removing the line from the config that activates the serial port, restore the altered file, and see if the behavior improves It would be under the <system>tag somewhere, "<enableserial>". Remove the line if it's there and then restore.</enableserial></system>

I can't test this now because I reconfigured by hand and put the box into production. This is almost certainly the issue though as the new box had the serial port disabled in the BIOS.

You might want to consider a warning and option to disable in the restore script, just as you have with interface remapping.

Well, it stopped working by itself after some time.

@ermal:

Probably try after some ndp timeout?

No clue what you mean.

@ermal:

I would be curious to know that when you cannot ping it there is no ndp entry for the carp ip on the host from where you are trying this?!

Do you mean what "ip -6 neighbor show" shows?

I downgraded from Squid3 to Squid2 and the problem is gone.

Edit:
No, the bug is back today:
-rw-r–r-- 1 root 65 19485720 Apr 25  2013 dhcpd6.leases
-rw-r--r-- 1 1002 65 19559977 Apr 25 16:00 dhcpd6.leases~
-rw-r--r-- 1 root 65      186 Apr 25 16:00 dhcpd.leases
-rw-r--r-- 1 1002 65      186 Apr 25 07:23 dhcpd.leases~

Hrm the bug seems to affect even pfSense even though never seen probably because that again loop is rarely(maybe at all) used.

I will merge teh patch just for correctnes.

The quoting there has other issues actually. If a user has international characters it needs a call to utf8_encode/utf8_decode in various places as well. I'm not sure why it's run through html encoded there, it probably shouldn't be done at that stage, only if the text needs transmitted back to the user in the GUI somewhere.

When I first implemented that a couple years ago, it worked for me and others who tried it.

What does your /var/etc/relayd.conf file look like?