Great, that's almost exactly what I was looking for.

Thanks!

I'll keep this thread updated with my progress.

Hi.

Thanks for your many answers.
I think my searchwords are wrong…... ???
Ok, thanks for the fantastic posts.

...OpenVPN is my next challenge.
I read some docs but it doesn't works until today.
On my next holiday I work on it.. ;)

Lars

Does anyone happen to have a syslog-ng config file that duplicates the output from pfSense's syslog.conf file?

I think I found a start here: http://forum.pfsense.org/index.php/topic,7793.0.html

*referenced here for anyone that might be interested.

Yes this is possible.
Just set up VIPs on the WAN.
limitation: currently you can only have additional static IPs.
NOT dynamic IPs.

DNS entries for each IP is nothing the pfSense controlls.
You have to talk to the admin that manages the DNS server on which your domains are listed.

The answer then is - not with the base install.  You'll need to add some FreeBSD packages and your own scripts to do this.

Hi there,

I'm getting a similar problem with a cron job I have setup and each time the embedded device reboots it will overwrite the crontab back to default.

This may be a crappy question to ask, but it looks as though there are a few crontab entries in the config.xml file under each . Why don't these show up and would I expect my to not show up when i run crontab -l because it's running from somewhere else.

Thanks

Found the issue or at least what I think the issue is. I was using the 4.2.2.1-6 DNS server. I was looking at some information regarding how Google can geographically locate your dns query and give a response based in this information, so I decided to change the forwarders to Comcast. It appears using the Comcast dns servers has fixed the issue. Is it possible Comcast slows or aggregates response times across their network to external dns servers? (This would conform to network neutrality would it?)

Anyway just wanted to post it wasn’t a pfsense issue but rather a Comcast issue from the looks.

Thanks to those who helped and inputted,
Peter

@GruensFroeschli:

The failover and loadbalancing pools are used within firewall rules.
When traffic arrives from the LAN and gets handled by the firewall rule(s) the traffic gets passed over to the balancing/failover pool specified in the firewall rule.
The traffic then gets balanced/failovered according to the specified pool.

Thank GruensFroeschli  very much. I understand now. I had tried to test failover in the pfsense host, that is not correct.  My setting of failover is OK, but my testing way is wrong. Now I have tested it from one of LAN computers, it works well.

Thanks again.

I am having a similar issue but with a static IP.  I have a multiwan setup with one static cable and one pppoe DSL.  I have the voip traffic all pushing through the static connection.  There are 2 different voip providers I am using.  One has no issues and the other always loses registration overtime and I have to clear the state manually to fix this.  The state always says multiple:multiple and has 2 entries for in/out paths.  I am trying the state timeout to see if it will help me in this scenario.

Funny thing is when I push the traffic from that provider out through the pppoe link everything works well but I have no traffic shaper as that has been configured on the static line and there is no multiwan traffic shaper yet.  I need the shaper because calls tend to get choppy when it gets busy otherwise.

I've never tried to do this. I've not seen any instructions anywhere else for doing it. Its a long while since I've done an install so my recollection of the install options might be incorrect. Here are a few different ways I would tackle the problem.

If I had two disks I would the two versions to the separate disks, selecting the FreeBSD boot loader. On startup the boot loader gives the option of booting from either disk, defaulting to the one previously used.

If I had only one disk I would install the two versions to two different '"slices", selecting the FreeBSD boot loader. On startup, the FreeBSD boot loader gives the option of booting from either slice, defaulting to the one previously used.

If I had limited physical access to the system and I had time on my hands I would try either of the above variants but use GRUB as the boot loader. (I seem to recall some recent reports of problems with GRUB as the boot loader but I don't recall the details. I've never used GRUB to boot FreeBSD. I have used GRUB to boot Linux systems.) GRUB would probably be better suited to unattended operation than the FreeBSD boot loader in that you can specify a default kernel in the GRUB configuration file and the default is unchanged by booting a non-default kernel. Thus you could make (for example) version 1.2.3 the default and version 2.0 as an option. Then if you boot version 2.0 and the system reboots it should boot version 1.2.3.

I don't know if there is a way to get the FreeBSD boot loader to forget what was last booted. But this would probably not be an issue if you planned to run version 2.0 only while you are in attendance.

your question gave me the answer. i stopped squid and it went away. but i still don't understand why it's communicating with itself.

There's a search feature.  How about you use it?

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