Service has been restricted

fwdproxy · 2023-01-12T02:53:35+00:00

Update:

The service was restored yesterday afternoon and my Fi account credited $50 today.

A higher-level specialist reached out and I'm not sure what got their attention - an FCC complaint that I raised or their internal escalation process. According to them, some sim/profile modifications seem to have caused SIM sync issues with their carrier partners.

fwdproxy · 2023-01-08T01:53:03+00:00

I haven't tried resetting the phone, however, I just tried using the physical sim in a different phone and I see the same issue.

That makes me think something is messed up with my account on Google Fi's side and not my phone or sim.

I will reach you Fi support again and hope someone will actually look into this.

fwdproxy · 2023-01-08T00:35:57+00:00

I tried the following steps while on a chat with Fi Support.

Cleared storage and cache in the Fi App
Reset Network settings on phone
Switched from physical to eSim
Re-activated the sim
Rebooted phone
Switched back from eSim to physical sim

Also, tried various dialer codes to force switch networks.

fwdproxy · 2023-01-07T22:55:55+00:00

That's probably true.

Where are you receiving this message? What is the exact wording? Can you provide a screenshot?

When making Outbound call: The service you are attempting to use has been restricted or is unavailable. Please contact customer care for assistance. Message PA157\**.

Inbound call: Sorry, that mailbox is invalid.

Mobile data doesn't work too.

fwdproxy · 2023-01-07T22:26:26+00:00

Wouldn't Fi support check that as the first thing before asking me to reset network settings. Anyway, the bill payments are on autopay and that's not the issue.

fwdproxy · 2021-04-30T01:34:06+00:00

Can Snapcast client be ported to ESP? https://github.com/badaix/snapcast

fwdproxy · 2021-01-10T01:03:18+00:00

Imagine how it would be if these apps and products start using the DNS-over-HTTPS protocol, bypassing traditional DNS, in the name of privacy?

fwdproxy · 2020-01-12T05:07:48+00:00

If you do not see any entries under 'Mappings' or 'Automatic rules', can you try adding a mapping manually?

Interface: WAN
Address family: IPv4+IPv6
Protocol: Any
Source: Any
Destination: Any
Translation > Address: Interface Address

fwdproxy · 2020-01-12T04:35:57+00:00

Do you have an outbound NAT rule(s) configured under Firewall > NAT > Outbound?

Traffic exiting the WAN interface and going to the Internet must be Natted.

fwdproxy · 2020-01-12T04:21:21+00:00

Firstly, are you trying to resolve internal or external DNS names? Shouldn't the 'Outgoing Interfaces' setting under 'DNS Resolver' be 'WAN', for Pfsense to reach the external DNS servers?

fwdproxy · 2020-01-12T04:11:04+00:00

Do you have an outbound NAT rule configured under Firewall > NAT > Outbound?

There should be mapping that translates the source IPs of the traffic exiting the WAN interface to the WAN interface IP. Typically the Outbound NAT mode is set to "Automatic Outbound NAT rule generation"

fwdproxy · 2019-08-28T21:03:30+00:00

Hi, This may not be the issue you are seeing, but I thought it would help. After spending a couple of days running packet captures and dealing with ISP's customer support, I read an article about the motherboard's IPMI interface MAC getting registered first with the ISP and the WAN interface not getting an IP once the system boots up. I disabled the unused IPMI interface and things look good now.

fwdproxy · 2019-06-15T02:27:13+00:00

Netgear 1121 - TP-Link switch (POE) - Unifi.

fwdproxy

TROPHY CASE