Menu
What's new
By:
Filters Better Search

Search results

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

  1. Pegasus9

    Replacing AC5300 -- AX6000 or AX11000

    Thanks for the input. I liked the AX11000 was looking at trying to get the best speed possible and good coverage for 3000sq ft. I will take a look at the AX86U before finalizing.
  2. Pegasus9

    Replacing AC5300 -- AX6000 or AX11000

    My AC5300 is dying and I need to replace it -- not the best timing but I can get it to hang on long enough to put somehting new on line. I am considering the ASUS AX6000 and AX11000. The price difference is negligible. I am not a gamer but like the power a gaming router gives me. 100+ Smart...
  3. Pegasus9

    RT-AC5300 Getting Rid of Ghost Device From Network List

    ..and then when I was almost asleep I remembered a file I created five years ago to allow WOL. A JFFS file that had the information for the PC I would use to access my system while on the road. I deleted the file with the old PCs information, rebooted the router -- and the ghost is gone. This...
  4. Pegasus9

    RT-AC5300 Getting Rid of Ghost Device From Network List

    Yep -- unplugged -- waited five and plugged back in. Still there. Maybe I need to sleep with the light on.
  5. Pegasus9

    RT-AC5300 Getting Rid of Ghost Device From Network List

    Did so, walked through it again to be sure. The entry for the PC is the last one in the list and shows active -- even though it does not exist. I renamed it Poltergeist and it stuck. It says it is a wired connection. I have unplugged all cables and it is still there.
  6. Pegasus9

    RT-AC5300 Getting Rid of Ghost Device From Network List

    Tried this and after an hour the ghost was back.
  7. Pegasus9

    RT-AC5300 Getting Rid of Ghost Device From Network List

    Well, it lasted for only about 8 hours, then the ghost was back.
  8. Pegasus9

    RT-AC5300 Getting Rid of Ghost Device From Network List

    Thanks!
  9. Pegasus9

    RT-AC5300 Getting Rid of Ghost Device From Network List

    I have applied every Merlin update within days of release, but I did not do a full factory reset of the device everytime I did that.
  10. Pegasus9

    RT-AC5300 Getting Rid of Ghost Device From Network List

    Okay, I had an epiphany, tried it, and it worked. Thought I would share in case anyone else ever runs into it. Gave a second system the offending IP, brought it on line -- bang the ghost system vanished. Changed the IP, leaving the offending ip free to reappear, but so far it has not come...
  11. Pegasus9

    RT-AC5300 Getting Rid of Ghost Device From Network List

    Thought rewording this might help get some input: Deleted PC three plus years ago. Have booted router numerous times since then but the PC still appears on the client list. IP isn't reserved or found anywhere on the network. TRACERT shows no mapping and not held in any cache anywhere I can...
  12. Pegasus9

    FireTV ip address weirdness on RT-AC5300

    That solved it, thanks and for the information about Pastebin
  13. Pegasus9

    FireTV ip address weirdness on RT-AC5300

    Wouldn't all fit in one message pegasus9@RT-AC5300-9110:/tmp/home/root# brctl show bridge name bridge id STP enabled interfaces br0 8000.2cfda1029110 yes vlan1 wl0.2...
  14. Pegasus9

    FireTV ip address weirdness on RT-AC5300

    ASUSWRT-Merlin RT-AC5300 386.3_2 Fri Aug 6 21:47:27 UTC 2021 pegasus9@RT-AC5300-9110:/tmp/home/root# ifconfig br0 Link encap:Ethernet HWaddr 2C:FD:A1:02:91:10 inet addr:192.168.123.99 Bcast:192.168.123.255 Mask:255.255.255.0 UP BROADCAST RUNNING ALLMULTI MULTICAST...
  15. Pegasus9

    FireTV ip address weirdness on RT-AC5300

    By stock, I mean one of the standard netwroks for the router, not one of the guest networks. It is connected to the 2.4 network.
  16. Pegasus9

    FireTV ip address weirdness on RT-AC5300

    Just reread this and checked out the device and network. I don't have active AIMesh, as I only have one node. The device is logged into the stock 2.4 network (5.0 was not staying connected).
  17. Pegasus9

    FireTV ip address weirdness on RT-AC5300

    Ah! That is where it came from! Thanks.
  18. Pegasus9

    FireTV ip address weirdness on RT-AC5300

    I have an Amazon FireTV device that shows up within the router having an ip address of 192.168.101.168. The problem is that the network ip's are 192.168.123.xxx. This device has an ip assigned using the correct subnet but for some reason is ignoring it. It works, I just don't like the wierd...
  19. Pegasus9

    RT-AC5300 Getting Rid of Ghost Device From Network List

    Yes, many times. Merlin Firmware Version:386.3_2. None that I am aware of. This is not the first device to leave the network but the only one I am having a problem with still showing up in the router.
  20. Pegasus9

    RT-AC5300 Getting Rid of Ghost Device From Network List

    I had an HP PC several years ago. I got rid of it because it died. The entry in the Network Map is still there. There is no reserved ip for the device either, it just won't go away. Any suggestions?
Top