Sysop: | Amessyroom |
---|---|
Location: | Fayetteville, NC |
Users: | 26 |
Nodes: | 6 (0 / 6) |
Uptime: | 53:40:23 |
Calls: | 632 |
Files: | 1,187 |
D/L today: |
27 files (19,977K bytes) |
Messages: | 178,640 |
I now use the Private Internet Access app (PIA) for VPN working.
Since upgrading to Tahoe, when I turn off VPN access, IrCOve found
that I need to renew the DHCP lease to continue non-VPN internet
access. Admittedly this is quite easy to do via System Settings
or creating an alias to call:
rCysudo ifconfig set en0 BOOTP ; sudo ifconfig set en0 DHCPrCO
So, am I online in seeing this behaviour?
I now use the Private Internet Access app (PIA) for VPN working.
Since upgrading to Tahoe, when I turn off VPN access, IrCOve found
that I need to renew the DHCP lease to continue non-VPN internet
access. Admittedly this is quite easy to do via System Settings
or creating an alias to call:
rCysudo ifconfig set en0 BOOTP ; sudo ifconfig set en0 DHCPrCO
So, am I online in seeing this behaviour?
On 17.09.2025 16:31, Alan B wrote:
I now use the Private Internet Access app (PIA) for VPN working.
Since upgrading to Tahoe, when I turn off VPN access, IrCOve found
that I need to renew the DHCP lease to continue non-VPN internet
access. Admittedly this is quite easy to do via System Settings
or creating an alias to call:
rCysudo ifconfig set en0 BOOTP ; sudo ifconfig set en0 DHCPrCO
So, am I online in seeing this behaviour?
No, itrCOs not just you. Or rather, not only you. This is not a unique glitch of your Mac, but a known peculiarity of the interaction between
PIA and the network changes in macOS 15 Tahoe.
try:
sudo ifconfig en0 down
sudo ifconfig en0 up
or so:
sudo ipconfig set en0 DHCP
Check the service order in System Settings raA Network raA (rCa) Set Service
Order. If the PIA VPN service is listed above Wi-Fi/Ethernet, try moving
it down.
On 2025-09-17, -i-|-+-#-e-+-# <senatov@tample.org> wrote:
On 17.09.2025 16:31, Alan B wrote:
I now use the Private Internet Access app (PIA) for VPN working.
Since upgrading to Tahoe, when I turn off VPN access, IrCOve found
that I need to renew the DHCP lease to continue non-VPN internet
access. Admittedly this is quite easy to do via System Settings
or creating an alias to call:
rCysudo ifconfig set en0 BOOTP ; sudo ifconfig set en0 DHCPrCO
So, am I online in seeing this behaviour?
No, itrCOs not just you. Or rather, not only you. This is not a unique
glitch of your Mac, but a known peculiarity of the interaction between
PIA and the network changes in macOS 15 Tahoe.
try:
sudo ifconfig en0 down
sudo ifconfig en0 up
or so:
sudo ipconfig set en0 DHCP
Check the service order in System Settings raA Network raA (rCa) Set Service
Order. If the PIA VPN service is listed above Wi-Fi/Ethernet, try moving
it down.
With PIA running I only see 3 services:
USB 10/100/1000 LAN
Wi-Fi
Thunderbolt Bridge
However moving Wi-Fi to the top seems to have cured the problem.
Thanks for your reply :)
On 17 Sep 2025 at 16:29:47 BST, Alan B wrote:
On 2025-09-17, ??????? <senatov@tample.org> wrote:
On 17.09.2025 16:31, Alan B wrote:
I now use the Private Internet Access app (PIA) for VPN working.
Since upgrading to Tahoe, when I turn off VPN access, I've found
that I need to renew the DHCP lease to continue non-VPN internet
access. Admittedly this is quite easy to do via System Settings
or creating an alias to call:
'sudo ifconfig set en0 BOOTP ; sudo ifconfig set en0 DHCP'
So, am I online in seeing this behaviour?
No, it's not just you. Or rather, not only you. This is not a unique
glitch of your Mac, but a known peculiarity of the interaction between
PIA and the network changes in macOS 15 Tahoe.
try:
sudo ifconfig en0 down
sudo ifconfig en0 up
or so:
sudo ipconfig set en0 DHCP
Check the service order in System Settings -> Network -> (...) Set Service
Order. If the PIA VPN service is listed above Wi-Fi/Ethernet, try moving >>> it down.
With PIA running I only see 3 services:
USB 10/100/1000 LAN
Wi-Fi
Thunderbolt Bridge
However moving Wi-Fi to the top seems to have cured the problem.
Thanks for your reply :)
I gave that a go but didn't seem to help. Only way for me was to restart the computer after each time PIA used.
I tried their online help and they suggested:
--
Here are the steps on how you can change the DNS of your device:
1. Go to System Settings and click Network.
2. Select the network interface you are using (Wi-Fi or Ethernet) and click on
Details...
3. Open the DNS tab and click the + button at the bottom to add the DNS server
addresses: 208.67.222.222 and 208.67.220.220
4. Click OK to save the changes.
--
Which seems to work. For now.
RJH <patchmoney@gmx.com> wrote:
On 17 Sep 2025 at 16:29:47 BST, Alan B wrote:
On 2025-09-17, ??????? <senatov@tample.org> wrote:
On 17.09.2025 16:31, Alan B wrote:
I now use the Private Internet Access app (PIA) for VPN working.
Since upgrading to Tahoe, when I turn off VPN access, I've found
that I need to renew the DHCP lease to continue non-VPN internet
access. Admittedly this is quite easy to do via System Settings
or creating an alias to call:
'sudo ifconfig set en0 BOOTP ; sudo ifconfig set en0 DHCP'
So, am I online in seeing this behaviour?
No, it's not just you. Or rather, not only you. This is not a unique
glitch of your Mac, but a known peculiarity of the interaction between >>>> PIA and the network changes in macOS 15 Tahoe.
try:
sudo ifconfig en0 down
sudo ifconfig en0 up
or so:
sudo ipconfig set en0 DHCP
Check the service order in System Settings -> Network -> (...) Set Service
Order. If the PIA VPN service is listed above Wi-Fi/Ethernet, try moving >>>> it down.
With PIA running I only see 3 services:
USB 10/100/1000 LAN
Wi-Fi
Thunderbolt Bridge
However moving Wi-Fi to the top seems to have cured the problem.
Thanks for your reply :)
I gave that a go but didn't seem to help. Only way for me was to restart the >> computer after each time PIA used.
I tried their online help and they suggested:
--
Here are the steps on how you can change the DNS of your device:
1. Go to System Settings and click Network.
2. Select the network interface you are using (Wi-Fi or Ethernet) and click on
Details...
3. Open the DNS tab and click the + button at the bottom to add the DNS server
addresses: 208.67.222.222 and 208.67.220.220
4. Click OK to save the changes.
--
Which seems to work. For now.
For various reasons I've rebuilt my M1 MBP system from scratch and re-installed
PIA. I've tried the fix suggested earlier by ??????? and also the extra DNS server addresses - sadly neither seem to work now. The default DNS server address is 192.168.1.254 of my wireless router.
Update: I've re-instated the default DHCP server address and using
the terminal command 'sudo ipconfig set en0 DHCP' (as also suggested by senatov) seems to be working. Not ideal but beats restarting!
RJH <patchmoney@gmx.com> wrote:
On 17 Sep 2025 at 16:29:47 BST, Alan B wrote:
On 2025-09-17, ??????? <senatov@tample.org> wrote:
On 17.09.2025 16:31, Alan B wrote:
I now use the Private Internet Access app (PIA) for VPN working.
Since upgrading to Tahoe, when I turn off VPN access, I've found
that I need to renew the DHCP lease to continue non-VPN internet
access. Admittedly this is quite easy to do via System Settings
or creating an alias to call:
'sudo ifconfig set en0 BOOTP ; sudo ifconfig set en0 DHCP'
So, am I online in seeing this behaviour?
No, it's not just you. Or rather, not only you. This is not a unique
glitch of your Mac, but a known peculiarity of the interaction between >>>> PIA and the network changes in macOS 15 Tahoe.
try:
sudo ifconfig en0 down
sudo ifconfig en0 up
or so:
sudo ipconfig set en0 DHCP
Check the service order in System Settings -> Network -> (...) Set Service
Order. If the PIA VPN service is listed above Wi-Fi/Ethernet, try moving >>>> it down.
With PIA running I only see 3 services:
USB 10/100/1000 LAN
Wi-Fi
Thunderbolt Bridge
However moving Wi-Fi to the top seems to have cured the problem.
Thanks for your reply :)
I gave that a go but didn't seem to help. Only way for me was to restart the >> computer after each time PIA used.
I tried their online help and they suggested:
--
Here are the steps on how you can change the DNS of your device:
1. Go to System Settings and click Network.
2. Select the network interface you are using (Wi-Fi or Ethernet) and click on
Details...
3. Open the DNS tab and click the + button at the bottom to add the DNS server
addresses: 208.67.222.222 and 208.67.220.220
4. Click OK to save the changes.
--
Which seems to work. For now.
For various reasons I've rebuilt my M1 MBP system from scratch and re-installed
PIA.
I've tried the fix suggested earlier by ??????? and also the extra DNS server addresses - sadly neither seem to work now. The default DNS server address is 192.168.1.254 of my wireless router.
On 2025-09-23, Alan B <alanrichardbarker@gmail.com.invalid> wrote:
[snip]
Update: I've re-instated the default DHCP server address and using
the terminal command 'sudo ipconfig set en0 DHCP' (as also suggested by
senatov) seems to be working. Not ideal but beats restarting!
I should have said ".... re-instated the default DNS ...."
On 23 Sep 2025 at 08:35:27 BST, Alan B wrote:
RJH <patchmoney@gmx.com> wrote:
On 17 Sep 2025 at 16:29:47 BST, Alan B wrote:
On 2025-09-17, ??????? <senatov@tample.org> wrote:
On 17.09.2025 16:31, Alan B wrote:
I now use the Private Internet Access app (PIA) for VPN working.
Since upgrading to Tahoe, when I turn off VPN access, I've found
that I need to renew the DHCP lease to continue non-VPN internet
access. Admittedly this is quite easy to do via System Settings
or creating an alias to call:
'sudo ifconfig set en0 BOOTP ; sudo ifconfig set en0 DHCP'
So, am I online in seeing this behaviour?
No, it's not just you. Or rather, not only you. This is not a unique >>>>> glitch of your Mac, but a known peculiarity of the interaction between >>>>> PIA and the network changes in macOS 15 Tahoe.
try:
sudo ifconfig en0 down
sudo ifconfig en0 up
or so:
sudo ipconfig set en0 DHCP
Check the service order in System Settings -> Network -> (...) Set Service
Order. If the PIA VPN service is listed above Wi-Fi/Ethernet, try moving >>>>> it down.
With PIA running I only see 3 services:
USB 10/100/1000 LAN
Wi-Fi
Thunderbolt Bridge
However moving Wi-Fi to the top seems to have cured the problem.
Thanks for your reply :)
I gave that a go but didn't seem to help. Only way for me was to restart the
computer after each time PIA used.
I tried their online help and they suggested:
--
Here are the steps on how you can change the DNS of your device:
1. Go to System Settings and click Network.
2. Select the network interface you are using (Wi-Fi or Ethernet) and click on
Details...
3. Open the DNS tab and click the + button at the bottom to add the DNS server
addresses: 208.67.222.222 and 208.67.220.220
4. Click OK to save the changes.
--
Which seems to work. For now.
For various reasons I've rebuilt my M1 MBP system from scratch and re-installed
PIA.
Just OoI, can you do that with the original Apple ID and avoid importing all the rubbish associated with that account? Thinking particularly of the 200+ apps - less the apps themselves (which I could just bin), more the configuration files, caches etc. Must be 15 years of stuff, most of which I don't use.
It all seems to work fine with the DNS addresses they listed, but only if I keep the VPN active. Once I close the VPN the wireless internet connection is very patchy.
I've sent an email support request - I'll post any answers they come up with. Although I suspect it needs a software update.
On 23 Sep 2025 at 09:36:06 BST, Alan B wrote:
On 2025-09-23, Alan B <alanrichardbarker@gmail.com.invalid> wrote:
[snip]
Update: I've re-instated the default DHCP server address and using
the terminal command 'sudo ipconfig set en0 DHCP' (as also suggested by
senatov) seems to be working. Not ideal but beats restarting!
I should have said ".... re-instated the default DNS ...."
Is that what 'sudo ipconfig set en0 DHCP' does?
If so I could give it (another) whirl - I take it it needs to be done each time PIA is used/stopped?
On 2025-09-23, RJH <patchmoney@gmx.com> wrote:
On 23 Sep 2025 at 09:36:06 BST, Alan B wrote:
On 2025-09-23, Alan B <alanrichardbarker@gmail.com.invalid> wrote:
[snip]
Update: I've re-instated the default DHCP server address and using
the terminal command 'sudo ipconfig set en0 DHCP' (as also suggested by >>> senatov) seems to be working. Not ideal but beats restarting!
I should have said ".... re-instated the default DNS ...."
Is that what 'sudo ipconfig set en0 DHCP' does?
I *think* that the command reconfigures the wireless (en0) i/f to use
the default DHCP server - the wireless router in my case.
If so I could give it (another) whirl - I take it it needs to be done each time PIA is used/stopped?
Yes.
Alan B <alanrichardbarker@gmail.com.invalid> wrote:
On 2025-09-23, RJH <patchmoney@gmx.com> wrote:
On 23 Sep 2025 at 09:36:06 BST, Alan B wrote:
On 2025-09-23, Alan B <alanrichardbarker@gmail.com.invalid> wrote:
[snip]
Update: I've re-instated the default DHCP server address and using
the terminal command 'sudo ipconfig set en0 DHCP' (as also suggested by >>> senatov) seems to be working. Not ideal but beats restarting!
I should have said ".... re-instated the default DNS ...."
Is that what 'sudo ipconfig set en0 DHCP' does?
I *think* that the command reconfigures the wireless (en0) i/f to use
the default DHCP server - the wireless router in my case.
If so I could give it (another) whirl - I take it it needs to be done each
time PIA is used/stopped?
Yes.
FYI: I too have this issue after closing the PIA VPN. Fortunately I
only have to do that to stream TV, otherwise I leave the VPN active.
In my case, after closing the VPN: in Settings/Network/WiFi/
[connected network] Details/TCP-IP/DHCP lease - Renew DHCP Lease
restores a working connection.
I hope that PIA will fix this pronto, it's a PITA.
Just OoI, can you do that with the original Apple ID and avoid importing all >> the rubbish associated with that account? Thinking particularly of the 200+ >> apps - less the apps themselves (which I could just bin), more the
configuration files, caches etc. Must be 15 years of stuff, most of which I >> don't use.
No apps previously purchased from the AppStore automatically re-installed themselves so I was able pick which ones I needed immediately. I'm
assuming I can manually download any others in the future. If I include
other non-AppStore apps I don't really need, I must have saved many GBs
of redundant data.
FYI: I too have this issue after closing the PIA VPN. Fortunately I
only have to do that to stream TV, otherwise I leave the VPN active.
In my case, after closing the VPN: in Settings/Network/WiFi/
[connected network] Details/TCP-IP/DHCP lease - Renew DHCP Lease
restores a working connection.
Yes that's a good solution and doesn't involve messing with the CLI :)
I hope that PIA will fix this pronto, it's a PITA.
Yes indeed!
In my case, after closing the VPN: in Settings/Network/WiFi/
[connected network] Details/TCP-IP/DHCP lease - Renew DHCP Lease
restores a working connection.
Yes that's a good solution and doesn't involve messing with the CLI :)
+1 - works here too.
I hope that PIA will fix this pronto, it's a PITA.
RJH <patchmoney@gmx.com> wrote:
[...]
+1 - works here too.In my case, after closing the VPN: in Settings/Network/WiFi/
[connected network] Details/TCP-IP/DHCP lease - Renew DHCP Lease
restores a working connection.
Yes that's a good solution and doesn't involve messing with the CLI :)
I hope that PIA will fix this pronto, it's a PITA.
I've opened Ticket # 30553056 with PIA.
Sn!pe <snipeco.2@gmail.com> wrote:
RJH <patchmoney@gmx.com> wrote:
[...]
+1 - works here too.In my case, after closing the VPN: in Settings/Network/WiFi/
[connected network] Details/TCP-IP/DHCP lease - Renew DHCP Lease
restores a working connection.
Yes that's a good solution and doesn't involve messing with the CLI :) >>>>
I hope that PIA will fix this pronto, it's a PITA.
I've opened Ticket # 30553056 with PIA.
Ticket # 30554902 here.
On 24 Sep 2025 at 10:02:46 BST, Alan B wrote:
Sn!pe <snipeco.2@gmail.com> wrote:
RJH <patchmoney@gmx.com> wrote:
[...]
+1 - works here too.In my case, after closing the VPN: in Settings/Network/WiFi/
[connected network] Details/TCP-IP/DHCP lease - Renew DHCP Lease
restores a working connection.
Yes that's a good solution and doesn't involve messing with the CLI :) >>>>>
I hope that PIA will fix this pronto, it's a PITA.
I've opened Ticket # 30553056 with PIA.
Ticket # 30554902 here.
and Ticket # 30546573 from me.
On 24 Sep 2025 at 13:30:45 GMT+1, "RJH" <patchmoney@gmx.com> wrote:
On 24 Sep 2025 at 10:02:46 BST, Alan B wrote:
Sn!pe <snipeco.2@gmail.com> wrote:
RJH <patchmoney@gmx.com> wrote:
[...]
+1 - works here too.In my case, after closing the VPN: in Settings/Network/WiFi/
[connected network] Details/TCP-IP/DHCP lease - Renew DHCP Lease >>>>>>> restores a working connection.
Yes that's a good solution and doesn't involve messing with the CLI :) >>>>>>
I hope that PIA will fix this pronto, it's a PITA.
I've opened Ticket # 30553056 with PIA.
Ticket # 30554902 here.
and Ticket # 30546573 from me.
I've had an email from PIA Support with a link to a new alpha build of PIA. Sadly I get the folllowing error message from Firefox (Safari gives a shorter version).
This XML file does not appear to have any style information associated with it. The document tree is shown below.
<Error>
<Code>AccessDenied</Code>
<Message>Access Denied</Message>
<RequestId>MRCF70KSW6WC8EGB</RequestId>
<HostId>
MGX41Ie7Cpg7K9rRmh4tB83cukskEwqolPzzRCYp9RxFaC44h30TuKxTVsXur5yvGNeLyBf3XQWS1 ioYHUrlh2X8qxr1RxoMQWkVadsuSxE=
</HostId>
</Error>
I've reported the issue back to PIA Support.
On 24 Sep 2025 at 13:30:45 GMT+1, "RJH" <patchmoney@gmx.com> wrote:
On 24 Sep 2025 at 10:02:46 BST, Alan B wrote:
Sn!pe <snipeco.2@gmail.com> wrote:
RJH <patchmoney@gmx.com> wrote:
[...]
+1 - works here too.In my case, after closing the VPN: in Settings/Network/WiFi/
[connected network] Details/TCP-IP/DHCP lease - Renew DHCP Lease >>>>>>>> restores a working connection.
Yes that's a good solution and doesn't involve messing with the CLI :) >>>>>>>
I hope that PIA will fix this pronto, it's a PITA.
I've opened Ticket # 30553056 with PIA.
Ticket # 30554902 here.
and Ticket # 30546573 from me.
I've had an email from PIA Support with a link to a new alpha build of PIA. >> Sadly I get the folllowing error message from Firefox (Safari gives a shorter
version).
This XML file does not appear to have any style information associated with >> it. The document tree is shown below.
<Error>
<Code>AccessDenied</Code>
<Message>Access Denied</Message>
<RequestId>MRCF70KSW6WC8EGB</RequestId>
<HostId>
MGX41Ie7Cpg7K9rRmh4tB83cukskEwqolPzzRCYp9RxFaC44h30TuKxTVsXur5yvGNeLyBf3XQWS1
ioYHUrlh2X8qxr1RxoMQWkVadsuSxE=
</HostId>
</Error>
I've reported the issue back to PIA Support.
Update:
I've received another email (actually sent earlier) with a link that
actually works. It downloads pia-macos-3.7-alpha.1-08401.zip and on
unzipping and installing the alpha app it appears to work now.
I've now responded more favourably!
On 25 Sep 2025 at 07:53:34 BST, Alan B wrote:
On 24 Sep 2025 at 13:30:45 GMT+1, "RJH" <patchmoney@gmx.com> wrote:
On 24 Sep 2025 at 10:02:46 BST, Alan B wrote:
Sn!pe <snipeco.2@gmail.com> wrote:
RJH <patchmoney@gmx.com> wrote:
[...]
+1 - works here too.In my case, after closing the VPN: in Settings/Network/WiFi/ >>>>>>>>> [connected network] Details/TCP-IP/DHCP lease - Renew DHCP Lease >>>>>>>>> restores a working connection.
Yes that's a good solution and doesn't involve messing with the CLI :) >>>>>>>>
I hope that PIA will fix this pronto, it's a PITA.
I've opened Ticket # 30553056 with PIA.
Ticket # 30554902 here.
and Ticket # 30546573 from me.
I've had an email from PIA Support with a link to a new alpha build of PIA. >>> Sadly I get the folllowing error message from Firefox (Safari gives a shorter
version).
This XML file does not appear to have any style information associated with >>> it. The document tree is shown below.
<Error>
<Code>AccessDenied</Code>
<Message>Access Denied</Message>
<RequestId>MRCF70KSW6WC8EGB</RequestId>
<HostId>
MGX41Ie7Cpg7K9rRmh4tB83cukskEwqolPzzRCYp9RxFaC44h30TuKxTVsXur5yvGNeLyBf3XQWS1
ioYHUrlh2X8qxr1RxoMQWkVadsuSxE=
</HostId>
</Error>
I've reported the issue back to PIA Support.
Update:
I've received another email (actually sent earlier) with a link that
actually works. It downloads pia-macos-3.7-alpha.1-08401.zip and on
unzipping and installing the alpha app it appears to work now.
I've now responded more favourably!
Much the same here. The original link had a full stop at the end of the zip extension. Removing that and it worked. And from a brief test, all seems fine.
On 2025-09-25, RJH <patchmoney@gmx.com> wrote:[...]
On 25 Sep 2025 at 07:53:34 BST, Alan B wrote:
Update:
I've received another email (actually sent earlier) with a link that
actually works. It downloads pia-macos-3.7-alpha.1-08401.zip and
on unzipping and installing the alpha app it appears to work now.
I've now responded more favourably!
Much the same here. The original link had a full stop at the end of the
zip extension. Removing that and it worked. And from a brief test, all seems fine.
Missed the full stop - should have gone to Sp........
Anyway, as you say, all seems fine now :)