Linksys WMP54G causes infinite reboot



  • I've added a linksys wireless card into my pfsense configuration, everything went well on the first boot. Then I attempted to make configurations for the OPT1(WLAN) settings. After commiting the settings and rebooting the system, it wouldnt load into the console menu anymore. Everytime it reaches "Configuring OPT1", it will reboot on itself after 5 secs at that point. I'm currently using pfsense 1.2.3 RC1 .



  • Is your wireless interface name ral0?

    What the date of the build of pfSense (displayed by the pfSense web GUI home page) and is it based on FreeBSD 7.1 or 7.2 (see output of shell command uname -a)?



  • @wallabybob:

    Is your wireless interface name ral0?

    What the date of the build of pfSense (displayed by the pfSense web GUI home page) and is it based on FreeBSD 7.1 or 7.2 (see output of shell command uname -a)?

    yeah the wireless interface is named ral0 .. and the FreeBSD is based on 7.1 .. tried 7.2 it also gives the same problem

    update: if i placed OPT1 into another subnet with its own DHCP then everything would work just fine.  :S



  • @calvinz:

    update: if i placed OPT1 into another subnet with its own DHCP then everything would work just fine.  :S

    How was your OPT1 previously configured?



  • @wallabybob:

    @calvinz:

    update: if i placed OPT1 into another subnet with its own DHCP then everything would work just fine.  :S

    How was your OPT1 previously configured?

    previously I bridged it with my LAN connection. Association takes awful long and couldn't get any DHCP address as well from the LAN side.



  • I'm also getting random ping latency spikes every 10~15pings or so …

    Reply from 10.1.1.1: bytes=32 time<1ms TTL=64
    Reply from 10.1.1.1: bytes=32 time<1ms TTL=64
    Reply from 10.1.1.1: bytes=32 time<1ms TTL=64
    Reply from 10.1.1.1: bytes=32 time=1ms TTL=64
    Reply from 10.1.1.1: bytes=32 time=1ms TTL=64
    Reply from 10.1.1.1: bytes=32 time<1ms TTL=64
    Reply from 10.1.1.1: bytes=32 time=1ms TTL=64
    Reply from 10.1.1.1: bytes=32 time<1ms TTL=64
    Reply from 10.1.1.1: bytes=32 time=1ms TTL=64
    Reply from 10.1.1.1: bytes=32 time<1ms TTL=64
    Reply from 10.1.1.1: bytes=32 time=1ms TTL=64
    Reply from 10.1.1.1: bytes=32 time=1ms TTL=64
    Reply from 10.1.1.1: bytes=32 time=2ms TTL=64
    Reply from 10.1.1.1: bytes=32 time<1ms TTL=64
    Reply from 10.1.1.1: bytes=32 time=1ms TTL=64
    Reply from 10.1.1.1: bytes=32 time<1ms TTL=64
    Reply from 10.1.1.1: bytes=32 time=1ms TTL=64
    Reply from 10.1.1.1: bytes=32 time<1ms TTL=64
    Reply from 10.1.1.1: bytes=32 time<1ms TTL=64
    Reply from 10.1.1.1: bytes=32 time=1ms TTL=64
    Reply from 10.1.1.1: bytes=32 time<1ms TTL=64
    Reply from 10.1.1.1: bytes=32 time<1ms TTL=64
    Reply from 10.1.1.1: bytes=32 time<1ms TTL=64
    Reply from 10.1.1.1: bytes=32 time=50ms TTL=64
    Reply from 10.1.1.1: bytes=32 time=1ms TTL=64
    Reply from 10.1.1.1: bytes=32 time=82ms TTL=64
    Reply from 10.1.1.1: bytes=32 time=24ms TTL=64
    Reply from 10.1.1.1: bytes=32 time<1ms TTL=64
    Reply from 10.1.1.1: bytes=32 time<1ms TTL=64
    Reply from 10.1.1.1: bytes=32 time=3ms TTL=64
    Reply from 10.1.1.1: bytes=32 time=112ms TTL=64
    Reply from 10.1.1.1: bytes=32 time=110ms TTL=64
    Reply from 10.1.1.1: bytes=32 time<1ms TTL=64
    Reply from 10.1.1.1: bytes=32 time<1ms TTL=64
    Reply from 10.1.1.1: bytes=32 time<1ms TTL=64
    Reply from 10.1.1.1: bytes=32 time<1ms TTL=64
    Reply from 10.1.1.1: bytes=32 time=1ms TTL=64
    Reply from 10.1.1.1: bytes=32 time<1ms TTL=64

    Ping statistics for 10.1.1.1:
        Packets: Sent = 38, Received = 38, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 0ms, Maximum = 112ms, Average = 10ms



  • @calvinz:

    previously I bridged it with my LAN connection. Association takes awful long and couldn't get any DHCP address as well from the LAN side.

    Don't know about "association takes awful long" but for DHCP to work in this configuration its necessary to have firewall rules to pass the DHCP traffic. Did you have such rules?



  • @wallabybob:

    @calvinz:

    previously I bridged it with my LAN connection. Association takes awful long and couldn't get any DHCP address as well from the LAN side.

    Don't know about "association takes awful long" but for DHCP to work in this configuration its necessary to have firewall rules to pass the DHCP traffic. Did you have such rules?

    i've tried creating a firewall rule allowing everything to pass through on OPT1 … but still no DHCP address comes through.. :(



  • I gave up trying to get this card to work.  I had huge problems.  Good luck.


Log in to reply