Hi, I run 2.3 Update 1 with my APU2 without any problem. Uptime: 13 Days 02 Hours 32 Minutes 51 Seconds Following packages are installed: Backup sysutils 0.4_1 Cron sysutils 0.3.6_2 RRD_Summary sysutils 1.3.1_2 Shellcmd sysutils 1.0.2_2 Temp is always 56.6 °C and very stable.

Pull request https://github.com/pfsense/pfsense/pull/2967

Here is a gif of the start of the process… [image: Alix-231-upgrade.gif_thumb] [image: Alix-231-upgrade.gif]

thanks

Hello. https://forum.pfsense.org/index.php?topic=111514.msg623303#msg623303 http://www.javcasta.com/?smd_process_download=1&download_id=10725 Regards.

Yes - everything is working for all clients on LAN - I am just not able to open the HTTP or HTTPS on the Comcast box.

validate the fqdn your trying to go to resolves to what its suppose to resolve too server.domain.local simple ping, nslookup, dig, drill whatever your fav dns query tool is so you can see the answer.  Ping works in a pinch to what the name resolves too.  Be it answers or not.

Thanks. The install, then upgrade to 2.3_1 went off without a hitch. I previously had pfSense installed onto a very, very old and cheap SSD and it ran without issue for 2 years, right up until the drive failed. Then I switched to Live CD, which was just fine for my use, then that was discontinued, so I tried nano, that was miserable. I'll see how long this cheap SanDisk SSD lasts. I've had a lot of their flash media over the years, and nothing has ever failed. Still even use my 15 year-old 256 MB flash drive for transferring small files.

@johnpoz: You mean you didn't have to leave it off and unplugged from power and ethernet for 15 minutes??  You don't freaking say.. wTF… And what you don't have UPnP enabled -- no shit, clearly mister expert was sure that xbox and ps4 both require UPnP to even get on the internet..  Just flabbergasted he didn't have clue one to what he was talking about ;) heheheh LOL!

Sounds like an OpenVPN setup issue. Perhaps try over in the OpenVPN forum with some more details of your setup.

It only restores the section you request.

@jbhowlesr: I would suggest that if you send a request to be delisted from the blocked list, that you include some data about your network to include any finding of infected machine, hijacks etc and exactly what you did to fix the problem and steps taken to ensure it doesn't happen again. Typically when providing this level of detail, companies who list spam offenders will give extra consideration since you put in the effort on your end to solve any issue. Considering working with them to get off the list. Otherwise, if you only ask to be removed with as little or few words as possible; your request will sound less than genuine. The problem in this case has nothing to with sending spam. The blacklist in question is for sites with botched MX records that fail to for example to provide A records for hosts listed in the MX records for the domain.

Hy! Only thing I know: https://forum.pfsense.org/index.php?topic=99938.msg556842#msg556842 …so: apparently not at that time...

When you ssh from pfSense to a remote system over an IPsec tunnel, the connection is sourced from the firewall itself. Your IPsec tunnel has a phase2 entry that declares certain traffic interesting to IPsec and thus "routed" over the tunnel. Try using the -b IP-Address option to ssh with IP-address being an address on the firewall that is included in the phase 2 entry. If you have a LAN interface of 192.168.1.1/24 and a remote network of 172.16.1.1/24 and a phase 2 between those networks try ssh -b 192.168.1.1 172.16.1.1 I do not know if this will work. I have never tried it. I generally have a management workstation on the network that is included in the IPsec Phase 2 entries from which I do these things. Doing it from the firewall can be problematic. Linux and FreeBSD are free. So is XenServer and ESXi.

We don't test each release on all available hardware.  That would be a LOT of work.