LAN/WAN on the same subnet
-
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.
