Skip to content
Snippets Groups Projects
  1. Oct 11, 2013
  2. Oct 10, 2013
    • Felix Fietkau's avatar
      ath9k: fix rx issues introduced in my last commit (fixes #14307) · a3cc10cb
      Felix Fietkau authored
      
      Signed-off-by: default avatarFelix Fietkau <nbd@openwrt.org>
      
      SVN-Revision: 38362
      a3cc10cb
    • Jo-Philipp Wich's avatar
      firewall: small improvements in nat reflection · db301385
      Jo-Philipp Wich authored
      	- do not insert duplicate rules when setting up reflection to a zone containing multiple interfaces
      	- set up reflection for any protocol, not just TCP and UDP
      
      SVN-Revision: 38361
      db301385
    • Jo-Philipp Wich's avatar
      Incorrect checkout of git submodules · 97fc11af
      Jo-Philipp Wich authored
      
      When checking out git packages, buildroot doesn't seem to track the revisions
      correctly of any submodules referenced by that project. As a result, the
      submodule stays at whatever revision was referenced by the head of the master
      branch. Running a 'git submodule update' after the checkout fixes this problem.
      
      Signed-off-by: default avatarOwen Kirby <osk@exegin.com>
      
      SVN-Revision: 38359
      97fc11af
    • Jo-Philipp Wich's avatar
      ppp: correct module loaded check in proto_pptp_setup · 5380fa27
      Jo-Philipp Wich authored
      
      proto_pptp_setup is responsible for loading the required modules to establish
      a pptp connection to a foreign peer. The function checks whether all required
      modules are already loaded, before actually loading them.
      
      It seems that the filter being used to accomplish this, is not restrictive
      enough in some cases. For instance when pptp nat helper modules are present on
      a system, and already loaded before a pptp connection is enabled. Then the
      search filter (possibly) returns the following for module=pptp, where actually
      no matches are expected, resulting in the pptp.ko module not being loaded,
      thereby failing to establish the pptp connection.
      
      # module="pptp" ; grep "$module" /proc/modules
      nf_nat_pptp 1312 0 - Live 0x86ce7000
      nf_conntrack_pptp 3072 1 nf_nat_pptp, Live 0x86cb9000
      nf_nat_proto_gre 784 1 nf_nat_pptp, Live 0x86cba000
      nf_conntrack_proto_gre 2368 1 nf_conntrack_pptp, Live 0x86cbf000
      nf_nat 9792 13 nf_nat_rtsp,nf_nat_tftp,nf_nat_sip,nf_nat_pptp,nf_nat_h323,nf_nat_proto_gre,nf_nat_amanda,nf_nat_irc,nf_nat_ftp,ipt_REDIRECT,ipt_NETMAP,ipt_MASQUERADE,iptable_nat, Live 0x86ca8000
      nf_conntrack 37264 31 nf_nat_rtsp,nf_conntrack_rtsp,nf_nat_tftp,nf_conntrack_tftp,nf_nat_snmp_basic,nf_conntrack_snmp,nf_nat_sip,nf_conntrack_sip,nf_nat_pptp,nf_conntrack_pptp,nf_nat_h323,nf_conntrack_h323,nf_conntrack_proto_gre,nf_nat_amanda,nf_conntrack_amanda,nf_conntrack_broadcast,nf_nat_irc,nf_conntrack_irc,nf_nat_ftp,nf_conntrack_ftp,ipt_MASQUERADE,iptable_nat,nf_nat,xt_helper,xt_connmark,xt_connbytes,xt_conntrack,xt_CT,xt_NOTRACK,xt_state,nf_conntrack_ipv4, Live 0x86c90000
      
      The search filter can be made more accurate/restrictive, by requiring the
      occurance of the exact name of the module at the beginning of a line in
      /proc/modules.
      
      # module="pptp" ; grep "^$module " /proc/modules
      pptp 13296 2 - Live 0x86e80000
      
      Signed-off-by: default avatarTijs Van Buggenhout <tvb@able.be>
      
      SVN-Revision: 38358
      5380fa27
    • Jo-Philipp Wich's avatar
      dropbear: update to 2013.59 (released 4 october 2013) · 61e83f9c
      Jo-Philipp Wich authored
      - drop mirror www.mirrors.wiretapped.net (not working anymore)
      - drop patch 300-ipv6_addr_port_split.patch, included upstream
      - refresh patches
      - various upstream changes: http://matt.ucc.asn.au/dropbear/CHANGES
      
      
      
      Signed-off-by: default avatarCatalin Patulea <cat@vv.carleton.ca>
      
      SVN-Revision: 38356
      61e83f9c
    • Jo-Philipp Wich's avatar
      x86: kvm: disable squashfs and jffs2 images by default · 0c2ce3f3
      Jo-Philipp Wich authored
      SVN-Revision: 38355
      0c2ce3f3
    • Felix Fietkau's avatar
      ath9k: add some cleanups and minor fixes · d45a1618
      Felix Fietkau authored
      
      Signed-off-by: default avatarFelix Fietkau <nbd@openwrt.org>
      
      SVN-Revision: 38354
      d45a1618
    • Hauke Mehrtens's avatar
      kernel: add default config for ARM_ERRATA symbols for kernel 3.3 · a05d20a6
      Hauke Mehrtens authored
      
      Commit r37470 did not add a default conig for the ARM_ERRATA symbols for kernel 3.3.
      
      Signed-off-by: default avatarHauke Mehrtens <hauke@hauke-m.de>
      
      SVN-Revision: 38352
      a05d20a6
  3. Oct 09, 2013
  4. Oct 08, 2013
    • John Crispin's avatar
      ralink: add support for the mt7530 eval board · e382d2c7
      John Crispin authored
      
      Signed-off-by: default avatarJohn Crispin <blogic@openwrt.org>
      
      SVN-Revision: 38345
      e382d2c7
    • John Crispin's avatar
      ralink: add missing header file to mt7530 driver · 697bb191
      John Crispin authored
      
      Signed-off-by: default avatarJohn Crispin <blogic@openwrt.org>
      
      SVN-Revision: 38344
      697bb191
    • John Crispin's avatar
      lantiq: fix up diag.sh · 654dfb17
      John Crispin authored
      
      init no longer exists as a parameter
      
      Signed-off-by: default avatarJohn Crispin <blogic@openwrt.org>
      
      SVN-Revision: 38342
      654dfb17
    • John Crispin's avatar
      925f37a5
    • John Crispin's avatar
      kernel: remove debug code from module insert script · 4b47d5b7
      John Crispin authored
      
      Signed-off-by: default avatarJohn Crispin <blogic@openwrt.org>
      
      SVN-Revision: 38340
      4b47d5b7
    • Felix Fietkau's avatar
      hostapd: recognize 8021x as an authentication mode · ff40bc2d
      Felix Fietkau authored
      
      Currently, in order to configure the authentication daemon in
      8021x mode, we need to set wireless.@wifi-iface[0].encryption="wpa"
      Though it works it confuses folks as 8021x is using WEP
      encryption and not WPA. Therefore the terminology itself is
      confusing. This change adds 8021x as a recognized string for 8021x
      authentication.
      
      Signed-off-by: default avatarMathieu Olivari <mathieu@qca.qualcomm.com>
      Signed-off-by: default avatarLuis R. Rodriguez <mcgrof@qca.qualcomm.com>
      
      SVN-Revision: 38339
      ff40bc2d
    • Felix Fietkau's avatar
      hostapd: add external registrar support · 9beaea6f
      Felix Fietkau authored
      
      Setting wireless.@wifi-iface[N].ext_registrar=1 will enable UPNP
      advertising and add an external registrar to the interface this vif
      belongs to (br-lan if the vif is included in the LAN bridge). By
      enabling this we append upnp_iface=xxx to the hostapd config file.
      
      Signed-off-by: default avatarSujith Manoharan <c_manoha@qca.qualcomm.com>
      Signed-off-by: default avatarMathieu Olivari <mathieu@qca.qualcomm.com>
      Signed-off-by: default avatarLuis R. Rodriguez <mcgrof@qca.qualcomm.com>
      
      SVN-Revision: 38338
      9beaea6f
    • Felix Fietkau's avatar
      hostapd: enable WPS2 support on hostapd-full.config · 246e9b44
      Felix Fietkau authored
      
      Enable CONFIG_WPS2 for hostapd. This is required to support
      options like Virtual Push Button in WPS.
      
      Signed-off-by: default avatarSujith Manoharan <c_manoha@qca.qualcomm.com>
      Signed-off-by: default avatarLuis R. Rodriguez <mcgrof@qca.qualcomm.com>
      
      SVN-Revision: 38337
      246e9b44
    • Felix Fietkau's avatar
      hostapd: fix hostapd RSN preauthentication PMKSA caching · bcbc9b1e
      Felix Fietkau authored
      In 2009 OpenWrt's hostapd config added an "auth_cache" boolean
      to be used to address a reported issue #12129 [0] on a forum [1].
      The reported issue on the ticket is different that the one
      described on the forum. The commit was r33359. This change broke
      proper RSN preauthentication [2] [3] [4] expectations on hostapd's
      configuration for WPA2 and this in turn disabled PMKSA caching and
      Opportunistic Key Caching. This change:
      
        * Leaves the "auth_cache" to be used only for WPA networks for those
          looking to use this as a workaround to a reported issue but annotates
          a warning over its usage.
      
        * Separate "auth_cache" from WPA2 RSN preauthentication, leaving
          WPA2 RSN preauthentication to enabled only with "rsn_preauth" with
          the expected and recommended settings.
      
        * Adds a new WPA2 RSN preauthentication "rsn_preauth_testing" to
          be used when evaluating funcionality for WPA2 RSN preauthentication
          with the expected and recommended settings with the only difference
          so far with what should be enabled by default to disable Opportunistic
          Key Caching.
      
      Disabling the PMKSA cache should mean the STA could not roam off and back
      onto the AP that had PMKSA caching disabled and would require a full
      authentication cycle. This fixes this for WPA2 networks with
      RSN preauthentication enabled.
      
      This change should be applied to AA as well as trunk.
      
        TL DR;
      
      The issue described on the forum has to do with failure of a STA
      being able to try to authenticate again with the AP if it failed
      its first try. This may have been an issue with hostapd in 2009
      but as per some tests I cannot reproduce this today on a WPA2
      network.
      
      The issue described on the ticket alludes to a security issue with the
      design of using a Radius server to authenticate to an AP. The issue
      vaguely alludes to the circumstances of zapping a user, deleting their
      authentication credentials to log in to the network, and that if
      RSN preauthentication is enabled with PMKSA caching that the user
      that was zapped would still be able to authenticate.
      
      Lets treat these as separate issues.
      
      I cannot reproduce the first issue reported on the forums of not
      being able to authenticate anymore on a WPA2 network.
      
      The issue reported on the ticket modified WPA2 RSN preauthentication
      by adding two fields to the hostapd configuration if auth_cache
      was enabled:
      
        * disable_pmksa_caching=1
        * okc=0
      
      The first one disables PMKSA authentication cache.
      The second one disables Opportunistic Key Caching.
      
      The issue reported on the ticket was fixed by implementing a workaround
      in hostapd's configuration. Disabling PMKSA caching breaks proper use
      of WPA2 RSN pre authentication. The usage of disable_pmksa_caching=1
      prevents hostapd from adding PMKSA entries into its cache when a successful
      802.1x authentication occurs. In practice RSN preauthentication would
      trigger a STA to perform authentication with other APs on the same SSID,
      it would then have its own supplicant PMKSA cache held. If a STA roams
      between one AP to another no new authenitcation would need to be performed
      as the new AP would already have authenticated the STA. The purpose of the
      PMKSA cache on the AP side would be for the AP to use the same PMKID for
      a STA when the STA roams off onto another BSSID and later comes back to it.
      
      Disabling Opportunistic Key Caching could help the reported issue
      as well but its not the correct place to address this. Opportunistic
      Key Caching enables an AP with different interfaces to share the
      PMKSA cache. Its a technical enhancement and disabling it would
      be useful to let a testing suite properly test for RSN preauthentication
      given that otherwise Opportunistic Key Caching would enable an
      interface being tested to derive its own derive the PMKSA entry.
      In production though okc=1 should be enabled to help with RSN
      preauthentication.
      
      The real fix for this particular issue outside of the scope of hostapd's
      configuration and it should not be dealt with as a workaround to
      its configuration and breaking expected RSN preauthentication and
      technical optimizations. Revert this change and enable users to pick
      and choose to enable or disable disable_pmksa_caching and okc expecting them
      to instead have read clearly more what these do.
      
      As for the core issure ported, the correct place to fix this is to
      enable a sort of messaging between the RADIUS server and its peers
      so that if caching for authentication is enabled that cache can be
      cleared upon user credential updates. Updating a user password
      (not just zapping a user) is another possible issue that would need
      to be resolved here. Another part of the solution might be to reduce
      the cache timing to account for any systematic limitations (RADIUS
      server not able to ask peers to clear cache might be
      one).
      
      [0] https://dev.openwrt.org/changeset/33359
      [1] https://forum.openwrt.org/viewtopic.php?id=19596
      [2] http://wireless.kernel.org/en/users/Documentation/hostapd#IEEE_802.11i.2FRSN.2FWPA2_pre-authentication
      [3] http://wireless.kernel.org/en/users/Documentation/wpa_supplicant#RSN_preauthentication
      [4] http://wiki.openwrt.org/doc/recipes/rsn_preauthentication
      
      
      
      Signed-off-by: default avatarLuis R. Rodriguez <mcgrof@do-not-panic.com>
      
      SVN-Revision: 38336
      bcbc9b1e
    • Felix Fietkau's avatar
      40aec9ed
    • Felix Fietkau's avatar
      hostapd: Add eap_reauth_period config option · 4689bc85
      Felix Fietkau authored
      
      This adds the eap_reauth_period to be used for modifying
      the RADIUS server reauthentication authentication period,
      a parameter that gets passed directly to the hostapd
      configuration file.
      
      Signed-off-by: default avatarMathieu Olivari <mathieu@qca.qualcomm.com>
      Signed-off-by: default avatarLuis R. Rodriguez <mcgrof@qca.qualcomm.com>
      
      SVN-Revision: 38334
      4689bc85
  5. Oct 07, 2013
Loading