• Wireless router puzzle

    From liz@liz@poppyrecords.invalid.invalid (Liz Tuddenham) to uk.comp.sys.mac on Tue Nov 3 08:48:35 2026
    From Newsgroup: uk.comp.sys.mac

    (Mac Mini OS 10.15.7)

    I've just had a wireless router fitted as part of the change to fibre,
    it identifies itself as a "Heights Telecom HT-6766BE". I can log into
    it by Ethernet but do not seem to be able to contact it by wireless.

    I thought it was connecting by Wireless when I first tried it using the
    default settings but I now realise the Ethernet was also connected and
    that might have misled me. When I changed the SSID and password, then
    tested by removing the Ethernet plug, I found I had no connection.

    I have checked that the passwords in the router and Keychain are
    identical. The Network>Wi-Fi panel shows "Wi-Fi is connected and has
    the IP address 192.169.1.105". If I change the router password to
    nonsense, switch off the Wi-Fi and switch it back on again, the
    Network>Wi-Fi panel again shows it is connected when it obviously can't
    be.

    What is going on?.
    --
    ~ Liz Tuddenham ~
    (Remove the ".invalid"s and add ".co.uk" to reply)
    www.poppyrecords.co.uk
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From liz@liz@poppyrecords.invalid.invalid (Liz Tuddenham) to uk.comp.sys.mac on Tue Nov 3 09:04:41 2026
    From Newsgroup: uk.comp.sys.mac

    [...]

    Followup: I've just tried changing the password to nonsense again and
    this time it failed to connect, so that was a red herring. The router
    still won't connect to the Internet by Wi-Fi.
    --
    ~ Liz Tuddenham ~
    (Remove the ".invalid"s and add ".co.uk" to reply)
    www.poppyrecords.co.uk
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From David Brooks@boaterdave@hotmail.co.uk to uk.comp.sys.mac on Tue Nov 3 09:43:27 2026
    From Newsgroup: uk.comp.sys.mac

    On 03/11/2026 09:04, Liz Tuddenham wrote:
    [...]

    Followup: I've just tried changing the password to nonsense again and
    this time it failed to connect, so that was a red herring. The router
    still won't connect to the Internet by Wi-Fi.

    Classic Usenet diagnostic puzzle from Liz. Putting the pieces together,
    a few distinct technical factors explain what's happening on uk.comp.sys.mac:1. The Hardware & Software MismatchThe Router: The
    Heights Telecom HT-6766BE is a modern Wi-Fi 7 (BE6500) gateway (commonly deployed by UK fibre altnets like Zzoomm) running OpenSync/Plume
    containerized firmware. Out of the box, these routers default to strict
    WPA3 or modern WPA3/WPA2 mixed mode encryption with Protected Management Frames (PMF) enabled. The Client: A Mac Mini running macOS 10.15.7 (Catalina). Released back in late 2020, CatalinarCOs Wi-Fi supplicant has notoriously flaky or incomplete support for modern WPA3 SAE
    (Simultaneous Authentication of Equals) handshakes and Wi-Fi 7 beacon parameters.2. The False-Positive "Connected" StateLiz notes that even
    after breaking the password or changing it to nonsense, the Network pane stubbornly claims Wi-Fi is connected.Layer 2 vs. Layer 3/Handshake:
    macOS Catalina caches SSID profiles aggressively. When the Mac sees the broadcast SSID match a saved profile, the menu bar often registers a
    Layer 2 association or reads from cached state.The Handshake Failure:
    Even though the Mac associates with the radio broadcast, the actual
    4-way WPA authentication key exchange fails because Catalina cannot
    properly negotiate the modern encryption cipher requested by the
    HT-6766BE. Hence, no DHCP lease is pulled, traffic doesn't flow, and
    dropping the Ethernet cable leaves her stranded without an IP route.
    (Her mention of 192.169.1.105 is likely a minor transposition for
    192.168. or a self-assigned link-local artifact from a stalled DHCP negotiation).The Remedy for LizTo get the Catalina Mac Mini talking to
    the new fibre router over wireless, she needs to log into the HT-6766BE
    admin panel via Ethernet and drop the wireless security setting from its default WPA3/mixed mode down to standard WPA2-PSK (AES). Once legacy-compatible WPA2 encryption is enforced on the router's
    2.4GHz/5GHz bands, the older Mac's supplicant will successfully complete
    the handshake.

    =

    That was the answer from Gemini.

    I hope it helps.
    --
    David
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris@ithinkiam@gmail.com to uk.comp.sys.mac on Tue Nov 3 12:10:55 2026
    From Newsgroup: uk.comp.sys.mac

    Liz Tuddenham <liz@poppyrecords.invalid.invalid> wrote:
    [...]

    Followup: I've just tried changing the password to nonsense again and
    this time it failed to connect, so that was a red herring. The router
    still won't connect to the Internet by Wi-Fi.

    Does it connect to the router? i.e. can you get into the router's admin interface when only connected by wifi?

    If you can, which sounds like the case, this is a router issue and your ISP should be able to help.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From John@Man@the.keyboard to uk.comp.sys.mac on Tue Nov 3 12:13:52 2026
    From Newsgroup: uk.comp.sys.mac

    On Tue, 3 Nov 2026 08:48:35 +0000, liz@poppyrecords.invalid.invalid
    (Liz Tuddenham) wrote:

    (Mac Mini OS 10.15.7)

    I've just had a wireless router fitted as part of the change to fibre,
    it identifies itself as a "Heights Telecom HT-6766BE". I can log into
    it by Ethernet but do not seem to be able to contact it by wireless.

    I know that this is admitting defeat before you've even tried to fix
    it but have you considered calling the Helpdesk of your fibre
    provider. the guys who fitted the box?

    They may have a quick, simple, "Please press button Q, Ma'am." type
    of suggestion. :)


    I thought it was connecting by Wireless when I first tried it using the >default settings but I now realise the Ethernet was also connected and
    that might have misled me. When I changed the SSID and password, then
    tested by removing the Ethernet plug, I found I had no connection.

    Yeah I did that, years ago, when first setting up a connection. It
    only occurred to me that I was going through the wire when I sat down
    and the wire popped out. :)




    I have checked that the passwords in the router and Keychain are
    identical. The Network>Wi-Fi panel shows "Wi-Fi is connected and has
    the IP address 192.169.1.105". If I change the router password to
    nonsense, switch off the Wi-Fi and switch it back on again, the
    Network>Wi-Fi panel again shows it is connected when it obviously can't
    be.

    What is going on?.

    Stupid question, but does your Mini actually *know* that you want to
    use the wi-fi? Have you switched on the protocols and other bits to
    activate it? I ask because the Mini, being a really clever little
    bugger, may have over-ridden wi-fi when it saw a quicker, easier route
    that she could use.

    Sorry if that's idiotic and if you've already checked.

    Mac Mini boxes are really good kit. :)

    J.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From liz@liz@poppyrecords.invalid.invalid (Liz Tuddenham) to uk.comp.sys.mac on Tue Nov 3 14:21:29 2026
    From Newsgroup: uk.comp.sys.mac

    John <Man@the.keyboard> wrote:

    On Tue, 3 Nov 2026 08:48:35 +0000, liz@poppyrecords.invalid.invalid
    (Liz Tuddenham) wrote:

    (Mac Mini OS 10.15.7)

    I've just had a wireless router fitted as part of the change to fibre,
    it identifies itself as a "Heights Telecom HT-6766BE". I can log into
    it by Ethernet but do not seem to be able to contact it by wireless.

    I know that this is admitting defeat before you've even tried to fix
    it but have you considered calling the Helpdesk of your fibre
    provider. the guys who fitted the box?

    They may have a quick, simple, "Please press button Q, Ma'am." type
    of suggestion. :)

    I have waited an hour on hold without getting an answer, there are
    reviews that say their waiting time is longer than 2 hours. E-mails
    receive an automated response saying there will be a reply in 4 days -
    but there often isn't. Apparently they have recently bought another ISP
    and have been overwhelmed with the work it has created.

    I have had a '4-day' reponse to an e-mail I sent them with a request for
    a reverse DNS; as a precautionary measure I have backed it up with a
    letter addressed to their registered office
    --
    ~ Liz Tuddenham ~
    (Remove the ".invalid"s and add ".co.uk" to reply)
    www.poppyrecords.co.uk
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From liz@liz@poppyrecords.invalid.invalid (Liz Tuddenham) to uk.comp.sys.mac on Tue Nov 3 14:21:29 2026
    From Newsgroup: uk.comp.sys.mac

    Chris <ithinkiam@gmail.com> wrote:

    Liz Tuddenham <liz@poppyrecords.invalid.invalid> wrote:
    [...]

    Followup: I've just tried changing the password to nonsense again and
    this time it failed to connect, so that was a red herring. The router still won't connect to the Internet by Wi-Fi.

    Does it connect to the router? i.e. can you get into the router's admin interface when only connected by wifi?

    If you can, which sounds like the case, this is a router issue and your ISP should be able to help.

    I don't think it would allow admin access by Wi_fi , the previous one
    didn't.
    --
    ~ Liz Tuddenham ~
    (Remove the ".invalid"s and add ".co.uk" to reply)
    www.poppyrecords.co.uk
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From John@Man@the.keyboard to uk.comp.sys.mac on Tue Nov 3 14:59:47 2026
    From Newsgroup: uk.comp.sys.mac

    On Tue, 3 Nov 2026 14:21:29 +0000, liz@poppyrecords.invalid.invalid
    (Liz Tuddenham) wrote:

    John <Man@the.keyboard> wrote:

    On Tue, 3 Nov 2026 08:48:35 +0000, liz@poppyrecords.invalid.invalid
    (Liz Tuddenham) wrote:

    (Mac Mini OS 10.15.7)

    I've just had a wireless router fitted as part of the change to fibre,
    it identifies itself as a "Heights Telecom HT-6766BE". I can log into
    it by Ethernet but do not seem to be able to contact it by wireless.

    I know that this is admitting defeat before you've even tried to fix
    it but have you considered calling the Helpdesk of your fibre
    provider. the guys who fitted the box?

    They may have a quick, simple, "Please press button Q, Ma'am." type
    of suggestion. :)

    I have waited an hour on hold without getting an answer, there are
    reviews that say their waiting time is longer than 2 hours. E-mails
    receive an automated response saying there will be a reply in 4 days -
    but there often isn't. Apparently they have recently bought another ISP
    and have been overwhelmed with the work it has created.

    Oh.

    Right.

    Sorry. I'm still thinking of the days when I did some support stuff,
    when we opened the phone line within a couple of rings and tried to
    deal with stuff immediately the caller told us what was going on. It's
    been a while since "Helpdesk" actually included help as part of their
    function, :) .


    You *might* find support online for your router at these search page
    results:


    https://www.startpage.com/do/dsearch?q=Heights+Telecom+HT-6766BE&cat=web&language=english
    somewhere in the list could be something useful. If not, at least
    you'll have something to read for a while.



    I have had a '4-day' reponse to an e-mail I sent them with a request for
    a reverse DNS; as a precautionary measure I have backed it up with a
    letter addressed to their registered office

    Yes, well, in UKland a snail-mail, made-of-paper letter is almost
    guaranteed to be delivered sometime before the heatdeath of the
    cosmos, unless they lose it or it's not "First Class". Again, there
    was once a time when letters could be delivered the day after postage
    almost anywhere on the mainland and on most islands if the weather
    co-operated. This hasn't been true for years.

    Still, you are probably correct in thinking that the paper copy could
    arrive years before they look at the emails. :)

    I apologise for bothering you,

    J.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From liz@liz@poppyrecords.invalid.invalid (Liz Tuddenham) to uk.comp.sys.mac on Tue Nov 3 16:03:51 2026
    From Newsgroup: uk.comp.sys.mac

    John <Man@the.keyboard> wrote:

    [...]
    You *might* find support online for your router at these search page results:


    https://www.startpage.com/do/dsearch?q=Heights+Telecom+HT-6766BE&cat=web&l anguage=english somewhere in the list could be something useful. If not,
    at least you'll have something to read for a while.

    [...]

    I apologise for bothering you,

    No bother - I hadn't thought there was any chance of finding a manual -
    so I hadn't bothered looking. Thanks for pointing me in a potentially
    helpful direction.
    --
    ~ Liz Tuddenham ~
    (Remove the ".invalid"s and add ".co.uk" to reply)
    www.poppyrecords.co.uk
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From David Sankey@davidsankey9@icloud.com to uk.comp.sys.mac on Tue Nov 3 16:25:45 2026
    From Newsgroup: uk.comp.sys.mac

    On 03/11/2026 09:43, David Brooks wrote:
    On 03/11/2026 09:04, Liz Tuddenham wrote:
    [...]

    Followup:-a I've just tried changing the password to nonsense again and
    this time it failed to connect, so that was a red herring.-a The router
    still won't connect to the Internet by Wi-Fi.

    Classic Usenet diagnostic puzzle from Liz. Putting the pieces together,
    a few distinct technical factors explain what's happening on uk.comp.sys.mac:1. The Hardware & Software MismatchThe Router: The
    Heights Telecom HT-6766BE is a modern Wi-Fi 7 (BE6500) gateway (commonly deployed by UK fibre altnets like Zzoomm) running OpenSync/Plume containerized firmware. Out of the box, these routers default to strict
    WPA3 or modern WPA3/WPA2 mixed mode encryption with Protected Management Frames (PMF) enabled.-a-a The Client: A Mac Mini running macOS 10.15.7 (Catalina). Released back in late 2020, CatalinarCOs Wi-Fi supplicant has notoriously flaky or incomplete support for modern WPA3 SAE
    (Simultaneous Authentication of Equals) handshakes and Wi-Fi 7 beacon parameters.2. The False-Positive "Connected" StateLiz notes that even
    after breaking the password or changing it to nonsense, the Network pane stubbornly claims Wi-Fi is connected.Layer 2 vs. Layer 3/Handshake:
    macOS Catalina caches SSID profiles aggressively. When the Mac sees the broadcast SSID match a saved profile, the menu bar often registers a
    Layer 2 association or reads from cached state.The Handshake Failure:
    Even though the Mac associates with the radio broadcast, the actual 4-
    way WPA authentication key exchange fails because Catalina cannot
    properly negotiate the modern encryption cipher requested by the
    HT-6766BE. Hence, no DHCP lease is pulled, traffic doesn't flow, and dropping the Ethernet cable leaves her stranded without an IP route.
    (Her mention of 192.169.1.105 is likely a minor transposition for
    192.168. or a self-assigned link-local artifact from a stalled DHCP negotiation).The Remedy for LizTo get the Catalina Mac Mini talking to
    the new fibre router over wireless, she needs to log into the HT-6766BE admin panel via Ethernet and drop the wireless security setting from its default WPA3/mixed mode down to standard WPA2-PSK (AES). Once legacy- compatible WPA2 encryption is enforced on the router's 2.4GHz/5GHz
    bands, the older Mac's supplicant will successfully complete the handshake.

    =

    That was the answer from Gemini.

    I hope it helps.

    That's not actually crazy!
    If we are talking macOS 10.15.7 then enabling obsolete encryption is
    probably necessary, the WiFi itself should automatically fall back to something compatible.

    192.169.x.x is hopefully just a typo, should be 192.168.x.x.

    D
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Theo@theom+news@chiark.greenend.org.uk to uk.comp.sys.mac on Tue Nov 3 16:47:29 2026
    From Newsgroup: uk.comp.sys.mac

    John <Man@the.keyboard> wrote:
    On Tue, 3 Nov 2026 14:21:29 +0000, liz@poppyrecords.invalid.invalid
    (Liz Tuddenham) wrote:

    John <Man@the.keyboard> wrote:

    On Tue, 3 Nov 2026 08:48:35 +0000, liz@poppyrecords.invalid.invalid
    (Liz Tuddenham) wrote:

    (Mac Mini OS 10.15.7)

    I've just had a wireless router fitted as part of the change to fibre,
    it identifies itself as a "Heights Telecom HT-6766BE". I can log into
    it by Ethernet but do not seem to be able to contact it by wireless.

    I know that this is admitting defeat before you've even tried to fix
    it but have you considered calling the Helpdesk of your fibre
    provider. the guys who fitted the box?

    They may have a quick, simple, "Please press button Q, Ma'am." type
    of suggestion. :)

    I have waited an hour on hold without getting an answer, there are
    reviews that say their waiting time is longer than 2 hours. E-mails >receive an automated response saying there will be a reply in 4 days -
    but there often isn't. Apparently they have recently bought another ISP >and have been overwhelmed with the work it has created.

    My Truespeed service is on a 4 working day fault resolution time, but I've
    not had cause to contact them as nothing has gone wrong. When neighbours
    have they've been there same-day or next-day.

    (I went with them somewhat grudgingly, given I had a lot of run-ins with the County Broadband salespeople, but the FTTC was increasingly unreliable so
    was left with little option. The now-Truespeed FTTP has been flawless, and thus far I've managed to avoid talking to them)

    https://www.startpage.com/do/dsearch?q=Heights+Telecom+HT-6766BE&cat=web&language=english
    somewhere in the list could be something useful. If not, at least
    you'll have something to read for a while.

    I have a Heights HT-360AXI-V2. The main issue I had was getting into it initially - I don't remember exactly but I think I was using the wrong IP. Mine is set up for the router admin interface on 192.168.0.1 which wasn't
    what the instructions said. The admin and wifi passwords printed on the
    label were correct.

    I don't use the wifi so I had turned it off, but I just turned it back on
    and connected to it using the password printed on the label. That worked
    fine. I'm only getting about 3Mbps using it, because the router is in an awkward location. So nothing wrong that I could see (from Ubuntu 26.04).

    Not sure what else to suggest, but you could open Terminal while the wifi is connected. Can you try the following and post the results (use Ctrl-C to
    stop the pings):

    ping 192.168.1.1 # or whatever the router's IP is

    ping 8.8.8.8 # a Google server on the internet

    host www.example.com

    sudo wdutil info # asks for your account password


    Theo
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From David Brooks@boaterdave@hotmail.co.uk to uk.comp.sys.mac on Tue Nov 3 17:36:14 2026
    From Newsgroup: uk.comp.sys.mac

    On 03/11/2026 16:25, David Sankey wrote:
    On 03/11/2026 09:43, David Brooks wrote:
    On 03/11/2026 09:04, Liz Tuddenham wrote:
    [...]

    Followup:-a I've just tried changing the password to nonsense again and
    this time it failed to connect, so that was a red herring.-a The router
    still won't connect to the Internet by Wi-Fi.

    Classic Usenet diagnostic puzzle from Liz. Putting the pieces
    together, a few distinct technical factors explain what's happening on
    uk.comp.sys.mac:1. The Hardware & Software MismatchThe Router: The
    Heights Telecom HT-6766BE is a modern Wi-Fi 7 (BE6500) gateway
    (commonly deployed by UK fibre altnets like Zzoomm) running OpenSync/
    Plume containerized firmware. Out of the box, these routers default to
    strict WPA3 or modern WPA3/WPA2 mixed mode encryption with Protected
    Management Frames (PMF) enabled.-a-a The Client: A Mac Mini running
    macOS 10.15.7 (Catalina). Released back in late 2020, CatalinarCOs Wi-Fi
    supplicant has notoriously flaky or incomplete support for modern WPA3
    SAE (Simultaneous Authentication of Equals) handshakes and Wi-Fi 7
    beacon parameters.2. The False-Positive "Connected" StateLiz notes
    that even after breaking the password or changing it to nonsense, the
    Network pane stubbornly claims Wi-Fi is connected.Layer 2 vs. Layer 3/
    Handshake: macOS Catalina caches SSID profiles aggressively. When the
    Mac sees the broadcast SSID match a saved profile, the menu bar often
    registers a Layer 2 association or reads from cached state.The
    Handshake Failure: Even though the Mac associates with the radio
    broadcast, the actual 4- way WPA authentication key exchange fails
    because Catalina cannot properly negotiate the modern encryption
    cipher requested by the HT-6766BE. Hence, no DHCP lease is pulled,
    traffic doesn't flow, and dropping the Ethernet cable leaves her
    stranded without an IP route. (Her mention of 192.169.1.105 is likely
    a minor transposition for 192.168. or a self-assigned link-local
    artifact from a stalled DHCP negotiation).The Remedy for LizTo get the
    Catalina Mac Mini talking to the new fibre router over wireless, she
    needs to log into the HT-6766BE admin panel via Ethernet and drop the
    wireless security setting from its default WPA3/mixed mode down to
    standard WPA2-PSK (AES). Once legacy- compatible WPA2 encryption is
    enforced on the router's 2.4GHz/5GHz bands, the older Mac's supplicant
    will successfully complete the handshake.

    =

    That was the answer from Gemini.

    I hope it helps.

    That's not actually crazy!
    If we are talking macOS 10.15.7 then enabling obsolete encryption is probably necessary, the WiFi itself should automatically fall back to something compatible.

    192.169.x.x is hopefully just a typo, should be 192.168.x.x.

    I suspect that the OP didn't read my answer.

    Thank YOU for so doing. EfOe
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From nospam@nospam@de-ster.demon.nl (J. J. Lodder) to uk.comp.sys.mac on Tue Nov 3 21:16:13 2026
    From Newsgroup: uk.comp.sys.mac

    Liz Tuddenham <liz@poppyrecords.invalid.invalid> wrote:

    Chris <ithinkiam@gmail.com> wrote:

    Liz Tuddenham <liz@poppyrecords.invalid.invalid> wrote:
    [...]

    Followup: I've just tried changing the password to nonsense again and this time it failed to connect, so that was a red herring. The router still won't connect to the Internet by Wi-Fi.

    Does it connect to the router? i.e. can you get into the router's admin interface when only connected by wifi?

    If you can, which sounds like the case, this is a router issue and your ISP should be able to help.

    I don't think it would allow admin access by Wi_fi , the previous one
    didn't.

    Strange. My Fritz! boxes never had such a problem,

    Jan
    (never logged in on it hard-wired)
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris@ithinkiam@gmail.com to uk.comp.sys.mac on Tue Nov 3 23:32:21 2026
    From Newsgroup: uk.comp.sys.mac

    Liz Tuddenham <liz@poppyrecords.invalid.invalid> wrote:
    Chris <ithinkiam@gmail.com> wrote:

    Liz Tuddenham <liz@poppyrecords.invalid.invalid> wrote:
    [...]

    Followup: I've just tried changing the password to nonsense again and
    this time it failed to connect, so that was a red herring. The router
    still won't connect to the Internet by Wi-Fi.

    Does it connect to the router? i.e. can you get into the router's admin
    interface when only connected by wifi?

    If you can, which sounds like the case, this is a router issue and your ISP >> should be able to help.

    I don't think it would allow admin access by Wi_fi , the previous one
    didn't.

    Have you tried? Works fine for a couple of TP-Link routers I have.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From liz@liz@poppyrecords.invalid.invalid (Liz Tuddenham) to uk.comp.sys.mac on Wed Nov 4 09:23:32 2026
    From Newsgroup: uk.comp.sys.mac

    Chris <ithinkiam@gmail.com> wrote:

    Liz Tuddenham <liz@poppyrecords.invalid.invalid> wrote:
    Chris <ithinkiam@gmail.com> wrote:

    Liz Tuddenham <liz@poppyrecords.invalid.invalid> wrote:
    [...]

    Followup: I've just tried changing the password to nonsense again and >>> this time it failed to connect, so that was a red herring. The router >>> still won't connect to the Internet by Wi-Fi.

    Does it connect to the router? i.e. can you get into the router's admin
    interface when only connected by wifi?

    If you can, which sounds like the case, this is a router issue and your ISP
    should be able to help.

    I don't think it would allow admin access by Wi_fi , the previous one didn't.

    Have you tried? Works fine for a couple of TP-Link routers I have.

    It doesn't connect - but neither does anything else connect by Wi-Fi.
    --
    ~ Liz Tuddenham ~
    (Remove the ".invalid"s and add ".co.uk" to reply)
    www.poppyrecords.co.uk
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From liz@liz@poppyrecords.invalid.invalid (Liz Tuddenham) to uk.comp.sys.mac on Wed Nov 4 10:13:41 2026
    From Newsgroup: uk.comp.sys.mac

    John <Man@the.keyboard> wrote:

    [...]
    You *might* find support online for your router at these search page results:


    https://www.startpage.com/do/dsearch?q=Heights+Telecom+HT-6766BE&cat=web&l anguage=english somewhere in the list could be something useful. If not,
    at least you'll have something to read for a while.

    Sadly the 'manuals' I have found so far are either advertising flyers or
    user guides that just state the obvious. Meanwhile I have tried
    downgrading the security to WPA2 (which matches the security of the Mac
    Mini) and 'Open" - but it doesn't work with either of those.
    --
    ~ Liz Tuddenham ~
    (Remove the ".invalid"s and add ".co.uk" to reply)
    www.poppyrecords.co.uk
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From jbrennand@brennand@ntlworld.com to uk.comp.sys.mac on Wed Nov 4 15:33:49 2026
    From Newsgroup: uk.comp.sys.mac

    On 03/11/2026 08:48, Liz Tuddenham wrote:
    (Mac Mini OS 10.15.7)

    I've just had a wireless router fitted as part of the change to fibre,
    it identifies itself as a "Heights Telecom HT-6766BE". I can log into
    it by Ethernet but do not seem to be able to contact it by wireless.

    I thought it was connecting by Wireless when I first tried it using the default settings but I now realise the Ethernet was also connected and
    that might have misled me. When I changed the SSID and password, then
    tested by removing the Ethernet plug, I found I had no connection.

    I have checked that the passwords in the router and Keychain are
    identical. The Network>Wi-Fi panel shows "Wi-Fi is connected and has
    the IP address 192.169.1.105". If I change the router password to
    nonsense, switch off the Wi-Fi and switch it back on again, the
    Network>Wi-Fi panel again shows it is connected when it obviously can't
    be.

    What is going on?.

    You haven't said (I think)who your BB supplier is - I think... BeFibre
    and Zzoomm use that router?

    I believe it is a WiFi-7 one... so was wondering if that is where the underlying issue is - e.g. if your equipment is only WiFi 5/6? But I
    dont know if that matters?

    Also I have never ever used the wifi from any router my BB business
    supplies (currently VM)- they go straight into modem mode and I use my
    own wifi equipment - Apple Airports and TP-Link's. Have you tried that
    - perhaps with an old or borrowed router - just as a test?

    Apologies if none of this is relevant.

    JohnB

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From liz@liz@poppyrecords.invalid.invalid (Liz Tuddenham) to uk.comp.sys.mac on Wed Nov 4 16:15:34 2026
    From Newsgroup: uk.comp.sys.mac

    jbrennand <brennand@ntlworld.com> wrote:

    On 03/11/2026 08:48, Liz Tuddenham wrote:
    (Mac Mini OS 10.15.7)

    I've just had a wireless router fitted as part of the change to fibre,
    it identifies itself as a "Heights Telecom HT-6766BE". I can log into
    it by Ethernet but do not seem to be able to contact it by wireless.

    I thought it was connecting by Wireless when I first tried it using the default settings but I now realise the Ethernet was also connected and
    that might have misled me. When I changed the SSID and password, then tested by removing the Ethernet plug, I found I had no connection.

    I have checked that the passwords in the router and Keychain are identical. The Network>Wi-Fi panel shows "Wi-Fi is connected and has
    the IP address 192.169.1.105". If I change the router password to nonsense, switch off the Wi-Fi and switch it back on again, the Network>Wi-Fi panel again shows it is connected when it obviously can't
    be.

    What is going on?.

    You haven't said (I think)who your BB supplier is

    It is Truespeed.


    I believe it is a WiFi-7 one... so was wondering if that is where the underlying issue is - e.g. if your equipment is only WiFi 5/6? But I
    dont know if that matters?

    It appears to connect to the router but won't connect to the internet.


    Also I have never ever used the wifi from any router my BB business
    supplies (currently VM)- they go straight into modem mode and I use my
    own wifi equipment - Apple Airports and TP-Link's. Have you tried that
    - perhaps with an old or borrowed router - just as a test?

    I haven't yet tried it, I have a TP-Link router that was used on the
    landline but I don't suppose it will connect to the fibre interface.
    --
    ~ Liz Tuddenham ~
    (Remove the ".invalid"s and add ".co.uk" to reply)
    www.poppyrecords.co.uk
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Graham J@nobody@nowhere.co.uk to uk.comp.sys.mac on Wed Nov 4 16:38:02 2026
    From Newsgroup: uk.comp.sys.mac

    Liz Tuddenham wrote:

    [snip]

    It appears to connect to the router but won't connect to the internet.

    Using the computer connected by wifi can you:

    - ping the router by IP address?

    - ping any other computer connected to the LAN by Ethernet?

    - open the router's management page using a browser? Does this page
    show that your device is connected by wifi?

    - does the router have a firewall which controls whether the WiFi port
    can have internet access?

    Using a computer connecting to the router via an Ethernet cable, can you:

    - ping the router by IP address?

    - open the router's management page using a browser?

    - connect to the internet?

    Also I have never ever used the wifi from any router my BB business
    supplies (currently VM)- they go straight into modem mode and I use my
    own wifi equipment - Apple Airports and TP-Link's. Have you tried that
    - perhaps with an old or borrowed router - just as a test?

    I haven't yet tried it, I have a TP-Link router that was used on the
    landline but I don't suppose it will connect to the fibre interface.

    Did Truespeed provide you with an Optical Network Termination (ONT) or equivalent, which accepts the fibre cable and has a single Ethernet
    socket for connection to the router? Alternatively does it combine the function of ONT and router in one box?

    If you have an ONT then any Ethernet router can be used instead of the HT-6766BE.
    --
    Graham J
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From David Sankey@davidsankey9@icloud.com to uk.comp.sys.mac on Wed Nov 4 16:41:36 2026
    From Newsgroup: uk.comp.sys.mac

    On 04/11/2026 16:15, Liz Tuddenham wrote:
    jbrennand <brennand@ntlworld.com> wrote:

    On 03/11/2026 08:48, Liz Tuddenham wrote:
    (Mac Mini OS 10.15.7)

    I've just had a wireless router fitted as part of the change to fibre,
    it identifies itself as a "Heights Telecom HT-6766BE". I can log into
    it by Ethernet but do not seem to be able to contact it by wireless.

    I thought it was connecting by Wireless when I first tried it using the
    default settings but I now realise the Ethernet was also connected and
    that might have misled me. When I changed the SSID and password, then
    tested by removing the Ethernet plug, I found I had no connection.

    I have checked that the passwords in the router and Keychain are
    identical. The Network>Wi-Fi panel shows "Wi-Fi is connected and has
    the IP address 192.169.1.105". If I change the router password to
    nonsense, switch off the Wi-Fi and switch it back on again, the
    Network>Wi-Fi panel again shows it is connected when it obviously can't
    be.

    What is going on?.

    You haven't said (I think)who your BB supplier is

    It is Truespeed.


    I believe it is a WiFi-7 one... so was wondering if that is where the
    underlying issue is - e.g. if your equipment is only WiFi 5/6? But I
    dont know if that matters?

    It appears to connect to the router but won't connect to the internet.

    If you can access the router over WiFi but not the outside world then
    this is your routing tables.

    Assuming that 192.169.1.105 above is a typo (should be 192.168.x.x) then
    look in your network settings for the WiFi in System Settings for the
    Router address (or more accurately the default route), which should be
    the IP address of your router.

    This should be being assigned by DHCP - if you've got an explicit entry
    there remove it.

    Also I have never ever used the wifi from any router my BB business
    supplies (currently VM)- they go straight into modem mode and I use my
    own wifi equipment - Apple Airports and TP-Link's. Have you tried that
    - perhaps with an old or borrowed router - just as a test?

    I haven't yet tried it, I have a TP-Link router that was used on the
    landline but I don't suppose it will connect to the fibre interface.


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Theo@theom+news@chiark.greenend.org.uk to uk.comp.sys.mac on Wed Nov 4 17:22:01 2026
    From Newsgroup: uk.comp.sys.mac

    Graham J <nobody@nowhere.co.uk> wrote:
    Did Truespeed provide you with an Optical Network Termination (ONT) or equivalent, which accepts the fibre cable and has a single Ethernet
    socket for connection to the router? Alternatively does it combine the function of ONT and router in one box?

    My Truespeed Heights Telecom HT-360AXI box contains a GPON transceiver, with the fibre going into a green LC connector behind a little hatch, so there's
    no separate ONT. But there's also a version the HT-360AXE that doesn't have GPON and it's easy to get them confused.

    It appears the HT-6766BE doesn't have GPON so there should be a separate
    ONT box. Which surprises me as County Broadband have traditionally fitted all-in-one boxes. Perhaps after the takeover they went with Truespeed's alternative two-box approach?

    If you have an ONT then any Ethernet router can be used instead of the HT-6766BE.

    But if you are taking telephone from Truespeed you will need to use their router.

    It's actually a quite capable router with a lot of configurability so I wouldn't be in a hurry to replace it.

    On the WPA2/WPA3 question, my HT-360AXI offers:

    Open
    WPA-PSK
    WPA2-PSK
    WPA3-SAE
    Mixed WPA2/WPA-PSK
    Mixed WPA3/WPA2-PSK

    so it could be worth dropping down to say WPA2-PSK and see if that changes things. Mine has WPA2-PSK as the default.

    Theo
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris@ithinkiam@gmail.com to uk.comp.sys.mac on Wed Nov 4 19:37:45 2026
    From Newsgroup: uk.comp.sys.mac

    Liz Tuddenham <liz@poppyrecords.invalid.invalid> wrote:
    jbrennand <brennand@ntlworld.com> wrote:

    On 03/11/2026 08:48, Liz Tuddenham wrote:
    (Mac Mini OS 10.15.7)

    I've just had a wireless router fitted as part of the change to fibre,
    it identifies itself as a "Heights Telecom HT-6766BE". I can log into
    it by Ethernet but do not seem to be able to contact it by wireless.

    I thought it was connecting by Wireless when I first tried it using the
    default settings but I now realise the Ethernet was also connected and
    that might have misled me. When I changed the SSID and password, then
    tested by removing the Ethernet plug, I found I had no connection.

    I have checked that the passwords in the router and Keychain are
    identical. The Network>Wi-Fi panel shows "Wi-Fi is connected and has
    the IP address 192.169.1.105". If I change the router password to
    nonsense, switch off the Wi-Fi and switch it back on again, the
    Network>Wi-Fi panel again shows it is connected when it obviously can't
    be.

    What is going on?.

    You haven't said (I think)who your BB supplier is

    It is Truespeed.


    I believe it is a WiFi-7 one... so was wondering if that is where the
    underlying issue is - e.g. if your equipment is only WiFi 5/6? But I
    dont know if that matters?

    It appears to connect to the router but won't connect to the internet.

    That contradicts what you said previously. You said nothing connects via
    wifi and you can't access to the admin interface.

    What makes you say now that it connects to the router? If true then you
    will be able to access the admin interface of the router.


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From liz@liz@poppyrecords.invalid.invalid (Liz Tuddenham) to uk.comp.sys.mac on Wed Nov 4 21:29:55 2026
    From Newsgroup: uk.comp.sys.mac

    Theo <theom+news@chiark.greenend.org.uk> wrote:

    Graham J <nobody@nowhere.co.uk> wrote:
    Did Truespeed provide you with an Optical Network Termination (ONT) or equivalent, which accepts the fibre cable and has a single Ethernet
    socket for connection to the router? Alternatively does it combine the function of ONT and router in one box?

    My Truespeed Heights Telecom HT-360AXI box contains a GPON transceiver, with the fibre going into a green LC connector behind a little hatch, so there's no separate ONT. But there's also a version the HT-360AXE that doesn't have GPON and it's easy to get them confused.

    It appears the HT-6766BE doesn't have GPON so there should be a separate
    ONT box. Which surprises me as County Broadband have traditionally fitted all-in-one boxes. Perhaps after the takeover they went with Truespeed's alternative two-box approach?

    There are two boxes on the wall, a small one with the optical joint and
    the spare fibre coiled up inside it and a slightly larger one with power
    and the fibre going in and a wire coming out to a socket on the the
    router marked "2G-WAN".


    If you have an ONT then any Ethernet router can be used instead of the HT-6766BE.

    But if you are taking telephone from Truespeed you will need to use their router.

    I shall be taking telephone from them as soon as they notify me of the changeover.

    It's actually a quite capable router with a lot of configurability so I wouldn't be in a hurry to replace it.

    On the WPA2/WPA3 question, my HT-360AXI offers:

    Open
    WPA-PSK
    WPA2-PSK
    WPA3-SAE
    Mixed WPA2/WPA-PSK
    Mixed WPA3/WPA2-PSK

    so it could be worth dropping down to say WPA2-PSK and see if that changes things. Mine has WPA2-PSK as the default.

    I've done that and it makes no differenc - neither does dropping it to
    "Open".
    --
    ~ Liz Tuddenham ~
    (Remove the ".invalid"s and add ".co.uk" to reply)
    www.poppyrecords.co.uk
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From liz@liz@poppyrecords.invalid.invalid (Liz Tuddenham) to uk.comp.sys.mac on Wed Nov 4 21:29:55 2026
    From Newsgroup: uk.comp.sys.mac

    Chris <ithinkiam@gmail.com> wrote:

    Liz Tuddenham <liz@poppyrecords.invalid.invalid> wrote:
    jbrennand <brennand@ntlworld.com> wrote:

    On 03/11/2026 08:48, Liz Tuddenham wrote:
    (Mac Mini OS 10.15.7)

    I've just had a wireless router fitted as part of the change to fibre, >>> it identifies itself as a "Heights Telecom HT-6766BE". I can log into >>> it by Ethernet but do not seem to be able to contact it by wireless.

    I thought it was connecting by Wireless when I first tried it using the >>> default settings but I now realise the Ethernet was also connected and >>> that might have misled me. When I changed the SSID and password, then >>> tested by removing the Ethernet plug, I found I had no connection.

    I have checked that the passwords in the router and Keychain are
    identical. The Network>Wi-Fi panel shows "Wi-Fi is connected and has
    the IP address 192.169.1.105". If I change the router password to
    nonsense, switch off the Wi-Fi and switch it back on again, the
    Network>Wi-Fi panel again shows it is connected when it obviously can't >>> be.

    What is going on?.

    You haven't said (I think)who your BB supplier is

    It is Truespeed.


    I believe it is a WiFi-7 one... so was wondering if that is where the
    underlying issue is - e.g. if your equipment is only WiFi 5/6? But I
    dont know if that matters?

    It appears to connect to the router but won't connect to the internet.

    That contradicts what you said previously. You said nothing connects via
    wifi and you can't access to the admin interface.

    What makes you say now that it connects to the router? If true then you
    will be able to access the admin interface of the router.

    The Network>Wi-Fi panel shows "Wi-Fi is connected to [SSID] and has the
    IP address 192.169.1.105" (That is not a misprint, it really is
    192.169.1.105). If I ping that IP, it responds but if I ping 8.8.8.8 it times-out. If I direct Firefox to 192.168.0.1 (the router's webpage) it doesn't respomd on Wi-Fi but it does respond by Ethernet.
    --
    ~ Liz Tuddenham ~
    (Remove the ".invalid"s and add ".co.uk" to reply)
    www.poppyrecords.co.uk
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From liz@liz@poppyrecords.invalid.invalid (Liz Tuddenham) to uk.comp.sys.mac on Wed Nov 4 21:29:56 2026
    From Newsgroup: uk.comp.sys.mac

    David Sankey <davidsankey9@icloud.com> wrote:

    On 04/11/2026 16:15, Liz Tuddenham wrote:
    jbrennand <brennand@ntlworld.com> wrote:

    On 03/11/2026 08:48, Liz Tuddenham wrote:
    (Mac Mini OS 10.15.7)

    I've just had a wireless router fitted as part of the change to fibre, >>> it identifies itself as a "Heights Telecom HT-6766BE". I can log into >>> it by Ethernet but do not seem to be able to contact it by wireless.

    I thought it was connecting by Wireless when I first tried it using the >>> default settings but I now realise the Ethernet was also connected and >>> that might have misled me. When I changed the SSID and password, then >>> tested by removing the Ethernet plug, I found I had no connection.

    I have checked that the passwords in the router and Keychain are
    identical. The Network>Wi-Fi panel shows "Wi-Fi is connected and has
    the IP address 192.169.1.105". If I change the router password to
    nonsense, switch off the Wi-Fi and switch it back on again, the
    Network>Wi-Fi panel again shows it is connected when it obviously can't >>> be.

    What is going on?.

    You haven't said (I think)who your BB supplier is

    It is Truespeed.


    I believe it is a WiFi-7 one... so was wondering if that is where the
    underlying issue is - e.g. if your equipment is only WiFi 5/6? But I
    dont know if that matters?

    It appears to connect to the router but won't connect to the internet.

    If you can access the router over WiFi but not the outside world then
    this is your routing tables.

    Assuming that 192.169.1.105 above is a typo ...

    No, that really is the IP address that the Mac Mini says it is connected
    to.
    --
    ~ Liz Tuddenham ~
    (Remove the ".invalid"s and add ".co.uk" to reply)
    www.poppyrecords.co.uk
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From nospam@nospam@de-ster.demon.nl (J. J. Lodder) to uk.comp.sys.mac on Wed Nov 4 23:38:56 2026
    From Newsgroup: uk.comp.sys.mac

    Liz Tuddenham <liz@poppyrecords.invalid.invalid> wrote:

    Chris <ithinkiam@gmail.com> wrote:

    Liz Tuddenham <liz@poppyrecords.invalid.invalid> wrote:
    jbrennand <brennand@ntlworld.com> wrote:

    On 03/11/2026 08:48, Liz Tuddenham wrote:
    (Mac Mini OS 10.15.7)

    I've just had a wireless router fitted as part of the change to fibre, >>> it identifies itself as a "Heights Telecom HT-6766BE". I can log into >>> it by Ethernet but do not seem to be able to contact it by wireless. >>>
    I thought it was connecting by Wireless when I first tried it using the >>> default settings but I now realise the Ethernet was also connected and >>> that might have misled me. When I changed the SSID and password, then >>> tested by removing the Ethernet plug, I found I had no connection.

    I have checked that the passwords in the router and Keychain are
    identical. The Network>Wi-Fi panel shows "Wi-Fi is connected and has >>> the IP address 192.169.1.105". If I change the router password to
    nonsense, switch off the Wi-Fi and switch it back on again, the
    Network>Wi-Fi panel again shows it is connected when it obviously can't >>> be.

    What is going on?.

    You haven't said (I think)who your BB supplier is

    It is Truespeed.


    I believe it is a WiFi-7 one... so was wondering if that is where the
    underlying issue is - e.g. if your equipment is only WiFi 5/6? But I
    dont know if that matters?

    It appears to connect to the router but won't connect to the internet.

    That contradicts what you said previously. You said nothing connects via wifi and you can't access to the admin interface.

    What makes you say now that it connects to the router? If true then you will be able to access the admin interface of the router.

    The Network>Wi-Fi panel shows "Wi-Fi is connected to [SSID] and has the
    IP address 192.169.1.105" (That is not a misprint, it really is 192.169.1.105). If I ping that IP, it responds but if I ping 8.8.8.8 it times-out. If I direct Firefox to 192.168.0.1 (the router's webpage) it doesn't respomd on Wi-Fi but it does respond by Ethernet.

    192.169.x.x is a range of internal IP adresses,
    so 192.169.1.105 is the local IP assigned to your machine
    by the router,

    Jan


    Jan
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Theo@theom+news@chiark.greenend.org.uk to uk.comp.sys.mac on Wed Nov 4 22:46:22 2026
    From Newsgroup: uk.comp.sys.mac

    Liz Tuddenham <liz@poppyrecords.invalid.invalid> wrote:

    The Network>Wi-Fi panel shows "Wi-Fi is connected to [SSID] and has the
    IP address 192.169.1.105" (That is not a misprint, it really is 192.169.1.105). If I ping that IP, it responds but if I ping 8.8.8.8 it times-out. If I direct Firefox to 192.168.0.1 (the router's webpage) it doesn't respomd on Wi-Fi but it does respond by Ethernet.

    That .169 is a problem - that's a public IP belonging to RGnet of Crystal Spring, Washington. It should be nowhere on your LAN.

    My guess is that you have the wifi network on your Mac configured for static IP, not Automatic (DHCP), with that erroneous IP. It's your WLAN IP so you
    can ping it, but it's detached from the reality of your network so it's not
    a sensible local IP and packets from the router won't reach it. Perhaps it
    was set during a previous session of trying things with the wifi and was forgotten?

    I suggest deleting the saved wifi networks. Go to System Preferences -> Network, click on the Wi-Fi adapter, click Advanced... then in the Wi-Fi
    tab select each network and click the minus button:

    https://superuser.com/questions/1322025/macos-remove-remembered-wifi-network-connections

    Once that's blank, start by connecting to the Truespeed wifi network afresh. That should be default make an Automatic (DHCP) connection which asks the router for the IP address.

    If you are still having problems after that, it's possible the DHCP settings
    on the router are strange. It's worth checking them in the web interface -
    on my HT-360AXI it's Advanced Setup -> LAN -> IPv4 Autoconfig

    My router has (all the factory defaults):

    'IP address' is '192.168.0.1'
    'Subnet mask' is 255.255.255.0
    'Enable IGMP Snooping' is ticked
    'Standard mode' is unselected / 'Blocking mode' is selected
    'Enable LAN side firewall' is unticked
    'Enable DHCP server' is selected
    'Start IP address' is 192.168.0.2
    'End IP address' is 192.168.0.254
    'Primary DNS server' is 192.168.0.1
    'Secondary DNS server' is 0.0.0.0
    'Leased Time (hour)' is 24
    'Reserved addresses' is empty

    I don't have any 'DHCP advanced settings' and the 'Static Lease List' is
    empty.

    Don't change the IP address as you could find you can't login to the router
    any more. But the above settings should be similar to what you have.

    However my money is on there being a bad setting at the Mac end, since the
    DHCP server is also used for the ethernet connection and that seems to work.

    Theo
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Theo@theom+news@chiark.greenend.org.uk to uk.comp.sys.mac on Wed Nov 4 22:51:43 2026
    From Newsgroup: uk.comp.sys.mac

    J. J. Lodder <nospam@de-ster.demon.nl> wrote:

    192.169.x.x is a range of internal IP adresses,
    so 192.169.1.105 is the local IP assigned to your machine
    by the router,

    It's not, 192.169.x.x is a range of public IPs:

    $ whois 192.169.1.105
    NetRange: 192.169.0.0 - 192.169.1.255
    CIDR: 192.169.0.0/23
    NetName: PSG169
    NetHandle: NET-192-169-0-0-1
    Parent: NET192 (NET-192-0-0-0-0)
    NetType: Direct Allocation
    OriginAS:
    Organization: RGnet, LLC (RGNETI-1)
    RegDate: 2005-04-12
    Updated: 2021-12-14
    Comment: Geofeed https://rg.net/geofeed
    Ref: https://rdap.arin.net/registry/ip/192.169.0.0


    OrgName: RGnet, LLC
    OrgId: RGNETI-1
    Address: 5147 Crystal Spring
    City: Bainbridge Island
    StateProv: WA
    PostalCode: 98110
    Country: US
    RegDate: 1990-10-01
    Updated: 2021-10-06
    Ref: https://rdap.arin.net/registry/entity/RGNETI-1


    192.168.x.x is a range reserved for private use:

    $ whois 192.168.1.105
    NetRange: 192.168.0.0 - 192.168.255.255
    CIDR: 192.168.0.0/16
    NetName: PRIVATE-ADDRESS-CBLK-RFC1918-IANA-RESERVED
    NetHandle: NET-192-168-0-0-1
    Parent: NET192 (NET-192-0-0-0-0)
    NetType: IANA Special Use
    OriginAS:
    Organization: Internet Assigned Numbers Authority (IANA)
    RegDate: 1994-03-15
    Updated: 2024-05-24
    Comment: These addresses are in use by many millions of independently operated networks, which might be as small as a single computer connected to a home gateway, and are automatically configured in hundreds of millions of devices. They are only intended for use within a private context and traffic that needs to cross the Internet will need to use a different, unique address.
    Comment:
    Comment: These addresses can be used by anyone without any need to coordinate with IANA or an Internet registry. The traffic from these addresses does not come from ICANN or IANA. We are not the source of activity you may see on logs or in e-mail records. Please refer to http://www.iana.org/abuse/answers
    Comment:
    Comment: These addresses were assigned by the IETF, the organization that develops Internet protocols, in the Best Current Practice document, RFC 1918 which can be found at:
    Comment: http://datatracker.ietf.org/doc/rfc1918
    Ref: https://rdap.arin.net/registry/ip/192.168.0.0


    Even if you decide to number your LAN using 192.169.x.x anyway, things are likely to not work properly.

    Theo
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Graham J@nobody@nowhere.co.uk to uk.comp.sys.mac on Thu Nov 5 08:20:13 2026
    From Newsgroup: uk.comp.sys.mac

    Theo wrote:
    Liz Tuddenham <liz@poppyrecords.invalid.invalid> wrote:

    The Network>Wi-Fi panel shows "Wi-Fi is connected to [SSID] and has the
    IP address 192.169.1.105" (That is not a misprint, it really is
    192.169.1.105). If I ping that IP, it responds but if I ping 8.8.8.8 it
    times-out. If I direct Firefox to 192.168.0.1 (the router's webpage) it
    doesn't respomd on Wi-Fi but it does respond by Ethernet.

    That .169 is a problem - that's a public IP belonging to RGnet of Crystal Spring, Washington. It should be nowhere on your LAN.

    My guess is that you have the wifi network on your Mac configured for static IP, not Automatic (DHCP), with that erroneous IP. It's your WLAN IP so you can ping it, but it's detached from the reality of your network so it's not
    a sensible local IP and packets from the router won't reach it. Perhaps it was set during a previous session of trying things with the wifi and was forgotten?

    [snip]

    Theo is almost certainly correct.

    Can you connect to this router using any other wifi device? A phone,
    another computer?
    --
    Graham J
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From liz@liz@poppyrecords.invalid.invalid (Liz Tuddenham) to uk.comp.sys.mac on Thu Nov 5 08:47:44 2026
    From Newsgroup: uk.comp.sys.mac

    Theo <theom+news@chiark.greenend.org.uk> wrote:

    Liz Tuddenham <liz@poppyrecords.invalid.invalid> wrote:

    The Network>Wi-Fi panel shows "Wi-Fi is connected to [SSID] and has the
    IP address 192.169.1.105" (That is not a misprint, it really is 192.169.1.105). If I ping that IP, it responds but if I ping 8.8.8.8 it times-out. If I direct Firefox to 192.168.0.1 (the router's webpage) it doesn't respomd on Wi-Fi but it does respond by Ethernet.

    That .169 is a problem - that's a public IP belonging to RGnet of Crystal Spring, Washington. It should be nowhere on your LAN.

    My guess is that you have the wifi network on your Mac configured for static IP, not Automatic (DHCP), with that erroneous IP. It's your WLAN IP so you can ping it, but it's detached from the reality of your network so it's not
    a sensible local IP and packets from the router won't reach it. Perhaps it was set during a previous session of trying things with the wifi and was forgotten?

    I suggest deleting the saved wifi networks. Go to System Preferences -> Network, click on the Wi-Fi adapter, click Advanced... then in the Wi-Fi
    tab select each network and click the minus button:

    https://superuser.com/questions/1322025/macos-remove-remembered-wifi-netwo rk-connections

    Once that's blank, start by connecting to the Truespeed wifi network afresh. That should be default make an Automatic (DHCP) connection which asks the router for the IP address.

    If you are still having problems after that, it's possible the DHCP settings on the router are strange. It's worth checking them in the web interface - on my HT-360AXI it's Advanced Setup -> LAN -> IPv4 Autoconfig

    My router has (all the factory defaults):

    'IP address' is '192.168.0.1'
    'Subnet mask' is 255.255.255.0
    'Enable IGMP Snooping' is ticked
    'Standard mode' is unselected / 'Blocking mode' is selected
    'Enable LAN side firewall' is unticked
    'Enable DHCP server' is selected
    'Start IP address' is 192.168.0.2
    'End IP address' is 192.168.0.254
    'Primary DNS server' is 192.168.0.1
    'Secondary DNS server' is 0.0.0.0
    'Leased Time (hour)' is 24
    'Reserved addresses' is empty

    I don't have any 'DHCP advanced settings' and the 'Static Lease List' is empty.

    Don't change the IP address as you could find you can't login to the router any more. But the above settings should be similar to what you have.

    However my money is on there being a bad setting at the Mac end, since the DHCP server is also used for the ethernet connection and that seems to work.

    I've re-set the Mac to:

    IP 192.168.1.50
    Subnet mask 255.255.255.0
    Router 192.168.0.1
    DNS 9.9.9.9

    ...No improvement.
    --
    ~ Liz Tuddenham ~
    (Remove the ".invalid"s and add ".co.uk" to reply)
    www.poppyrecords.co.uk
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From liz@liz@poppyrecords.invalid.invalid (Liz Tuddenham) to uk.comp.sys.mac on Thu Nov 5 08:47:45 2026
    From Newsgroup: uk.comp.sys.mac

    Graham J <nobody@nowhere.co.uk> wrote:

    Theo wrote:
    Liz Tuddenham <liz@poppyrecords.invalid.invalid> wrote:

    The Network>Wi-Fi panel shows "Wi-Fi is connected to [SSID] and has the
    IP address 192.169.1.105" (That is not a misprint, it really is
    192.169.1.105). If I ping that IP, it responds but if I ping 8.8.8.8 it >> times-out. If I direct Firefox to 192.168.0.1 (the router's webpage) it >> doesn't respomd on Wi-Fi but it does respond by Ethernet.

    That .169 is a problem - that's a public IP belonging to RGnet of Crystal Spring, Washington. It should be nowhere on your LAN.

    My guess is that you have the wifi network on your Mac configured for static
    IP, not Automatic (DHCP), with that erroneous IP. It's your WLAN IP so you can ping it, but it's detached from the reality of your network so it's not a sensible local IP and packets from the router won't reach it. Perhaps it was set during a previous session of trying things with the wifi and was forgotten?

    [snip]

    Theo is almost certainly correct.

    Can you connect to this router using any other wifi device? A phone,
    another computer?

    No, the Mac Mini is the only one in the house with (potentially) working
    Wi-Fi.
    --
    ~ Liz Tuddenham ~
    (Remove the ".invalid"s and add ".co.uk" to reply)
    www.poppyrecords.co.uk
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Graham J@nobody@nowhere.co.uk to uk.comp.sys.mac on Thu Nov 5 08:55:49 2026
    From Newsgroup: uk.comp.sys.mac

    Liz Tuddenham wrote:

    [snip]


    However my money is on there being a bad setting at the Mac end, since the >> DHCP server is also used for the ethernet connection and that seems to work.

    I've re-set the Mac to:

    IP 192.168.1.50
    Subnet mask 255.255.255.0
    Router 192.168.0.1
    DNS 9.9.9.9


    Pleas PLEASE P L E A S E do not manually set these network parameters.
    Tell the Mac to use DHCP. Apple may call it something uninformative
    like "automatic configuration". Having changed the setting to use DHCP
    reboot the Mac before testing.

    If you really must have a known static IP address for the Mac it is
    sometimes possible to achieve this by "binding" in the router. But get
    the wifi connection working first!
    --
    Graham J
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Graham J@nobody@nowhere.co.uk to uk.comp.sys.mac on Thu Nov 5 08:58:48 2026
    From Newsgroup: uk.comp.sys.mac

    Liz Tuddenham wrote:

    [snip]


    No, the Mac Mini is the only one in the house with (potentially) working Wi-Fi.

    Does the mac Mini connect to wifi when you take it to a friends house?
    Clearly you need to have it configured to use DHCP as per my previous
    post, but this test would establish whether the wifi hardware is working properly.
    --
    Graham J
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From liz@liz@poppyrecords.invalid.invalid (Liz Tuddenham) to uk.comp.sys.mac on Thu Nov 5 09:19:19 2026
    From Newsgroup: uk.comp.sys.mac

    Graham J <nobody@nowhere.co.uk> wrote:

    Liz Tuddenham wrote:

    [snip]


    However my money is on there being a bad setting at the Mac end, since
    the DHCP server is also used for the ethernet connection and that seems
    to work.

    I've re-set the Mac to:

    IP 192.168.1.50
    Subnet mask 255.255.255.0
    Router 192.168.0.1
    DNS 9.9.9.9


    Pleas PLEASE P L E A S E do not manually set these network parameters.
    Tell the Mac to use DHCP. Apple may call it something uninformative
    like "automatic configuration". Having changed the setting to use DHCP reboot the Mac before testing.

    If you really must have a known static IP address for the Mac it is sometimes possible to achieve this by "binding" in the router. But get
    the wifi connection working first!

    I've re-set it to DHCP and, after deleting and re-instating the
    connection and re-booting the Mac, it is now showing IP 192.168.0.85

    Wi-Fi still isn't connecting to the internet.
    --
    ~ Liz Tuddenham ~
    (Remove the ".invalid"s and add ".co.uk" to reply)
    www.poppyrecords.co.uk
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From liz@liz@poppyrecords.invalid.invalid (Liz Tuddenham) to uk.comp.sys.mac on Thu Nov 5 09:19:18 2026
    From Newsgroup: uk.comp.sys.mac

    Graham J <nobody@nowhere.co.uk> wrote:

    Liz Tuddenham wrote:

    [snip]


    No, the Mac Mini is the only one in the house with (potentially) working Wi-Fi.

    Does the mac Mini connect to wifi when you take it to a friends house? Clearly you need to have it configured to use DHCP as per my previous
    post, but this test would establish whether the wifi hardware is working properly.

    When Plusnet pulled the plug on my broadband, I tried to connect through
    a neighbour's Wireless router (with his permission) but assumed the
    reason I couldn't get through to the internet was because Plusnet had disconnected the service at their end.

    Previous to that, about 3 weeks ago, I was able to use Wi-Fi with the
    TP-Link wired (landline) router.
    --
    ~ Liz Tuddenham ~
    (Remove the ".invalid"s and add ".co.uk" to reply)
    www.poppyrecords.co.uk
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Graham J@nobody@nowhere.co.uk to uk.comp.sys.mac on Thu Nov 5 09:34:29 2026
    From Newsgroup: uk.comp.sys.mac

    Liz Tuddenham wrote:

    [snip]

    I've re-set it to DHCP and, after deleting and re-instating the
    connection and re-booting the Mac, it is now showing IP 192.168.0.85

    Wi-Fi still isn't connecting to the internet.

    So, now we can do some baby diagnostic steps.

    First, did you make any changes to the factory default settings in the
    router? If so, please explain what and why.

    Please show the subnet mask, default gateway (i.e. router address) and
    DNS setting(s) reported for the wifi connection.

    Can the Mac Mini ping itself? We expect this to work, since it has done
    so before.

    Can the Mac Mini ping the router, at the default gateway address shown
    for the wifi connection? Does this IP address match the documentation
    for the router?

    Can the Mac Mini ping another computer (or other networked device) which
    is connected by Ethernet to the router?

    Can the Mac Mini open the router's management web page?

    I will be out for a few hours but others will follow this up, I'm sure.
    --
    Graham J
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From liz@liz@poppyrecords.invalid.invalid (Liz Tuddenham) to uk.comp.sys.mac on Thu Nov 5 10:15:30 2026
    From Newsgroup: uk.comp.sys.mac

    Graham J <nobody@nowhere.co.uk> wrote:

    Liz Tuddenham wrote:

    [snip]

    I've re-set it to DHCP and, after deleting and re-instating the
    connection and re-booting the Mac, it is now showing IP 192.168.0.85

    Wi-Fi still isn't connecting to the internet.

    So, now we can do some baby diagnostic steps.

    First, did you make any changes to the factory default settings in the router? If so, please explain what and why.

    I changed the SSID and password. I have checked that they are identical
    (Copy & Paste) in the Keychain and in the router settings.

    Other settings may have been changed remotely when my friend set up the
    e-mail server attached to the router, as I gave him remote access.


    Please show the subnet mask, default gateway (i.e. router address) and
    DNS setting(s) reported for the wifi connection.

    IPv4 Address: 192.186.1.50
    Subnet Mask: 255.255.255.0
    Router: 192.168.0.1

    DNS: 9.9.9.9


    Can the Mac Mini ping itself? We expect this to work, since it has done
    so before.

    IP 192.168.0.85 - Yes.


    Can the Mac Mini ping the router, at the default gateway address shown
    for the wifi connection? Does this IP address match the documentation
    for the router?

    IP 192.168.0.1 - Yes


    Can the Mac Mini ping another computer (or other networked device) which
    is connected by Ethernet to the router?

    IP 192.168.0.86 (A Mac G3 ) - Yes


    Can the Mac Mini open the router's management web page?

    Yes


    I will be out for a few hours but others will follow this up, I'm sure.

    The router's management system shows the Mini is only connected by
    Ethernet but the Mini Network Preferences shows it is connected by both Ethernet and Wi-Fi ... and the Wi-Fi connection has the IP address: 192.168.1.50
    --
    ~ Liz Tuddenham ~
    (Remove the ".invalid"s and add ".co.uk" to reply)
    www.poppyrecords.co.uk
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From liz@liz@poppyrecords.invalid.invalid (Liz Tuddenham) to uk.comp.sys.mac on Thu Nov 5 10:47:17 2026
    From Newsgroup: uk.comp.sys.mac

    Graham J <nobody@nowhere.co.uk> wrote:

    [...]
    Can the Mac Mini ping the router, at the default gateway address shown
    for the wifi connection? Does this IP address match the documentation
    for the router?

    UPDATE

    IP 192.168.1.50 - Yes. That address is not shown in the documentation
    that came with the router, it is shown in the Network Preferences panel
    for Wi-Fi.
    --
    ~ Liz Tuddenham ~
    (Remove the ".invalid"s and add ".co.uk" to reply)
    www.poppyrecords.co.uk
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From liz@liz@poppyrecords.invalid.invalid (Liz Tuddenham) to uk.comp.sys.mac on Thu Nov 5 11:04:50 2026
    From Newsgroup: uk.comp.sys.mac

    Graham J <nobody@nowhere.co.uk> wrote:

    [...]

    I've just spotted a tiny square button on the router marked "WIFI".
    Pressing it or holding it down for a few seconds doesn't seem to make
    any difference and there is no indicator associated with it.

    There is another button next to it, marked "WPS"; holding that dowm
    makes the green LED on the Ethernet port flash occasionally.
    --
    ~ Liz Tuddenham ~
    (Remove the ".invalid"s and add ".co.uk" to reply)
    www.poppyrecords.co.uk
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Graham J@nobody@nowhere.co.uk to uk.comp.sys.mac on Thu Nov 5 11:07:35 2026
    From Newsgroup: uk.comp.sys.mac

    Liz Tuddenham wrote:

    [snip]

    First, did you make any changes to the factory default settings in the
    router? If so, please explain what and why.

    I changed the SSID and password. I have checked that they are identical (Copy & Paste) in the Keychain and in the router settings.

    Other settings may have been changed remotely when my friend set up the e-mail server attached to the router, as I gave him remote access.

    I think you should ask your friend for assistance, given that he may
    have done things that he has not documented for you. As a minimum, you
    should understand what settings he has changed and why.
    Please show the subnet mask, default gateway (i.e. router address) and
    DNS setting(s) reported for the wifi connection.

    IPv4 Address: 192.186.1.50

    That is inconsistent with your previous post! Which showed 192.168.0.85
    - so are you sure you are looking at the wifi interface on the Mac Mini.

    Subnet Mask: 255.255.255.0
    Router: 192.168.0.1
    DNS: 9.9.9.9

    That is unexpected. I would expect the Mac Mini to show the DNS
    provided by the router, which in turn might come from the ISP. Have you
    paid the ISP for the Quad9 DNS service?

    Can the Mac Mini ping itself? We expect this to work, since it has done
    so before.

    IP 192.168.0.85 - Yes.

    But as I state above this is inconsistent! You must resolve this before
    any other tests will make sense.

    Can the Mac Mini ping the router, at the default gateway address shown
    for the wifi connection? Does this IP address match the documentation
    for the router?

    IP 192.168.0.1 - Yes

    Can the Mac Mini ping another computer (or other networked device) which
    is connected by Ethernet to the router?

    IP 192.168.0.86 (A Mac G3 ) - Yes

    Can the Mac Mini open the router's management web page?

    Yes

    I will be out for a few hours but others will follow this up, I'm sure.

    The router's management system shows the Mini is only connected by
    Ethernet but the Mini Network Preferences shows it is connected by both Ethernet and Wi-Fi ... and the Wi-Fi connection has the IP address: 192.168.1.50

    That is clearly wrong. Does the router continue to show this confusing information even after it has been rebooted?

    Are you ABSOLUTELY SURE that you have disconnected the Ethernet cable
    between the router and the Mac Mini.

    Please use the browser on the Mac G3 connected by Ethernet cable to
    monitor the router's management system while you are testing the wifi connection to the Mac Mini.
    --
    Graham J
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Theo@theom+news@chiark.greenend.org.uk to uk.comp.sys.mac on Thu Nov 5 11:10:59 2026
    From Newsgroup: uk.comp.sys.mac

    Liz Tuddenham <liz@poppyrecords.invalid.invalid> wrote:
    Graham J <nobody@nowhere.co.uk> wrote:

    Please show the subnet mask, default gateway (i.e. router address) and
    DNS setting(s) reported for the wifi connection.

    IPv4 Address: 192.186.1.50
    Subnet Mask: 255.255.255.0
    Router: 192.168.0.1

    DNS: 9.9.9.9

    That's wrong. If the router is at 192.168.0.1 and the subnet mask is 255.255.255.0 then the Mini's IPv4 address should be between 192.168.0.2 and 192.168.0.254.

    Are you really sure it's .186. and not .168.? .186. is another public IP range.

    Can the Mac Mini ping itself? We expect this to work, since it has done
    so before.

    IP 192.168.0.85 - Yes.

    Where are you getting this address from, since it's reporting .1.50 above?


    Can the Mac Mini ping the router, at the default gateway address shown
    for the wifi connection? Does this IP address match the documentation
    for the router?

    IP 192.168.0.1 - Yes


    Can the Mac Mini ping another computer (or other networked device) which
    is connected by Ethernet to the router?

    IP 192.168.0.86 (A Mac G3 ) - Yes


    Can the Mac Mini open the router's management web page?

    Yes

    So the above seems to be ok, ie the Mini can ping the router. But if you
    have given it an address outside the 192.168.0.x subnet then the router
    can't route packets from the internet to it.

    I will be out for a few hours but others will follow this up, I'm sure.

    The router's management system shows the Mini is only connected by
    Ethernet but the Mini Network Preferences shows it is connected by both Ethernet and Wi-Fi ... and the Wi-Fi connection has the IP address: 192.168.1.50

    That seems like a hangover from the previous setup. Are you sure you deleted all the wifi networks as per the instructions in my previous post? And are only using 'Automatic (DHCP)' not entering addresses manually?

    Theo
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Graham J@nobody@nowhere.co.uk to uk.comp.sys.mac on Thu Nov 5 11:27:15 2026
    From Newsgroup: uk.comp.sys.mac

    Liz Tuddenham wrote:
    Graham J <nobody@nowhere.co.uk> wrote:

    [...]
    Can the Mac Mini ping the router, at the default gateway address shown
    for the wifi connection? Does this IP address match the documentation
    for the router?

    UPDATE

    IP 192.168.1.50 - Yes. That address is not shown in the documentation
    that came with the router, it is shown in the Network Preferences panel
    for Wi-Fi.

    Sorry, I did not express my question properly. The address for the
    default gateway (= router) which should appear in the display of the Mac Mini's wifi connection I expect to be 192.168.0.1. It is this address
    which should be shown in the router's documentation.

    It cannot possibly be 192.168.1.50 since you have told us that is the
    address allocated (at some point in the past) to the wifi connection of
    the Mac Mini.

    In summary, the Mac Mini should show:

    IP address 192.168.0.??? is the address of the Mac Mini. It is issued
    by the DHCP service in the router and should match the value shown in
    the router for the Mac Mini. If you see something different then there
    is some very strange problem. Reboot both the router and the Mac Mini
    and see it the same conflict appears

    Subnet mask 255.255.255.0 is the mask for the LAN, and it is issued by
    the DHCP service in the router.

    Router or Default Gateway 192.168.0.1 is the address of the router. It
    is fixed in the router and issued to the Mac Mini by the DHCP service in
    the router.

    DNS 9.9.9.9 . Don't know where this comes from. Ordinarily the DNS is
    issued to the Mac Mini by the DHCP service in the router. It might be
    the address of the router itself or the DNS provided by Truespeed (which
    I can't find on the internet, so maybe they don't have one?). Some
    routers will allow you to specify it so that it is issued to all their
    DHCP supplicants, but if that was so you (or your friend who set up the
    mail server) would have to have done it.

    Hope this helps.
    --
    Graham J
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Graham J@nobody@nowhere.co.uk to uk.comp.sys.mac on Thu Nov 5 11:34:21 2026
    From Newsgroup: uk.comp.sys.mac

    Liz Tuddenham wrote:
    Graham J <nobody@nowhere.co.uk> wrote:

    [...]

    I've just spotted a tiny square button on the router marked "WIFI".
    Pressing it or holding it down for a few seconds doesn't seem to make
    any difference and there is no indicator associated with it.

    There is another button next to it, marked "WPS"; holding that down
    makes the green LED on the Ethernet port flash occasionally.

    These should be explained in the router's documentation. It is likely
    that they work with devices that auto-configure their wifi settings -
    things like wifi extenders built into mauls power sockets. Google WPS
    for more info.
    --
    Graham J
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From liz@liz@poppyrecords.invalid.invalid (Liz Tuddenham) to uk.comp.sys.mac on Thu Nov 5 11:47:01 2026
    From Newsgroup: uk.comp.sys.mac

    Graham J <nobody@nowhere.co.uk> wrote:

    Liz Tuddenham wrote:

    [snip]

    First, did you make any changes to the factory default settings in the
    router? If so, please explain what and why.

    I changed the SSID and password. I have checked that they are identical (Copy & Paste) in the Keychain and in the router settings.

    Other settings may have been changed remotely when my friend set up the e-mail server attached to the router, as I gave him remote access.

    I think you should ask your friend for assistance, given that he may
    have done things that he has not documented for you. As a minimum, you should understand what settings he has changed and why.

    I have asked him and he is making attempts to identify the problem but
    he hasn't suggested that he has made any alterations that might have
    caused it.

    Please show the subnet mask, default gateway (i.e. router address) and
    DNS setting(s) reported for the wifi connection.

    IPv4 Address: 192.186.1.50

    That is inconsistent with your previous post! Which showed 192.168.0.85
    - so are you sure you are looking at the wifi interface on the Mac Mini.

    I re-checked with the Ethernet plug removed and it was 192.168.0.85,
    after a re-boot it now reads 192.168.1.50



    Subnet Mask: 255.255.255.0
    Router: 192.168.0.1
    DNS: 9.9.9.9

    That is unexpected. I would expect the Mac Mini to show the DNS
    provided by the router, which in turn might come from the ISP. Have you
    paid the ISP for the Quad9 DNS service?

    I put that in at the suggestion of my friend, I have now removed it and
    the panel is showing 192.168.0.1 greyed-out.


    Can the Mac Mini ping itself? We expect this to work, since it has done >> so before.

    IP 192.168.0.85 - Yes.

    But as I state above this is inconsistent! You must resolve this before
    any other tests will make sense.

    Can the Mac Mini ping the router, at the default gateway address shown
    for the wifi connection? Does this IP address match the documentation
    for the router?

    IP 192.168.0.1 - Yes

    Can the Mac Mini ping another computer (or other networked device) which >> is connected by Ethernet to the router?

    IP 192.168.0.86 (A Mac G3 ) - Yes

    Can the Mac Mini open the router's management web page?

    Yes

    I will be out for a few hours but others will follow this up, I'm sure.

    The router's management system shows the Mini is only connected by
    Ethernet but the Mini Network Preferences shows it is connected by both Ethernet and Wi-Fi ... and the Wi-Fi connection has the IP address: 192.168.1.50

    That is clearly wrong. Does the router continue to show this confusing information even after it has been rebooted?

    Are you ABSOLUTELY SURE that you have disconnected the Ethernet cable
    between the router and the Mac Mini.

    After a re-boot with the Ethernet plug removed, the message is:

    "Wi-Fi is connected to [router wireless SSID] and has the IP address 192.168.1.50"


    Please use the browser on the Mac G3 connected by Ethernet cable to
    monitor the router's management system while you are testing the wifi connection to the Mac Mini.

    I have tried two browsers on the G3 and they both deliver a blank page.
    The source code was:
    ~~~~~~~~~
    <html><head><script language='javascript'> parent.location='http://192.168.0.1:80/login.html' </script></head><body></body></html>
    ~~~~~~~~~
    I went to 'http://192.168.0.1:80/login.html' and it gave me a login box
    - I put in the router's password and pressed Enter - but after that I
    just got "403 forbidden".
    --
    ~ Liz Tuddenham ~
    (Remove the ".invalid"s and add ".co.uk" to reply)
    www.poppyrecords.co.uk
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From nospam@nospam@de-ster.demon.nl (J. J. Lodder) to uk.comp.sys.mac on Thu Nov 5 12:48:36 2026
    From Newsgroup: uk.comp.sys.mac

    Liz Tuddenham <liz@poppyrecords.invalid.invalid> wrote:

    Graham J <nobody@nowhere.co.uk> wrote:

    Liz Tuddenham wrote:

    [snip]


    However my money is on there being a bad setting at the Mac end, since >> the DHCP server is also used for the ethernet connection and that seems >> to work.

    I've re-set the Mac to:

    IP 192.168.1.50
    Subnet mask 255.255.255.0
    Router 192.168.0.1
    DNS 9.9.9.9


    Pleas PLEASE P L E A S E do not manually set these network parameters.
    Tell the Mac to use DHCP. Apple may call it something uninformative
    like "automatic configuration". Having changed the setting to use DHCP reboot the Mac before testing.

    If you really must have a known static IP address for the Mac it is sometimes possible to achieve this by "binding" in the router. But get
    the wifi connection working first!

    I've re-set it to DHCP and, after deleting and re-instating the
    connection and re-booting the Mac, it is now showing IP 192.168.0.85

    Wi-Fi still isn't connecting to the internet.

    Good, so you now have a connection to your router.
    The router itself (the admin interface) will probably be reachable
    at 192.168.0.1 in your web browser.
    You will need to set an admin password,
    or find the default one printed on the back, or in the manual,

    Jan

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From nospam@nospam@de-ster.demon.nl (J. J. Lodder) to uk.comp.sys.mac on Thu Nov 5 13:01:17 2026
    From Newsgroup: uk.comp.sys.mac

    Liz Tuddenham <liz@poppyrecords.invalid.invalid> wrote:

    Graham J <nobody@nowhere.co.uk> wrote:

    [...]
    Can the Mac Mini ping the router, at the default gateway address shown
    for the wifi connection? Does this IP address match the documentation
    for the router?

    UPDATE

    IP 192.168.1.50 - Yes. That address is not shown in the documentation
    that came with the router, it is shown in the Network Preferences panel
    for Wi-Fi.

    It is necessary and unavoidable that the ethernet and Wifi interfaces of
    your Mini have different interal IP adresses.

    Jan
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From liz@liz@poppyrecords.invalid.invalid (Liz Tuddenham) to uk.comp.sys.mac on Thu Nov 5 12:28:54 2026
    From Newsgroup: uk.comp.sys.mac

    Theo <theom+news@chiark.greenend.org.uk> wrote:

    Liz Tuddenham <liz@poppyrecords.invalid.invalid> wrote:
    Graham J <nobody@nowhere.co.uk> wrote:

    Please show the subnet mask, default gateway (i.e. router address) and DNS setting(s) reported for the wifi connection.

    IPv4 Address: 192.186.1.50
    Subnet Mask: 255.255.255.0
    Router: 192.168.0.1

    DNS: 9.9.9.9

    That's wrong. If the router is at 192.168.0.1 and the subnet mask is 255.255.255.0 then the Mini's IPv4 address should be between 192.168.0.2 and 192.168.0.254.

    Are you really sure it's .186. and not .168.? .

    A misprint, I'm afraid - it was 168
    --
    ~ Liz Tuddenham ~
    (Remove the ".invalid"s and add ".co.uk" to reply)
    www.poppyrecords.co.uk
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From liz@liz@poppyrecords.invalid.invalid (Liz Tuddenham) to uk.comp.sys.mac on Thu Nov 5 12:28:54 2026
    From Newsgroup: uk.comp.sys.mac

    Graham J <nobody@nowhere.co.uk> wrote:

    Liz Tuddenham wrote:
    Graham J <nobody@nowhere.co.uk> wrote:

    [...]

    I've just spotted a tiny square button on the router marked "WIFI". Pressing it or holding it down for a few seconds doesn't seem to make
    any difference and there is no indicator associated with it.

    There is another button next to it, marked "WPS"; holding that down
    makes the green LED on the Ethernet port flash occasionally.

    These should be explained in the router's documentation.

    The 'documentation' consisted of a label stuck on the packaging - there
    was nothing else. I have looked online but haven't found a proper
    detailed guide.

    I finally switched everything off, all the computers and the router,
    then I switched on the router and allowed it several minutes to sort
    itself out, then switched everything else back on. Now Wi-Fi works
    (with the Ethernet plug lying on the table top alongside the Mini).

    The Wi-Fi connection now shows up in the Network Preferences
    as:192.168.0.88

    Many thanks to everyone who went to so much trouble to help me
    --
    ~ Liz Tuddenham ~
    (Remove the ".invalid"s and add ".co.uk" to reply)
    www.poppyrecords.co.uk
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From liz@liz@poppyrecords.invalid.invalid (Liz Tuddenham) to uk.comp.sys.mac on Thu Nov 5 12:28:54 2026
    From Newsgroup: uk.comp.sys.mac

    Theo <theom+news@chiark.greenend.org.uk> wrote:

    [...]
    Are you sure you deleted
    all the wifi networks as per the instructions in my previous post? And are only using 'Automatic (DHCP)' not entering addresses manually?

    I finally switched everything off, all the computers and the router,
    then I switched on the router and allowed it several minutes to sort
    itself out, then switched everything else back on. Now Wi-Fi works
    (with the Ethernet plug lying on the table top alongside the Mini).

    The Wi-Fi connection now shows up in the Network Preferences
    as:192.168.0.88

    Many thanks to everyone who went to so much trouble to help me.
    --
    ~ Liz Tuddenham ~
    (Remove the ".invalid"s and add ".co.uk" to reply)
    www.poppyrecords.co.uk
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Graham J@nobody@nowhere.co.uk to uk.comp.sys.mac on Thu Nov 5 12:39:34 2026
    From Newsgroup: uk.comp.sys.mac

    Liz Tuddenham wrote:

    [snip]

    I think you should ask your friend for assistance, given that he may
    have done things that he has not documented for you. As a minimum, you
    should understand what settings he has changed and why.

    I have asked him and he is making attempts to identify the problem but
    he hasn't suggested that he has made any alterations that might have
    caused it.

    Ordinarily I would expect that to be true. But if he documents what he
    has done and why you can at least check ...

    [snip]

    I re-checked with the Ethernet plug removed and it was 192.168.0.85,
    after a re-boot it now reads 192.168.1.50

    That's encouraging ...

    Subnet Mask: 255.255.255.0
    Router: 192.168.0.1
    DNS: 9.9.9.9

    That is unexpected. I would expect the Mac Mini to show the DNS
    provided by the router, which in turn might come from the ISP. Have you
    paid the ISP for the Quad9 DNS service?

    I put that in at the suggestion of my friend, I have now removed it and
    the panel is showing 192.168.0.1 greyed-out.

    So you're still not doing what I asked, which is to let DHCP configure
    the wifi interface!

    After a re-boot with the Ethernet plug removed, the message is:

    "Wi-Fi is connected to [router wireless SSID] and has the IP address 192.168.1.50"

    So that is consistent.

    Please use the browser on the Mac G3 connected by Ethernet cable to
    monitor the router's management system while you are testing the wifi
    connection to the Mac Mini.

    I have tried two browsers on the G3 and they both deliver a blank page.

    Not surprising. The Mac G3 is so old that it's browser won't work with
    a modern router, or indeed most websites on the internet.

    This gives you a real problem in diagnosing things, because I suspect
    you are swapping the Mac Mini from Ethernet to wifi and back. DON'T DO
    THIS!

    Leave the Mac Mini using wifi only and get your friend to view the
    router's management page remotely and report what he sees.

    Alternatively, give up on wifi and use Ethernet exclusively. This will
    be much more reliable.
    --
    Graham J
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Graham J@nobody@nowhere.co.uk to uk.comp.sys.mac on Thu Nov 5 12:45:49 2026
    From Newsgroup: uk.comp.sys.mac

    Liz Tuddenham wrote:

    [snip]

    I finally switched everything off, all the computers and the router,

    This is probably the best diagnostic step you ever took!

    then I switched on the router and allowed it several minutes to sort
    itself out, then switched everything else back on. Now Wi-Fi works
    (with the Ethernet plug lying on the table top alongside the Mini).

    If you want the Mac Mini to have a consistent IP address please explain
    why. It might be possible to achieve this with the correct
    configuration in the router. Even then you can't normally make it the
    same for both wifi and Ethernet.
    --
    Graham J
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From liz@liz@poppyrecords.invalid.invalid (Liz Tuddenham) to uk.comp.sys.mac on Thu Nov 5 12:51:40 2026
    From Newsgroup: uk.comp.sys.mac

    Graham J <nobody@nowhere.co.uk> wrote:

    [...]
    Alternatively, give up on wifi and use Ethernet exclusively. This will
    be much more reliable.

    I normally only use Ethernet but like to keep the Wi-Fi as a backup in
    case of a problem.

    This all started when I thought I would check to see how fast my new 'Ultrafast" fibre connection really was and found it was often slower
    than the previous wired connection, with long pauses. A direct Ethernet connection from the Mini to the router, bypassing the switch, was
    stupendously fast, so I concluded that the new system was being
    throttled by the switch.

    Just as a quick check, I decided to see how fast it was with Wi-Fi
    ...and that was when the troubles began.

    P.S. I have a new switch on order - I hope it will still interface with
    the G3.
    --
    ~ Liz Tuddenham ~
    (Remove the ".invalid"s and add ".co.uk" to reply)
    www.poppyrecords.co.uk
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From liz@liz@poppyrecords.invalid.invalid (Liz Tuddenham) to uk.comp.sys.mac on Thu Nov 5 13:01:01 2026
    From Newsgroup: uk.comp.sys.mac

    Graham J <nobody@nowhere.co.uk> wrote:

    Liz Tuddenham wrote:

    [snip]

    I finally switched everything off, all the computers and the router,

    This is probably the best diagnostic step you ever took!

    then I switched on the router and allowed it several minutes to sort
    itself out, then switched everything else back on. Now Wi-Fi works
    (with the Ethernet plug lying on the table top alongside the Mini).

    If you want the Mac Mini to have a consistent IP address please explain
    why. It might be possible to achieve this with the correct
    configuration in the router. Even then you can't normally make it the
    same for both wifi and Ethernet.

    I might have to configure the LAN manually in order to include two
    printers, a Canon CLBP 460 and a Laserjet 6MP, which don't seem to obey
    the usual rules. Neither of them can be accessed from the Mini, the
    Canon shows up on the G3 but the Laserjet has to have its 'Asante'
    interface (Mac bus to Ethernet) re-booted each time it is selected.

    With manual Ethernet configuration this might be sorted out but I shall
    not be doing it unaided. The Wi-Fi shouldn't need any further attention
    as long as I keep clear of its IP.
    --
    ~ Liz Tuddenham ~
    (Remove the ".invalid"s and add ".co.uk" to reply)
    www.poppyrecords.co.uk
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Graham J@nobody@nowhere.co.uk to uk.comp.sys.mac on Thu Nov 5 16:22:30 2026
    From Newsgroup: uk.comp.sys.mac

    Liz Tuddenham wrote:

    [snip]

    I might have to configure the LAN manually in order to include two
    printers, a Canon CLBP 460 and a Laserjet 6MP, which don't seem to obey
    the usual rules. Neither of them can be accessed from the Mini, the
    Canon shows up on the G3 but the Laserjet has to have its 'Asante'
    interface (Mac bus to Ethernet) re-booted each time it is selected.

    With manual Ethernet configuration this might be sorted out but I shall
    not be doing it unaided. The Wi-Fi shouldn't need any further attention
    as long as I keep clear of its IP.

    I remember that you talked about these printers before.

    A good thing to remember is that almost everything on the LAN might
    cache some parameters for an unknown length of time; which can cause no
    end of confusion. So if you make a change, a reboot of everything
    relevant might be a good idea. In time I guess you will learn when
    things seem to behave inconsistently.
    --
    Graham J
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Graham J@nobody@nowhere.co.uk to uk.comp.sys.mac on Thu Nov 5 16:36:09 2026
    From Newsgroup: uk.comp.sys.mac

    Liz Tuddenham wrote:
    Graham J <nobody@nowhere.co.uk> wrote:

    [...]
    Alternatively, give up on wifi and use Ethernet exclusively. This will
    be much more reliable.

    I normally only use Ethernet but like to keep the Wi-Fi as a backup in
    case of a problem.

    This all started when I thought I would check to see how fast my new 'Ultrafast" fibre connection really was and found it was often slower
    than the previous wired connection, with long pauses. A direct Ethernet connection from the Mini to the router, bypassing the switch, was stupendously fast, so I concluded that the new system was being
    throttled by the switch.

    Just as a quick check, I decided to see how fast it was with Wi-Fi
    ...and that was when the troubles began.

    P.S. I have a new switch on order - I hope it will still interface with
    the G3.

    That's a very strange fault and would suggest a hardware failure or
    serious cross-talk within an Ethernet cable. Apple used to provide
    Ethernet cables with only 2 pairs - which should work up to 100
    Mbits/sec - but if a 2-pair segment is connected to a 4-pair segment two
    of the pairs in the 4-pair segment are not terminated at one end, and
    can pick up damaging interference. The long pauses suggest the
    possibility that the network speed is being re-negotiated - something
    that normally happens just once as the cable is plugged in. Or that the
    RJ45 connector is making intermittent contact - do they all have their retaining barbs in place and functional?

    So if you see the same problem with the new switch then look for such
    cables.

    Ethernet hardware is generally regarded as industrial strength so is
    pretty well specified and debugged. I've only once seen a cheap Windows laptop that failed to connect via a switch but worked OK when connected directly to the router, and that was resolved by updating the NIC driver.
    --
    Graham J
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From David Brooks@boaterdave@hotmail.co.uk to uk.comp.sys.mac on Thu Nov 5 16:54:13 2026
    From Newsgroup: uk.comp.sys.mac

    On 05/11/2026 16:36, Graham J wrote:
    [....]

    That's a very strange fault and would suggest a hardware failure or
    serious cross-talk within an Ethernet cable.-a Apple used to provide Ethernet cables with only 2 pairs - which should work up to 100 Mbits/
    sec - but if a 2-pair segment is connected to a 4-pair segment two of
    the pairs in the 4-pair segment are not terminated at one end, and can
    pick up damaging interference.-a The long pauses suggest the possibility that the network speed is being re-negotiated - something that normally happens just once as the cable is plugged in.-a Or that the RJ45
    connector is making intermittent contact - do they all have their
    retaining barbs in place and functional?

    So if you see the same problem with the new switch then look for such cables.

    Ethernet hardware is generally regarded as industrial strength so is
    pretty well specified and debugged.-a I've only once seen a cheap Windows laptop that failed to connect via a switch but worked OK when connected directly to the router, and that was resolved by updating the NIC driver.


    I wonder if you'd like to comment on THIS item?

    https://www.youtube.com/watch?v=Y2PIEpTzybk
    --
    David

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From nospam@nospam@de-ster.demon.nl (J. J. Lodder) to uk.comp.sys.mac on Thu Nov 5 20:10:42 2026
    From Newsgroup: uk.comp.sys.mac

    Liz Tuddenham <liz@poppyrecords.invalid.invalid> wrote:

    Theo <theom+news@chiark.greenend.org.uk> wrote:

    [...]
    Are you sure you deleted
    all the wifi networks as per the instructions in my previous post? And are only using 'Automatic (DHCP)' not entering addresses manually?

    I finally switched everything off, all the computers and the router,
    then I switched on the router and allowed it several minutes to sort
    itself out, then switched everything else back on. Now Wi-Fi works
    (with the Ethernet plug lying on the table top alongside the Mini).

    The Wi-Fi connection now shows up in the Network Preferences
    as:192.168.0.88

    There should be no problem with having both ethernet and WiFi connected.
    It may be marginally faster,

    Jan



    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From nospam@nospam@de-ster.demon.nl (J. J. Lodder) to uk.comp.sys.mac on Thu Nov 5 20:10:43 2026
    From Newsgroup: uk.comp.sys.mac

    Graham J <nobody@nowhere.co.uk> wrote:

    Liz Tuddenham wrote:

    [snip]

    I finally switched everything off, all the computers and the router,

    This is probably the best diagnostic step you ever took!

    then I switched on the router and allowed it several minutes to sort
    itself out, then switched everything else back on. Now Wi-Fi works
    (with the Ethernet plug lying on the table top alongside the Mini).

    If you want the Mac Mini to have a consistent IP address please explain
    why. It might be possible to achieve this with the correct
    configuration in the router. Even then you can't normally make it the
    same for both wifi and Ethernet.

    It may be convenient for screen sharing, for example.
    The interfaces on the Mini are characterised by their unique MAC Adress
    On all routers I have ever seen it is possible to connect those,
    so to tell the router's DHCP server
    to always assign the same internal IP adress
    to a given MAC Adress.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From liz@liz@poppyrecords.invalid.invalid (Liz Tuddenham) to uk.comp.sys.mac on Thu Nov 5 20:56:40 2026
    From Newsgroup: uk.comp.sys.mac

    Graham J <nobody@nowhere.co.uk> wrote:

    Liz Tuddenham wrote:

    [snip]

    I might have to configure the LAN manually in order to include two printers, a Canon CLBP 460 and a Laserjet 6MP, which don't seem to obey
    the usual rules. Neither of them can be accessed from the Mini, the
    Canon shows up on the G3 but the Laserjet has to have its 'Asante' interface (Mac bus to Ethernet) re-booted each time it is selected.

    With manual Ethernet configuration this might be sorted out but I shall
    not be doing it unaided. The Wi-Fi shouldn't need any further attention
    as long as I keep clear of its IP.

    I remember that you talked about these printers before.

    A good thing to remember is that almost everything on the LAN might
    cache some parameters for an unknown length of time; which can cause no
    end of confusion. So if you make a change, a reboot of everything
    relevant might be a good idea. In time I guess you will learn when
    things seem to behave inconsistently.

    I am still on the vertical part of the learning curve.
    --
    ~ Liz Tuddenham ~
    (Remove the ".invalid"s and add ".co.uk" to reply)
    www.poppyrecords.co.uk
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From liz@liz@poppyrecords.invalid.invalid (Liz Tuddenham) to uk.comp.sys.mac on Thu Nov 5 20:56:40 2026
    From Newsgroup: uk.comp.sys.mac

    Graham J <nobody@nowhere.co.uk> wrote:

    Liz Tuddenham wrote:
    Graham J <nobody@nowhere.co.uk> wrote:

    [...]
    Alternatively, give up on wifi and use Ethernet exclusively. This will
    be much more reliable.

    I normally only use Ethernet but like to keep the Wi-Fi as a backup in
    case of a problem.

    This all started when I thought I would check to see how fast my new 'Ultrafast" fibre connection really was and found it was often slower
    than the previous wired connection, with long pauses. A direct Ethernet connection from the Mini to the router, bypassing the switch, was stupendously fast, so I concluded that the new system was being
    throttled by the switch.

    Just as a quick check, I decided to see how fast it was with Wi-Fi
    ...and that was when the troubles began.

    P.S. I have a new switch on order - I hope it will still interface with
    the G3.

    That's a very strange fault and would suggest a hardware failure or
    serious cross-talk within an Ethernet cable. Apple used to provide
    Ethernet cables with only 2 pairs - which should work up to 100
    Mbits/sec - but if a 2-pair segment is connected to a 4-pair segment two
    of the pairs in the 4-pair segment are not terminated at one end, and
    can pick up damaging interference. The long pauses suggest the
    possibility that the network speed is being re-negotiated - something
    that normally happens just once as the cable is plugged in. Or that the
    RJ45 connector is making intermittent contact - do they all have their retaining barbs in place and functional?

    They are all in good condition and have been wokdkng flawlessly for over
    a decade. If the Mini is plugged directly into the socket on the wall
    of the back room, everything works at 60Mbs but with just the switch and
    one short cable extra, it is down to 1 Mbps. (The back room socket by
    the switch is cabled to another socket on the wall of the front room,
    near where the router is located, then a short cable connects that
    socket to the router.

    The switch is rated at 10 Mbs maximum, it connects the router to the
    Mini, the G3, two printers and a cable to another switch downstairs
    which conects to two more G3s and an iMac. The downstairs switch is
    left running but the computers on it are switched off until needed.

    The pauses only seem to happen when connecting to websites from the Mini
    (they didn't happen when it was on ADSL) - Usenet on the G3 is
    instantaneous
    --
    ~ Liz Tuddenham ~
    (Remove the ".invalid"s and add ".co.uk" to reply)
    www.poppyrecords.co.uk
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Graham J@nobody@nowhere.co.uk to uk.comp.sys.mac on Thu Nov 5 21:50:25 2026
    From Newsgroup: uk.comp.sys.mac

    Liz Tuddenham wrote:

    [snip]

    They are all in good condition and have been wokdkng flawlessly for over
    a decade. If the Mini is plugged directly into the socket on the wall
    of the back room, everything works at 60Mbs but with just the switch and
    one short cable extra, it is down to 1 Mbps. (The back room socket by
    the switch is cabled to another socket on the wall of the front room,
    near where the router is located, then a short cable connects that
    socket to the router.

    So the path from the Mac Mini to the wall, then to the4 front room, then
    to the router probably all uses 4 pair cable operating at 100 Mbits/sec.

    When the switch is connected, where physically is it? If the "one short
    cable extra" has only 2 pairs that could very likely cause a problem, especially because ..

    The switch is rated at 10 Mbs maximum,

    So everything going through it will only operate at 10 Mbits/sec - significantly slower than your fibre internet connection. Its not
    surprising that there are gaps in communication.

    I hope the new switch you've ordered is at least 100 Mbits/sec or
    ideally 1000 Mbits/sec.
    --
    Graham J
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From David Brooks@boaterdave@hotmail.co.uk to uk.comp.sys.mac on Thu Nov 5 22:50:57 2026
    From Newsgroup: uk.comp.sys.mac

    On 05/11/2026 21:50, Graham J wrote:
    Liz Tuddenham wrote:

    [snip]

    They are all in good condition and have been wokdkng flawlessly for over
    a decade.-a If the Mini is plugged-a directly into the socket on the wall
    of the back room, everything works at 60Mbs but with just the switch and
    one short cable extra, it is down-a to 1 Mbps.-a (The back room socket by
    the switch is cabled to another socket on the wall of the front room,
    near where the router is located, then a short cable connects that
    socket to the router.

    So the path from the Mac Mini to the wall, then to the4 front room, then
    to the router probably all uses 4 pair cable operating at 100 Mbits/sec.

    When the switch is connected, where physically is it?-a If the "one short cable extra" has only 2 pairs that could very likely cause a problem, especially because ..

    The switch is rated at 10 Mbs maximum,

    So everything going through it will only operate at 10 Mbits/sec - significantly slower than your fibre internet connection.-a Its not surprising that there are gaps in communication.

    I hope the new switch you've ordered is at least 100 Mbits/sec or
    ideally 1000 Mbits/sec.

    Did you WATCH the video I posted, Graham?
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Theo@theom+news@chiark.greenend.org.uk to uk.comp.sys.mac on Thu Nov 5 23:17:23 2026
    From Newsgroup: uk.comp.sys.mac

    Liz Tuddenham <liz@poppyrecords.invalid.invalid> wrote:
    Graham J <nobody@nowhere.co.uk> wrote:

    Liz Tuddenham wrote:

    [snip]

    I finally switched everything off, all the computers and the router,

    This is probably the best diagnostic step you ever took!

    Glad you got it sorted!

    then I switched on the router and allowed it several minutes to sort itself out, then switched everything else back on. Now Wi-Fi works
    (with the Ethernet plug lying on the table top alongside the Mini).

    If you want the Mac Mini to have a consistent IP address please explain why. It might be possible to achieve this with the correct
    configuration in the router. Even then you can't normally make it the
    same for both wifi and Ethernet.

    On my router it's Advanced Setup -> LAN -> IPv4 Autoconfig then at the
    bottom there is a 'static lease' section. If you press 'Add Entries' you
    can create a mapping from a MAC address to an IP address. The MAC address
    is either printed on the device label or you can go to Device Info -> DHCP
    and see the existing devices that are already connected and their MAC addresses.

    I might have to configure the LAN manually in order to include two
    printers, a Canon CLBP 460 and a Laserjet 6MP, which don't seem to obey
    the usual rules. Neither of them can be accessed from the Mini, the
    Canon shows up on the G3 but the Laserjet has to have its 'Asante'
    interface (Mac bus to Ethernet) re-booted each time it is selected.

    I'm not sure about the Asante interface but on the Laserjet 4 of that
    vintage with an ethernet card you just needed to configure the network connection as 'BOOTP' and it would get its IP address via DHCP (BOOTP is a predecessor subset of DHCP).

    With manual Ethernet configuration this might be sorted out but I shall
    not be doing it unaided. The Wi-Fi shouldn't need any further attention
    as long as I keep clear of its IP.

    It's fine to add devices with static IPs, but in my default settings the
    DHCP server takes up all of the subnet. In Advanced Setup -> LAN -> IPv4 Autoconfig you can change the Start IP Address and End IP Address. eg if
    you change the start IP to 192.168.0.100 and leave end at 192.168.0.254 then you can manually number devices with static IPs starting at 192.168.0.2 and upwards, and they won't clash wtih the DHCP server. Don't forget the
    netmask is 255.255.255.0 and gateway 192.168.0.1 when you configure devices.

    Theo
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From John@Man@the.keyboard to uk.comp.sys.mac on Fri Nov 6 02:23:27 2026
    From Newsgroup: uk.comp.sys.mac

    On Thu, 5 Nov 2026 12:28:54 +0000, liz@poppyrecords.invalid.invalid
    (Liz Tuddenham) wrote:

    Graham J <nobody@nowhere.co.uk> wrote:

    Liz Tuddenham wrote:
    Graham J <nobody@nowhere.co.uk> wrote:

    [...]

    I've just spotted a tiny square button on the router marked "WIFI".
    Pressing it or holding it down for a few seconds doesn't seem to make
    any difference and there is no indicator associated with it.

    There is another button next to it, marked "WPS"; holding that down
    makes the green LED on the Ethernet port flash occasionally.

    These should be explained in the router's documentation.

    The 'documentation' consisted of a label stuck on the packaging - there
    was nothing else. I have looked online but haven't found a proper
    detailed guide.

    I finally switched everything off, all the computers and the router,
    then I switched on the router and allowed it several minutes to sort
    itself out, then switched everything else back on. Now Wi-Fi works
    (with the Ethernet plug lying on the table top alongside the Mini).

    The Wi-Fi connection now shows up in the Network Preferences
    as:192.168.0.88

    "Ma'am, have you tried switching it off then switching it on again?"




    Many thanks to everyone who went to so much trouble to help me

    The only reason I didn't suggest the above procedure is that I
    really, really thought that you would have already done it. You are
    smart, skilled and experienced. :)

    My legendary Idiot Sister once called on me to help her get her
    Windows P.C.'s printer to work. I talked her through some diagnostics
    over the 'phone but they gave - from what she reported - inconsistent
    results so she picked me up, took me home with her and had me
    investigate in person. It turned out that the data connector from the
    printer was only half-way attached to the machine, it was loose and
    not screwed in - they had screws to hold them in in those days. I did
    ask her, repeatedly, on the call whether the cables were all attached
    and she had assured me that they were.

    A ten second inspection and repair job - which I managed to drag out
    to a good thirty-minutes-with-cup-of-tea event.

    She could have done it herself had she not been convinced that she
    already had.

    The reason for the above anecdote? It is *always* nice to eliminate
    the simple stuff before driving miles and collecting your smarter
    brother.

    I'm happy that you fixed it. :)

    J.




    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From nospam@nospam@de-ster.demon.nl (J. J. Lodder) to uk.comp.sys.mac on Fri Nov 6 10:07:34 2026
    From Newsgroup: uk.comp.sys.mac

    Liz Tuddenham <liz@poppyrecords.invalid.invalid> wrote:

    Graham J <nobody@nowhere.co.uk> wrote:

    Liz Tuddenham wrote:

    [snip]

    I might have to configure the LAN manually in order to include two printers, a Canon CLBP 460 and a Laserjet 6MP, which don't seem to obey the usual rules. Neither of them can be accessed from the Mini, the Canon shows up on the G3 but the Laserjet has to have its 'Asante' interface (Mac bus to Ethernet) re-booted each time it is selected.

    With manual Ethernet configuration this might be sorted out but I shall not be doing it unaided. The Wi-Fi shouldn't need any further attention as long as I keep clear of its IP.

    I remember that you talked about these printers before.

    A good thing to remember is that almost everything on the LAN might
    cache some parameters for an unknown length of time; which can cause no
    end of confusion. So if you make a change, a reboot of everything relevant might be a good idea. In time I guess you will learn when
    things seem to behave inconsistently.

    I am still on the vertical part of the learning curve.

    There should't be any learning curve.
    Ethernet under DHCP control should just work.
    Things may go wrong only when there is more than one
    active DHCP server on the network,

    Jan
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From liz@liz@poppyrecords.invalid.invalid (Liz Tuddenham) to uk.comp.sys.mac on Fri Nov 6 09:43:42 2026
    From Newsgroup: uk.comp.sys.mac

    Graham J <nobody@nowhere.co.uk> wrote:

    Liz Tuddenham wrote:

    [snip]

    They are all in good condition and have been wokdkng flawlessly for over
    a decade. If the Mini is plugged directly into the socket on the wall
    of the back room, everything works at 60Mbs but with just the switch and one short cable extra, it is down to 1 Mbps. (The back room socket by
    the switch is cabled to another socket on the wall of the front room,
    near where the router is located, then a short cable connects that
    socket to the router.

    So the path from the Mac Mini to the wall, then to the4 front room, then
    to the router probably all uses 4 pair cable operating at 100 Mbits/sec.

    When the switch is connected, where physically is it? If the "one short cable extra" has only 2 pairs that could very likely cause a problem, especially because ..

    Long description: (Short cable = 2 metres or less)

    The fibre drop-wire comes into the front bedroom beside the widow; on
    the wall by the window is a box which contains the joint between the
    drop wire and the internal system. Next to that is a slightly larger
    box which terminates the fibre; it has a 12v power supply and a short connecting lead to the "2G WAN" socket on the router.

    One Ethernet socket on the router connects by a short cable to a Mac
    Mini running Ubuntu which is always-on and runs the e-mail server.
    Another is connected by a short cable to an Ethernet socket on the wall
    which is cabled through the house to a socket in an alcove in the back
    bedroom, where the main computers are located. From there, another
    short cable takes it to a switch.

    From the switch there are short Ethernet cables to the Canon CLPB 460
    printer and the Asante adaptor which feeds an H.P. Laserjet 6MP.
    Another short cable feeds the G3. Two longer (5 metres) cables, around
    the back of the furniture, feed the Mac Mini and any 'visiting' computer
    (there aren't any at the moment, so the second one is left unconnected).

    A further short cable goes to another ethernet socket on the wall from
    where it is cabled down through the house to a socket beside the window
    of the front downstairs room (which is used as a sound editing studio).
    From there it is connected by a short cable to another switch which
    feeds a G3 by a short cable and by a longer cable to an iMac on the
    other side of the room.

    None of the 'short' cables appears to be anything other than a
    full-sized 4-conductor Ethernet cable and the house wiring is the
    standard product sold on drums for the purpose. A vast improvement in
    speed was obtained by taking the lead which runs from the Mini to the
    switch out of the switch and plugging it directly into the wall socket
    that leads to the router.



    The switch is rated at 10 Mbs maximum,

    So everything going through it will only operate at 10 Mbits/sec - significantly slower than your fibre internet connection. Its not surprising that there are gaps in communication.

    There weren't when I was feeding the same Ethernet from an ADSL router.


    I hope the new switch you've ordered is at least 100 Mbits/sec or
    ideally 1000 Mbits/sec.

    It is 10/100 with POE and a few other things I may never need.
    --
    ~ Liz Tuddenham ~
    (Remove the ".invalid"s and add ".co.uk" to reply)
    www.poppyrecords.co.uk
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From liz@liz@poppyrecords.invalid.invalid (Liz Tuddenham) to uk.comp.sys.mac on Fri Nov 6 09:43:42 2026
    From Newsgroup: uk.comp.sys.mac

    Theo <theom+news@chiark.greenend.org.uk> wrote:

    Liz Tuddenham <liz@poppyrecords.invalid.invalid> wrote:
    Graham J <nobody@nowhere.co.uk> wrote:

    Liz Tuddenham wrote:

    [snip]

    I finally switched everything off, all the computers and the router,

    This is probably the best diagnostic step you ever took!

    Glad you got it sorted!

    then I switched on the router and allowed it several minutes to sort itself out, then switched everything else back on. Now Wi-Fi works (with the Ethernet plug lying on the table top alongside the Mini).

    If you want the Mac Mini to have a consistent IP address please explain why. It might be possible to achieve this with the correct configuration in the router. Even then you can't normally make it the same for both wifi and Ethernet.

    On my router it's Advanced Setup -> LAN -> IPv4 Autoconfig then at the
    bottom there is a 'static lease' section. If you press 'Add Entries' you
    can create a mapping from a MAC address to an IP address. The MAC address
    is either printed on the device label or you can go to Device Info -> DHCP and see the existing devices that are already connected and their MAC addresses.

    I might have to configure the LAN manually in order to include two printers, a Canon CLBP 460 and a Laserjet 6MP, which don't seem to obey
    the usual rules. Neither of them can be accessed from the Mini, the
    Canon shows up on the G3 but the Laserjet has to have its 'Asante' interface (Mac bus to Ethernet) re-booted each time it is selected.

    I'm not sure about the Asante interface but on the Laserjet 4 of that
    vintage with an ethernet card you just needed to configure the network connection as 'BOOTP' and it would get its IP address via DHCP (BOOTP is a predecessor subset of DHCP).

    With manual Ethernet configuration this might be sorted out but I shall
    not be doing it unaided. The Wi-Fi shouldn't need any further attention
    as long as I keep clear of its IP.

    It's fine to add devices with static IPs, but in my default settings the
    DHCP server takes up all of the subnet. In Advanced Setup -> LAN -> IPv4 Autoconfig you can change the Start IP Address and End IP Address. eg if
    you change the start IP to 192.168.0.100 and leave end at 192.168.0.254 then you can manually number devices with static IPs starting at 192.168.0.2 and upwards, and they won't clash wtih the DHCP server. Don't forget the
    netmask is 255.255.255.0 and gateway 192.168.0.1 when you configure devices.

    I'm still trying to understand what all those things are and how they
    work.
    --
    ~ Liz Tuddenham ~
    (Remove the ".invalid"s and add ".co.uk" to reply)
    www.poppyrecords.co.uk
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From liz@liz@poppyrecords.invalid.invalid (Liz Tuddenham) to uk.comp.sys.mac on Fri Nov 6 09:43:42 2026
    From Newsgroup: uk.comp.sys.mac

    John <Man@the.keyboard> wrote:

    On Thu, 5 Nov 2026 12:28:54 +0000, liz@poppyrecords.invalid.invalid
    (Liz Tuddenham) wrote:

    Graham J <nobody@nowhere.co.uk> wrote:

    Liz Tuddenham wrote:
    Graham J <nobody@nowhere.co.uk> wrote:

    [...]

    I've just spotted a tiny square button on the router marked "WIFI".
    Pressing it or holding it down for a few seconds doesn't seem to make
    any difference and there is no indicator associated with it.

    There is another button next to it, marked "WPS"; holding that down
    makes the green LED on the Ethernet port flash occasionally.

    These should be explained in the router's documentation.

    The 'documentation' consisted of a label stuck on the packaging - there
    was nothing else. I have looked online but haven't found a proper
    detailed guide.

    I finally switched everything off, all the computers and the router,
    then I switched on the router and allowed it several minutes to sort
    itself out, then switched everything else back on. Now Wi-Fi works
    (with the Ethernet plug lying on the table top alongside the Mini).

    The Wi-Fi connection now shows up in the Network Preferences >as:192.168.0.88

    "Ma'am, have you tried switching it off then switching it on again?"




    Many thanks to everyone who went to so much trouble to help me

    The only reason I didn't suggest the above procedure is that I
    really, really thought that you would have already done it. You are
    smart, skilled and experienced. :)

    Don't assume too much - I definitely wasn't any of those in this case.
    --
    ~ Liz Tuddenham ~
    (Remove the ".invalid"s and add ".co.uk" to reply)
    www.poppyrecords.co.uk
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From liz@liz@poppyrecords.invalid.invalid (Liz Tuddenham) to uk.comp.sys.mac on Fri Nov 6 09:55:32 2026
    From Newsgroup: uk.comp.sys.mac

    J. J. Lodder <nospam@de-ster.demon.nl> wrote:

    Liz Tuddenham <liz@poppyrecords.invalid.invalid> wrote:

    Graham J <nobody@nowhere.co.uk> wrote:

    Liz Tuddenham wrote:

    [snip]

    I might have to configure the LAN manually in order to include two printers, a Canon CLBP 460 and a Laserjet 6MP, which don't seem to obey the usual rules. Neither of them can be accessed from the Mini, the Canon shows up on the G3 but the Laserjet has to have its 'Asante' interface (Mac bus to Ethernet) re-booted each time it is selected.

    With manual Ethernet configuration this might be sorted out but I shall not be doing it unaided. The Wi-Fi shouldn't need any further attention
    as long as I keep clear of its IP.

    I remember that you talked about these printers before.

    A good thing to remember is that almost everything on the LAN might
    cache some parameters for an unknown length of time; which can cause no end of confusion. So if you make a change, a reboot of everything relevant might be a good idea. In time I guess you will learn when things seem to behave inconsistently.

    I am still on the vertical part of the learning curve.

    There should't be any learning curve.

    There was when I didn't know what "DCHP", "WAN", "LAN" or any of the
    other abbreviations stood for - and even more when I didn't know what
    they did - and even more again when I didn't know how they did it.

    My background is in analogue electronics (even valves), computers are
    just a tool.
    --
    ~ Liz Tuddenham ~
    (Remove the ".invalid"s and add ".co.uk" to reply)
    www.poppyrecords.co.uk
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Theo@theom+news@chiark.greenend.org.uk to uk.comp.sys.mac on Fri Nov 6 11:33:30 2026
    From Newsgroup: uk.comp.sys.mac

    Liz Tuddenham <liz@poppyrecords.invalid.invalid> wrote:
    None of the 'short' cables appears to be anything other than a
    full-sized 4-conductor Ethernet cable and the house wiring is the
    standard product sold on drums for the purpose. A vast improvement in
    speed was obtained by taking the lead which runs from the Mini to the
    switch out of the switch and plugging it directly into the wall socket
    that leads to the router.

    Gigabit ethernet requires 8 conductors (4 pairs). 100 megabit ethernet only requires 4 conductors (2 pairs).

    Truespeed don't have a <100Mbit tier so you'll lose some speed. You can
    still get the full bandwidth via wifi though.

    The switch is rated at 10 Mbs maximum,

    So everything going through it will only operate at 10 Mbits/sec - significantly slower than your fibre internet connection. Its not surprising that there are gaps in communication.

    There weren't when I was feeding the same Ethernet from an ADSL router.

    Depending on the congestion control invovled it can cause back-ups, eg like trying to put the M25 into a single lane in each direction, which would
    cause jams where the traffic volumes of a single carriageway country road
    would handle it fine. You can end up with buffers overflowing and extreme backpressure, then packets get dropped, have to be resent, dropped again,
    etc.

    I hope the new switch you've ordered is at least 100 Mbits/sec or
    ideally 1000 Mbits/sec.

    It is 10/100 with POE and a few other things I may never need.

    OK. 1000M would have been better where your cabling allowed, but I suspect you'll still do much better at 100M than at 10M.

    Theo
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From liz@liz@poppyrecords.invalid.invalid (Liz Tuddenham) to uk.comp.sys.mac on Fri Nov 6 13:26:36 2026
    From Newsgroup: uk.comp.sys.mac

    Theo <theom+news@chiark.greenend.org.uk> wrote:


    [..]
    Gigabit ethernet requires 8 conductors (4 pairs). 100 megabit ethernet only requires 4 conductors (2 pairs).

    It didn't exist when I put those cables in.


    Truespeed don't have a <100Mbit tier so you'll lose some speed. You can still get the full bandwidth via wifi though.

    The Ethernet through the switch is giving around 10 Mbps upload and
    download; on Wireless I am getting 60 Mbps upload and 30 Mbps download.
    That's fast enough for anything I need at the moment. if I need faster,
    I can always temporarily bypass the switch.


    Now I'm waiting for my sent e-mails to be marked as kosher so they don't
    keep bouncing and for my telephone service to be switched over to VOIP -
    I am not expecting either of those to go smoothly.
    --
    ~ Liz Tuddenham ~
    (Remove the ".invalid"s and add ".co.uk" to reply)
    www.poppyrecords.co.uk
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Theo@theom+news@chiark.greenend.org.uk to uk.comp.sys.mac on Fri Nov 6 17:16:52 2026
    From Newsgroup: uk.comp.sys.mac

    Liz Tuddenham <liz@poppyrecords.invalid.invalid> wrote:
    Now I'm waiting for my sent e-mails to be marked as kosher so they don't
    keep bouncing and for my telephone service to be switched over to VOIP -
    I am not expecting either of those to go smoothly.

    BTW, you mentioned trying to purchase the static IP service. I've been with Truespeed (ex County Broadband in East Anglia) on the base package and since the service was installed in June the IP has never changed.

    So you may be ok to manage without paying for the extra service - seems like the service is mostly a guarantee that it won't change rather than them actually changing it regularly. ie the normal address is 'pseudo-static'.
    If you don't pay, it could be sufficient to use a dynamic DNS service to
    update the DNS record for your services when/if it ever detects changes.

    (although one of the spam checks is about the IP having valid reverse-DNS - being able to look up the IP address and get the correct hostname - which
    needs ISP help. So your static IP service may be paying for them to do
    that)

    Theo
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From liz@liz@poppyrecords.invalid.invalid (Liz Tuddenham) to uk.comp.sys.mac on Fri Nov 6 22:04:39 2026
    From Newsgroup: uk.comp.sys.mac

    Theo <theom+news@chiark.greenend.org.uk> wrote:

    Liz Tuddenham <liz@poppyrecords.invalid.invalid> wrote:
    Now I'm waiting for my sent e-mails to be marked as kosher so they don't keep bouncing and for my telephone service to be switched over to VOIP -
    I am not expecting either of those to go smoothly.

    BTW, you mentioned trying to purchase the static IP service. I've been with Truespeed (ex County Broadband in East Anglia) on the base package and since the service was installed in June the IP has never changed.

    So you may be ok to manage without paying for the extra service - seems like the service is mostly a guarantee that it won't change rather than them actually changing it regularly. ie the normal address is 'pseudo-static'.
    If you don't pay, it could be sufficient to use a dynamic DNS service to update the DNS record for your services when/if it ever detects changes.

    (although one of the spam checks is about the IP having valid reverse-DNS - being able to look up the IP address and get the correct hostname - which needs ISP help. So your static IP service may be paying for them to do
    that)

    My account with Truespeed is a a business account, so a static IP and
    reverse DNS should be available upon request. I have requested both and
    now some (not all) of my e-mails are starting to be delivered.
    --
    ~ Liz Tuddenham ~
    (Remove the ".invalid"s and add ".co.uk" to reply)
    www.poppyrecords.co.uk
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Theo@theom+news@chiark.greenend.org.uk to uk.comp.sys.mac on Sat Nov 7 12:49:03 2026
    From Newsgroup: uk.comp.sys.mac

    Liz Tuddenham <liz@poppyrecords.invalid.invalid> wrote:
    Theo <theom+news@chiark.greenend.org.uk> wrote:

    Liz Tuddenham <liz@poppyrecords.invalid.invalid> wrote:
    Now I'm waiting for my sent e-mails to be marked as kosher so they don't keep bouncing and for my telephone service to be switched over to VOIP - I am not expecting either of those to go smoothly.

    BTW, you mentioned trying to purchase the static IP service. I've been with
    Truespeed (ex County Broadband in East Anglia) on the base package and since
    the service was installed in June the IP has never changed.

    So you may be ok to manage without paying for the extra service - seems like
    the service is mostly a guarantee that it won't change rather than them actually changing it regularly. ie the normal address is 'pseudo-static'. If you don't pay, it could be sufficient to use a dynamic DNS service to update the DNS record for your services when/if it ever detects changes.

    (although one of the spam checks is about the IP having valid reverse-DNS - being able to look up the IP address and get the correct hostname - which needs ISP help. So your static IP service may be paying for them to do that)

    My account with Truespeed is a a business account, so a static IP and
    reverse DNS should be available upon request. I have requested both and
    now some (not all) of my e-mails are starting to be delivered.

    OK... by the way, in another group somebody mentioned the current Mythic Beasts status message:

    2026-11-06 15:08 rCo we've become aware that Microsoft have implemented a significant, unannounced change to their mail policy, and are now rejecting
    all mail that does not have a DMARC record. This issue affects mail sent to Hotmail, Outlook and other Microsoft services. If this affects your domain, then adding a DMARC DNS record (TXT record, hostname: "_dmarc", data "v=DMARC1;p=none") should fix the issue. You may wish to tell affected recipients to complain to Microsoft as this issue is affecting other
    providers, and so it is likely that they are losing other legitimate email.


    So you are likely to need to have DMARC set on your domain to be able to
    send to anyone using Microsoft systems (which is a lot, especially
    businesses). Ask the people who you pay for your domain if you don't know
    what the above means.

    Theo
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From liz@liz@poppyrecords.invalid.invalid (Liz Tuddenham) to uk.comp.sys.mac on Sat Nov 7 13:26:48 2026
    From Newsgroup: uk.comp.sys.mac

    Theo <theom+news@chiark.greenend.org.uk> wrote:

    Liz Tuddenham <liz@poppyrecords.invalid.invalid> wrote:
    Theo <theom+news@chiark.greenend.org.uk> wrote:

    Liz Tuddenham <liz@poppyrecords.invalid.invalid> wrote:
    Now I'm waiting for my sent e-mails to be marked as kosher so they don't
    keep bouncing and for my telephone service to be switched over to VOIP -
    I am not expecting either of those to go smoothly.

    BTW, you mentioned trying to purchase the static IP service. I've
    been with Truespeed (ex County Broadband in East Anglia) on the base package and since the service was installed in June the IP has never changed.

    So you may be ok to manage without paying for the extra service -
    seems like the service is mostly a guarantee that it won't change
    rather than them actually changing it regularly. ie the normal
    address is 'pseudo-static'. If you don't pay, it could be sufficient
    to use a dynamic DNS service to update the DNS record for your
    services when/if it ever detects changes.

    (although one of the spam checks is about the IP having valid
    reverse-DNS - being able to look up the IP address and get the correct hostname - which needs ISP help. So your static IP service may be
    paying for them to do that)

    My account with Truespeed is a a business account, so a static IP and reverse DNS should be available upon request. I have requested both and now some (not all) of my e-mails are starting to be delivered.

    OK... by the way, in another group somebody mentioned the current Mythic Beasts status message:

    2026-11-06 15:08 rCo we've become aware that Microsoft have implemented a significant, unannounced change to their mail policy, and are now rejecting all mail that does not have a DMARC record. This issue affects mail sent to Hotmail, Outlook and other Microsoft services. If this affects your domain, then adding a DMARC DNS record (TXT record, hostname: "_dmarc", data "v=DMARC1;p=none") should fix the issue. You may wish to tell affected recipients to complain to Microsoft as this issue is affecting other providers, and so it is likely that they are losing other legitimate email.

    I have been telling them that gmail are blocking some of their e-mails
    for the last two years but they just shrug and assume it is something
    wrong with my e-mail setup. The commonest response is "Nobody else has complained" ; they can't seem to understand that they wouldn't be able
    to see the complaints from anyone whose e-mails have been blocked.


    So you are likely to need to have DMARC set on your domain to be able to
    send to anyone using Microsoft systems (which is a lot, especially businesses). Ask the people who you pay for your domain if you don't know what the above means.

    There appears to be a DMARC entry in the TXT /dmarc record of my
    outgoing domain host ...and gmail is letting through my e-mails but
    flagging them as potential spam. This is a big improvement on what they
    were doing a couple of years ago: deleting them without a bounce
    message.

    On the incoming side, I get about one spam e-mail per day and it is
    always from a gmail address. They need to fix their own security first.
    --
    ~ Liz Tuddenham ~
    (Remove the ".invalid"s and add ".co.uk" to reply)
    www.poppyrecords.co.uk
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From liz@liz@poppyrecords.invalid.invalid (Liz Tuddenham) to uk.comp.sys.mac on Sat Nov 7 13:36:35 2026
    From Newsgroup: uk.comp.sys.mac

    Theo <theom+news@chiark.greenend.org.uk> wrote:

    [...]
    2026-11-06 15:08 rCo we've become aware that Microsoft have implemented a significant, unannounced change to their mail policy, and are now rejecting all mail that does not have a DMARC record.

    I have checked with my knowledgeable friend and he says my DMARC record
    and SPF are all set up correctly.
    --
    ~ Liz Tuddenham ~
    (Remove the ".invalid"s and add ".co.uk" to reply)
    www.poppyrecords.co.uk
    --- Synchronet 3.22a-Linux NewsLink 1.2