Wireless not giving ip if bridged with Lan



  • OPT1 =wireless if bridged with Lan ,it refuses to give an ip ,the only way to make it work is to put it on DHCP on a different subnet ,and in this case the lan subnet and the wireless subnet can't communicate.
    Lan =192.168.1.1
    OPT1=192.168.2.1
    Is this a bug in 1.3 ALPHA-ALPHA ?



  • Try running the dhcp server on top of the bridge interface after assigning it.
    Actually try assigning the bridge interface as LAN and filter on it rather than doing it as 1.2 way.



  • 1-I tried to assign DHCP on the bridge interface but it didn't work ,something strange happened and i kept loosing the connection to the pfsense box .

    2-this setup works but it is strange :

    LAN fxp0=192.168.1.1 / DHCP=192.168.1.10-50
    OPT1 ath0=192.168.2.1 /DHCP=192.168.2.10-50

    bridged =LAN & OPT1
    I was able to get ip on LAN and OPT1 with the same range of LAN (192.168.1.49 for wireless - 192.168.1.50 for eth)



  • Actually to enable DHCP on the bridge you should go to System->Advanced and make Filter member interfaces 0 and Filter on bridge interface 1 for it to work as expected.



  • @ermal:

    Actually to enable DHCP on the bridge you should go to System->Advanced and make Filter member interfaces 0 and Filter on bridge interface 1 for it to work as expected.

    Hi ermal

    I set net.link.bridge.pfil_member=0 and net.link.bridge.pfil_bridge=1
    I bridged LAN +OPT1 +OPT2  ,but still i can't get an ip address from OPT1 and OPT2
    LAN : is the DHCP server
    OPT1: is LAN2
    OPT2: is WLAN

    is there something else i have to check .

    Thanks



  • Long procedure:
    1- give the lan interface another ip in the same network range(just to have access on the gui)
    2- create the bridge interface with the member interfaces
    3- assign the new created bridge under the interfaces->assign
    4- give the new assigned bridge interface the previous LAN address
    5- Remove the ip address from the lan interface(type none on interface configuration screen)
    6- pfil_member = 0 and pfil_bridge = 1
    7- disable dhcp server on the lan interface
    8- activate the dhcp server on the bridge interface
    9- add a firewall rule to allow traffic to pass on the bridge interface

    At least this is my recommandation for a clear setup on such things that would work as expected without tricks.

    If you feel the suggested setup above is somewhat complicated(i am looking at making this simpler for now) you can try the previous setup you had you need to rules to allow the dhcp traffic on opt1 and opt2 interfaces otherwise it would drop the dhcp requests.



  • Hi ermal,

    I am looking at your post and getting confused and stuck with the following line:

    6- pfil_member = 0 and pfil_bridge = 1

    I assume this allows the bridge to access the web GUI.  I cant quite figure out what you have in mind with this setup.  If its not, than how do I allow access from the bridge or optional network card to the web GUI?

    My intent is to bridge multiple network cards and create a single LAN switch.  Eventually, I would like to add a wireless card into the bridge.  The end state should be multiple network cards looking like a switch and behaving similar to how an off the shelf linksys or similar router would.

    One way this might work better is to have an option under the bridge to cause the bridged interfaces to work like a switch.  when this box is checked, it should allow traffic to flow between interfaces freely, disable dhcp server on individual interfaces that are apart of the bridge, if LAN interface is apart of the bridge than allow the bridge access to the web GUI and assign the ip address of the LAN to the bridge, and remove the ip address of the individual network cards.

    Other than that one line, this answered many questions I had about how pfsense handles the bridge.

    Thanks,
    -V



  • Here is an update,

    I think I got it working.  I followed much of ermal's directions but had a couple problems along the way.  Here is a step by step of what I did to get mine working.

    @ermal:

    Long procedure:
    1- give the LAN interface another ip in the same network range(just to have access on the gui)
    2- create the bridge interface with the member interfaces
    3- assign the new created bridge under the interfaces->assign
    4- give the new assigned bridge interface the previous LAN address

    Here is where I differed:
    5- add a firewall rule to allow traffic to pass on the bridge interface
    6- Disable the LAN DHCP server
    7- Setup DHCP on the bridge
    8- Remove the IP address from the LAN interface by selecting none under type of interface

    • at this point, my web GUI stopped working.  I realized that the bridge lost its ip address for some reason.  therefore step 6 may be pointless.
      9- In the counsel, give the bridge an ip address and enable DHCP server if desired.
      10- Release and renew ip address so your computers DNS gets reset and you can access the web again.

    I still am not sure what ermal intended to do with his step 6- pfil_member = 0 and pfil_bridge = 1.  I'm not even sure if its needed.  Maybe some of you smarter people can help me.

    Anyway, good luck,
    -V



  • Here is another update,

    It would seem my bridge failed.  I added another bridge to test the 2 on board realtek gigabit cards which are 8110 series if memory serves.  They didn't work under pfsense 1.2.  Anyway, the first time I rebooted the router, the bridges lost their ip address and DHCP servers.  I set them back up from the counsel and was able to get into the web gui but was unable to restore internet access.  I'm not quite sure why that is but I would guess its a glitch unless that was what "pfil_member = 0 and pfil_bridge = 1 was suppose to do".  To trouble shoot a bit more, I went back to a setting with a single bridge with network ports I knew should work.  After the first reboot, the same thing happened.

    Further more, with 2 bridges set up, my CPU was pegged.  However, I cant blame this on the bridge or pfsense.  I suspect that was a problem with the realtek network cards.  Just so you know my setup, I'm running pfsense on a jetway j7f4e1g2.  It has a via c7.  In the pci slot, I'm running a dlink 4port 10/100 network card.

    Out of curiosity, is there another place I should be posting this experience where it may be beneficial to the developers?

    Anyway, I think I have had enough for one night.  Frustration is starting to get the better of me.  I'll keep watching this post and if any ideas strike me, I'll test them out and post my findings.
    -V


Locked