Routing LAN networks
-
@awebster This is the kind of pointless answer that is the source of my frustration. pfSense is primarily managed through its web interface, so I would expect an answer that told me where in this user interface I would need to configure my settings (a screenshot etc). I already know the principles of routing, and I never had any issues with commercial firewalls and routers, but for some reason pfSense refuses to cooperate. And how is this getting support for an unrelated product? Isn't pfSense made by NetGate? Mind you, I didn't ask for help with Hyper-V or VLAN tagging, I only answered @johnpoz question about Hyper-V VLAN tags. But I only asked and expected answers, only regarding the routing firewall rules in pfSense. I did mention the whole setup so you would better understand my configuration, but I've also mentioned last that I removed all that to avoid all potential sources of problems, tied pfSense to physical NICs and connected physical clients, all for testing. I will deal with VLAN tagging and all that later.
Your answer was no help to me as I already understand the principle of "allow all traffic". But since I failed to get it to work so I asked for some clear examples yet all I get are vague answers that are no help to anyone without intricate knowledge of the UI. I have no doubt pfSense can do what I want, but I needed to know how to set it up. Visually. You know, a screenshot? Something to help me relate to the UI of pfSense.
But no matter, I asked the same question in a different forum and immediately got an answer with a screenshot of how it was supposed to be set up and where, and it worked once I adjusted the settings for my network setup.
To @johnpoz and the others, thanks for the assistance. I understand there's a lot of posts and a lot of members asking for stuff, I was just getting frustrated that this topic went on for so long without a single clear answer of how to setup pfSense to allow traffic between networks.
Thank you for an excellent product, been using pfSense since I switched from Smoothwall some 10 years ago, but until now I never needed to do any manual routing or anything like that. And it's been rock solid.
-
@mrpijey said in Routing LAN networks:
where in this user interface I would need to configure my settings (a screenshot etc). I already know the principles of routing, and I never had any issues with commercial firewalls and routers
(my emphasis) but WOW! ...truly astonishing!
You asked for help and the forum helped but you balked, but if what you really wanted was a YouTube video showing you how to set it up, then all you had to do was search for pfSense in YouTube; there are hundreds!
First hit: https://www.youtube.com/watch?v=9kSZ1oM-4ZM no affiliation and the dude looks pretty competent.See also: http://xyproblem.info/
-
@awebster I did not ask for a youtube video, I asked for some professional help in the public forum of the company that made the product.
I did however not ask for your unprofessional attitude. Please do not reply to my threads anymore.
My issue has been resolved.
Thank you.
-
@mrpijey said in Routing LAN networks:
went on for so long without a single clear answer of how to setup pfSense to allow traffic between networks.
As already stated there is NOTHING to do for routing.. NOTHING!!!! I mean ANY router that has directly attached interfaces will know how to route between them.. PERIOD!! The only time you would have to add routing info would be if you have specific upstream networks that need to go somewhere different than your default router, or you have downstream networks via a transit network.
Your also running a firewall - so yes you will have to create a firewall rule to allow the traffic. Pfsense only put default any any rule on your lan, any other interfaces you create will have zero rules out of the box.
Your thread turned into asking about vlans and hyper-v.
You were told less than 30minutes after your post that you would have to create firewall rules to allow traffic between interfaces.
