You will have nat issues this way unless you set outbound nat on pfsense to reach local services with pfsense ip. My suggestion is to install haproxy on pfsense and configure your proxied services there. In both configurations, server log wil never show client's public ip.

@Cry: Multicast is not related to ports, but to IPs - you can't "port forward" that kind of traffic. However, please read the fine documentation. I haven't done anything with multicast and pfSense myself. Yup but my provider uses port 5820 UDP to send multicast traffic. I successfully configured IGMP proxy and created firewall rule to allow UDP 5820 to my LAN from OPT1 iface (plugged directly into modem). And now I have passed MC traffic to my LAN and can watch IPTV (securely :)) on it! Yay!

Are you seeing anything in the logs of either equipment? Check the pfSense firewall logs to see if it's blocking the ping reply for some reason. Steve

Yepp, that is it. I have one "offline" gateway - which is the WAN uplink gateway, the PtP address of the PPPoE link. That gateway definitively is online (I'm accessing the webConfigurator through an SSH tunnel through a connection via this link). Edit: apparently the gateway cannot be pinged, if I ping the gw address from the router it receives "Communication prohibited by filter" from the GW IP. I turned off (tick on System>Advanced>Miscellaneous>Gateway Monitoring>States) and now filter reloads happen without disconnect. Thanks jimp.

Thanks! that worked great

found it via google after some work. thanks mates.

Thanks, I have figured out it was caused by a left over rules on Floating when I try to setup Squid on multiwan.

im using pfsense fo loadblancing ,and mikrotik for giving internet to users by hotspot and ppoe im looking for best peformance

You know, I think its fixed. It was the WNDR3400 itself. I reconnected my WRT54G and could reach it just fine.  I just flashed the WNDR3400 with DD-WRT and like magic I can reach it the admin interface on it from my LAN.

take a look on doc.pfsense.org There will be a lot of examples on doing these steps.

Thank you for your reply. Oh! That's not good news! There is not even a workaround?

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!