Reboots usually happen when irq is shared and/or memory. On Wed, Feb 24, 2016, 20:17 Espen Johansen <[email protected]> wrote:
> You might try to put the wlan card in another slot on the motherboard. > Also use bios to disable stuff like sound card, unused usb ports, Lpt, com > ports etc. > > On Wed, Feb 24, 2016, 20:15 Espen Johansen <[email protected]> wrote: > >> Remove the wlan card. Then remove config. It sounds like you might have a >> irq or other resource allocation problem. But without any more details its >> hard to say. >> >> On Wed, Feb 24, 2016, 19:51 Sean Pohl <[email protected]> >> wrote: >> >>> Ok. Thank you very much. Any advice on how to get it out of the endless >>> boot loop? Or will my path of least resistance be to simply do a fresh >>> install again? Many thanks. >>> On Feb 24, 2016 12:26, "Espen Johansen" <[email protected]> wrote: >>> >>> > 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 >>> > >>> _______________________________________________ >>> 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
