same issue here pfsense 2.1.5 fesh install. after many tests/reinstalls I isolated the issue to igmp proxy. as soon I enable this the shell does not work any more most commands fails thinks like ls cp… etc to have the system back 1 boot on single user mode. 2 mount a fat32 usb mount -t msdosfs /dev/da0s1 /mnt 3 copy /conf/config.xml /mnt/config.xml 4 edit the file on the usb. (This is because I can't get the vi to work in single user mode. remove the section  5 copy the file back to the system. repeat step 2 and reverse 3 Reboot the system and it should be back alive without igmp proxy. sorry there might me mistatakes since I'm new to pfsense and freebsd just a couple of weeks working with this. please does any one know how to fix this igmpproxy issue. I could deal with all the other issues I have but without igmp proxy there is no iptv and I can't live with that. Regards.

Why do people complain before rebooting?  Its trouble shooting 101.

@stephenw10: Do you see any errors on the Status: Interfaces: page? If you run 'top -aSH' at the command line what does it show? Steve None, i have been looking at various possible errors on the interfaces, but nothing.

You might want to take a look at the 2.2-BETA snapshots.  The 2.1.x code based on FreeBSD 8.3 is quite old and a lot of things have been update din the newer snapshots.  Release candidate is coming soon with a final release early in the new year from what I've read recently. http://snapshots.pfsense.org/

thanks Steve makes a lot more sense now its working as I was beginning to think it was my ability of understanding and following instruction but now I have a much better understanding and proving to be a rather powerful tool three cheers for the community!

Check the ppp log, is it trying to connect? Any errors shown? Is the parent interface showing a connection? Which NIC is it? Steve

Got that. But after warmstart the same error is still present. And I also see more interfaces as cuaU0.0 (which should be the modem?!) [image: fiKBbPd.jpg] EDIT: OK, I was to fast. It works now, thank you! :)

Install bandwidthd, goto Services->Bandwidth and enable it on LAN. Wait a few minutes, click the Access Bandwidthd tab and the graphs should be there.

They are close to an RC build, so while they say you shouldn't use it for production purposes, it's getting very close to release.  Lots of stuff has been fixed, lots of new goodies added.  If you're new, I might recommend that you start off with the new base instead of using the much-older FreeBSD 8.3-based pfSense.

What are you trying to accomplish?  Pfsense would be meant to replace your soho router, yes it can be run in vm.  I run mine on a esxi host and works great for my whole network. You could then leverage your current wifi router as just an AP for your network.

5353 is mdns..  You sure that is chromecast??  I would think that is most likely some other apple type device on your wifi network.

Happy to help  ;)

Thanks allot! ;)

Thank you!

Excuse me sir, how to solved this problem (update windows with ssl bump squid3-dev)?  :)

Unless it's very low traffic you're going to need a syslog server of some sort then. Steve

Thanks for your help! I configure all as  your words but not lucky, dhcp not work. From wan net able ping to lan, ok. From client, i configure manually with ip 192.168.3.10 and gateway 192.168.3.2 (interface wan2 of pfsense), and work ok, is possible ping to lan and work internet. The problem is dhcp, not work and is active in pfsense (interface wan 2). Assing me ip generic: Log of pfsense register this: Nov 25 20:00:36 WAN_VODAFONE_4G Icon Reverse Resolve with DNS  Icon Easy Rule: Add to Block List 169.254.34.122:137 Icon Reverse Resolve with DNS  Icon Easy Rule: Pass this traffic 169.254.255.255:137 Any Ideas? I can´t to admin menu of Router. Thanks. Regards.

Exactly, these are real 'hardware' switches. They just have an open bootloader for the SoC that runs the management firmware so you can load an alternative if you so desire. Exactly like OpenWRT on a SOHO router just with an emphasis on switching and much much more powerful hardware.  ;) Makes me think that an OpenWRT switch might not be far off at all. Steve

If you are happy for (want) all devices to be able to talk to each other on a single LAN, then you do not need to have different actual interfaces. You can just assign static-mapped DHCP for each "known" device to put them in a particular piece of the 1 big subnet. Then leave the "unknown" guest devices in the ordinary DHCP pool. Then your rules can allow/block differently for the different parts of your 1 subnet. But that provides no real security - any guest can set an IP address themselves, rather than taking DHCP, and effective put themselves in a "more trusted" part of your subnet/rules. So you need to decide what is your internal known/trusted network, and what are guests and other public stuff. I suspect that you will want printers and other local network resources (NAS, your own file server…) on the trusted LAN along with your home computers, so they all just see each other. Many people would end up with: LAN - your own home computers, printers, NAS, file server, an AP for your home WiFi. Guest - and AP for your friends to use, with no (or very controlled) access to LAN and more generous internet access DMZ - anything you have that provides public services (public web site...) WAN - 1 or more actual uplinks to your ISP/s So you might end up with 3,4... interfaces on pfSense. If you have that many physical NICs, then easy. Otherwise you need a VLAN switch also. Then pick some private address space for each of LAN, Guest, DMZ...