Yup, that ^. You can't run pfSense and something else there unless both are virtualised. Steve

Nothing I can think if currently. Yeah any sort of packet loss will kill throughput.

Hmm, those are really the only config options available to you? If so you can only connect outbound. One option there is to have some external server at a public IP, say something cloud based, and connect out to that from both the internal pfSense and external clients. Steve

@trumee Glad to see you got it working. I don't have any access to a system with a PPPoE interface to test with but I'll see if I can put these notes in the instructions for others who might want to do the same.

Right so add an IPAlias at 10.0.0.100 on the pfSense LAN in that subnet. Then add a port forward (or 1:1 NAT rule) for 10.0.0.100 to the new IP on the other side of the tunnel. Steve

@stephenw10 said in Is a read-only installation possible?: And floppy disks. They were horrible, just plain horrible - that we thought it was good tech is like moving from stone knives to first copper/tin-bronze swords.. Yeah they are better than a sharp rock.. But they don't compare to high carbon steel, etc. They always failed when you needed them most, and while might work in your drive - took it somewhere and that drive alignment being a bit off and you couldn't read your disk.. The 3.5 were better than the old 5.25 that were so great when they came out. Especially when you could just use your hole punch and double the capacity ;) What was NT 3.1 like 20 something floppies.. I had bunch of old floppy drives on my shelf for quite some time, a few years back I finally said.. WTF would I ever need these for and got rid of them ;) If anyone has fond memories of such setups - its that nostalgic thing that happens when your remember shit that was horrible fondly ;) edit: "Rosy Retrospection" was the term I was looking for ;)

Then it's probably not booting correctly. Connect to the console directly and see what's happening.

@ikonomn said in DHCP Leases: I am VERY new to firewall and networks so.... Like saying " I don't have my type rating for the Boeing 737 I just bought". (pfSense being the Boeing here ;) ) That's not an issue. I'll tell you something that needs no understanding : we're all born with any networking knowledge. ( I'm even born before all this existed ) So, the extreme good news is : you'll be good for the walking down the road we all took. Take a book, see a good movie, take your time. And, as I'm curious, tell us if you found a short cut ;) edit : And keep the Boeing : I advise you to get X-Planes and the ZIBO 737 mod. Some other pay-ware tools are strongly advised, like the Navigraph / Jeppesen charts - and get these paddles and joystick out of the box. This took me two years ....... and a lot of virtual crashes. Didn't find any short cuts.

@thearm Glad you figured it out. I ended up going full Omada so I haven't had any issues like I did before but obviously couldn't chime back in with any experience.

@timm_zahn said in Unbound 1.13.x in pfSense Plus 21.05.x: uncheck the DHCP Registration box Alternately, making the lease time longer should expand/delay the restarts. DHCP renewals occur at half the lease time.

There have been some bugs in the past that could present like that but nothing recently. If it was failing to re-connect I would expect to see an error logged. Steve

Might just be how your link behaves then.

You are running thing on the firewall directly? And the application itself does not support binding to a specific address? Something that runs as a proxy and does allow binding to one source IP might allow that. Not something I've ever tried though. If you ran it on something behind the firewall you could just policy route it. Steve

@stephenw10 Perfect. Thanks for all your help. I think I have it mapped out in my head how to solve my problem. Just need to read some pfsense code to fill in the details.

@stephenw10 yeah thats what i thought, don't know why i didn't ping the whole route initially so apologies for that, i'll play on the cisco side now lol

@stephenw10 well I disable darkstat, even removed it. It did nothing. I can't see anything else packages wise that would cause this problem as I think I only really install darkstat, and cron... I found the problem. I had a freaking traffic shaper! A while nack I was fiddling with trying to get a level balance of all primary devices. Once I disabled this I could get my speeds. All that for this!! [image: 1641237191277-screen-shot-2022-01-02-at-2.26.59-pm.png] well it was a good deep dive I guess, and I sure know what I sohuld be looking for in the future. Thanks to all Guy

Hi, So you are saying that "reordering you FW rules" then putting them back the way they were fixed you issue with not being able to access the internet after the update to 2.5.2? MP

@stephenw10 It is. So here's my progression thru firewalls. I started with Untangle on a pc with multiple NICs. Then I moved to the ALL-encompassing Unifi network with Pro 4 USG, 16 port POE switch, 24 port switch, and several AP's. When they were hacked and people started shedding the USG for other options I returned to UNatngle and bought the U150. However, I had issues with networking rules not behaving. I had a WatchGuard XCS570 laying around so I put pfSense on it and it's been running beautifully until today. That's my journey and I'm not repeating the mistakes I made in the past. PfSense works, it does exactly what I need it too and I am grateful for that. Thanks again!

Well it depends who's using it. If your users are accessing Facebook and demand 99.999% uptime then maybe hold off/ But I have been using it home as my edge device (22.01 at least) for months now without any real problems. Reinstalling and recovering is relatively trivial for me though. Steve

@perjoh91 IP Passthrough?