• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login
Netgate Discussion Forum
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login

Problem with wep on rc2

Scheduled Pinned Locked Moved Wireless
6 Posts 5 Posters 3.4k Views
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • K
    kalonu
    last edited by Aug 26, 2006, 11:28 AM

    I upgraded from rc1 to rc2 and as a result the wifi was not working anymore. When I did a scan available networks on the client machine, it was reporting my ssid was not wep enabled. I then tried rc2a->f still no wifi with wep.
    I checked the same issue as previous topic : http://forum.pfsense.org/index.php/topic,1709.msg9890.html#msg9890

    I then downgraded to rc1 and my wifi network was back up with reported wep. I am using adhoc (ibss). 128bit wep on a netgear 311 802.11b.
    What has changed in rc2?

    1 Reply Last reply Reply Quote 0
    • S
      sullrich
      last edited by Aug 26, 2006, 5:47 PM

      Reboot the unit twice after upgrading and see if this helps.  WEP somehow took 1 reboot more when we tested it with RC2 during the hackathon but it does work ok.

      1 Reply Last reply Reply Quote 0
      • S
        ScaredyCat
        last edited by Sep 3, 2006, 4:24 PM

        I have the same problem here running rc2 and an Atheros AR5213A chipset card WEP just doesn't work at all regardless of the number of reboots I do. Sadly the pcmcia card in my laptop only supports WEP and not WPA…

        :(

        SC

        1 Reply Last reply Reply Quote 0
        • H
          hoba
          last edited by Sep 3, 2006, 4:43 PM

          Make sure your setting for "shared" or "open system" is correct. This is important for WEP. You should prefer "open system" as it is more secure (if you can call WEP secure at all).

          1 Reply Last reply Reply Quote 0
          • S
            ScaredyCat
            last edited by Sep 3, 2006, 9:40 PM

            @hoba:

            Make sure your setting for "shared" or "open system" is correct. This is important for WEP.

            I've tried 'shared', 'open' and 'both'. None seem to make any difference. I finally got fed up and double checked with kismet which reports that there's no WEP enabled - even though the web interface says it is.

            @hoba:

            You should prefer "open system" as it is more secure (if you can call WEP secure at all).

            I appreciate that WEP isn't secure, but it's simply the first step in keeping my wireless data secure. ATM I've got the captive portal running (https), I guess the next step is going to be some mechanism that would allow me to force wireless connections to have to connect to a vpn in order to send any traffic … then WEP wouldn't matter at all.. (any hints on the best mechanism to do this would be appreciated :D )

            thanks

            SC

            1 Reply Last reply Reply Quote 0
            • J
              jeroen234
              last edited by Sep 4, 2006, 7:35 PM

              guess the next step is going to be some mechanism that would allow me to force wireless connections to have to connect to a vpn in order to send any traffic … then WEP wouldn't matter at all.. (any hints on the best mechanism to do this would be appreciated Cheesy )

              setup ptpp server on pfsense
              block all trafic on wireless interface
              open all trafic on ptpp clients interface

              now you can only internet true vpn

              1 Reply Last reply Reply Quote 0
              • First post
                Last post
              Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
                This community forum collects and processes your personal information.
                consent.not_received