Retired > 2.0-RC Snapshot Feedback and Problems - RETIRED

HOW TO - EASY (wireless) bridge configuration in 2.0

(1/7) > >>

gnhb:
------------------- Updated May 2, 2010 ----------------
SKIP DOWN to my next POST to see step by step instructions

Hello All,

I read this post http://forum.pfsense.org/index.php/topic,12101.0.html titled "wireless not giving IP when bridged with LAN" and it took me a long time to figure out how to implement it on my box, so I offer this clarification.

I'm running 2.0-ALPHA-ALPHA-nanobsd built on Sept 15th, 2009 on an ALIX 2D3 board.

I have attached below an image of my "interfaces assign" page from the web GUI. This setup defines OPT1 (renamed WLAN) as my wireless interface, OPT2 as one of my 10/100 interfaces.
The bridge interface includes OPT1 and OPT2.
I didn't have to create ANY new firewall rules for this to operate smoothly. Clients on the wired LAN or WLAN can get to the internet and can get to each other.

The second image is from the System => Advanced => System Tunables page.
The DHCP server setting are unchanged from the default settings (running on the LAN interface.)

GNB

grantemsley:
I've been trying to duplicate this for most of the day.
Following your instructions, I was able to get DHCP addresses from both the wifi and lan, however neither could connect to anything - they couldn't even ping the pfsense box.

Does this still work on the latest (as of yesterday) beta?

gnhb:
Hi,

Yes, it still works. I'm on a snapshot from April 18th. I'll be testing the May 1st 2G Nano snapshot in the next hour.

Here's the procedure I use to create the bridge interface and assign it to the LAN port. This procedure doesn't cause you to loose connectivity to the GUI or have to monkey around with assigning IP addresses to other ports temporarily.

Assume we're starting with these interface definitions:
WAN -> fx0
LAN -> fx1
OPT1 -> ath0
Also, assume that the DHCP server is already enabled on the LAN interface and is running.

1. On Interfaces Assign page create another OPT interface called OPT2 (create more than one if you want to bridge physical ports too - we'll call any additional ports OPTx.)
2. Assign a physical port or a vlan port, or a PPP port to OPT2 just as a place holder.
2a. Assign physical ports to the other OPTx interfaces you've created.
3. Go to the Interfaces -> OPT2 page and click the "Enable" checkbox. (Repeat for all OPTx interfaces.)
4. Go to the Interfaces -> (assign) page and click on the "Bridge" tab.
5. Select OPT1, OPT2, OPTx (if you created additional ports for the bridge) to be members of the bridge interface and Save.
6. Go to Interfaces -> (assign) page again and select "BRIDGE0" for the LAN interface, and select the fx1 port (formerly assigned to LAN) for the OPT2 interface and Save.

Now we have these interface definitions.
WAN -> fx0
LAN -> BRIDGE0
OPT1 -> ath0
OPT2 -> fx1
OPTx -> <whatever else you want>

7. Go to the System -> Advanced -> System Tunables page and make it look like the pic I posted earlier.

No loss of connectivity to the GUI or the router will occur during this procedure.
You DON'T need ANY new firewall rules for this to operate smoothly.
Clients on the wired LAN or WLAN can get addresses from DHCP and can get to the internet (WAN) and can get to each other. (However, be sure to set up your wireless config properly. There is a checkbox in wireless config that allows or prevents wireless clients from seeing each other.)

Hope it works for you.

GB

grantemsley:
Thank you so much for posting this.  I got it working following those instructions.

Efonne:
Just wanted to note that if you have an extra interface that you are keeping out of the bridge, the bridge configuration is easier if you access the web GUI over that interface instead of accessing it over an interface you are going to put into the bridge.  This way there is no chance you will lose access to the web GUI before you finish the configuration.

Navigation

[0] Message Index

[#] Next page

Go to full version