Selfhosted

40220 readers

1318 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago

MODERATORS

[email protected]

PFSense: Can't ping physical devices on network, but can ping virutal machines? (lemmy.world)

submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/[email protected]

9 comments fedilink hide all child comments

So, I am running ProxMox with PFSense virtualized on it, and I am having some issues with SSH and Ping access between my physical machines and the rest of the network. The two computers are running into an unmanaged switch before then connecting to the NIC port that is set as the LAN interface.

As the diagram attached hopefully helps demonstrate. The only problems are running between the two physical devices, and from PFSense to the two physical devices. The physical devices can connect to the virtual devices, and they can connect to PFSense just fine via SSH and can ping PFSense, but PFSense can not ping back, and PFSense can not SSH into the physical devices.

This whole mess is utterly confusing to me, to be honest. I still am very much a novice when it comes to PFSense as I only swapped to it about a month ago, but hopefully someone here will be able to help!

Please let me know if there is any more information I can provide. I am sure that this post is a bit confusing, but hopefully I can clarify in the comments!

Edit: Thanks to Starfer I fixed the issue! I errantly left Windows Defender on!

top 7 comments

sorted by: hot top controversial new old

[–] [email protected] 8 points 1 year ago* (last edited 1 year ago) (1 children)

pfSense comes with a fairly closed default firewall. You’ve done a decent job of describing the physical configuration of the network. What is the logical configuration? What VLAN(s) have you set up? In the firewall page, what tabs/headings are there? At minimum, you should see “Floating”, “WAN”, and “LAN”.

Also, please include the networking config for Proxmox and the pfSense VM. You can grab those details from the Proxmox GUI.

[–] [email protected] 2 points 1 year ago

Thank you so much for the response! However, it as actually much much simpler. I skipped a step in my procedures after resetting my computer, apparently, and forgot to turn off Windows Defender!

[–] [email protected] 5 points 1 year ago (1 children)

Are they Windows PCs? If so, Windows firewall blocks pings by default.

[–] [email protected] 7 points 1 year ago (1 children)

So I was in the middle of typing out "I always turn off Windows Defender for this exact reason!", but I thought better of it and checked.... turns out when I reset my computer last I skipped a step in my procedures lol

Thank you for pointing out the obvious! It is almost always helpful!

[–] [email protected] 1 points 1 year ago

No problem, happy to help! Figured this might be the case, since I run into this situation a lot at work.

[–] [email protected] 3 points 1 year ago (1 children)

Have you checked that your physical devices aernt blocking incoming ping requests? Like windows firewall?

[–] [email protected] 1 points 1 year ago

You were exactly right as well! It was Windows Defender that was causing the issue!

Thank you so much!

load more comments