Definately, I can accomplish that as I have a DHCP WAN. I appreciate everyone's comments! Very helpful!

Ah, good result! Interesting that pfSense didn't log that. I would normally expect to see 'xxxx is using my IP address' entries.

@HorstZimmermann said in [SOLVED]LCP: no reply to 1 echo request on PPPOE: but they kept denying An ISP denying they have a problem? I'm shocked!

@june said in Backup config file: I am putting it into usb mini slot in front of the rj45 which I am unplugging from my pc. Hmm, that's confusing There is no USB-mini socket on the 4100. There is a USB-micro socket but that's for the serial console only. It's not clear what you're trying to do here. Steve

@Pablomdli said in OpenVPN site to site not working both ways: The only weird things is that it gives the ip 10.0.8.0 to de office#2 openvpn client So I'd suspect, that you stated this IP in the CSO. You should enter an IP out of the tunnel network there, but it have to be one from the second upwards.

@johnpoz oops... You were correct! In previous setups I did some static routes to mimic my outgoing Juniper.... With that fixed, I can move on to the next phase. Crash and burn, I mean, testing LOL. You've been a great help as I journey to the pfSense world. Cheers.

@viragomann That was it. Once I removed the NAT entry and added the firewall rule to allow it back in, it started working. Thanks,

@stephenw10 Hi Sorry for the delay, did get some strange error but now it working :) Thanks alot for all the help

Found my issue. I had the wrong IP set in the backend. thanks,

@stephenw10 At least it's fixed now for me and looks like the missing /n after the "missing interface" comment was the culprit.

Hmm, what did you actually change? I'd expect to see that repopulated correctly after saving the config in the gui.

Yup it's that. If an interface goes down then IP addresses on the firewall change. I agree it's a bit of a big hammer and ideally could be far more nuanced. But that's what you're seeing. Interestingly there is a quirk you can probably use to stop this happening. If you enable IPv6 on the wifi interface and set it to track a WAN for v6, even if there is no IPv6, it will by ignored. Steve

@mikeehendricks said in PFSense no internet: Thanks for your help! You are welcome, glad that it helped.

Here you are just capturing all packets on the WAN to what, if anything, is there. I expect to see either the gateway monitoring pings or ARP requests at least. Probably not much else. But if you see the upstream gateway sending ARP requests for example that gives us a clue. You can run the packet capture from the webgui: https://docs.netgate.com/pfsense/en/latest/diagnostics/packetcapture/webgui.html

You can add the gateway status widget. If you have the monitoring for gateways set to something external, like 8.8.8.8, then that's a pretty definitely indication. Steve

Yes, our offering there is still in development. There are some third party tools for doing this but we don't endorse any of them.

It's that OBN rule bug as shown in the report above. Almost certainly.

That's expected on a 2100.

@johnpoz Thank you for the information. I will wait for a fix.

@c0ff33h4x Thanks for the feed back. Be assured : I would have also fallen into the trap. It is (was) easy for me to say : as soon as we know a newer pfSense is out, only upgrade packages after I've upgraded pfSense. Packages repositories should be 'per pfSense version', or, way easier : package upgrading (using the GUI) should show a warning (or even block ?) if this information is isn't 'current' and/or not showing the green "The system is on the latest version". [image: 1700640642019-e7f89436-7e5a-42ff-89df-cbd9261e87f7-image.png]