Do not bridge and do not use same subnet. If you want lan and wlan to talk add rules for the subnets to talk to each other.
On Wed, Feb 24, 2016, 19:12 Sean Pohl <[email protected]> wrote: > The problem is an endless boot-loop on my pfSense installation after I > made one > change to the WLAN interface. > > I have an older x86 32 bit machine with three NICs: > 1. On-board Ethernet > 2. Ethernet card > 3. WLAN 801.11g > > I was able to configure the WAN & LAN interfaces just fine. When I > enabled the > WLAN interface and set about configuring and saving WLAN interface things > went > well until I set the WLAN as DHCP. When I did and saved it then the > monitor > directly attached to the pfSense box filled completely with random > characters > and then it would reboot. During the boot, it would come to the > "configuring > WLAN" and then the screen would fill with random characters and reboot > again. > > I read about creating a bridge between a WLAN interface and a LAN > interface. I > was able to do that successfully and was able to connect to the WLAN on > the box > but it never assigned me an IP address. So, it wasn't until I changed the > WLAN > interface setting to DHCP that it would get into this loop. > > Should I just set that WLAN interface to be static and then give it a fixed > address in the same subnet as the LAN that I trying to bridge to or > something > else? > > Any suggestions are greatly appreciated. > > Thanks. > _______________________________________________ > pfSense mailing list > https://lists.pfsense.org/mailman/listinfo/list > Support the project with Gold! https://pfsense.org/gold > _______________________________________________ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold
