it's a 'feature" from our fruity friends ;)

I managed to install the sudo package as I'm accessing remotely and don't have RSA Keys setup for the root user.

The IGMP Proxy was restarted from the command line with:

#sudo pfSsh.php playback svc restart igmpproxy

I then played around with the cron job tool and have managed to schedule a working IGMP Proxy restart at 01:00 every morning with the following command ran as root:

/usr/local/sbin/pfSsh.php playback svc restart igmpproxy

Hopefully now the 2 channels which kept going off after a couple of days (Nickelodian and Disney) will stay working and my wife will be off my case.

Thanks a lot!!

@priller:

Are you trying to reach your CM interface via the commonly used http://192.168.100.1 address?

That just works for me with no special configuration.  Always has.

Well now I feel like an idiot.  I just assumed that wouldn't work so I didn't even try it.  It works fine, thanks.

The LAN IP can be used for DNS if you have the DNS forwarder (Services->DNS Forwarder) turned on. If you want to make use of the DNS forwarder make sure it's on and change the DNS address given to DHCP clients in the settings of the DHCP Server (Services->DHCP Server) to the LAN IP address.

https://doc.pfsense.org/index.php/Port_Forward_Troubleshooting

vSphere.

Create an "Alias" and use it as "Source" ;)

https://doc.pfsense.org/index.php/Aliases

A Reading at the Doc's wouldn't hurt you :P

https://doc.pfsense.org/index.php/Main_Page

You could put pfsense in a bridge with filtering turned off and some of the packages mentioned in the link.
I am not sure if they work on the bridge interface or LAN/WAN or if at all. But it is worth a shot.

A transparent proxy is invisible for all intents and purposes to the client

You could log all traffic, but when it is encrypted you will just see a garbled mess

You will not be able to see encrypted traffic without modifying the clients

A 1gb port can do 1gb both ways, which is 2gb/s.