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. R

    Wireguard site to site help - AVM Fritzbox strange behavior

    Slightly different, but about 18 months ago I was trying to set up Wireguard from Fritz 7530 to Asus RT-AX86S. - I gave up after Christmas, so didn't spot this - you got further than I did. Just tried again and absolutely same issue despite numerous updates on both ends in terms of firmware. I...
  2. R

    RT-AX86S and saved syslog showing: kernel: br0: received packet on eth1 with own address as source address

    Re loopback - understood. I would have to say don't think there is much there unless any of the "intelligent" devices are doing something that I'm not aware of. I usually configure most things to not dial home etc. but doesn't mean I haven't missed something. re. ports, I have direct connection...
  3. R

    RT-AX86S and saved syslog showing: kernel: br0: received packet on eth1 with own address as source address

    I do, but manually when I'm looking at web interfaces on speakers, recorder boxes etc. but not at the rate that this seems to be clocking up messages. Is that what you meant? not heard of look back before, what's the purpose? but again surely if this is causing the logging to overflow from...
  4. R

    RT-AX86S and saved syslog showing: kernel: br0: received packet on eth1 with own address as source address

    Well, I had one guest network (seems a sensible idea) and disabling that got rid of br1, but br2 remains. I assume, given the br0 : ...on eth1 text, that br0 is the wired LAN interface.
  5. R

    RT-AX86S and saved syslog showing: kernel: br0: received packet on eth1 with own address as source address

    So, purchased new router before Christmas. Installed and running OK. This to replace an ageing Draytek, which was solid but couldn't process the new 300M fibre link. No real issues, everything was fast and looked OK. Then we had one or two instances of delayed page loading in browsers on wired...
  6. R

    Asus WifiPro ET12 & AsusWRT advice sought

    Thanks, I'll bung that part of the i/f in the ignore bucket then for now. At the end of the day that's a nice to have.
  7. R

    Asus WifiPro ET12 & AsusWRT advice sought

    Thanks. I sort of got there in the end. Not being used to AsusWRT interface I think I made a couple of assumptions about what it was telling me and they were wrong. Lack of AiMesh node connecting was actually incorrect. It did connect, but slowly for some reason even tho' cabled and didn't show...
  8. R

    Zenwifi Pro XT12 2.4GHz wifi

    Well, fixed the Dell, despite Microsoft and Intel automatic driver checkers telling me it was the latest driver, it wasn't. Downloaded manually (from the Intel site !??), updated and it's seeing the new network SSIDs now.
  9. R

    Zenwifi Pro XT12 2.4GHz wifi

    Not sure it helps per se, but I have a couple of Windows 10 devices that can't see an SSID on a new ET12 2.4GHz network. One is a laptop (old dell XPS 13) that dual boots into Mint and same hardware with Mint sees the network fine and connects so it's definitely not the laptop hardware it's the...
  10. R

    Asus WifiPro ET12 & AsusWRT advice sought

    So, just bought a pair of ET12s, to extend my network into the newer age as far as Wifi is concerned. Great hopes for this and chosen because it's "so easy" to set up and from what I've read AsusWRT is really configurable etc. so should be able to do most of what I want in the future. but... no...
Top