DD-WRT :: View topic - ASUS RT-AC5300 Switch Ports

ASUS RT-AC5300 Switch Ports

DD-WRT Forum Index -> Broadcom SoC based Hardware

Goto page Previous 1, 2, 3 Next

View previous topic :: View next topic

Author

Message

<Kong>
DD-WRT Guru

Joined: 15 Dec 2010
Posts: 4339
Location: Germany

Posted: Tue Sep 13, 2016 5:57 Post subject: Re: WOW!

rommer wrote:

Thanks Kong, just sent you a little something for your efforts.

Working great right out of the shoot. DHCP works on the ethernet ports.

Yes because I added a fix for it, will commit that after I looked through my other changes.
Thanks for the contribution!
_________________
KONG PB's: http://www.desipro.de/ddwrt/
KONG Info: http://tips.desipro.de/

Sponsor

rommer
DD-WRT Novice

Joined: 13 Apr 2016
Posts: 39

Posted: Tue Sep 13, 2016 14:34 Post subject:

Your welcome.

Unit continues to be stable but I was not able to associate any new clients to radio 2 the 5ghz access point. There were 4 or 5 clients already connected. Nothing was showing in the logs for the connection attempts. Not sure if I have to set a more verbose logging level.

I rebooted the router and things were able to connect again.

I'll try to get you a log of the bootup tonight. There is definitely a bunch of devices/chips identified with your build vs BS's build.

<Kong>
DD-WRT Guru

Joined: 15 Dec 2010
Posts: 4339
Location: Germany

Posted: Tue Sep 13, 2016 16:53 Post subject:

rommer wrote:

I had issues yesterday setting up my R8000 with a few vaps, could not connect until I rebooted. Inssider reported that encryption state was WEP, for those were I could not connect, after reboot this was OK. Thus if you see the problem again, try to use a wireless scan tool and check if it shows the wrong encryption flag.

Also check if you have disabled beamforming, someone reported, that disabling beamforming on the R8500(same radios as in AC5300) seems to solve the same issue in his setup. I had no connection/stability issue on the R8500 so far.
_________________
KONG PB's: http://www.desipro.de/ddwrt/
KONG Info: http://tips.desipro.de/

rommer
DD-WRT Novice

Joined: 13 Apr 2016
Posts: 39

Posted: Wed Sep 14, 2016 13:39 Post subject:

After 24 hours, wifi has been strong and no change to WEP.

Code:

$ nmcli device wifi list
* SSID MODE CHAN RATE SIGNAL BARS SECURITY
Wake-N-Waves Infra 1 54 Mbit/s 100 ▂▄▆█ WPA2
* Wake-N-Waves_5G Infra 100 54 Mbit/s 66 ▂▄▆_ WPA2
Silchoy Infra 3 54 Mbit/s 49 ▂▄__ WPA2
Silchoy_5G Infra 40 54 Mbit/s 35 ▂▄__ WPA2

Wake-N-Waves_5G is the one I had the problem with. So far the reboot has things running smoothly.

rommer
DD-WRT Novice

Joined: 13 Apr 2016
Posts: 39

Posted: Thu Sep 15, 2016 4:01 Post subject:

No boot log yet since the unit is still up. Just a warning though, don't use erase nvram, use web interface reset defaults.

I screwed up one of my AC5300's. It boots but no ethernet ports and I get only one wifi radio up but it uses one of my ssid's but in ad-hoc mode with WEP encryption. I have no idea what the password is since when it was working it was using WPA2 on all 3 channels.

FWIW this router doesn't appear to have a cfe. I've tried what feels like 100 times to get it to go into recovery mode but the power light stays lit and does not flash.

rommer
DD-WRT Novice

Joined: 13 Apr 2016
Posts: 39

Posted: Thu Sep 15, 2016 11:51 Post subject:
Firmware: DD-WRT v3.0-r30615M kongac (09/12/16) Time: 07:49:04 up 2 days, 10 min, load average: 0.00, 0.02, 0.00 Still looking good!

rommer
DD-WRT Novice

Joined: 13 Apr 2016
Posts: 39

Posted: Sun Sep 18, 2016 15:17 Post subject: Trouble after 5 days of uptime.

Could only ping unit. Radios were detected with wpa2 encryption but could not connect to any radios, 2.4 or 5ghz.

No crash log but I did grab the boot log.

Code:

Dec 31 19:00:13 Wake-N-Waves4 syslog.info syslogd started: BusyBox v1.24.2
Jan 1 00:00:13 Wake-N-Waves4 kern.notice kernel: klogd started: BusyBox v1.24.2 (2016-09-12 21:11:55 CEST)
Jan 1 00:00:13 Wake-N-Waves4 kern.warn kernel: PCIE 0001:02:0038: ASMedia DownPort Link status 0x7012
Jan 1 00:00:13 Wake-N-Waves4 kern.debug kernel: pci 0001:02:07.0: [1b21:1182] type 01 class 0x060400
Jan 1 00:00:13 Wake-N-Waves4 kern.warn kernel: PCIE: Doing ASMedia switch Init...Test Read = 20010002
Jan 1 00:00:13 Wake-N-Waves4 kern.debug kernel: pci 0001:02:07.0: PME# supported from D0 D3hot D3cold
Jan 1 00:00:13 Wake-N-Waves4 kern.warn kernel: PCI: Fixing up bus 2 domain 1
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: PCI: bus2: Fast back to back transfers disabled
Jan 1 00:00:13 Wake-N-Waves4 kern.debug kernel: pci 0001:03:00.0: [14e4:4365] type 00 class 0x028000
Jan 1 00:00:13 Wake-N-Waves4 kern.debug kernel: pci 0001:03:00.0: reg 0x10: [mem 0x00000000-0x00007fff 64bit]
Jan 1 00:00:13 Wake-N-Waves4 kern.debug kernel: pci 0001:03:00.0: reg 0x18: [mem 0x00000000-0x003fffff 64bit]
Jan 1 00:00:13 Wake-N-Waves4 kern.debug kernel: pci 0001:03:00.0: supports D1 D2
Jan 1 00:00:13 Wake-N-Waves4 kern.warn kernel: PCI: Fixing up bus 3 domain 1
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: PCI: bus3: Fast back to back transfers disabled
Jan 1 00:00:13 Wake-N-Waves4 kern.debug kernel: pci_bus 0001:03: busn_res: [bus 03-ff] end is updated to 03
Jan 1 00:00:13 Wake-N-Waves4 kern.debug kernel: pci 0001:04:00.0: [14e4:4365] type 00 class 0x028000
Jan 1 00:00:13 Wake-N-Waves4 kern.debug kernel: pci 0001:04:00.0: reg 0x10: [mem 0x00000000-0x00007fff 64bit]
Jan 1 00:00:13 Wake-N-Waves4 kern.debug kernel: pci 0001:04:00.0: reg 0x18: [mem 0x00000000-0x003fffff 64bit]
Jan 1 00:00:13 Wake-N-Waves4 kern.debug kernel: pci 0001:04:00.0: supports D1 D2
Jan 1 00:00:13 Wake-N-Waves4 kern.warn kernel: PCI: Fixing up bus 4 domain 1
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: PCI: bus4: Fast back to back transfers disabled
Jan 1 00:00:13 Wake-N-Waves4 kern.debug kernel: pci_bus 0001:04: busn_res: [bus 04-ff] end is updated to 04
Jan 1 00:00:13 Wake-N-Waves4 kern.debug kernel: pci_bus 0001:02: busn_res: [bus 02-ff] end is updated to 04
Jan 1 00:00:13 Wake-N-Waves4 kern.debug kernel: pci_bus 0001:01: busn_res: [bus 01-ff] end is updated to 04
Jan 1 00:00:13 Wake-N-Waves4 kern.debug kernel: pci_bus 0001:00: busn_res: [bus 00-ff] end is updated to 04
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: pci 0001:00:00.0: BAR 8: assigned [mem 0x08000000-0x08bfffff]
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: pci 0001:01:00.0: BAR 8: assigned [mem 0x08000000-0x08bfffff]
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: pci 0001:02:03.0: BAR 8: assigned [mem 0x08000000-0x085fffff]
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: pci 0001:02:07.0: BAR 8: assigned [mem 0x08600000-0x08bfffff]
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: pci 0001:03:00.0: BAR 2: assigned [mem 0x08000000-0x083fffff 64bit]
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: pci 0001:03:00.0: BAR 0: assigned [mem 0x08400000-0x08407fff 64bit]
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: pci 0001:02:03.0: PCI bridge to [bus 03]
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: pci 0001:02:03.0: bridge window [mem 0x08000000-0x085fffff]
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: pci 0001:04:00.0: BAR 2: assigned [mem 0x08800000-0x08bfffff 64bit]
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: pci 0001:04:00.0: BAR 0: assigned [mem 0x08600000-0x08607fff 64bit]
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: pci 0001:02:07.0: PCI bridge to [bus 04]
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: pci 0001:02:07.0: bridge window [mem 0x08600000-0x08bfffff]
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: pci 0001:01:00.0: PCI bridge to [bus 02-04]
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: pci 0001:01:00.0: bridge window [mem 0x08000000-0x08bfffff]
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: pci 0001:00:00.0: PCI bridge to [bus 01-04]
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: pci 0001:00:00.0: bridge window [mem 0x08000000-0x08bfffff]
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: PCIE2 link=1
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: PCIE2 switching to GEN2
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: PCIE2 link=1
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: PCI host bridge to bus 0002:00
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: pci_bus 0002:00: root bus resource [mem 0x20000000-0x27ffffff]
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: pci_bus 0002:00: No busn resource found for root bus, will use [bus 00-ff]
Jan 1 00:00:13 Wake-N-Waves4 kern.debug kernel: pci 0002:00:00.0: [14e4:d612] type 01 class 0x060400
Jan 1 00:00:13 Wake-N-Waves4 kern.debug kernel: pci 0002:00:00.0: PME# supported from D0 D3hot D3cold
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: PCI: bus0: Fast back to back transfers disabled
Jan 1 00:00:13 Wake-N-Waves4 kern.debug kernel: pci 0002:01:00.0: [14e4:4365] type 00 class 0x028000
Jan 1 00:00:13 Wake-N-Waves4 kern.debug kernel: pci 0002:01:00.0: reg 0x10: [mem 0x00000000-0x00007fff 64bit]
Jan 1 00:00:13 Wake-N-Waves4 kern.debug kernel: pci 0002:01:00.0: reg 0x18: [mem 0x00000000-0x003fffff 64bit]
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: pci 0002:01:00.0: Max Payload Size set to 512 (was 128, max 512)
Jan 1 00:00:13 Wake-N-Waves4 kern.debug kernel: pci 0002:01:00.0: supports D1 D2
Jan 1 00:00:13 Wake-N-Waves4 kern.warn kernel: PCI: Fixing up bus 1 domain 2
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: PCI: bus1: Fast back to back transfers disabled
Jan 1 00:00:13 Wake-N-Waves4 kern.debug kernel: pci_bus 0002:01: busn_res: [bus 01-ff] end is updated to 01
Jan 1 00:00:13 Wake-N-Waves4 kern.debug kernel: pci_bus 0002:00: busn_res: [bus 00-ff] end is updated to 01
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: pci 0002:00:00.0: BAR 8: assigned [mem 0x20000000-0x205fffff]
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: pci 0002:01:00.0: BAR 2: assigned [mem 0x20000000-0x203fffff 64bit]
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: pci 0002:01:00.0: BAR 0: assigned [mem 0x20400000-0x20407fff 64bit]
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: pci 0002:00:00.0: PCI bridge to [bus 01]
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: pci 0002:00:00.0: bridge window [mem 0x20000000-0x205fffff]
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: PCIE3 link=0
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: futex hash table entries: 512 (order: 3, 32768 bytes)
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: squashfs: version 3.0 (2006/03/15) Phillip Lougher
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: io scheduler noop registered (default)
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: io scheduler cfq registered
Jan 1 00:00:13 Wake-N-Waves4 kern.warn kernel: PCIE: Doing ASMedia switch Init...Test Read = 20010002
Jan 1 00:00:13 Wake-N-Waves4 kern.warn kernel: PCIE: Doing ASMedia switch Init...Test Read = 20010002
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: serial8250_init
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: Serial: 8250/16550 driver, 3 ports, IRQ sharing disabled
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: console [ttyS0] disabled
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: serial8250.0: ttyS0 at MMIO 0x18000300 (irq = 117, base_baud = 7812500) is a 16550
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: console [ttyS0] enabled
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: serial8250.0: ttyS1 at MMIO 0x18000400 (irq = 117, base_baud = 7812500) is a 16550
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: brd: module loaded
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: loop: module loaded
Jan 1 00:00:13 Wake-N-Waves4 kern.warn kernel: Unknown flash, device_id:0x00
Jan 1 00:00:13 Wake-N-Waves4 kern.err kernel: bcmsflash: found no supported devices
Jan 1 00:00:13 Wake-N-Waves4 kern.warn kernel: Boot partition size = 524288(0x80000)
Jan 1 00:00:13 Wake-N-Waves4 kern.warn kernel: lookup_nflash_rootfs_offset: offset = 0x200000 size = 0x1e00000, 0x20000
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: found TRX Header on nflash!
Jan 1 00:00:13 Wake-N-Waves4 kern.notice kernel: nflash: squash filesystem with lzma found at block 29
Jan 1 00:00:13 Wake-N-Waves4 kern.notice kernel: Creating 4 MTD partitions on "nflash":
Jan 1 00:00:13 Wake-N-Waves4 kern.notice kernel: 0x000000000000-0x000000080000 : "boot"
Jan 1 00:00:13 Wake-N-Waves4 kern.notice kernel: 0x000000080000-0x000000200000 : "nvram"
Jan 1 00:00:13 Wake-N-Waves4 kern.notice kernel: 0x000000200000-0x000002000000 : "linux"
Jan 1 00:00:13 Wake-N-Waves4 kern.notice kernel: 0x0000003a0000-0x000002000000 : "rootfs"
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: tun: Universal TUN/TAP device driver, 1.6
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: tun: (C) 1999-2004 Max Krasnyansky
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: PPP generic driver version 2.4.2
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: PPP BSD Compression module registered
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: PPP Deflate Compression module registered
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: PPP MPPE Compression module registered
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: NET: Registered protocol family 24
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: GACT probability NOT on
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: Simple TC action Loaded
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: netem: version 1.3
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: u32 classifier
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: Performance counters on
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: input device check on
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: Actions configured
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: Netfilter messages via NETLINK v0.30.
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: nf_conntrack version 0.5.0 (8034 buckets, 32136 max)
Jan 1 00:00:13 Wake-N-Waves4 kern.warn kernel: nf_conntrack_rtsp v0.7 loading
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: xt_time: kernel timezone is -0000
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: ip_set: protocol 6
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: gre: GRE over IPv4 demultiplexor driver
Jan 1 00:00:13 Wake-N-Waves4 kern.warn kernel: nf_nat_rtsp v0.7 loading
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: ip_tables: (C) 2000-2006 Netfilter Core Team
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: NET: Registered protocol family 17
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: bridge: automatic filtering via arp/ip/ip6tables has been deprecated. Update your scripts to load br_netfilter if you need this.
Jan 1 00:00:13 Wake-N-Waves4 kern.notice kernel: Bridge firewalling registered
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: 8021q: 802.1Q VLAN Support v1.8
Jan 1 00:00:13 Wake-N-Waves4 kern.notice kernel: Registering SWP/SWPB emulation handler
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: max nvram space = 131072
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: read 131072 bytes to offset 0
Jan 1 00:00:13 Wake-N-Waves4 kern.notice kernel: Key type encrypted registered
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: Northstar brcmnand NAND Flash Controller driver, Version 0.1 (c) Broadcom Inc. 2012
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: nand: device found, Manufacturer ID: 0x01, Chip ID: 0xf1
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: nand: AMD/Spansion NAND 128MiB 3,3V 8-bit
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: nand: 128 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
Jan 1 00:00:13 Wake-N-Waves4 kern.warn kernel: Spare area=64 eccbytes 56, ecc bytes located at:
Jan 1 00:00:13 Wake-N-Waves4 kern.warn kernel: 2 3 4 5 6 7 8 9 10 11 12 13 14 15 18 19 20 21 22 23 24 25 26 27 28 29 30 31 34 35 36 37 38 39 40 41 42 43 44 45 46 47 50 51 52 53 54 55 56 57 58 59 60 61 62 63
Jan 1 00:00:13 Wake-N-Waves4 kern.warn kernel: Available 7 bytes at (off,len):
Jan 1 00:00:13 Wake-N-Waves4 kern.warn kernel: (1,1) (16,2) (32,2) (48,2) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0)
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: Scanning device for bad blocks
Jan 1 00:00:13 Wake-N-Waves4 kern.warn kernel: Options: NO_SUBPAGE_WRITE,
Jan 1 00:00:13 Wake-N-Waves4 kern.notice kernel: Creating 1 MTD partitions on "brcmnand":
Jan 1 00:00:13 Wake-N-Waves4 kern.notice kernel: 0x000002000000-0x000008000000 : "ddwrt"
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: VFS: Mounted root (squashfs filesystem) readonly on device 31:3.
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: Freeing unused kernel memory: 344K (80498000 - 804ee000)
Jan 1 00:00:13 Wake-N-Waves4 kern.warn kernel: et: module license 'Proprietary' taints kernel.
Jan 1 00:00:13 Wake-N-Waves4 kern.warn kernel: Disabling lock debugging due to kernel taint
Jan 1 00:00:13 Wake-N-Waves4 kern.warn kernel: et_module_init: msglevel set to 0x1
Jan 1 00:00:13 Wake-N-Waves4 kern.warn kernel: et_module_init: passivemode set to 0x0
Jan 1 00:00:13 Wake-N-Waves4 kern.warn kernel: et_module_init: txworkq set to 0x0
Jan 1 00:00:13 Wake-N-Waves4 kern.warn kernel: et_module_init: et_txq_thresh set to 0xce4
Jan 1 00:00:13 Wake-N-Waves4 kern.warn kernel: et_module_init: et_rxlazy_timeout set to 0x3e8
Jan 1 00:00:13 Wake-N-Waves4 kern.warn kernel: et_module_init: et_rxlazy_framecnt set to 0x20
Jan 1 00:00:13 Wake-N-Waves4 kern.warn kernel: et_module_init: et_rxlazy_dyn_thresh set to 0
Jan 1 00:00:13 Wake-N-Waves4 kern.warn kernel: et core0: bind to et0
Jan 1 00:00:13 Wake-N-Waves4 kern.warn kernel: si_doattach: incoming bus is PCI but it's a lie, switching to SI devid:0x4715
Jan 1 00:00:13 Wake-N-Waves4 kern.warn kernel: Found chip type NAI (0x3f00cf26)
Jan 1 00:00:13 Wake-N-Waves4 kern.warn kernel: Chipc: rev 42, caps 0x48000a, chipst 0x0 pmurev 0, pmucaps 0x0
Jan 1 00:00:13 Wake-N-Waves4 kern.warn kernel: et0: chipattach error
Jan 1 00:00:13 Wake-N-Waves4 kern.emerg kernel: et0: etc_attach() failed
Jan 1 00:00:13 Wake-N-Waves4 kern.warn kernel: et core1: bind to et1
Jan 1 00:00:13 Wake-N-Waves4 kern.warn kernel: si_doattach: incoming bus is PCI but it's a lie, switching to SI devid:0x4715
Jan 1 00:00:13 Wake-N-Waves4 kern.warn kernel: Found chip type NAI (0x3f00cf26)
Jan 1 00:00:13 Wake-N-Waves4 kern.warn kernel: Chipc: rev 42, caps 0x48000a, chipst 0x0 pmurev 0, pmucaps 0x0
Jan 1 00:00:13 Wake-N-Waves4 kern.warn kernel: et1: chipattach: invalid format: et1macaddr=00:00:00:00:00:00
Jan 1 00:00:13 Wake-N-Waves4 kern.warn kernel: et1: chipattach error
Jan 1 00:00:13 Wake-N-Waves4 kern.emerg kernel: et1: etc_attach() failed
Jan 1 00:00:13 Wake-N-Waves4 kern.warn kernel: et core2: bind to et2
Jan 1 00:00:13 Wake-N-Waves4 kern.warn kernel: si_doattach: incoming bus is PCI but it's a lie, switching to SI devid:0x4715
Jan 1 00:00:13 Wake-N-Waves4 kern.warn kernel: Found chip type NAI (0x3f00cf26)
Jan 1 00:00:13 Wake-N-Waves4 kern.warn kernel: Chipc: rev 42, caps 0x48000a, chipst 0x0 pmurev 0, pmucaps 0x0
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: ET Corerev 7
Jan 1 00:00:13 Wake-N-Waves4 kern.warn kernel: et2: online cpus 2
Jan 1 00:00:13 Wake-N-Waves4 kern.warn kernel: eth0: Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller 7.14.89.21 (r524987 WLTEST)
Jan 1 00:00:13 Wake-N-Waves4 kern.warn kernel: et3: et3macaddr not found, ignore it
Jan 1 00:00:13 Wake-N-Waves4 kern.warn kernel: et core3: can not bind to et3
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: roboswitch: Probing device 'eth0'
Jan 1 00:00:13 Wake-N-Waves4 kern.warn kernel: et2: chipphyrd: not supported
Jan 1 00:00:13 Wake-N-Waves4 kern.warn kernel: et2: chipphyrd: not supported
Jan 1 00:00:13 Wake-N-Waves4 kern.warn kernel: et2: chipphyrd: not supported
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: roboswitch: trying a 53012! at eth0
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: detected CPU Port is 8
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: roboswitch: found a 53012! at eth0
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: detected CPU Port is 8
Jan 1 00:00:13 Wake-N-Waves4 kern.warn kernel: PCI: Enabling device 0001:03:00.0 (0140 -> 0142)
Jan 1 00:00:13 Wake-N-Waves4 kern.warn kernel: PCI: Enabling device 0001:04:00.0 (0140 -> 0142)
Jan 1 00:00:13 Wake-N-Waves4 kern.notice kernel: random: nonblocking pool is initialized
Jan 1 00:00:13 Wake-N-Waves4 kern.warn kernel: PCI: Enabling device 0002:01:00.0 (0140 -> 0142)
Jan 1 00:00:13 Wake-N-Waves4 kern.warn kernel: wl_module_init: msglevel set to 0x1
Jan 1 00:00:13 Wake-N-Waves4 kern.warn kernel: wl_module_init: msglevel2 set to 0x0
Jan 1 00:00:13 Wake-N-Waves4 kern.warn kernel: wl_module_init: phymsglevel set to 0x1
Jan 1 00:00:13 Wake-N-Waves4 kern.warn kernel: wl_module_init: passivemode set to 0x0
Jan 1 00:00:13 Wake-N-Waves4 kern.warn kernel: wl_module_init: txworkq set to 0x0
Jan 1 00:00:13 Wake-N-Waves4 kern.warn kernel: eth0: mixed HW and IP checksum settings.
Jan 1 00:00:13 Wake-N-Waves4 kern.warn kernel: et2: discarding duplicate mcast filter entry
Jan 1 00:00:13 Wake-N-Waves4 kern.warn kernel: et2: discarding duplicate mcast filter entry
Jan 1 00:00:13 Wake-N-Waves4 kern.warn kernel: et2: discarding duplicate mcast filter entry
Jan 1 00:00:13 Wake-N-Waves4 kern.warn kernel: et2: discarding duplicate mcast filter entry
Jan 1 00:00:13 Wake-N-Waves4 kern.warn kernel: et2: discarding duplicate mcast filter entry
Jan 1 00:00:13 Wake-N-Waves4 kern.warn kernel: et2: discarding duplicate mcast filter entry
Jan 1 00:00:13 Wake-N-Waves4 kern.warn kernel: et2: discarding duplicate mcast filter entry
Jan 1 00:00:13 Wake-N-Waves4 kern.warn kernel: et2: discarding duplicate mcast filter entry
Jan 1 00:00:13 Wake-N-Waves4 kern.warn kernel: et2: discarding duplicate mcast filter entry
Jan 1 00:00:13 Wake-N-Waves4 kern.warn kernel: et2: discarding duplicate mcast filter entry
Jan 1 00:00:13 Wake-N-Waves4 kern.warn kernel: et2: discarding duplicate mcast filter entry
Jan 1 00:00:13 Wake-N-Waves4 kern.warn kernel: et2: discarding duplicate mcast filter entry
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: device br0 entered promiscuous mode
Jan 1 00:00:13 Wake-N-Waves4 kern.warn kernel: et2: discarding duplicate mcast filter entry
Jan 1 00:00:13 Wake-N-Waves4 kern.warn kernel: et2: discarding duplicate mcast filter entry
Jan 1 00:00:13 Wake-N-Waves4 kern.warn kernel: et2: discarding duplicate mcast filter entry
Jan 1 00:00:13 Wake-N-Waves4 kern.warn kernel: et2: discarding duplicate mcast filter entry
Jan 1 00:00:13 Wake-N-Waves4 kern.warn kernel: et2: discarding duplicate mcast filter entry
Jan 1 00:00:13 Wake-N-Waves4 kern.warn kernel: et2: discarding duplicate mcast filter entry
Jan 1 00:00:13 Wake-N-Waves4 kern.warn kernel: et2: discarding duplicate mcast filter entry
Jan 1 00:00:13 Wake-N-Waves4 kern.warn kernel: et2: discarding duplicate mcast filter entry
Jan 1 00:00:13 Wake-N-Waves4 kern.warn kernel: et2: discarding duplicate mcast filter entry
Jan 1 00:00:13 Wake-N-Waves4 kern.warn kernel: et2: discarding duplicate mcast filter entry
Jan 1 00:00:13 Wake-N-Waves4 kern.warn kernel: et2: discarding duplicate mcast filter entry
Jan 1 00:00:13 Wake-N-Waves4 kern.warn kernel: et2: discarding duplicate mcast filter entry
Jan 1 00:00:13 Wake-N-Waves4 kern.warn kernel: et2: discarding duplicate mcast filter entry
Jan 1 00:00:13 Wake-N-Waves4 kern.warn kernel: et2: discarding duplicate mcast filter entry
Jan 1 00:00:13 Wake-N-Waves4 kern.warn kernel: et2: discarding duplicate mcast filter entry
Jan 1 00:00:13 Wake-N-Waves4 kern.warn kernel: et2: discarding duplicate mcast filter entry
Jan 1 00:00:13 Wake-N-Waves4 kern.warn kernel: et2: discarding duplicate mcast filter entry
Jan 1 00:00:13 Wake-N-Waves4 kern.warn kernel: et2: discarding duplicate mcast filter entry
Jan 1 00:00:13 Wake-N-Waves4 kern.warn kernel: et2: discarding duplicate mcast filter entry
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: device vlan1 entered promiscuous mode
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: device eth0 entered promiscuous mode
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: br0: port 1(vlan1) entered forwarding state
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: br0: port 1(vlan1) entered forwarding state
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: device vlan2 entered promiscuous mode
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: br0: port 2(vlan2) entered forwarding state
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: br0: port 2(vlan2) entered forwarding state
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: device eth1 entered promiscuous mode
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: br0: port 3(eth1) entered forwarding state
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: br0: port 3(eth1) entered forwarding state
Jan 1 00:00:13 Wake-N-Waves4 kern.warn kernel: IGMP Query send failed
Jan 1 00:00:13 Wake-N-Waves4 kern.warn kernel: IGMP Query send failed
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: device eth3 entered promiscuous mode
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: br0: port 4(eth3) entered forwarding state
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: br0: port 4(eth3) entered forwarding state
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: device br0 left promiscuous mode
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: device br0 entered promiscuous mode
Jan 1 00:00:13 Wake-N-Waves4 kern.info kernel: device br0 left promiscuous mode
Jan 1 00:00:13 Wake-N-Waves4 user.info : upnp : upnp daemon successfully started
Jan 1 00:00:13 Wake-N-Waves4 user.info : cron : cron daemon successfully started
Jan 1 00:00:13 Wake-N-Waves4 cron.info cron[998]: (CRON) STARTUP (fork ok)
Jan 1 00:00:13 Wake-N-Waves4 authpriv.warn dropbear[1018]: Failed loading /tmp/root/.ssh/ssh_host_dss_key
Jan 1 00:00:13 Wake-N-Waves4 user.info : dropbear : ssh daemon successfully started
Jan 1 00:00:13 Wake-N-Waves4 authpriv.info dropbear[1023]: Running in background
Dec 31 19:00:13 Wake-N-Waves4 daemon.info dnsmasq[1028]: started, version 2.77 cachesize 1500
Dec 31 19:00:13 Wake-N-Waves4 daemon.info dnsmasq[1028]: compile time options: IPv6 GNU-getopt no-RTC no-DBus no-i18n no-IDN DHCP DHCPv6 no-Lua no-TFTP no-conntrack no-ipset auth no-DNSSEC loop-detect inotify
Dec 31 19:00:13 Wake-N-Waves4 daemon.info dnsmasq-dhcp[1028]: DHCP, IP range 192.168.0.100 -- 192.168.0.149, lease time 1d
Jan 1 00:00:13 Wake-N-Waves4 user.info : dnsmasq : dnsmasq daemon successfully started
Dec 31 19:00:13 Wake-N-Waves4 daemon.info dnsmasq[1028]: reading /tmp/resolv.dnsmasq
Dec 31 19:00:13 Wake-N-Waves4 daemon.info dnsmasq[1028]: using nameserver 8.8.8.8#53
Dec 31 19:00:13 Wake-N-Waves4 daemon.info dnsmasq[1028]: read /etc/hosts - 10 addresses
Jan 1 00:00:13 Wake-N-Waves4 user.info : vpn modules : vpn modules successfully unloaded
Jan 1 00:00:13 Wake-N-Waves4 user.info : vpn modules : nf_conntrack_proto_gre successfully loaded
Jan 1 00:00:13 Wake-N-Waves4 user.info : vpn modules : nf_nat_proto_gre successfully loaded
Jan 1 00:00:13 Wake-N-Waves4 user.info : vpn modules : nf_conntrack_pptp successfully loaded
Jan 1 00:00:13 Wake-N-Waves4 user.info : vpn modules : nf_nat_pptp successfully loaded
Jan 1 00:00:14 Wake-N-Waves4 user.info : ttraff : traffic counter daemon successfully started
Dec 31 19:00:17 Wake-N-Waves4 daemon.info dnsmasq-dhcp[1028]: DHCPDISCOVER(br0) 00:40:7f:75:11:8c
Dec 31 19:00:17 Wake-N-Waves4 daemon.info dnsmasq-dhcp[1028]: DHCPOFFER(br0) 192.168.0.83 00:40:7f:75:11:8c
Dec 31 19:00:17 Wake-N-Waves4 daemon.info dnsmasq-dhcp[1028]: DHCPREQUEST(br0) 192.168.0.83 00:40:7f:75:11:8c
Dec 31 19:00:17 Wake-N-Waves4 daemon.info dnsmasq-dhcp[1028]: DHCPACK(br0) 192.168.0.83 00:40:7f:75:11:8c SecuritySys
Jan 1 00:00:27 Wake-N-Waves4 kern.info kernel: br0: port 1(vlan1) entered forwarding state
Jan 1 00:00:27 Wake-N-Waves4 kern.info kernel: br0: port 2(vlan2) entered forwarding state
Jan 1 00:00:27 Wake-N-Waves4 kern.info kernel: br0: port 3(eth1) entered forwarding state
Jan 1 00:00:28 Wake-N-Waves4 kern.info kernel: br0: port 4(eth3) entered forwarding state
Jan 1 00:00:29 Wake-N-Waves4 user.info : NAS : NAS lan (wl0 interface) successfully started
Jan 1 00:00:29 Wake-N-Waves4 user.info : NAS : NAS wan (wl1 interface) successfully started
Jan 1 00:00:29 Wake-N-Waves4 user.info : NAS : NAS lan (wl2 interface) successfully started
Jan 1 00:00:29 Wake-N-Waves4 user.info : klogd : kernel log daemon successfully stopped
Jan 1 00:00:29 Wake-N-Waves4 kern.notice kernel: klogd: exiting
Jan 1 00:00:29 Wake-N-Waves4 user.info : resetbutton : resetbutton daemon successfully stopped
Jan 1 00:00:29 Wake-N-Waves4 user.info : syslogd : syslog daemon successfully stopped
Dec 31 19:00:29 Wake-N-Waves4 syslog.info syslogd exiting
Dec 31 19:00:29 Wake-N-Waves4 syslog.info syslogd started: BusyBox v1.24.2
Jan 1 00:00:29 Wake-N-Waves4 user.info : resetbutton : resetbutton daemon successfully started
Jan 1 00:00:29 Wake-N-Waves4 kern.notice kernel: klogd started: BusyBox v1.24.2 (2016-09-12 21:11:55 CEST)
Dec 31 19:00:36 Wake-N-Waves4 daemon.info dnsmasq-dhcp[1028]: DHCPREQUEST(br0) 192.168.0.127 f0:5b:7b:3f:31:7f
Dec 31 19:00:36 Wake-N-Waves4 daemon.info dnsmasq-dhcp[1028]: DHCPACK(br0) 192.168.0.127 f0:5b:7b:3f:31:7f android-83bd00591366b8e8
Dec 31 19:00:41 Wake-N-Waves4 daemon.info dnsmasq-dhcp[1028]: DHCPREQUEST(br0) 192.168.0.102 00:22:75:90:10:e1
Dec 31 19:00:41 Wake-N-Waves4 daemon.info dnsmasq-dhcp[1028]: DHCPACK(br0) 192.168.0.102 00:22:75:90:10:e1 WDTVLiveWNW
Jan 1 00:00:44 Wake-N-Waves4 user.info : vpn modules : vpn modules successfully unloaded
Jan 1 00:00:44 Wake-N-Waves4 user.info : vpn modules : nf_conntrack_proto_gre successfully loaded
Jan 1 00:00:44 Wake-N-Waves4 user.info : vpn modules : nf_nat_proto_gre successfully loaded
Jan 1 00:00:44 Wake-N-Waves4 user.info : vpn modules : nf_conntrack_pptp successfully loaded
Jan 1 00:00:44 Wake-N-Waves4 user.info : vpn modules : nf_nat_pptp successfully loaded
Jan 1 00:00:44 Wake-N-Waves4 user.info : process_monitor successfully started
Jan 1 00:00:44 Wake-N-Waves4 user.info : upnp : upnp daemon successfully stopped
Dec 31 19:00:44 Wake-N-Waves4 daemon.info dnsmasq-dhcp[1028]: DHCPDISCOVER(br0) 00:6b:9e:d9:a0:4c
Dec 31 19:00:44 Wake-N-Waves4 daemon.info dnsmasq-dhcp[1028]: DHCPOFFER(br0) 192.168.0.144 00:6b:9e:d9:a0:4c
Dec 31 19:00:44 Wake-N-Waves4 daemon.info dnsmasq[1028]: reading /tmp/resolv.dnsmasq
Dec 31 19:00:44 Wake-N-Waves4 daemon.info dnsmasq[1028]: using nameserver 8.8.8.8#53
Dec 31 19:00:44 Wake-N-Waves4 daemon.info dnsmasq[1028]: using nameserver 8.8.4.4#53
Dec 31 19:00:44 Wake-N-Waves4 daemon.info dnsmasq[1028]: using nameserver 192.168.30.1#53
Dec 31 19:00:44 Wake-N-Waves4 daemon.info dnsmasq-dhcp[1028]: DHCPREQUEST(br0) 192.168.0.144 00:6b:9e:d9:a0:4c
Dec 31 19:00:44 Wake-N-Waves4 daemon.info dnsmasq-dhcp[1028]: DHCPACK(br0) 192.168.0.144 00:6b:9e:d9:a0:4c
Jan 1 00:00:44 Wake-N-Waves4 user.info : upnp : upnp daemon successfully started
Jan 1 00:00:44 Wake-N-Waves4 user.info : wland : WLAN daemon successfully stopped
Sep 18 15:03:32 Wake-N-Waves4 user.info : cron : cron daemon successfully stopped
Sep 18 15:03:32 Wake-N-Waves4 user.info : wland : WLAN daemon successfully started
Sep 18 11:03:32 Wake-N-Waves4 daemon.info dnsmasq[1028]: reading /tmp/resolv.dnsmasq
Sep 18 11:03:32 Wake-N-Waves4 daemon.info dnsmasq[1028]: using nameserver 8.8.8.8#53
Sep 18 11:03:32 Wake-N-Waves4 daemon.info dnsmasq[1028]: using nameserver 8.8.4.4#53
Sep 18 11:03:32 Wake-N-Waves4 daemon.info dnsmasq[1028]: using nameserver 192.168.30.1#53
Sep 18 15:03:33 Wake-N-Waves4 daemon.debug process_monitor[1463]: Restarting cron (time sync change)
Sep 18 15:03:33 Wake-N-Waves4 user.info : snmpd : SNMP Daemon successfully stopped
Sep 18 15:03:33 Wake-N-Waves4 user.info : cron : cron daemon successfully started
Sep 18 15:03:33 Wake-N-Waves4 cron.info cron[1585]: (CRON) STARTUP (fork ok)
Sep 18 15:03:33 Wake-N-Waves4 user.info : vpn modules : vpn modules successfully unloaded
Sep 18 15:03:33 Wake-N-Waves4 user.info : vpn modules : nf_conntrack_proto_gre successfully loaded
Sep 18 15:03:33 Wake-N-Waves4 user.info : vpn modules : nf_nat_proto_gre successfully loaded
Sep 18 15:03:33 Wake-N-Waves4 user.info : vpn modules : nf_conntrack_pptp successfully loaded
Sep 18 15:03:33 Wake-N-Waves4 user.info : vpn modules : nf_nat_pptp successfully loaded
Sep 18 15:03:33 Wake-N-Waves4 user.info : process_monitor : Process Monitor successfully stopped
Sep 18 15:03:33 Wake-N-Waves4 user.info : process_monitor successfully started
Sep 18 15:03:33 Wake-N-Waves4 user.info : upnp : upnp daemon successfully stopped
Sep 18 15:03:33 Wake-N-Waves4 user.info : upnp : upnp daemon successfully started
Sep 18 15:03:33 Wake-N-Waves4 user.info : wland : WLAN daemon successfully stopped
Sep 18 15:03:33 Wake-N-Waves4 user.info : wland : WLAN daemon successfully started
Sep 18 15:03:33 Wake-N-Waves4 user.info : WAN is up. IP: 192.168.30.5
Sep 18 15:03:36 Wake-N-Waves4 daemon.err process_monitor[1629]: Last update failed, we need to re-update after 30 seconds
Sep 18 15:03:36 Wake-N-Waves4 daemon.debug process_monitor[1629]: We need to re-update after 3600 seconds
Sep 18 15:03:36 Wake-N-Waves4 daemon.info process_monitor[1629]: set timer: 3600 seconds, callback: ntp_main()
Sep 18 15:03:47 Wake-N-Waves4 user.debug : ttraff: data collection started
Sep 18 11:03:54 Wake-N-Waves4 daemon.info dnsmasq-dhcp[1028]: DHCPREQUEST(br0) 192.168.0.134 e4:8b:7f:a2:c2:ba
Sep 18 11:03:54 Wake-N-Waves4 daemon.info dnsmasq-dhcp[1028]: DHCPACK(br0) 192.168.0.134 e4:8b:7f:a2:c2:ba iPad

Hope that helps.

oso97
DD-WRT Novice

Joined: 21 Dec 2016
Posts: 7

Posted: Fri Dec 30, 2016 1:40 Post subject:

I posted this in one of the other ASUS RT-AC5300 threads, but this one appears to be a bit more active, and includes the Kong who is doing the builds...

I'm not able to get external internet.

NOTE: All connections are wired.

Firmware: DD-WRT v3.0-r30965M (12/21/16).
Router connecting via DHCP and receiving an IP address of 192.168.1.143.
DHCP is active. No modifications have been made to any default settings. Local computer receives an ip address.

The external network indicator light is red on the front of the router.

Local computer is unable to access the external internet.

I have also verified that plugging the network cable going into the router directly into the computer will allow access. Something is definitely going on at the level of the router.

UPDATE: This problem only appears if the subnet that the RT-AC5300 is being pugged into is 192.168.1.x. I suspect it may be a configuration issue? Note that in this case, the LED light for the external internet still is RED.

chchia
DD-WRT User

Joined: 20 Dec 2009
Posts: 63

Posted: Fri Dec 30, 2016 2:20 Post subject:

oso97 wrote:

just wonder, your router dhcp is leasing what ip to connected client?

dd-wrt by default is 192.168.1.x
and you mention that the wan port is getting ip 192.168.1.143

from what i understand this will cause conflict, perhaps you can try change your dd-wrt ip to something else like 192.168.10.x

oso97
DD-WRT Novice

Joined: 21 Dec 2016
Posts: 7

Posted: Fri Dec 30, 2016 2:33 Post subject:

So, this is definitely specific to this model of router. I've had others (a Netgear R6300 and a Netgear WNR2000 v2) that I can set their DHCP to be giving out 192.168.1.x addresses and it works just fine.

There's actually a specific reason I need to do this actually that has to do with some highly un-configurable pieces of equipment (they can operate on 192.168.1.101-199) and their need to be on the same subnet as the computer that will need to interface with them. And the system needs to be able to be plopped down into different venues, some of which have their internal networks operating on the 192.168.1.x subnet.

Previously I was using the Netgear WNR2000 v2 as the gateway/DHCP server, but I wanted to upgrade to something with better wireless capabilities and a number of other options that I'm hoping to deploy.

chchia
DD-WRT User

Joined: 20 Dec 2009
Posts: 63

Posted: Fri Dec 30, 2016 3:20 Post subject:

oso97 wrote:

i too used to have some similar situation as you, what i did i disabled the wan connection, use vlan to bind the wan port to lan, disable the dhcp server on the router, set an ip on the router and start using. hope this method work for you too.

ps: i will never like to have two dhcp server giving same subnet running same time.

rommer
DD-WRT Novice

Joined: 13 Apr 2016
Posts: 39

Posted: Sun Apr 30, 2017 22:47 Post subject: After not using my system since the beginning of winter...
...Ethernet ports just refuse to work. Even with static ips. It all worked before I put the boat away but now it doesn't. I tried the latest Kong build and even went back to the one he released for me on 9/12/16 and I can't get the switch ports to work. Help?

rommer
DD-WRT Novice

Joined: 13 Apr 2016
Posts: 39

Posted: Mon May 01, 2017 1:04 Post subject:
Just finished some more testing. 1) DHCP does not work on switch ports. 2) Static wired connections can ping other wired connections. 3) Wireless connections can ping other wireless connections. 4) Wired can't ping wireless. 5) Wireless can't ping wired. So strange since it USED to work?????

Per Yngve Berg
DD-WRT Guru

Joined: 13 Aug 2013
Posts: 6870
Location: Romerike, Norway

Posted: Mon May 01, 2017 7:12 Post subject:
What is the output of "nvram show \| grep vlan*.ports"? It appears that the port that connects the switch to the router is mis-configured.

rommer
DD-WRT Novice

Joined: 13 Apr 2016
Posts: 39

Posted: Mon May 01, 2017 11:38 Post subject:
nvram show \| grep vlan.ports vlan2ports=0 5u size: 59667 bytes (71405 left) vlan1ports=1 2 3 4 5

Goto page Previous 1, 2, 3 Next

Display posts from previous:

Page 2 of 3

DD-WRT Forum Index -> Broadcom SoC based Hardware

All times are GMT

Navigation

Jump to:

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You can attach files in this forum
You can download files in this forum

Log in

ASUS RT-AC5300 Switch Ports

Quick Links

Log in