Bandwidth Limiter does not work when Specific Gateway defined under DHCP

johnpoz

That is not a policy route.. So no that wouldn't work!

And you have opt network on the same network as UTM? Already went over that would be asymmetrical.

Change your clients to a different network than this 10.5.20 network.. Use that 10.5.20 as your transit and policy route with a outbound nat.

Even if your UTM some other network, how would it know how to route back via pfsense to get to this other network.

sanketgroup

Thanks for bearing with me and guiding me without any displeasure

Correct, my mistake for not setting up separate interface for DHCP.
Cannot create VLAN as PFSense is on VMWare workstation and On-board LAN card does not support Intel Teaming (Virtual adapter)
So I will have to arrange extra LAN port.

If i am able to manage setting up return route on UTM then setup would be like this:

OPT1: 192.168.0.1 (DHCP: 192.168.0.50-100)
OPT2: 10.5.20.1

Create Rule on OPT1:
Action = Pass /// Interface = OPT1 /// Source = OPT1 net /// question: Destination = shall it be Single Host (UTM 10.5.20.2) or OPT2 net

=============
If I am not able to create return path on UTM then create NAT in PFSense as follow:

Make OPT2 as WAN2 Port and create NAT between OPT1 and WAN2/OPT2

johnpoz

@sanketgroup said in Bandwidth Limiter does not work when Specific Gateway defined under DHCP:

Action = Pass /// Interface = OPT1 /// Source = OPT1 net /// question: Destination = shall it be Single Host (UTM 10.5.20.2) or OPT2 net

That is not a policy route.. You have to select gateway in the rule if you want to route. 10.5.20.2 would be setup as a gateway in pfsense. Did you read the link provided?

You would then be able to create an outbound nat for it.. Hybrid is all that is needed.

As to your whatever your workstation does for cards and teaming - that has zero to do with vm passing tags or not passing tags for a vlan.. But sure if you want to create another vm nic and do it that way that works too.. How you do vlans and do your connections have little to do with the logistics of the network. Pfsense doesn't care if its a vlan or a native interface.. How you tie that to the physical world is up to you.