@stephenw10 ^exactly but if your multihoming with a SAN only network or a backup network. Where the server/host has its own private network with say your nas or backup server that is easy to make sure no routing problems. But yeah as Steve states - lots of issues with users just messing it up.. And I wouldn't multihome a box into multiple networks that other devices are going to talk to it from, etc. Example I have my pc and nas multihomed so they can talk to each other over 2.5ge - but this is an isolated network that only they are in. These IPs have no gateway.. Its just a storage network.

Can that test client ping the pfSense internal IP address? Can it ping the pfSense WAN IP address? Sounds like the client might lost it's default route. Is it using a static IP? Steve

@stephenw10 ok ill fix that in a few after we try to fix this other issue don't want to change to anything at one time

You can open a feature request: https://redmine.pfsense.org/ Looks like apprise is written in Python. It also looks like people have run it in FreeBSD but I don't see a FreeBSD port for it which would make it far easier to create a package from. There would also be some PHP work to integrate it with pfSense. Steve

@bingo600 thank you, Bingo. Following your idea, I was able to configure the LocPrf for the BGP. Here the link that I read https://docs.frrouting.org/en/latest/bgp.html Thanks again, Mauro

In that sort of setup you just need to add port forwards in pfSense to whatever you need to access. You can't just route between them because your clients are using the ISP router as their gateway. I doubt you can add vlans or static routes to that router. Steve

@stephenw10 Thank you, Steve Have a nice weekend. Mauro

@jarhead he left.. Deleted his account..

@gabacho4 said in SG 5100 WAN IP no Internet: https://docs.netgate.com/pfsense/en/latest/troubleshooting/connectivity.html Those docs are good. But in my case not too fruitful. The WAN IP addressing and DNS is under Status>Interfaces. My WAN is clearly labeled as "WAN Interface (wan igb0)" Those labels help a lot! I had configured my PFSense as a client to ExpressVPN a month or two back. I didn't get the full config they way I wanted and decided to come back to that project later. Well the service started up again on reboot and that kicked me off the network. It's not supposed to work that way, but it does right now. So stopping that service gives me the desired result. I think I may just clear that config and come back and do the whole thing when I can get it done. Anyway, I think that resolved it. I can ping public IP addresses now and google.com. Thanks!

@lassard Really appreciate your help. Thank you.

Yes, I would expect that to work.

SOLVED! After opening a support contract with Netgate, my problems were solved in short order. They had me send my config file to them and emailed a response with a few minutes. Thanks to all who responded. Bart

That value is unused as far as I know. It's an ugly message but it does nothing. That said it looks like a simple enough fix. Open a bug report. Or a pull request. Steve

@freek_box said in Ping on name not working: when I trie to do a ping on it from the VPS it says: Name or service unknown: ping mirror1.freepbx.org/modules/packages/pm2/pm2-16.0.8.tgz.gpg You cannot ping a file name, but only a host name or an IP address. So you can at best ping mirror1.freepbx.org

Those are just local broadcast/multicast things, normal for it to do on the network segment. Not indicative of a problem. It's how it finds other devices on the network and vice versa.

@heper I just would like to squeeze every bit of performance. I'm running suricata, pfblocker and AdGuard Home inside my pfSense. I think I was able to bring back the bursting experience by making sure all offloadings are disabled and leaving to default, parameters that impact security. The advise found in the link above I think is so strict. Speed is very stable now and it's bursting to ny subscribed speed

@bmeeks Thanks, you're right. Will check out which rule is blocking VPN.

Hmm, I think I just googled it. Like: https://asnlookup.com/organization/facebook/

Anyone still hitting this who can test there is a patch now available here: https://redmine.pfsense.org/issues/13671#note-4 We need feedback there to confirm it. Steve

There's a patch on the ticket now available if anyone can test it. If we get some positive feedback there we can commit it for 23.01. https://redmine.pfsense.org/issues/13671#note-4 Steve