Raspberry Pi could not connect to Internet on FIOS but could reach all local nodes and DNS

I have a Raspberry Pi network monitor that lost access to the Internet. DNS worked but everything else was blocked. Local network connectivity worked fine in both directions. It took me a couple of hours to identify the FIOS firewall issue.

What Didn't Work

  1. Raspberry Pi could not curl or ping Internet services.
  2. Raspberry Pi could not get updates
  3. O/S re-installation

What Worked

  1. Other machines on the local network could retrieve resources from the Internet via browser and command line.
  2. Other machines on the local network could ssh into the Raspberry Pi.
  3. Other machines on the local network could ping the Raspberry Pi.
  4. Raspberry Pi could ping the local machine.
  5. Raspberry Pi initiated DNS lookup worked
  6. Raspberry Pi traceroute to 8.8.8.8 or www.google.com would timeout
  7. Raspberry Pi /etc/dhcpcd.conf was unchanged.
  8. Raspberry Pi /etc/resolv.conf had the two needed rows in it

Other Info

  1. This ran for two years without issue.
  2. Raspberry Pi IP issued via DHCP.  Other DHCP devices had no issues.
  3. I ran an O/S update around the time it lost internet access.

My Network

  1. Verizon Fios Router/Firewall
  2. Apple Airport Extreme - bridge mode
  3. Raspberry Pi 
  4. A PC and a Mac

The Fix

My FIOS router had blocked the Raspberry Pi Internet Access.  You can see it in the devices list.

Log into the FIOS router web admin interface and look at Devices. 

You can Enable the device using the Device Options dropdown list

Revision History

Created 2022 11

Comments

Post a Comment

Popular posts from this blog

Understanding your WSL2 RAM and swap - Changing the default 50%-25%

Image
The Windows Subsystem for Linux operates as a virtual machine that can dynamically grow the amount of RAM to a maximum set at startup time.  Microsoft sets a default maximum RAM available to 50% of the physical memory and a swap-space that is 1/4 of the maximum WSL RAM.  You can scale those numbers up or down to allocate more or less RAM to the Linux instance. The first drawing shows the default WSL memory and swap space sizing. The images below show a developer machine that is running a dev environment in WSL2 and Docker Desktop.  Docker Desktop has two of its own WSL modules that need to be accounted for.  You can see that the memory would actually be oversubscribed, 3 x 50% if every VM used its maximum memory.  The actual amount of memory used is significantly smaller allowing every piece to fit. Click to Enlarge The second drawing shows the memory allocation on my 64GB laptop. WSL Linux defaults to a maximum RAM size of 5
Read more

Installing the RNDIS driver on Windows 11 to use USB Raspberry Pi as network attached

Image
I do a lot of my development and configuration via ssh into my Raspberry Pi Zero over the RNDIS connection. Some models of the Raspberry PIs can be configured with  gadget drivers  that let the Raspberry pi emulate different devices when plugged into computers via USB. My favorite gadget  is the network profile that makes a Raspberry Pi look like an RNDIS-attached network device.  All types of network services travel over an RNDIS device without knowing it is a USB hardware connection. A Raspberry Pi shows up as a Remote NDIS (RNDIS) device when you plug the Pi into a PC or Mac via a USB cable. The gadget  in the Windows Device Manager picture shows this RNDIS Gadget connectivity between a Windows machine and a Raspberry Pi. The Problem Windows 11 and Windows 10 no longer auto-installs the RNDIS driver that makes magic happen. Windows recognizes that the Raspberry Pi is some type of generic USB COM device. Manually running W indows Update  or  Update Driver  does  not  install the RNDI
Read more

DNS for Azure Point to Site (P2S) VPN - getting the internal IPs

Image
I wanted to access all my Azure resources without making any of them visible to the Internet.   The easiest give my local machine access to everything on my Azure Virtual Network (VNET) was to connect to it over VPN. It turns out creating Azure VPN gateways and connecting to Azure VPN endpoints is easy.  There are some subtleties in getting DNS name resolution to work that can confuse when first starting out. Setting the Stage There are a few ways to get to Azure endpoints and resources that are blocked from the internet.  We can  Create a Point-to-Site connection from our local machines to Azure Network Gateways Create a Site-to-Site network connection from our local networks to Azure Network Gateways. Use Bastion Hosts Use Cloud Shell Leave everything open to the internet. I chose a Point-to-Site (P2S) VPN connection that connects from my laptop to a VNet Gateway.  That joins my laptop
Read more