I checked a couple of them and all the ones I checked have invalid configuration...
(DNS name configured as gateway address does not exist or returns RFC1918 address)
Rob
On 11/29/22 22:17, Charles Hargrove via 44net wrote:
Last week I submitted the below list to the database
and technical managers to
point out a major discrepancy between the portal's gateways entries and what is
actually being sent out in the encap.txt file or broadcast. This would explain
why certain subnets are having trouble being routed. If a system does not get
the route data then the connection goes nowhere. After some thought and some
input from a few, I suspect that the subnets that are dropped are actually
using a dynamic address FQDN in their portal entry as opposed to a truly
numeric dotted quad address. Maybe the stations listed below can verify my
guess.