David; On Thu, 2019-01-03 at 23:09 +0000, David Pechon via 44Net wrote: Here's what you *may* want to consider: - 44-net IP mappings change very frequently and it's very difficult to keep an eye on which ones do - you don't have a static IP - no-ip services will help keep you linked easier - consider a Pi for a post router to your Cisco When I had a T1 line back in the day, I had a 2600 series router off my smartjack. While I had a 44-net IP and ran IPIP, it didn't "route" for me. My xNOS was my 44-net router at the time as it was anyway so I set my 2600 up as a node off of xNOS. I didn't have to worry about hourly route changes on 44/8 or anything else. NOS handled all that for me at the time - and there was no portal back then. You may want to consider something like an RPi unit to act as your 44/8 post router system and use it as I did xNOS back then. The ram in your cisco will remain a LOT cleaner as well. The RPi can also handle a dyndns software to keep your IP updated in the portal. -- I love Tinder. It used to be I could get rejected by about a dozen people a night. Thanks to modern technology I can be rejected by hundreds. It's so much more efficient! ----- 73 de Brian N1URO IPv6 Certified n1uro-dawt-ampr-dawt-org uronode-dawt-n1uro-dawt-com

I'd think about what Brian wrote about using a Raspberry Pi. But if you must; you can look at this script by Antonio, AH6BW & Jason, KY9J that generates router tunnel configurations. Be aware that the UCSD address is now: 169.228.38.84 https://www.qsl.net/kb9mwr/wapr/tcpip/amprroutes.pl.txt Steve, KB9MWR On Thu, Jan 3, 2019 at 5:13 PM David Pechon via 44Net <44net(a)mailman.ampr.org> wrote: