#15006: WAN port on WNDR3700v2 does not work
------------------------+----------------------------------
  Reporter:  anonymous  |      Owner:  developers
      Type:  defect     |     Status:  new
  Priority:  normal     |  Milestone:  Chaos Calmer (trunk)
 Component:  packages   |    Version:  Trunk
Resolution:             |   Keywords:
------------------------+----------------------------------

Comment (by i24):

 I can confirm this issue on a WNDR4300v1 (wndrnand r46541.)  Related
 symptoms listed below.

 1. On the '''Status | Overview''' page under '''Leases''' for IPv4 the
 Hostname, IPv4-Address, MAC-Address, Leasetime were all shown correctly.
 However, for IPv6 one of the LAN clients was missing and another client
 hostname was displayed as "'''?'''"

 2. On the '''Interfaces''' page, the MAC address of the WAN interface was
 displayed as '''00:00:00:00:00:00'''

 3. To obtain a WAN IP I had to force override the default (zero) MAC
 address with a spoofed address.  Both v4 & v6 WAN address was then
 assigned correctly by DHCP, but could not ping anything beyond the ISP's
 gateway.


 4. To enable web browsing I did this:

  WAN - Use builtin IPv6-management = disabled
  WAN6 - Request IPv6-address = disabled
  WAN6 - bring up on boot = disabled

  (did not test each one individually, just rebooted)


 5. When I was able to browse the web, the indicators read as follows:

  '''Status | Overview | Network'''

   - IPv4 WAN Status = CONNECTED
   - MWAN Interface Live Status wan (eth0.2) = DISABLED
  '''Network | Interfaces | Overview'''

   - WAN eth0.2 = '''NOT''' CONNECTED (indicator is RED when working)
   - TOR = CONNECTED (is that the intended default?)
 ______________

 After several hours, all of the hardware traffic lights for the client
 devices began to blink rapidly & continuously in perfect sync.  The
 problem has survived a reboot AND disconnecting the modem.  All of the
 lights now blink continuously while power is applied.  However, it did not
 affect browsing.  When I changed the WAN MAC address again to see what
 would happen, web access was lost (but not the WAN connection.)  Rebooting
 the modem did not restore internet connectivity as it normally would.  At
 this point the device was taken offline and awaits a future update because
 it is unusable.
 ________

 '''Notes:'''

 There were 4 LAN clients in this test but after enabling WAN only 2 active
 leases were displayed on the '''Status''' page.

 At some point the system & kernel log menu options quit working and the UI
 began to ask for a password on every page load.  A reboot seemed to
 resolve this.

 The Tor virtual interface cannot be disabled and I did not expect it to be
 brought up at boot by default.  Was it accidentally swapped with the WAN
 interface?

 Is the bug only present in Atheros builds?

 If the MAC address override is changed in oWRT, it seems to take much
 longer for the ISP to restore connectivity than it took with the stock
 firmware and DD-WRT.

 --------

  Default DNS forwardings are shown as:


 {{{
  127.0.0.1#5300
  /0.openwrt.pool.ntp.org/8.8.8.8
  /1.openwrt.pool.ntp.org/8.8.8.8
  /2.openwrt.pool.ntp.org/8.8.8.8
  /3.openwrt.pool.ntp.org/8.8.8.8
 }}}


  Is this a bug?  Other firmwares require only an IP address.
 --------

 Before posting here, I attempted to discuss these issues in the
 appropriate section of the forum, but could not register because my email
 address was falsely detected as SPAM.  (I did not use a disposable email
 address.)  It makes me wonder how many potential contributors to this
 project might have simply walked away because they cannot get online OR
 join the forum.

--
Ticket URL: <https://dev.openwrt.org/ticket/15006#comment:24>
OpenWrt <http://openwrt.org>
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
[email protected]
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-tickets

Reply via email to