It looks good. You may find that the logging is not sufficient for your requirements. I don't use lightsquid so I can't comment directly but you should make sure it will do what you need.
pfSense stores all it's logs in RAM and is therefore limited in what is stored.
If you need complete logging of everything you will need to use a syslog server on a different machine.

Steve

@marcelloc:

Check linezing.com ip address and then start a tcpdump from console listening on lan for traffic on this ip

This won't work because OpenDNS is blocking the resolution of that name and hence you'll never get any traffic sent there.

Kind of ugly but functional way to find this from tcpdump:

tcpdump -ni em0 port 53 |grep linezing.com

replacing em0 with your LAN NIC. Let that run until you see some output. That'll catch any DNS request for *.linezing.com

@cmb:

As long as you have unique gateway IPs on each connection, that's fine. Lot of discussion on considerations for multi-WAN ISP selection in http://pfsense.org/book

Take the subnet into account, too. With the Motorola/Netopia ADSL modems they have an option to perform PPP and assign the IP address via DHCP. Well when using that the subnet mask from DHCP is 255.0.0.0  so the gateways can't begin with the same octet.

You can put clonezilla on /tftpboot in pfSense and then once you PXE boot mount any SMB, NFS, etc network share to store/retrieve disk images. I wouldn't use pfSense as a file server, but I don't see an issue with read-only TFTP for a few static files.

Hi,

here I described or pointed to links how to get a WLAN AP with WPA2 enterprise and freeradius working:
http://doc.pfsense.org/index.php/FreeRADIUS_2.x_package#FreeRADIUS_.2B_WLAN_.2B_PEAP_and_MSCHAPv2_.2B_Windows_.28XP.29_Client

I tried it with freeradius2 package and an Linksys AP with DD-WRT firmware.
It should not be so difficult from tomatousb.

Check the docs:

http://doc.pfsense.org/index.php/Accessing_modem_from_inside_firewall

@stephenw10:

Check that you have a valid setting for the update server.
Look in the web gui System: Firmware: Updater Settings.

If there is no entry or it is set to a custom URL then select on the of the 'Default Auto Update URLs' instead.

Steve

That was the solution.  Thanks!

Solved. Looks like it was not providing the full path to the FTP binary and a botched cron entry. Thanks to those who assisted with this!

@Cry:

I'd check the SSH server logs, possibly increasing the logging level if required. It should help you identify the problem.

Thanks for the advice. I'm glad to see the lack of 'me too' responses. I'm hoping it's a ssh config problem on my server.  My fear was that it could be a pfsense issue, but the general tone of the replies indicates that's not the likely problem

check interface speed and duplex, there are some posts explaining how to force a specific speed and duplex mode.

Nice one!
Could have saved some time if I'd thought you may have been running 64bit in the first place!  ::)
Actually I'm quite surprised it doesn't have some checks in the package sysetem to stop this happening. Lesson learned.

Steve

You need to put the DSL box into bridge mode.  Then setup the interface in pfSense to use PPPoE and supply the DLS credentials in pfSense.

@mikesamo:

I get this working using static route with a bad gateway

LAN 87.230.0.0/16
LAN 178.77.0.0/16

Don't do that, just block those networks via a firewall rule.

Just want to confirm that it works. Some extra block rules are required so that the traffic doesn't slip in with the default "pass any to any" rule.
I find this solution really neat and simple, a lot better than what I was originally asking for.

You have two ways

first way:

unistall gui package

install nrpe freebsd package

save changes to config file

second way

change nrpe inc file that creates config file

apply config on gui

Of course backup your config before changing anything

Do you have any firewall rules built for it?

Look at your firewall logs during incoming and then outgoing calls…  Are you seeing the RTP ports being blocked?

Sip services are very different from provider to provider...  You might try turning off the RTP proxy and see what that does...

Under "Registered Devices" do you show your phones?  Are you cloning your number on more than one port?

For port 22, the best way to do this are using multiple nat on wan with different port for each server.

Server 1 port 2201 wan to 22 internal
Server 2 port 2202 wan to 22 internal

Or you could use openvpn to establish a connection to your lan