Recent content by NickBurns

I guess I'll have to accept that... that the lldpd service, while present, was not intended for use as I would like to you use - for network mapping purposes - since it's freely advertising itself on the local network. For now I've written a script task to ssh into my four routers/repeaters and...

I suppose I'd like some help to learn how to manipulate the system here. I can see the executables make a call to a run_lldpd.sh script, if present. In the /tmp sub-directory on each of my routers/repeaters there is one. It does not have the +x bit set. Doing so I can run it (and I can edit it...

So I've made some headway on this. The default LLDPD running is lldpd -L /usr/sbin/lldpcli -I eth2,eth1,eth5,eth6,eth7,wl1.2,wds0.*.*,wds1.*.* -s RT-AX86U ... and thinking now bond0/br0 are no no's (thank you btw) why the order above is/was selected considering I have two ports in LAG. Guess...

So my mistake - yes this is bond0 vs br0. The moment I enable bond0 I get the LLDP advertisements to my connected switch. Where are you reading that LLDP should not be advertised by bonded/LAG interfaces?

Not in this case. Definitely LLDP. I support products that draw network maps based on LLDP data advertised by devices to switches/routers that support LLDP and SNMP.

Hello All. RT-AC5300 RT-AX86U RP-AC1900 I have my ASUS routers under LAN -> Switch Control set for link aggregation. The resulting interface is br0. The default LLDPD call appears to be below which omits br0. The line below is from my RP-AC1900 which also incorrectly identifies the product as...

So I think I've reproduced it. I re-enabled / re-linked Alexa. In order to do so I had to change my WAN HTTPS port from x back to 443. I then asked Alexa ASUS ROUTER to simply enable a guest Wifi. The Alexa app said it created network Y with a code for 3 hours - Amazingly it worked. During this...

What you are seeing is normal AFAIK. The May 5th date - not sure where the system gets that but that is the date it has on a cold start boot. When it finally NTP syncs its time to get a real clock it shifts to the current date/time stamp. This is from my router tonight since I'm troubleshooting...

Working on this some more tonight. I have a feeling this is ALEXA/IFTTT. I've never enabled IFTTT (yet GUI says I've successfully registered)... I've now disabled ASUSWRT on the alexa.amazon.com side and rebooted my router. I watched it try to reach out to the server; spawn a few nt_center...

I did the full factory reset 14 days ago as much as it was a pain. It's about the fourth time in just over a year. It's taking less time to recover/rebuild however since I'm getting much better at wash, rinse, repeat. What bothers me is that following a reboot the router will operate fine for...

nt_center admin@RT-AC5300:/tmp# netstat -anp|grep -i nt_cent tcp 518 0 <my_ISP_ip>:43382 99.83.159.30:443 CLOSE_WAIT 23602/nt_center tcp 518 0 <my_ISP_ip>:43384 99.83.159.30:443 CLOSE_WAIT 23602/nt_center tcp 348 0 <my_ISP_ip>:43394...

... I have a feeling the unattended restarts are due to the /tmp/HTTPD_DEBUG flag being set.

I left the system alone with TCP sessions in ESTABLISHED state as above... the below entries - I did not initiate a restart @ 11:16. May 28 11:02:51 RT-AC5300: start httpd:80 May 28 11:02:52 httpd...

I've been chasing this issue for quite a long time now spanning several releases of ASUSWRT. I am currently on the latest - 386_2.4 and have diligently updated as time has gone by and have twice factory defaulted and configured from scratch this router. I am looking to avoid that hassle again...

Strangely, this issue just 'went away' and I haven't seen it re-occur since I first reported it 07/15. If I run 'netstat -nl' now it terminates correctly and doesn't constant loop.