@Dave: Hi, First day with pfsense. I'm trying to configure SMTP notifications. My mail server is behind a NAT on 10.10.10.2 and uses SSL on port 62933. I can connect to the SSL service over telnet from pfsense, but the pfsense gui says "Could not send the message to user@host.localdomin – Error: could not connect to the host "10.10.10.2": ?? Do I need to load the SMTP server (self-signed) into pfsense somehow? If a self-signed cert is being used, yes it will have to be trusted by pfSense.  There is a thread or two in the forums that should have enough how to info. https://forum.pfsense.org/index.php?topic=115884.msg644702#msg644702 https://forum.pfsense.org/index.php?topic=115884.msg644709#msg644709

Thanks for answering my dumb question all!

I've got a number of voip setups using voip.ms as the DID provider. I use pfSense as the central router and I've never had to "register" the router, just the end device(s). In most cases I setup an Asterisk box to handle local phones, but I have registered phones directly. In many cases, pfSense has not needed any special configurations at all, others required a few NAT tweaks depending on the ISP at the local end.

It's actually easier said than done… I didn't find the option of setting the gateway, and wouldn't have been able to work out how to do this without this post:- http://community.virginmedia.com/t5/QuickStart-set-up-and/SuperHub-2-Cannot-change-LAN-IP/td-p/1870936 but I do have it working now, and I guess it makes a decent wireless access point.

I might need to rephrase the question since I got no answer so far. Is it possible to forward a tagged VLAN (7) from WAN to an INTERNAL OPTx in pfsense? And if so, how? I have looked in QinQ and Brdige, but that did not work so far…

Yep, seems I mixed it up, over all my setup was 750, I was shooting for power efficient and long term setup.

Make sure you have your default LAN rule setup. Firewall->Rules->LAN  

Agreed. What's the point of implementation if it does not do what it's supposed to do? Implementation of SMART is supposed to report prior to failure. NetGate/PfSense guys, this should be fixed or removed from the GUI. I'd personally like to see it fixed. I'd also like to see some kind of email reporting if a rule had been triggered. Say in this case, if a CAM error had been seen in the system logs, then the system would email.

Hello, I attached a "Packet Capture": it seems that the communication with radius server never starts. – Regards, Marco Mangiante [image: vpn_vdf_pfsense_client.png] [image: vpn_vdf_pfsense_client.png_thumb]

All of the NIC's interrupted pinned to the same CPU is a strange setup. Could be more of a corner case than a bug, but it does sound undesirable.

pfSense itself does not have an HTTP(S) timeout, only a TCP timeout, which defaults to 24 hours. If you're running a proxy, your proxy may need to have the HTTP(S) timeout configured.

I would do a clean install and re-apply the config. The only barf you are likely to see is maybe pfSense will complain about the NIC's and you'll need to re-set that bit.

Thanks for the info! I will try this first thing tomorrow-

General For things that do not fit into one of the more specific categories below.

I bought a T-shirt and Polo.  Pretty cheap all things considered.

Thank you :)