VLAN traffic problem

[rickygm]

Hi forum , I have a problem with my pfsense, I'm doing vlan routing with pfsense and a 2960g cisco, I have 3 vlan defined by: vlan 11, vlan12, vlan13, those same on the cisco 2960g switch, I have no problems with the vlan 11 and vlan 13 se communicate well, the problem is with the vlan 12 wifi user, if I want to get to the vlan 13 pinging did not arrive, and I have allowed the traffic from vlan 12 to 13, I make a tracert from a pc in vlan wifi to another pc from the vlan 13 and I see that the wifi catches the public ip of the pfsense not the private ip of the vlan wifi.

in vlan 12 i have a dhcp running with the same pfsense

gw vlan user : 192.168.13.1
gw vlan wifi : 192.168.12.1
gw vlan server: 192.168.11.1

I hope some help , regards

 9.26.39 p. m..png)
 9.26.39 p. m..png_thumb)

[Grimson]

Any floating rules?

Also if you ping a windows machine you have to turn off/reconfigure the windows firewall, by default it blocks pings from different subnets.

[rickygm]

@Grimson:

Any floating rules?

yes, this is the use to limit the bandwidth to some users.

Also if you ping a windows machine you have to turn off/reconfigure the windows firewall, by default it blocks pings from different subnets.

my windows users firewall is off

 10.03.04 a. m..png)
 10.03.04 a. m..png_thumb)

[johnpoz]

What interfaces and directions do you have those floating rules setup on.  Your forcing traffic out your wan it looks like so vlans would not be able to talk to other vlans if they trigger those rules and get forced out the wan.

"I have 3 vlan defined by: vlan 11, vlan12, vlan13, those same on the cisco 2960g switch"

How is that?  If you have a downstream router then pfsense would normally only have a transit network to the downstream router, etc.  You wouldn't need downstream vlans on pfsense.

It might help if you posted a diagram of your network so we could see how these vlans are actually connected to your network and their routing path if you have a downstream router in the mix.

[rickygm]

@johnpoz:

What interfaces and directions do you have those floating rules setup on.  Your forcing traffic out your wan it looks like so vlans would not be able to talk to other vlans if they trigger those rules and get forced out the wan.

vlan 11: 192.168.11.0/24
vlan 12: 192.168.12.0/24
vlan 13: 192.168.13.0/24

if I disable the floating rule, I have communication between the vlan, the problem is that some ip are free, but I limit them with a 4Mb bandwidth.

"I have 3 vlan defined by: vlan 11, vlan12, vlan13, those same on the cisco 2960g switch"
@johnpoz:

How is that?  If you have a downstream router then pfsense would normally only have a transit network to the downstream router, etc.  You wouldn't need downstream vlans on pfsense.

I do not have a router, it's a cisco switch 2960g L2

It might help if you posted a diagram of your network so we could see how these vlans are actually connected to your network and their routing path if you have a downstream router in the mix.

pfSense –-> Switch l2 ---other switch

[johnpoz]

Oh my bad… Sorry I saw cisco 2960 which can do L3 and figured you were using it as L3 and routing on it.  If your just using it as L2 that yes your vlans on pfsense make more sense ;)

"the problem is that some ip are free, but I limit them with a 4Mb bandwidth."

That fine you can run them through a limiter.. But when you force them out a specific gateway with that rule, then they can not get to other networks that gateway can not get too.

So in your rule with quick setup it since floating are evaluated before rules on the interface it would force say traffic from lan device out the wan - which wouldn't be able to get to vlan12 for example.  Just don't set the gateway on your rules or set them only when they are to non local networks could you force them out a specific gateway.

[rickygm]

@johnpoz:

Oh my bad… Sorry I saw cisco 2960 which can do L3 and figured you were using it as L3 and routing on it.  If your just using it as L2 that yes your vlans on pfsense make more sense ;)

Yes.

"the problem is that some ip are free, but I limit them with a 4Mb bandwidth."
@johnpoz:

That fine you can run them through a limiter.. But when you force them out a specific gateway with that rule, then they can not get to other networks that gateway can not get too.

So in your rule with quick setup it since floating are evaluated before rules on the interface it would force say traffic from lan device out the wan - which wouldn't be able to get to vlan12 for example.  Just don't set the gateway on your rules or set them only when they are to non local networks could you force them out a specific gateway.

I'm trying to understand this a bit better, you can give me an example of a rule in pfsense "screen shot" :)

[johnpoz]

Example of what exactly? a floating rule setting a client to use a limiter while still allowing it to access the vlans.  Do you want the limiter in place all the time or only when they go out the internet?

[rickygm]

@johnpoz:

Example of what exactly? a floating rule setting a client to use a limiter while still allowing it to access the vlans.

as I could continue to limit my bandwidth and be able to communicate with the other vlan, using your gw by default.

for example for vlan 12 the gw is 192.168.12.1, vlan 11 gw 192.168.11.1

@johnpoz:

Do you want the limiter in place all the time or only when they go out the internet?

my current floating rule limits the bandwidth when they go out internet

[johnpoz]

No your rule FORCES them out the wan gateway..  If you want that rule to only be used when going to the internet, and not be applied when going to other vlans. Then change the dest to only be the internet..

You can do that with dest rules set to NOT (!) your local networks.. Or create say an alias that contains all the rfc1918 space and use dest NOT that alias.. So that rule only triggers when they are not going local - or internet.

[rickygm]

Ok , I'll try