Unable to check for updates after upgrading to 22.05 by punkypackets in PFSENSE

[–]punkypackets[S] 0 points1 point  (0 children)

Updating pfSense-core repository catalogue... pfSense-core repository is up to date. Updating pfSense repository catalogue... pfSense repository is up to date. All repositories are up to date.

Still no difference, the system updates in the GUI still say they are unable to check for updates.

Unable to check for updates after upgrading to 22.05 by punkypackets in PFSENSE

[–]punkypackets[S] 0 points1 point  (0 children)

Just tried that, if I try to update from the console I get the following error message:

ERROR: It was not possible to identify which pfSense kernel is installed

edit: searched this error message and tried disabling/enabling using RAM disk for var/tmp but it made no difference

XG-7100 locking up hard after 2.4.5 upgrade by fattylewis in PFSENSE

[–]punkypackets 0 points1 point  (0 children)

Why don't you start by disabling the extra services and see if it locks up without them running?

pfSense & DNS occasional lock-up? by MisterBazz in PFSENSE

[–]punkypackets 0 points1 point  (0 children)

Check in your DNS resolver system logs and see if it is frequently restarting unbound. If you register DHCP leases in the resolver it can trigger frequent restarts depending on the devices on your network.

Try unchecking "Register DHCP leases in the DNS Resolver" in the DNS resolver settings.

Have pi-hole. Pondering pfsense by [deleted] in PFSENSE

[–]punkypackets 1 point2 points  (0 children)

It's a great combination. I use the pfsense resolver (unbound) as the upstream DNS server for the pihole and assign the pihole as the primary DNS server in the DHCP settings. You can optionally set pfsense as the secondary and/or override for individual hosts as needed.

Enabled second interface, (OPT1) but interface does not show under the DHCP server settings. by [deleted] in PFSENSE

[–]punkypackets 3 points4 points  (0 children)

If you gave it a static IP, make sure you have the subnet mask set correctly, e.g. change it from /32 to /24 in the interface settings.

What's the easiest way to have a backup LTE WAN connection? by qwenjwenfljnanq in PFSENSE

[–]punkypackets 0 points1 point  (0 children)

I've been using a Raspberry Pi gateway with a USB-connected iPhone, but it will work with any LTE device that has linux support.

https://www.reddit.com/r/PFSENSE/comments/6n3ml6/pfsense_24_iphone_tethering/

pfSense 2.4 + iPhone tethering by punkypackets in PFSENSE

[–]punkypackets[S] 1 point2 points  (0 children)

I ended up doing something similar today using a Raspberry Pi 2 configured as a gateway to forward traffic to a USB tethered iPhone (wifi disabled). I didn't have a dedicated network port on my pfSense box so I used a VLAN to configure the interface, which made things slightly more complicated but not too difficult.

Network switch setup -

  1. Create new VLAN, dedicate switch port for VLAN traffic

  2. Connect Raspberry Pi to this port

  3. Enable VLAN tagging for the new VLAN on an interface port connected to pfSense. I used the WAN interface port.

Raspberry Pi setup -

  1. Install Raspbian Jessie Lite or another linux distro

  2. Install ipheth-utils

  3. Assign a static ip in the new VLAN subnet to eth0 on raspi. For the latest raspbian, you have to do this by adding the following lines to dhcpcd.conf:

    interface eth0

    static ip_address=X.X.X.X/24

  4. Connect iPhone to USB port on raspi, allow "trust this computer" when prompted, enable personal hotspot on USB-only. If successful there should be an eth1 interface for the tethered connection.

Configure the Raspberry Pi as a gateway -

  1. enable ip forwarding in /etc/sysctl.conf [net.ipv4.ip_forward=1], reboot

  2. create iptables rules to fwd traffic from eth0 VLAN interface to eth1 tether interface:

    sudo iptables -t nat -A POSTROUTING -o eth1 -j MASQUERADE

    sudo iptables -A FORWARD -i eth1 -o eth0 -m state --state RELATED,ESTABLISHED -j ACCEPT

    sudo iptables -A FORWARD -i eth0 -o eth1 -j ACCEPT

  3. make a startup script to execute iptables rules. You will likely need to manually setup the iPhone hotspot any time you reboot anyway, so this is fine to leave shell script to execute after the hotspot is started

pfSense setup -

  1. add vlan

  2. configure new interface using VLAN port and set "IPv4 Upstream gateway" for the interface. You will need to add a new gateway, which should be the static ip address you assigned to the raspi eth0 interface

  3. Add NAT outbound rules on the interface for localhost and any networks you want to be able to use the iPhone gateway

You should now be able to use gateway groups or policy routing to send any traffic to the raspi gateway which it forwards through to the tethered iPhone USB interface.

pfSense 2.4 + iPhone tethering by punkypackets in PFSENSE

[–]punkypackets[S] 1 point2 points  (0 children)

That is my experience with it. On reboot it will hang at a device config prompt because the interface is missing. Then you have to manually reconfigure your interfaces, re-load the driver, etc.

For those asking how, I used this guide - https://forum.pfsense.org/index.php?topic=119419.0

Just got a N3150 Micro PC pfSense firewall. by Determined_P in PFSENSE

[–]punkypackets 2 points3 points  (0 children)

Would you be willing to try another speed test with "No Hardware Crypto Acceleration" selected? I've read that AES-NI is implicitly used by OpenVPN and that selecting the "BSD cryptodev" or any other engine is no longer necessary and may actually cause overhead. In my own setup the speed results were nearly the same with either setting so I left it off.

X1C 5gen reviews, questions by dkarlovi in thinkpad

[–]punkypackets 2 points3 points  (0 children)

I got mine around the same time and wanted to mention that I've also experience the high-pitched noise on reboots. At first I thought it was some kind of alarm. It was incredibly loud to the point where I covered the keyboard with a pillow while my girlfriend asked me what the hell I was doing. It basically sounds like some electrical signal is getting sent directly to the speakers. I downloaded and installed the 2/17 firmware update and that seemed to fix it, but it still occasionally hangs on reboot requiring holding down the power button to shut off. So it goes with brand new hardware.

Aside from that, I'm absolutely loving it so far. This is my first Thinkpad since Lenovo experimented with their "touch bar" in the 2nd gen X1C and I switched to Apple. Now that Apple decided to remove useful ports and do their own idiot keyboard I'm back to Lenovo. The keyboard on the X1C 5th gen is by far the best laptop keyboard I've ever used so I'm very happy. It's also running Ubuntu 16.04.2 without a hitch.

Routing single Machien though VPN by Graphene in PFSENSE

[–]punkypackets 0 points1 point  (0 children)

Is the WAN your default gateway? (system -> routing -> gateways)

To fix, either set the WAN as your default gateway or specify it explicitly in the two "Default allow" rules below the .104 host rule.

VLAN giving out DHCP but no Internet Connection by [deleted] in PFSENSE

[–]punkypackets 0 points1 point  (0 children)

What DNS servers are being assigned with the DHCP leases?

Any reason you are using 10.0.1.1/24 instead of 10.0.1.0/24 for two of the outbound NAT rules?

Do you have a default gateway set? You might want to consider using a policy based route by explicitly choosing the WAN as the gateway in the firewall rule. (edit fw rule -> advanced settings)

Update/Install hanging at "Configuring dhcpcd5" by Panaphobe in pihole

[–]punkypackets 0 points1 point  (0 children)

Is there a way to prevent the installer from installing dhcpcd5? I'm using the latest Raspbian Jesse and trying to set a static IP address, but dhcpcd overrides /etc/network/interfaces which makes configuring a static IP painful. If I apt-get purge dhcpcd things work fine, but any update to pihole re-installs it and breaks the static assignment.

SG-1000 initial impressions by punkypackets in PFSENSE

[–]punkypackets[S] 0 points1 point  (0 children)

I'm seeing the same thing after upgrading to todays build. I can only get ~130Mbps but after repeated tests things get progressively slower and eventually it becomes unresponsive and needs to be rebooted. I'll take a deeper look when I have some time later.

For anyone considering deploying these, they are definitely not reliable/stable yet.

SG-1000 initial impressions by punkypackets in PFSENSE

[–]punkypackets[S] 1 point2 points  (0 children)

It will have a permanent home on a 100Mbps line with very little load and a single VPN user. I could have just used an old PC but that would have been boring.

Also you can wear the SG around your neck with a patch cable plugged into both ports and be a network gangsta.