LAN/WAN on the same subnet
-
Hello,
Here's another topic on a subject you love as i can see on all the similar topics i've read.
I'll try not to pronounce the word b*****.I'm running an already configured pfSense 2.2.1 on an Alix APU board with Dual-WAN and DHCP relay.
Here's my setup :
WAN1 : re1 (DHCP/DHCP6)
WAN2 : re2 (DHCP/DHCP6)
LAN : re0 (192.168.1.1/none)
WLAN : ath0 (none/none)DHCP is relayed to our AD server on 192.168.1.102.
WLAN is working, i set it to 192.168.4.1 with DHCP server and everything was fine.I'm trying to set WLAN and LAN on the same network, so wired and wireless client are getting ip from our DHCP server.
I created a b*****0 with LAN and WLAN.I can't assign this interface to LAN since LAN is a member.
I can't assign this interface to re0 since re0 is already set to LAN.I've set : net.link.bridge.pfil_member=0 and net.link.bridge.pfil_bridge=1
I know trying this on a working pfSense is tricky but there must be a way to do it without loosing connectivity ?
Thanks :)
-
WLAN is working, i set it to 192.168.4.1 with DHCP server and everything was fine.
I'm trying to set WLAN and LAN on the same network, so wired and wireless client are getting ip from our DHCP server.Ever heard of DHCP relay? It works. Configure the DHCP server to give out IPs in 192.168.4.0/24. Relay the clients to it. Done.
-
I'm using DHCP relay as i said and it works well.
-
Hmmm, the point of this exercise is exactly what, then? You'll end up cut off the firewall sooner or later when trying to shuffle and bridge stuff you are sitting on. As a bonus, you'll probably end with screwed configuration as well.
-
I'm trying to have my lan and wlan interfaces on the same network : 192.168.1.0/24.
-
I'm trying to have my lan and wlan interfaces on the same network : 192.168.1.0/24.
Why? Because it works too well now? ::)
Either get a spare management interface or start from scratch with just WAN assigned and configure from WAN.
-
Because i want to ? Isn't that enough ?
The only way to make wlan work in that state is to set it to another network like 192.168.4.0/24.
But this way dhcp relay would give them an 192.168.1.X ip from 192.168.1.102 with a gateway on 192.168.1.1. So connectivity will fail.
And since i can't have dhcp relay on lan AND dhcp server on wlan, i don't have a workign solution.I can probably can set a spare management interface using an usb ethernet adapter, that's not an issue.
-
But this way dhcp relay would give them an 192.168.1.X ip from 192.168.1.102 with a gateway on 192.168.1.1. So connectivity will fail.
Uh, what? Configure a new scope (pool) on the DHCP server for 192.168.4.0/24. Use that scope for the WLAN clients. It works perfectly fine with the AD DHCP.
-
Yeah, it's a working solution, but i'd prefer having everything on the same subnet.
But i guess i can use it that way and start from scratch another time.
-
You can try from WAN if you don't have a spare NIC handy. From the interfaces that are going to get bridged, it's basically a no go. Reliably ended up cut off everytime I tried. The console needs to grow a bridge creation feature.
-
I'll try from wan outside office hours.
From this setup :
WAN1 : re1 (DHCP/DHCP6)
WAN2 : re2 (DHCP/DHCP6)
LAN : re0 (192.168.1.1/none)
WLAN : ath0 (192.168.4.1/none)I should go to this ?
WAN1 : re1 (DHCP/DHCP6)
WAN2 : re2 (DHCP/DHCP6)
LAN : BRIDGE0 (192.168.1.1/none)
WLAN : ath0 (none/none)
Bridge0 : re0
-
-
I should go to this ?
WAN1 : re1 (DHCP/DHCP6)
WAN2 : re2 (DHCP/DHCP6)
LAN : BRIDGE0 (192.168.1.1/none)
WLAN : ath0 (none/none)
Bridge0 : re0The bridge should consist of WLAN (ath0) and LAN (re0).
It won't let you make a bridge with one interface. Make the bridge with LAN and WLAN first, then change LAN to the bridge interface.
Good luck.
-
I know that :)
My question is what to do with the LAN interface which is currently on re0.
-
Make the bridge with LAN and WLAN first, then change LAN to the bridge interface.
-
Problem is, bridge0 can't be set on lan interface since lan is already a member of bridge0.
You mean bridge0 on re0?
-
You mean bridge0 on re0?
Huh? What? You just told us that re0 is your LAN… See, this is exactly why I told you that you should restart from scratch. (Not to mention how utterly pointless this whole thing is.)
-
pfSense interface named LAN is currently set on re0 port.
Ok, i have my answer :
http://www.stephenyeong.idv.hk/wp/2010/03/pfsense-wireless-bridge-working/Forgot one step.
WAN1 (DHCP/DHCP6) : re1
WAN2 (DHCP/DHCP6) : re2
LAN (192.168.1.1/none) : BRIDGE0 (OPT1+WLAN)
WLAN (none/none) : ath0
OPT1 (none/none) : re0Changes made through WAN and now it's working fine :)
Thanks.
