OpenWRT on WRT3200ACM not assigning DCHP addresses on one interface












0















I'm running OpenWRT 18.06.1 on a Linksys WRT3200ACM. The device has four antennae and shows three Atheros interfaces: an nac, a bgn, and a bgnac (in that order). The first interface works like a champ, but I'm trying to connect some 2.4GHz devices. The third seems to work best when configured with the same ESSID as one of the others but on a different frequency. That's another issue for another day.



Anyways, when I connect my laptop to the 2.4 GHz network, it works fine:



Mon Jan  7 03:57:46 2019 daemon.info hostapd: wlan1: STA 68:ec:c5:f5:37:0f IEEE 802.11: associated (aid 2)
Mon Jan 7 03:57:46 2019 daemon.notice hostapd: wlan1: AP-STA-CONNECTED 68:ec:c5:f5:37:0f
Mon Jan 7 03:57:46 2019 daemon.info hostapd: wlan1: STA 68:ec:c5:f5:37:0f WPA: pairwise key handshake completed (RSN)
Mon Jan 7 03:57:48 2019 daemon.info hostapd: wlan1: STA 68:ec:c5:f5:37:0f IEEE 802.11: authenticated
Mon Jan 7 03:57:48 2019 daemon.info hostapd: wlan1: STA 68:ec:c5:f5:37:0f IEEE 802.11: authenticated
Mon Jan 7 03:57:52 2019 daemon.info dnsmasq-dhcp[6663]: DHCPDISCOVER(br-lights) 68:ec:c5:f5:37:0f
Mon Jan 7 03:57:52 2019 daemon.info dnsmasq-dhcp[6663]: DHCPOFFER(br-lights) 192.168.2.194 68:ec:c5:f5:37:0f
Mon Jan 7 03:57:54 2019 daemon.info dnsmasq-dhcp[6663]: DHCPDISCOVER(br-lights) 68:ec:c5:f5:37:0f
Mon Jan 7 03:57:54 2019 daemon.info dnsmasq-dhcp[6663]: DHCPOFFER(br-lights) 192.168.2.194 68:ec:c5:f5:37:0f


When I connect my phone or most any other device (of about 10 devices, two of them worked) I see this:



Mon Jan  7 03:57:26 2019 daemon.info hostapd: wlan1: STA 40:4e:36:d2:be:30 IEEE 802.11: associated (aid 1)
Mon Jan 7 03:57:26 2019 daemon.notice hostapd: wlan1: AP-STA-CONNECTED 40:4e:36:d2:be:30
Mon Jan 7 03:57:26 2019 daemon.info hostapd: wlan1: STA 40:4e:36:d2:be:30 WPA: pairwise key handshake completed (RSN)
Mon Jan 7 03:57:36 2019 daemon.info hostapd: wlan1: STA 40:4e:36:d2:be:30 IEEE 802.11: authenticated
Mon Jan 7 03:57:45 2019 kern.debug kernel: [ 2413.233325] ieee80211 phy1: staid 2 deleted
...
Mon Jan 7 03:58:02 2019 kern.debug kernel: [ 2430.421936] ieee80211 phy1: staid 1 deleted


This only happens on the 2.4GHz bgn interface, and LuCI shows the device to be connected with a ? for the host field. I've tried this:




  • With a fresh flash, the only change being enabling the wireless network

  • With this interface on its own network

  • With this network as a 2.4GHz equivalent of the network running on nac


And I get the same problem regardless of what I do. I've tried restarting dnsmasq and restarting the network; I'm not sure what else to do. How can I get wlan1 to hand out DHCP addresses so my 2.4GHz only devices can work?










share|improve this question



























    0















    I'm running OpenWRT 18.06.1 on a Linksys WRT3200ACM. The device has four antennae and shows three Atheros interfaces: an nac, a bgn, and a bgnac (in that order). The first interface works like a champ, but I'm trying to connect some 2.4GHz devices. The third seems to work best when configured with the same ESSID as one of the others but on a different frequency. That's another issue for another day.



    Anyways, when I connect my laptop to the 2.4 GHz network, it works fine:



    Mon Jan  7 03:57:46 2019 daemon.info hostapd: wlan1: STA 68:ec:c5:f5:37:0f IEEE 802.11: associated (aid 2)
    Mon Jan 7 03:57:46 2019 daemon.notice hostapd: wlan1: AP-STA-CONNECTED 68:ec:c5:f5:37:0f
    Mon Jan 7 03:57:46 2019 daemon.info hostapd: wlan1: STA 68:ec:c5:f5:37:0f WPA: pairwise key handshake completed (RSN)
    Mon Jan 7 03:57:48 2019 daemon.info hostapd: wlan1: STA 68:ec:c5:f5:37:0f IEEE 802.11: authenticated
    Mon Jan 7 03:57:48 2019 daemon.info hostapd: wlan1: STA 68:ec:c5:f5:37:0f IEEE 802.11: authenticated
    Mon Jan 7 03:57:52 2019 daemon.info dnsmasq-dhcp[6663]: DHCPDISCOVER(br-lights) 68:ec:c5:f5:37:0f
    Mon Jan 7 03:57:52 2019 daemon.info dnsmasq-dhcp[6663]: DHCPOFFER(br-lights) 192.168.2.194 68:ec:c5:f5:37:0f
    Mon Jan 7 03:57:54 2019 daemon.info dnsmasq-dhcp[6663]: DHCPDISCOVER(br-lights) 68:ec:c5:f5:37:0f
    Mon Jan 7 03:57:54 2019 daemon.info dnsmasq-dhcp[6663]: DHCPOFFER(br-lights) 192.168.2.194 68:ec:c5:f5:37:0f


    When I connect my phone or most any other device (of about 10 devices, two of them worked) I see this:



    Mon Jan  7 03:57:26 2019 daemon.info hostapd: wlan1: STA 40:4e:36:d2:be:30 IEEE 802.11: associated (aid 1)
    Mon Jan 7 03:57:26 2019 daemon.notice hostapd: wlan1: AP-STA-CONNECTED 40:4e:36:d2:be:30
    Mon Jan 7 03:57:26 2019 daemon.info hostapd: wlan1: STA 40:4e:36:d2:be:30 WPA: pairwise key handshake completed (RSN)
    Mon Jan 7 03:57:36 2019 daemon.info hostapd: wlan1: STA 40:4e:36:d2:be:30 IEEE 802.11: authenticated
    Mon Jan 7 03:57:45 2019 kern.debug kernel: [ 2413.233325] ieee80211 phy1: staid 2 deleted
    ...
    Mon Jan 7 03:58:02 2019 kern.debug kernel: [ 2430.421936] ieee80211 phy1: staid 1 deleted


    This only happens on the 2.4GHz bgn interface, and LuCI shows the device to be connected with a ? for the host field. I've tried this:




    • With a fresh flash, the only change being enabling the wireless network

    • With this interface on its own network

    • With this network as a 2.4GHz equivalent of the network running on nac


    And I get the same problem regardless of what I do. I've tried restarting dnsmasq and restarting the network; I'm not sure what else to do. How can I get wlan1 to hand out DHCP addresses so my 2.4GHz only devices can work?










    share|improve this question

























      0












      0








      0








      I'm running OpenWRT 18.06.1 on a Linksys WRT3200ACM. The device has four antennae and shows three Atheros interfaces: an nac, a bgn, and a bgnac (in that order). The first interface works like a champ, but I'm trying to connect some 2.4GHz devices. The third seems to work best when configured with the same ESSID as one of the others but on a different frequency. That's another issue for another day.



      Anyways, when I connect my laptop to the 2.4 GHz network, it works fine:



      Mon Jan  7 03:57:46 2019 daemon.info hostapd: wlan1: STA 68:ec:c5:f5:37:0f IEEE 802.11: associated (aid 2)
      Mon Jan 7 03:57:46 2019 daemon.notice hostapd: wlan1: AP-STA-CONNECTED 68:ec:c5:f5:37:0f
      Mon Jan 7 03:57:46 2019 daemon.info hostapd: wlan1: STA 68:ec:c5:f5:37:0f WPA: pairwise key handshake completed (RSN)
      Mon Jan 7 03:57:48 2019 daemon.info hostapd: wlan1: STA 68:ec:c5:f5:37:0f IEEE 802.11: authenticated
      Mon Jan 7 03:57:48 2019 daemon.info hostapd: wlan1: STA 68:ec:c5:f5:37:0f IEEE 802.11: authenticated
      Mon Jan 7 03:57:52 2019 daemon.info dnsmasq-dhcp[6663]: DHCPDISCOVER(br-lights) 68:ec:c5:f5:37:0f
      Mon Jan 7 03:57:52 2019 daemon.info dnsmasq-dhcp[6663]: DHCPOFFER(br-lights) 192.168.2.194 68:ec:c5:f5:37:0f
      Mon Jan 7 03:57:54 2019 daemon.info dnsmasq-dhcp[6663]: DHCPDISCOVER(br-lights) 68:ec:c5:f5:37:0f
      Mon Jan 7 03:57:54 2019 daemon.info dnsmasq-dhcp[6663]: DHCPOFFER(br-lights) 192.168.2.194 68:ec:c5:f5:37:0f


      When I connect my phone or most any other device (of about 10 devices, two of them worked) I see this:



      Mon Jan  7 03:57:26 2019 daemon.info hostapd: wlan1: STA 40:4e:36:d2:be:30 IEEE 802.11: associated (aid 1)
      Mon Jan 7 03:57:26 2019 daemon.notice hostapd: wlan1: AP-STA-CONNECTED 40:4e:36:d2:be:30
      Mon Jan 7 03:57:26 2019 daemon.info hostapd: wlan1: STA 40:4e:36:d2:be:30 WPA: pairwise key handshake completed (RSN)
      Mon Jan 7 03:57:36 2019 daemon.info hostapd: wlan1: STA 40:4e:36:d2:be:30 IEEE 802.11: authenticated
      Mon Jan 7 03:57:45 2019 kern.debug kernel: [ 2413.233325] ieee80211 phy1: staid 2 deleted
      ...
      Mon Jan 7 03:58:02 2019 kern.debug kernel: [ 2430.421936] ieee80211 phy1: staid 1 deleted


      This only happens on the 2.4GHz bgn interface, and LuCI shows the device to be connected with a ? for the host field. I've tried this:




      • With a fresh flash, the only change being enabling the wireless network

      • With this interface on its own network

      • With this network as a 2.4GHz equivalent of the network running on nac


      And I get the same problem regardless of what I do. I've tried restarting dnsmasq and restarting the network; I'm not sure what else to do. How can I get wlan1 to hand out DHCP addresses so my 2.4GHz only devices can work?










      share|improve this question














      I'm running OpenWRT 18.06.1 on a Linksys WRT3200ACM. The device has four antennae and shows three Atheros interfaces: an nac, a bgn, and a bgnac (in that order). The first interface works like a champ, but I'm trying to connect some 2.4GHz devices. The third seems to work best when configured with the same ESSID as one of the others but on a different frequency. That's another issue for another day.



      Anyways, when I connect my laptop to the 2.4 GHz network, it works fine:



      Mon Jan  7 03:57:46 2019 daemon.info hostapd: wlan1: STA 68:ec:c5:f5:37:0f IEEE 802.11: associated (aid 2)
      Mon Jan 7 03:57:46 2019 daemon.notice hostapd: wlan1: AP-STA-CONNECTED 68:ec:c5:f5:37:0f
      Mon Jan 7 03:57:46 2019 daemon.info hostapd: wlan1: STA 68:ec:c5:f5:37:0f WPA: pairwise key handshake completed (RSN)
      Mon Jan 7 03:57:48 2019 daemon.info hostapd: wlan1: STA 68:ec:c5:f5:37:0f IEEE 802.11: authenticated
      Mon Jan 7 03:57:48 2019 daemon.info hostapd: wlan1: STA 68:ec:c5:f5:37:0f IEEE 802.11: authenticated
      Mon Jan 7 03:57:52 2019 daemon.info dnsmasq-dhcp[6663]: DHCPDISCOVER(br-lights) 68:ec:c5:f5:37:0f
      Mon Jan 7 03:57:52 2019 daemon.info dnsmasq-dhcp[6663]: DHCPOFFER(br-lights) 192.168.2.194 68:ec:c5:f5:37:0f
      Mon Jan 7 03:57:54 2019 daemon.info dnsmasq-dhcp[6663]: DHCPDISCOVER(br-lights) 68:ec:c5:f5:37:0f
      Mon Jan 7 03:57:54 2019 daemon.info dnsmasq-dhcp[6663]: DHCPOFFER(br-lights) 192.168.2.194 68:ec:c5:f5:37:0f


      When I connect my phone or most any other device (of about 10 devices, two of them worked) I see this:



      Mon Jan  7 03:57:26 2019 daemon.info hostapd: wlan1: STA 40:4e:36:d2:be:30 IEEE 802.11: associated (aid 1)
      Mon Jan 7 03:57:26 2019 daemon.notice hostapd: wlan1: AP-STA-CONNECTED 40:4e:36:d2:be:30
      Mon Jan 7 03:57:26 2019 daemon.info hostapd: wlan1: STA 40:4e:36:d2:be:30 WPA: pairwise key handshake completed (RSN)
      Mon Jan 7 03:57:36 2019 daemon.info hostapd: wlan1: STA 40:4e:36:d2:be:30 IEEE 802.11: authenticated
      Mon Jan 7 03:57:45 2019 kern.debug kernel: [ 2413.233325] ieee80211 phy1: staid 2 deleted
      ...
      Mon Jan 7 03:58:02 2019 kern.debug kernel: [ 2430.421936] ieee80211 phy1: staid 1 deleted


      This only happens on the 2.4GHz bgn interface, and LuCI shows the device to be connected with a ? for the host field. I've tried this:




      • With a fresh flash, the only change being enabling the wireless network

      • With this interface on its own network

      • With this network as a 2.4GHz equivalent of the network running on nac


      And I get the same problem regardless of what I do. I've tried restarting dnsmasq and restarting the network; I'm not sure what else to do. How can I get wlan1 to hand out DHCP addresses so my 2.4GHz only devices can work?







      wireless-networking wireless-router openwrt






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Jan 7 at 10:17









      onwsk8ronwsk8r

      11




      11






















          0






          active

          oldest

          votes











          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "3"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1391436%2fopenwrt-on-wrt3200acm-not-assigning-dchp-addresses-on-one-interface%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          0






          active

          oldest

          votes








          0






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes
















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Super User!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1391436%2fopenwrt-on-wrt3200acm-not-assigning-dchp-addresses-on-one-interface%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          8-я гвардейская общевойсковая армия

          Sun Ra

          Charles de Carteret