2WAN <-> 2LAN

GruensFroeschli

OK, of course that I agree, and because of problem with routing table I add fourth interface.

That's where you're wrong.
As far as the routing table is concerned you didnt add a 4th interface because you have the same subnet on two interface.

Why dont you just change the subnet of one of the interface?
If you want to let your users change the gateway you could as well let them change their subnet.

mojo-chan

If you used two different subnets would machines on either have access to each other? I'm guessing the two LAN interfaces would need to be bridged at least…

GruensFroeschli

If you bridge them you effectively make a single broadcast domain with 2 subnets on it.
You still need a router to access from one subnet the other.
–> A bridge is kind of useless.

blak111

I already answered this. It is based on interface, but you can't have two interfaces in the same network.

mojo-chan

It seems like there must be some way it can be set up, because obviously it works if you have two separate routers on the same subnet and simply use the client machine's default gateway to select which one to use (my current set up).

Combining two routers into one would save on hardware and electricity costs. Surely there must be some way to do this, even if it's not possible in the current pfSense GUI.

BUL

Ok.. I agree with all was said..
It sound very simple… just few simple rules.. but <sigh>I will reply during weekend what I do... one old router with different subnet on PfSense side (connected to LAN2) will solve my problem.

I will rephrase problem again just in case that there is some other solution.

"How to use one PfSense box with two (or more) Wan and allow users on same subnet to choose gateway on their own."

Best regards

It seems like there must be some way it can be set up, because obviously it works if you have two separate routers on the same subnet and simply use the client machine's default gateway to select which one to use (my current set up).

I have three gateways here on my work place.. two pfsense boxes (wireless and cable) and one "solo" :-) adsl.</sigh>

blak111

The problem is in a standard routing table. You have a network that is associated to one exit interface. It works with multiple routers because each one only has one entry. It works with the extra router in the middle because the routing table doesn't have entries for the same network, just one for the original network and another for the NAT network in between.

Perry

I've been some what reading / following this thread.
So BUL isn't the end goal really that a user can switch between going out of wan or wan2?
If not. I will go away :)
If yes. It can be done by giving each user 2 IP address that they can switch between

BUL

Yep Perry.. seems that this can be done by odd/even IP "rule" as you suggest :-) odd for WAN and even for WAN2 for example.. But that raise other possible problems.

Thanks to all. This really sound simple in start. I will drop after another shot on site and probably try to find some old router for LAN2.

blak111

So if it just needs to be setup for the user to be able to switch, you could set the PPTP server up so they can connect to that to use the WAN2 and just have standard LAN traffic go out WAN. Just set the firewall rule in the PPTP server to use the WAN2 as the gateway.
If they are using windows, then it would be as simple as clicking a VPN shortcut for less tech inclined users.

I know this works because I've done this to allow users access into a network attached to a pfSense machine.

Sorry, I wasn't aware that you were trying to give users the option to switch connections themselves.

BUL

Heh, this is nice. I will try it on site.

Thanks blak111 :-)

mojo-chan

The only problem with changing IP addresses on clients is that it tends to cause some temporary confusion on the network, particularly with Windows file shares.

blak111

that's what the pptp connection would be for. you still wouldn't lose your local IP

Perry

The only problem with changing IP addresses on clients is that it tends to cause some temporary confusion on the network, particularly with Windows file shares.

This made me think of some old bat files :)


netsh interface ip set address LAN-connection static 192.168.1.110 255.255.255.0 192.168.1.1 integer
netsh interface ip set dns LAN-connection static 192.168.1.1


@echo off
echo Enter username
color 01
set /P Username=
echo Enter Password
set /p Password=
cls
color 08
net use Z: \\192.168.1.200\data %Password% /user:%Username%
net use i: \\192.168.1.200\install