Now this is something new...
DNS records where only required to allow traffic to ampr hosts from the internet through the ampr gateway. It had nothig to do with the ability to establish tunnel links or to register and connect a gateway.
@K7MDI
Your old entry, 44.63.63.128/26 via 168.103.47.81 still shows up
in the RIP data.
You need to de-associate your subnet from that gateway, and
associate it with your new gateway via the portal.
Login and go to Gateways->Manage and click edit on the entry
for 168.103.47.81 and remove 44.63.63.128/26 from it.
Then click again on Manage, select edit on your new gateway and
add the network from the drop down list (it should be visible
after removing from the first one).
And then wait a while...
Marius, YO2LOJ
Good Morning,
Have you gotten DNS entries added for your IPs yet?
If not, feel free to reach out to your coordinator, or you can reply back directly to me and I will get those added. DNS Records are required to allow your IPIP tunnel to connect.
Please let me know if you have any questions or if I can help.
Stay well!
_________________________
Ronnie Montgomery (WØrdm)
On Tue, May 31, 2022 at 11:58 PM MD via 44net <44net@mailman.ampr.org> wrote:
Chris
For our routing we now have our Static IP address from T-Mobile 5G.
It is: 162.191.104.176
We have tried the Unbuntu Linux info but have had no success for
the IPIP tunnel.
Do you need any further information as the encap(date).txt does not show
our allocation: 44.63.63.128/26 in the encap file?
Previous Email ...
C
44.63.63.128 /26 might be non listed.
We are not up yet.
M
K7MDI
_______________________________________________
44net mailing list -- 44net@mailman.ampr.org
To unsubscribe send an email to 44net-leave@mailman.ampr.org
_______________________________________________ 44net mailing list -- 44net@mailman.ampr.org To unsubscribe send an email to 44net-leave@mailman.ampr.org