Hello, 44Net / AMPRNet Community!
I’m pleased to share that on Wednesday, April 3rd, at approximately 9am PDT / 4pm UTC, Chris G1FEF will release a new 44Net portal. We’ll give you a heads-up once we make the switch; expect some downtime starting at about 1am PDT / 8am UTC until launch time.
Here are the features the new portal will include:
* A new ticketing system to improve support response time * DNS management * Modern secure framework * Improved UI/UX * Capability to facilitate a pool of administrators
Of course, the portal upgrade will not change your address space assignment.
Also, along with any new launch – though we have done thorough testing with the TAC and staff– we expect that folks will find some bugs. We appreciate your patience should you find them, as well as your feedback.
If you have any questions in the meantime, please ask here or direct them to newportal@ardc.net.
73, Rosy KJ7RYV
It states below it will not change the address assignments but where are our address assignments in the new portal??
Thank you, Patrick
-----Original Message----- From: Rosy Schechter - KJ7RYV via 44net 44net@mailman.ampr.org Sent: Thursday, March 28, 2024 14:09 To: Amprnet 44 Net 44net@mailman.ampr.org Cc: newportal@ardc.net Subject: [44net] New 44Net Portal coming 4/3!
Hello, 44Net / AMPRNet Community!
I’m pleased to share that on Wednesday, April 3rd, at approximately 9am PDT / 4pm UTC, Chris G1FEF will release a new 44Net portal. We’ll give you a heads-up once we make the switch; expect some downtime starting at about 1am PDT / 8am UTC until launch time.
Here are the features the new portal will include:
* A new ticketing system to improve support response time * DNS management * Modern secure framework * Improved UI/UX * Capability to facilitate a pool of administrators
Of course, the portal upgrade will not change your address space assignment.
Also, along with any new launch – though we have done thorough testing with the TAC and staff– we expect that folks will find some bugs. We appreciate your patience should you find them, as well as your feedback.
If you have any questions in the meantime, please ask here or direct them to newportal@ardc.net.
73, Rosy KJ7RYV
-- Rosy Schechter - KJ7RYV Executive Director Amateur Radio Digital Communications (ARDC) ardc.net _______________________________________________ 44net mailing list -- 44net@mailman.ampr.org To unsubscribe send an email to 44net-leave@mailman.ampr.org
On Wed, Apr 3, 2024 at 5:26 PM Patrick Thompson via 44net 44net@mailman.ampr.org wrote:
It states below it will not change the address assignments but where are our address assignments in the new portal??
Logging into the portal, I saw a notification about a new ticket that had been created related to that; I assume that's for importing the allocation information into the new portal, but I don't have permissions to view the ticket.
- Dan C.
Thank you, Patrick
-----Original Message----- From: Rosy Schechter - KJ7RYV via 44net 44net@mailman.ampr.org Sent: Thursday, March 28, 2024 14:09 To: Amprnet 44 Net 44net@mailman.ampr.org Cc: newportal@ardc.net Subject: [44net] New 44Net Portal coming 4/3!
Hello, 44Net / AMPRNet Community!
I’m pleased to share that on Wednesday, April 3rd, at approximately 9am PDT / 4pm UTC, Chris G1FEF will release a new 44Net portal. We’ll give you a heads-up once we make the switch; expect some downtime starting at about 1am PDT / 8am UTC until launch time.
Here are the features the new portal will include:
- A new ticketing system to improve support response time
- DNS management
- Modern secure framework
- Improved UI/UX
- Capability to facilitate a pool of administrators
Of course, the portal upgrade will not change your address space assignment.
Also, along with any new launch – though we have done thorough testing with the TAC and staff– we expect that folks will find some bugs. We appreciate your patience should you find them, as well as your feedback.
If you have any questions in the meantime, please ask here or direct them to newportal@ardc.net.
73, Rosy KJ7RYV
-- Rosy Schechter - KJ7RYV Executive Director Amateur Radio Digital Communications (ARDC) ardc.net _______________________________________________ 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
I saw two of those notifications about subdomains but as you stated, no rights to see the ticket.
Thank you, Patrick
-----Original Message----- From: Dan Cross crossd@gmail.com Sent: Wednesday, April 3, 2024 16:44 To: Patrick Thompson patrick@pwthompson.net Cc: Rosy Schechter - KJ7RYV rosy@ardc.net; Amprnet 44 Net 44net@mailman.ampr.org Subject: Re: [44net] Re: New 44Net Portal coming 4/3!
On Wed, Apr 3, 2024 at 5:26 PM Patrick Thompson via 44net 44net@mailman.ampr.org wrote:
It states below it will not change the address assignments but where are our address assignments in the new portal??
Logging into the portal, I saw a notification about a new ticket that had been created related to that; I assume that's for importing the allocation information into the new portal, but I don't have permissions to view the ticket.
- Dan C.
Thank you, Patrick
-----Original Message----- From: Rosy Schechter - KJ7RYV via 44net 44net@mailman.ampr.org Sent: Thursday, March 28, 2024 14:09 To: Amprnet 44 Net 44net@mailman.ampr.org Cc: newportal@ardc.net Subject: [44net] New 44Net Portal coming 4/3!
Hello, 44Net / AMPRNet Community!
I’m pleased to share that on Wednesday, April 3rd, at approximately 9am PDT / 4pm UTC, Chris G1FEF will release a new 44Net portal. We’ll give you a heads-up once we make the switch; expect some downtime starting at about 1am PDT / 8am UTC until launch time.
Here are the features the new portal will include:
- A new ticketing system to improve support response time
- DNS management
- Modern secure framework
- Improved UI/UX
- Capability to facilitate a pool of administrators
Of course, the portal upgrade will not change your address space assignment.
Also, along with any new launch – though we have done thorough testing with the TAC and staff– we expect that folks will find some bugs. We appreciate your patience should you find them, as well as your feedback.
If you have any questions in the meantime, please ask here or direct them to newportal@ardc.net.
73, Rosy KJ7RYV
-- Rosy Schechter - KJ7RYV Executive Director Amateur Radio Digital Communications (ARDC) ardc.net _______________________________________________ 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
Same experience here, no network tab as well...
Mark - K9MEV
On 4/3/2024 4:58 PM, Patrick Thompson via 44net wrote:
I saw two of those notifications about subdomains but as you stated, no rights to see the ticket.
Thank you, Patrick
-----Original Message----- From: Dan Cross crossd@gmail.com Sent: Wednesday, April 3, 2024 16:44 To: Patrick Thompson patrick@pwthompson.net Cc: Rosy Schechter - KJ7RYV rosy@ardc.net; Amprnet 44 Net 44net@mailman.ampr.org Subject: Re: [44net] Re: New 44Net Portal coming 4/3!
On Wed, Apr 3, 2024 at 5:26 PM Patrick Thompson via 44net 44net@mailman.ampr.org wrote:
It states below it will not change the address assignments but where are our address assignments in the new portal??
Logging into the portal, I saw a notification about a new ticket that had been created related to that; I assume that's for importing the allocation information into the new portal, but I don't have permissions to view the ticket.
- Dan C.Thank you, Patrick
-----Original Message----- From: Rosy Schechter - KJ7RYV via 44net 44net@mailman.ampr.org Sent: Thursday, March 28, 2024 14:09 To: Amprnet 44 Net 44net@mailman.ampr.org Cc: newportal@ardc.net Subject: [44net] New 44Net Portal coming 4/3!
Hello, 44Net / AMPRNet Community!
I’m pleased to share that on Wednesday, April 3rd, at approximately 9am PDT / 4pm UTC, Chris G1FEF will release a new 44Net portal. We’ll give you a heads-up once we make the switch; expect some downtime starting at about 1am PDT / 8am UTC until launch time.
Here are the features the new portal will include:
- A new ticketing system to improve support response time
- DNS management
- Modern secure framework
- Improved UI/UX
- Capability to facilitate a pool of administrators
Of course, the portal upgrade will not change your address space assignment.
Also, along with any new launch – though we have done thorough testing with the TAC and staff– we expect that folks will find some bugs. We appreciate your patience should you find them, as well as your feedback.
If you have any questions in the meantime, please ask here or direct them to newportal@ardc.net.
73, Rosy KJ7RYV
-- Rosy Schechter - KJ7RYV Executive Director Amateur Radio Digital Communications (ARDC) ardc.net _______________________________________________ 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
44net mailing list -- 44net@mailman.ampr.org To unsubscribe send an email to 44net-leave@mailman.ampr.org
I've received the same, when trying to log-in I got an eULA that I can't actually click to accept, has anyone else had the same issue?
Nathan Brookfield | VK2NAB Director
NAB Investment Holdings Pty Ltd T/A Managed Networks W: http://nabih.com.au | E: Nathan.Brookfield@nabih.com.au | P: 0412 266 008
-----Original Message----- From: Patrick Thompson via 44net 44net@mailman.ampr.org Sent: Thursday, April 4, 2024 8:58 AM To: Dan Cross crossd@gmail.com Cc: Amprnet 44 Net 44net@mailman.ampr.org Subject: [44net] Re: New 44Net Portal coming 4/3!
I saw two of those notifications about subdomains but as you stated, no rights to see the ticket.
Thank you, Patrick
-----Original Message----- From: Dan Cross crossd@gmail.com Sent: Wednesday, April 3, 2024 16:44 To: Patrick Thompson patrick@pwthompson.net Cc: Rosy Schechter - KJ7RYV rosy@ardc.net; Amprnet 44 Net 44net@mailman.ampr.org Subject: Re: [44net] Re: New 44Net Portal coming 4/3!
On Wed, Apr 3, 2024 at 5:26 PM Patrick Thompson via 44net 44net@mailman.ampr.org wrote:
It states below it will not change the address assignments but where are our address assignments in the new portal??
Logging into the portal, I saw a notification about a new ticket that had been created related to that; I assume that's for importing the allocation information into the new portal, but I don't have permissions to view the ticket.
- Dan C.
Thank you, Patrick
-----Original Message----- From: Rosy Schechter - KJ7RYV via 44net 44net@mailman.ampr.org Sent: Thursday, March 28, 2024 14:09 To: Amprnet 44 Net 44net@mailman.ampr.org Cc: newportal@ardc.net Subject: [44net] New 44Net Portal coming 4/3!
Hello, 44Net / AMPRNet Community!
I’m pleased to share that on Wednesday, April 3rd, at approximately 9am PDT / 4pm UTC, Chris G1FEF will release a new 44Net portal. We’ll give you a heads-up once we make the switch; expect some downtime starting at about 1am PDT / 8am UTC until launch time.
Here are the features the new portal will include:
- A new ticketing system to improve support response time
- DNS management
- Modern secure framework
- Improved UI/UX
- Capability to facilitate a pool of administrators
Of course, the portal upgrade will not change your address space assignment.
Also, along with any new launch – though we have done thorough testing with the TAC and staff– we expect that folks will find some bugs. We appreciate your patience should you find them, as well as your feedback.
If you have any questions in the meantime, please ask here or direct them to newportal@ardc.net.
73, Rosy KJ7RYV
-- Rosy Schechter - KJ7RYV Executive Director Amateur Radio Digital Communications (ARDC) ardc.net _______________________________________________ 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
_______________________________________________ 44net mailing list -- 44net@mailman.ampr.org To unsubscribe send an email to 44net-leave@mailman.ampr.org
You have to read the EULA. The page forces you to scroll down to the bottom of the EULA as a way to encourage you to read it.
Charles Holliday KG5IRU
On Wed, Apr 3, 2024 at 5:19 PM David McAnally via 44net < 44net@mailman.ampr.org> wrote:
On Wed, Apr 3, 2024 at 5:15 PM Nathan Brookfield via 44net < 44net@mailman.ampr.org> wrote:
I've received the same, when trying to log-in I got an eULA that I can't actually click to accept, has anyone else had the same issue?
Yes.
David McAnally WD5M _______________________________________________ 44net mailing list -- 44net@mailman.ampr.org To unsubscribe send an email to 44net-leave@mailman.ampr.org
This didn’t make a difference, in Chrome and Firefox scrolling to the bottom didn’t unlock the elements to select.
Nathan Brookfield | VK2NAB Director
NAB Investment Holdings Pty Ltd T/A Managed Networks W: http://nabih.com.auhttp://nabih.com.au/ | E: Nathan.Brookfield@nabih.com.aumailto:Nathan.Brookfield@nabih.com.au | P: 0412 266 008
From: Charles Holliday kg5iru@gmail.com Sent: Thursday, April 4, 2024 9:21 AM To: David McAnally david.mcanally@gmail.com Cc: Amprnet 44 Net 44net@mailman.ampr.org; Dan Cross crossd@gmail.com; Nathan Brookfield Nathan.Brookfield@nabih.com.au; Patrick Thompson patrick@pwthompson.net Subject: Re: [44net] Re: New 44Net Portal coming 4/3!
You have to read the EULA. The page forces you to scroll down to the bottom of the EULA as a way to encourage you to read it.
Charles Holliday KG5IRU
On Wed, Apr 3, 2024 at 5:19 PM David McAnally via 44net <44net@mailman.ampr.orgmailto:44net@mailman.ampr.org> wrote: On Wed, Apr 3, 2024 at 5:15 PM Nathan Brookfield via 44net <44net@mailman.ampr.orgmailto:44net@mailman.ampr.org> wrote: I've received the same, when trying to log-in I got an eULA that I can't actually click to accept, has anyone else had the same issue?
Yes.
David McAnally WD5M _______________________________________________ 44net mailing list -- 44net@mailman.ampr.orgmailto:44net@mailman.ampr.org To unsubscribe send an email to 44net-leave@mailman.ampr.orgmailto:44net-leave@mailman.ampr.org
If you're doing it from mobile, set the tab to Desktop Mode. I had to do that to get it to load.
Get Outlook for Androidhttps://aka.ms/AAb9ysg ________________________________ From: Nathan Brookfield via 44net 44net@mailman.ampr.org Sent: Wednesday, April 3, 2024 5:24:12 PM To: Charles Holliday kg5iru@gmail.com; David McAnally david.mcanally@gmail.com Cc: Amprnet 44 Net 44net@mailman.ampr.org; Dan Cross crossd@gmail.com; Patrick Thompson patrick@pwthompson.net Subject: [44net] Re: New 44Net Portal coming 4/3!
This didn’t make a difference, in Chrome and Firefox scrolling to the bottom didn’t unlock the elements to select.
Nathan Brookfield | VK2NAB
Director
NAB Investment Holdings Pty Ltd T/A Managed Networks
W: http://nabih.com.auhttp://nabih.com.au/ | E: Nathan.Brookfield@nabih.com.aumailto:Nathan.Brookfield@nabih.com.au | P: 0412 266 008
From: Charles Holliday kg5iru@gmail.com Sent: Thursday, April 4, 2024 9:21 AM To: David McAnally david.mcanally@gmail.com Cc: Amprnet 44 Net 44net@mailman.ampr.org; Dan Cross crossd@gmail.com; Nathan Brookfield Nathan.Brookfield@nabih.com.au; Patrick Thompson patrick@pwthompson.net Subject: Re: [44net] Re: New 44Net Portal coming 4/3!
You have to read the EULA. The page forces you to scroll down to the bottom of the EULA as a way to encourage you to read it.
Charles Holliday
KG5IRU
On Wed, Apr 3, 2024 at 5:19 PM David McAnally via 44net <44net@mailman.ampr.orgmailto:44net@mailman.ampr.org> wrote:
On Wed, Apr 3, 2024 at 5:15 PM Nathan Brookfield via 44net <44net@mailman.ampr.orgmailto:44net@mailman.ampr.org> wrote:
I've received the same, when trying to log-in I got an eULA that I can't actually click to accept, has anyone else had the same issue?
Yes.
David McAnally
WD5M
_______________________________________________ 44net mailing list -- 44net@mailman.ampr.orgmailto:44net@mailman.ampr.org To unsubscribe send an email to 44net-leave@mailman.ampr.orgmailto:44net-leave@mailman.ampr.org
Nope, it didn't work, scrolling, different browsers, etc. Firefox console indicated they are using a feature that is probably not going to work well. Looks like they switched back to the old website. More debugging I expect.
David McAnally WD5M
On Wed, Apr 3, 2024 at 5:25 PM Jeff Parrish-Personal jeff@kb9gxk.net wrote:
If you're doing it from mobile, set the tab to Desktop Mode. I had to do that to get it to load.
Get Outlook for Android https://aka.ms/AAb9ysg
*From:* Nathan Brookfield via 44net 44net@mailman.ampr.org *Sent:* Wednesday, April 3, 2024 5:24:12 PM *To:* Charles Holliday kg5iru@gmail.com; David McAnally < david.mcanally@gmail.com> *Cc:* Amprnet 44 Net 44net@mailman.ampr.org; Dan Cross crossd@gmail.com; Patrick Thompson patrick@pwthompson.net *Subject:* [44net] Re: New 44Net Portal coming 4/3!
This didn’t make a difference, in Chrome and Firefox scrolling to the bottom didn’t unlock the elements to select.
Nathan Brookfield | VK2NAB
Director
NAB Investment Holdings Pty Ltd T/A Managed Networks
*W*: http://nabih.com.au | *E*: Nathan.Brookfield@nabih.com.au | *P*: 0412 266 008
*From:* Charles Holliday kg5iru@gmail.com *Sent:* Thursday, April 4, 2024 9:21 AM *To:* David McAnally david.mcanally@gmail.com *Cc:* Amprnet 44 Net 44net@mailman.ampr.org; Dan Cross crossd@gmail.com; Nathan Brookfield Nathan.Brookfield@nabih.com.au; Patrick Thompson < patrick@pwthompson.net> *Subject:* Re: [44net] Re: New 44Net Portal coming 4/3!
You have to read the EULA. The page forces you to scroll down to the bottom of the EULA as a way to encourage you to read it.
Charles Holliday
KG5IRU
On Wed, Apr 3, 2024 at 5:19 PM David McAnally via 44net < 44net@mailman.ampr.org> wrote:
On Wed, Apr 3, 2024 at 5:15 PM Nathan Brookfield via 44net < 44net@mailman.ampr.org> wrote:
I've received the same, when trying to log-in I got an eULA that I can't actually click to accept, has anyone else had the same issue?
Yes.
David McAnally
WD5M
44net mailing list -- 44net@mailman.ampr.org To unsubscribe send an email to 44net-leave@mailman.ampr.org
I’m glad I wasn’t the only one having this issue, I tried from Windows on my desktop with multiple browsers and then my mobile unsuccessfully.
I’ll rest easy knowing today isn’t the day I’m losing my mind :D
Nathan Brookfield | VK2NAB Director
NAB Investment Holdings Pty Ltd T/A Managed Networks W: http://nabih.com.auhttp://nabih.com.au/ | E: Nathan.Brookfield@nabih.com.aumailto:Nathan.Brookfield@nabih.com.au | P: 0412 266 008
From: David McAnally david.mcanally@gmail.com Sent: Thursday, April 4, 2024 9:29 AM To: Jeff Parrish-Personal jeff@kb9gxk.net Cc: Nathan Brookfield Nathan.Brookfield@nabih.com.au; Charles Holliday kg5iru@gmail.com; Amprnet 44 Net 44net@mailman.ampr.org; Dan Cross crossd@gmail.com; Patrick Thompson patrick@pwthompson.net Subject: Re: [44net] Re: New 44Net Portal coming 4/3!
Nope, it didn't work, scrolling, different browsers, etc. Firefox console indicated they are using a feature that is probably not going to work well. Looks like they switched back to the old website. More debugging I expect.
David McAnally WD5M
On Wed, Apr 3, 2024 at 5:25 PM Jeff Parrish-Personal <jeff@kb9gxk.netmailto:jeff@kb9gxk.net> wrote: If you're doing it from mobile, set the tab to Desktop Mode. I had to do that to get it to load.
Get Outlook for Androidhttps://aka.ms/AAb9ysg ________________________________ From: Nathan Brookfield via 44net <44net@mailman.ampr.orgmailto:44net@mailman.ampr.org> Sent: Wednesday, April 3, 2024 5:24:12 PM To: Charles Holliday <kg5iru@gmail.commailto:kg5iru@gmail.com>; David McAnally <david.mcanally@gmail.commailto:david.mcanally@gmail.com> Cc: Amprnet 44 Net <44net@mailman.ampr.orgmailto:44net@mailman.ampr.org>; Dan Cross <crossd@gmail.commailto:crossd@gmail.com>; Patrick Thompson <patrick@pwthompson.netmailto:patrick@pwthompson.net> Subject: [44net] Re: New 44Net Portal coming 4/3!
This didn’t make a difference, in Chrome and Firefox scrolling to the bottom didn’t unlock the elements to select.
Nathan Brookfield | VK2NAB
Director
NAB Investment Holdings Pty Ltd T/A Managed Networks
W: http://nabih.com.auhttp://nabih.com.au/ | E: Nathan.Brookfield@nabih.com.aumailto:Nathan.Brookfield@nabih.com.au | P: 0412 266 008
From: Charles Holliday <kg5iru@gmail.commailto:kg5iru@gmail.com> Sent: Thursday, April 4, 2024 9:21 AM To: David McAnally <david.mcanally@gmail.commailto:david.mcanally@gmail.com> Cc: Amprnet 44 Net <44net@mailman.ampr.orgmailto:44net@mailman.ampr.org>; Dan Cross <crossd@gmail.commailto:crossd@gmail.com>; Nathan Brookfield <Nathan.Brookfield@nabih.com.aumailto:Nathan.Brookfield@nabih.com.au>; Patrick Thompson <patrick@pwthompson.netmailto:patrick@pwthompson.net> Subject: Re: [44net] Re: New 44Net Portal coming 4/3!
You have to read the EULA. The page forces you to scroll down to the bottom of the EULA as a way to encourage you to read it.
Charles Holliday
KG5IRU
On Wed, Apr 3, 2024 at 5:19 PM David McAnally via 44net <44net@mailman.ampr.orgmailto:44net@mailman.ampr.org> wrote:
On Wed, Apr 3, 2024 at 5:15 PM Nathan Brookfield via 44net <44net@mailman.ampr.orgmailto:44net@mailman.ampr.org> wrote:
I've received the same, when trying to log-in I got an eULA that I can't actually click to accept, has anyone else had the same issue?
Yes.
David McAnally
WD5M
_______________________________________________ 44net mailing list -- 44net@mailman.ampr.orgmailto:44net@mailman.ampr.org To unsubscribe send an email to 44net-leave@mailman.ampr.orgmailto:44net-leave@mailman.ampr.org
Hey folks -
Thanks for chiming in about these bugs. They are some of the main ones that we are working on fixing.
We'll post more information as soon as we have it. Thank you for your patience!
Rosy
Rosy Schechter - KJ7RYV Executive Director Amateur Radio Digital Communications (ARDC) ardc.net
On 4/3/24 3:36 PM, Nathan Brookfield via 44net wrote:
I’m glad I wasn’t the only one having this issue, I tried from Windows on my desktop with multiple browsers and then my mobile unsuccessfully.
I’ll rest easy knowing today isn’t the day I’m losing my mind :D
Nathan Brookfield | VK2NAB
Director
NAB Investment Holdings Pty Ltd T/A Managed Networks
*W*: http://nabih.com.au http://nabih.com.au/ | *E*: Nathan.Brookfield@nabih.com.au mailto:Nathan.Brookfield@nabih.com.au | *P*: 0412 266 008
*From:*David McAnally david.mcanally@gmail.com *Sent:* Thursday, April 4, 2024 9:29 AM *To:* Jeff Parrish-Personal jeff@kb9gxk.net *Cc:* Nathan Brookfield Nathan.Brookfield@nabih.com.au; Charles Holliday kg5iru@gmail.com; Amprnet 44 Net 44net@mailman.ampr.org; Dan Cross crossd@gmail.com; Patrick Thompson patrick@pwthompson.net *Subject:* Re: [44net] Re: New 44Net Portal coming 4/3!
Nope, it didn't work, scrolling, different browsers, etc. Firefox console indicated they are using a feature that is probably not going to work well. Looks like they switched back to the old website. More debugging I expect.
David McAnally
WD5M
On Wed, Apr 3, 2024 at 5:25 PM Jeff Parrish-Personal <jeff@kb9gxk.net mailto:jeff@kb9gxk.net> wrote:
If you're doing it from mobile, set the tab to Desktop Mode. I had to do that to get it to load. Get Outlook for Android <https://aka.ms/AAb9ysg> ------------------------------------------------------------------------ *From:*Nathan Brookfield via 44net <44net@mailman.ampr.org <mailto:44net@mailman.ampr.org>> *Sent:* Wednesday, April 3, 2024 5:24:12 PM *To:* Charles Holliday <kg5iru@gmail.com <mailto:kg5iru@gmail.com>>; David McAnally <david.mcanally@gmail.com <mailto:david.mcanally@gmail.com>> *Cc:* Amprnet 44 Net <44net@mailman.ampr.org <mailto:44net@mailman.ampr.org>>; Dan Cross <crossd@gmail.com <mailto:crossd@gmail.com>>; Patrick Thompson <patrick@pwthompson.net <mailto:patrick@pwthompson.net>> *Subject:* [44net] Re: New 44Net Portal coming 4/3! This didn’t make a difference, in Chrome and Firefox scrolling to the bottom didn’t unlock the elements to select. Nathan Brookfield | VK2NAB Director NAB Investment Holdings Pty Ltd T/A Managed Networks *W*: http://nabih.com.au <http://nabih.com.au/> | *E*: Nathan.Brookfield@nabih.com.au <mailto:Nathan.Brookfield@nabih.com.au> | *P*: 0412 266 008 *From:*Charles Holliday <kg5iru@gmail.com <mailto:kg5iru@gmail.com>> *Sent:* Thursday, April 4, 2024 9:21 AM *To:* David McAnally <david.mcanally@gmail.com <mailto:david.mcanally@gmail.com>> *Cc:* Amprnet 44 Net <44net@mailman.ampr.org <mailto:44net@mailman.ampr.org>>; Dan Cross <crossd@gmail.com <mailto:crossd@gmail.com>>; Nathan Brookfield <Nathan.Brookfield@nabih.com.au <mailto:Nathan.Brookfield@nabih.com.au>>; Patrick Thompson <patrick@pwthompson.net <mailto:patrick@pwthompson.net>> *Subject:* Re: [44net] Re: New 44Net Portal coming 4/3! You have to read the EULA. The page forces you to scroll down to the bottom of the EULA as a way to encourage you to read it. Charles Holliday KG5IRU On Wed, Apr 3, 2024 at 5:19 PM David McAnally via 44net <44net@mailman.ampr.org <mailto:44net@mailman.ampr.org>> wrote: On Wed, Apr 3, 2024 at 5:15 PM Nathan Brookfield via 44net <44net@mailman.ampr.org <mailto:44net@mailman.ampr.org>> wrote: I've received the same, when trying to log-in I got an eULA that I can't actually click to accept, has anyone else had the same issue? Yes. David McAnally WD5M _______________________________________________ 44net mailing list -- 44net@mailman.ampr.org <mailto:44net@mailman.ampr.org> To unsubscribe send an email to 44net-leave@mailman.ampr.org <mailto:44net-leave@mailman.ampr.org>
44net mailing list -- 44net@mailman.ampr.org To unsubscribe send an email to 44net-leave@mailman.ampr.org
Worked ok on iPad pro, sounds like a good reason for a new gadget Nath :D
I also received emails about two tickets being created, but then wasn't able to view them..
It also said I needed to verify my callsign and address to raise my level of trust enough to view details of my /24, so I opened tickets for my callsigns, but the site never finished loading when I clicked the button to raise an address verification ticket.
--DG
On Thu, 4 Apr 2024 at 09:36, Nathan Brookfield via 44net < 44net@mailman.ampr.org> wrote:
I’m glad I wasn’t the only one having this issue, I tried from Windows on my desktop with multiple browsers and then my mobile unsuccessfully.
I’ll rest easy knowing today isn’t the day I’m losing my mind :D
Nathan Brookfield | VK2NAB
Director
NAB Investment Holdings Pty Ltd T/A Managed Networks
*W*: http://nabih.com.au | *E*: Nathan.Brookfield@nabih.com.au | *P*: 0412 266 008
*From:* David McAnally david.mcanally@gmail.com *Sent:* Thursday, April 4, 2024 9:29 AM *To:* Jeff Parrish-Personal jeff@kb9gxk.net *Cc:* Nathan Brookfield Nathan.Brookfield@nabih.com.au; Charles Holliday kg5iru@gmail.com; Amprnet 44 Net 44net@mailman.ampr.org; Dan Cross crossd@gmail.com; Patrick Thompson patrick@pwthompson.net *Subject:* Re: [44net] Re: New 44Net Portal coming 4/3!
Nope, it didn't work, scrolling, different browsers, etc. Firefox console indicated they are using a feature that is probably not going to work well. Looks like they switched back to the old website. More debugging I expect.
David McAnally
WD5M
On Wed, Apr 3, 2024 at 5:25 PM Jeff Parrish-Personal jeff@kb9gxk.net wrote:
If you're doing it from mobile, set the tab to Desktop Mode. I had to do that to get it to load.
Get Outlook for Android https://aka.ms/AAb9ysg
*From:* Nathan Brookfield via 44net 44net@mailman.ampr.org *Sent:* Wednesday, April 3, 2024 5:24:12 PM *To:* Charles Holliday kg5iru@gmail.com; David McAnally < david.mcanally@gmail.com> *Cc:* Amprnet 44 Net 44net@mailman.ampr.org; Dan Cross crossd@gmail.com; Patrick Thompson patrick@pwthompson.net *Subject:* [44net] Re: New 44Net Portal coming 4/3!
This didn’t make a difference, in Chrome and Firefox scrolling to the bottom didn’t unlock the elements to select.
Nathan Brookfield | VK2NAB
Director
NAB Investment Holdings Pty Ltd T/A Managed Networks
*W*: http://nabih.com.au | *E*: Nathan.Brookfield@nabih.com.au | *P*: 0412 266 008
*From:* Charles Holliday kg5iru@gmail.com *Sent:* Thursday, April 4, 2024 9:21 AM *To:* David McAnally david.mcanally@gmail.com *Cc:* Amprnet 44 Net 44net@mailman.ampr.org; Dan Cross crossd@gmail.com; Nathan Brookfield Nathan.Brookfield@nabih.com.au; Patrick Thompson < patrick@pwthompson.net> *Subject:* Re: [44net] Re: New 44Net Portal coming 4/3!
You have to read the EULA. The page forces you to scroll down to the bottom of the EULA as a way to encourage you to read it.
Charles Holliday
KG5IRU
On Wed, Apr 3, 2024 at 5:19 PM David McAnally via 44net < 44net@mailman.ampr.org> wrote:
On Wed, Apr 3, 2024 at 5:15 PM Nathan Brookfield via 44net < 44net@mailman.ampr.org> wrote:
I've received the same, when trying to log-in I got an eULA that I can't actually click to accept, has anyone else had the same issue?
Yes.
David McAnally
WD5M
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
The EULA is also outdated, referring to 44net as 44/8. Yes, I read it.
Can I suggest a review…
On Wed, 3 Apr 2024 at 23:21, Charles Holliday via 44net < 44net@mailman.ampr.org> wrote:
You have to read the EULA. The page forces you to scroll down to the bottom of the EULA as a way to encourage you to read it.
Charles Holliday KG5IRU
On Wed, Apr 3, 2024 at 5:19 PM David McAnally via 44net < 44net@mailman.ampr.org> wrote:
On Wed, Apr 3, 2024 at 5:15 PM Nathan Brookfield via 44net < 44net@mailman.ampr.org> wrote:
I've received the same, when trying to log-in I got an eULA that I can't actually click to accept, has anyone else had the same issue?
Yes.
David McAnally WD5M _______________________________________________ 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
Hi Charles,
Thank you for reading! We have a new EULA that is currently under review, which will be ready in the next month or two.
We should certainly have the EULA scrolling bug fixed by then ;)
Many thanks, Rosy
Rosy Schechter - KJ7RYV Executive Director Amateur Radio Digital Communications (ARDC) ardc.net
On 4/3/24 3:52 PM, Tom M0LTE via 44net wrote:
The EULA is also outdated, referring to 44net as 44/8. Yes, I read it.
Can I suggest a review…
On Wed, 3 Apr 2024 at 23:21, Charles Holliday via 44net <44net@mailman.ampr.org mailto:44net@mailman.ampr.org> wrote:
You have to read the EULA. The page forces you to scroll down to the bottom of the EULA as a way to encourage you to read it. Charles Holliday KG5IRU On Wed, Apr 3, 2024 at 5:19 PM David McAnally via 44net <44net@mailman.ampr.org <mailto:44net@mailman.ampr.org>> wrote: On Wed, Apr 3, 2024 at 5:15 PM Nathan Brookfield via 44net <44net@mailman.ampr.org <mailto:44net@mailman.ampr.org>> wrote: I've received the same, when trying to log-in I got an eULA that I can't actually click to accept, has anyone else had the same issue? Yes. David McAnally WD5M _______________________________________________ 44net mailing list -- 44net@mailman.ampr.org <mailto:44net@mailman.ampr.org> To unsubscribe send an email to 44net-leave@mailman.ampr.org <mailto:44net-leave@mailman.ampr.org> _______________________________________________ 44net mailing list -- 44net@mailman.ampr.org <mailto:44net@mailman.ampr.org> To unsubscribe send an email to 44net-leave@mailman.ampr.org <mailto:44net-leave@mailman.ampr.org>
44net mailing list -- 44net@mailman.ampr.org To unsubscribe send an email to 44net-leave@mailman.ampr.org
Why are we jumping through hoops to get enough points to be "trusted"? Aren't the current users and coordinators trusted enough? You can easily port over the current user list and just start from there with no issues.
On 4/3/2024 7:06 PM, Rosy Schechter - KJ7RYV via 44net wrote:
Hi Charles,
Thank you for reading! We have a new EULA that is currently under review, which will be ready in the next month or two.
We should certainly have the EULA scrolling bug fixed by then ;)
Many thanks, Rosy
Rosy Schechter - KJ7RYV Executive Director Amateur Radio Digital Communications (ARDC) ardc.net
On 4/3/24 3:52 PM, Tom M0LTE via 44net wrote:
The EULA is also outdated, referring to 44net as 44/8. Yes, I read it.
Can I suggest a review…
On Wed, 3 Apr 2024 at 23:21, Charles Holliday via 44net <44net@mailman.ampr.org mailto:44net@mailman.ampr.org> wrote:
You have to read the EULA. The page forces you to scroll down to the bottom of the EULA as a way to encourage you to read it.
Charles Holliday KG5IRU
On Wed, Apr 3, 2024 at 5:19 PM David McAnally via 44net <44net@mailman.ampr.org mailto:44net@mailman.ampr.org> wrote:
On Wed, Apr 3, 2024 at 5:15 PM Nathan Brookfield via 44net <44net@mailman.ampr.org mailto:44net@mailman.ampr.org> wrote:
I've received the same, when trying to log-in I got an eULA that I can't actually click to accept, has anyone else had the same issue?
Yes.
David McAnally WD5M
Is the UCSD gateway gone for good or just forgotten to be turned back on?
Microsoft Windows [Version 10.0.19045.4170] (c) Microsoft Corporation. All rights reserved.
C:\Users\n2nov>tracert 44.68.41.1
Tracing route to n2nov.ampr.org [44.68.41.1] over a maximum of 30 hops:
1 2 ms 3 ms 2 ms OPNsense.localdomain [192.168.1.1] 2 20 ms 10 ms 13 ms 024-193-224-001.res.spectrum.com [24.193.224.1] 3 13 ms 12 ms 18 ms lag-53.nycrnydf01h.netops.charter.com [68.173.201.236] 4 24 ms 14 ms 21 ms lag-131.nyclnyrg01r.netops.charter.com [68.173.197.0] 5 18 ms 21 ms 23 ms lag-29.nwrknjmd67w-bcr00.netops.charter.com [107.14.19.24] 6 84 ms 93 ms 85 ms lag-20.nycmny837aw-bcr00.netops.charter.com [66.109.5.138] 7 * 82 ms * lag-12.chcgildt87w-bcr00.netops.charter.com [66.109.6.25] 8 92 ms 77 ms * lag-11.snvacaid17w-bcr00.netops.charter.com [66.109.6.14] 9 91 ms 91 ms 96 ms lag-11.snjucacl67w-bcr00.netops.charter.com [66.109.6.8] 10 76 ms 143 ms 91 ms lag-0.pr1.sjc10.netops.charter.com [66.109.5.133] 11 84 ms 81 ms 78 ms eqix-sv5.cenic.com [206.223.117.118] 12 85 ms 90 ms 84 ms dc-svl-agg8--svl-agg10-300g.cenic.net [137.164.11.81] 13 96 ms 99 ms 86 ms dc-lax-agg8--svl-agg8--100ge--2.cenic.net [137.164.11.20] 14 99 ms 86 ms 92 ms dc-tus-agg8--lax-agg8-300g.cenic.net [137.164.11.83] 15 91 ms 93 ms 88 ms sand1-agg-01--tus-agg8--300g--01.cenic.net [137.164.11.85] 16 114 ms 93 ms 89 ms ucsd--sand1-agg-01--100g--01.cenic.net [137.164.23.177] 17 93 ms 87 ms 173 ms nodem-core-6807-vlan2767-gw.ucsd.edu [132.239.254.61] 18 87 ms 97 ms 173 ms sdsc-7710-7--mcore-vl2995-p2p.ucsd.edu [132.239.255.50] 19 * * * Request timed out. 20 * * * Request timed out. 21 * * * Request timed out. 22 * * * Request timed out. 23 * * * Request timed out. 24 * * * Request timed out. 25 * * * Request timed out. 26 * * * Request timed out. 27 * * * Request timed out. 28 * * * Request timed out. 29 * * * Request timed out. 30 * * * Request timed out.
Trace complete.
C:\Users\n2nov>
Hey All,
Just following up on this thread. I've been experiencing issues with the IPIP gateway (amprgw.ucsd.edu, 169.228.34.84) as well. I seem to be able to talk to other members of the mesh but not pass traffic through the gateway or to/from the internet. Similar traceroute to that below.
Last working traffic appears to be 3/4 on my end. FYI this is on the subnet 44.72.24.0/24.
*Anything change or is it just me?*
Mark - K9MEV
On 4/3/2024 9:08 PM, Charles Hargrove via 44net wrote:
Is the UCSD gateway gone for good or just forgotten to be turned back on?
Microsoft Windows [Version 10.0.19045.4170] (c) Microsoft Corporation. All rights reserved.
C:\Users\n2nov>tracert 44.68.41.1
Tracing route to n2nov.ampr.org [44.68.41.1] over a maximum of 30 hops:
1 2 ms 3 ms 2 ms OPNsense.localdomain [192.168.1.1] 2 20 ms 10 ms 13 ms 024-193-224-001.res.spectrum.com [24.193.224.1] 3 13 ms 12 ms 18 ms lag-53.nycrnydf01h.netops.charter.com [68.173.201.236] 4 24 ms 14 ms 21 ms lag-131.nyclnyrg01r.netops.charter.com [68.173.197.0] 5 18 ms 21 ms 23 ms lag-29.nwrknjmd67w-bcr00.netops.charter.com [107.14.19.24] 6 84 ms 93 ms 85 ms lag-20.nycmny837aw-bcr00.netops.charter.com [66.109.5.138] 7 * 82 ms * lag-12.chcgildt87w-bcr00.netops.charter.com [66.109.6.25] 8 92 ms 77 ms * lag-11.snvacaid17w-bcr00.netops.charter.com [66.109.6.14] 9 91 ms 91 ms 96 ms lag-11.snjucacl67w-bcr00.netops.charter.com [66.109.6.8] 10 76 ms 143 ms 91 ms lag-0.pr1.sjc10.netops.charter.com [66.109.5.133] 11 84 ms 81 ms 78 ms eqix-sv5.cenic.com [206.223.117.118] 12 85 ms 90 ms 84 ms dc-svl-agg8--svl-agg10-300g.cenic.net [137.164.11.81] 13 96 ms 99 ms 86 ms dc-lax-agg8--svl-agg8--100ge--2.cenic.net [137.164.11.20] 14 99 ms 86 ms 92 ms dc-tus-agg8--lax-agg8-300g.cenic.net [137.164.11.83] 15 91 ms 93 ms 88 ms sand1-agg-01--tus-agg8--300g--01.cenic.net [137.164.11.85] 16 114 ms 93 ms 89 ms ucsd--sand1-agg-01--100g--01.cenic.net [137.164.23.177] 17 93 ms 87 ms 173 ms nodem-core-6807-vlan2767-gw.ucsd.edu [132.239.254.61] 18 87 ms 97 ms 173 ms sdsc-7710-7--mcore-vl2995-p2p.ucsd.edu [132.239.255.50] 19 * * * Request timed out. 20 * * * Request timed out. 21 * * * Request timed out. 22 * * * Request timed out. 23 * * * Request timed out. 24 * * * Request timed out. 25 * * * Request timed out. 26 * * * Request timed out. 27 * * * Request timed out. 28 * * * Request timed out. 29 * * * Request timed out. 30 * * * Request timed out.
Trace complete.
C:\Users\n2nov>
here's traceroutes from my 44.63.18.113
C:>tracert 44.68.41.1
Tracing route to n2nov.ampr.org [44.68.41.1] over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms t40.wa4zlw.org [10.195.10.3] 2 1 ms <1 ms <1 ms core100.wa4zlw.ampr.org [44.63.18.113] 3 41 ms 42 ms 41 ms gw.n2nov.ampr.org [44.68.41.2] 4 42 ms 42 ms 46 ms n2nov.ampr.org [44.68.41.1]
Trace complete.
C:>tracert 44.72.24.1
Tracing route to host-44-72-24-1.k9mev.ampr.org [44.72.24.1] over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms t40.wa4zlw.org [10.195.10.3] 2 2 ms <1 ms <1 ms core100.wa4zlw.ampr.org [44.63.18.113] 3 * * * Request timed out. 4 * * * Request timed out. 5 * * * Request timed out. 6 * * * Request timed out. 7 * * * Request timed out. 8 * * * Request timed out. 9 ^C C:>
On 4/5/2024 3:15 PM, Mark Van Daele via 44net wrote:
Hey All,
Just following up on this thread. I've been experiencing issues with the IPIP gateway (amprgw.ucsd.edu, 169.228.34.84) as well. I seem to be able to talk to other members of the mesh but not pass traffic through the gateway or to/from the internet. Similar traceroute to that below.
Last working traffic appears to be 3/4 on my end. FYI this is on the subnet 44.72.24.0/24.
*Anything change or is it just me?*
Mark - K9MEV
On 4/3/2024 9:08 PM, Charles Hargrove via 44net wrote:
Is the UCSD gateway gone for good or just forgotten to be turned back on?
Microsoft Windows [Version 10.0.19045.4170] (c) Microsoft Corporation. All rights reserved.
C:\Users\n2nov>tracert 44.68.41.1
Tracing route to n2nov.ampr.org [44.68.41.1] over a maximum of 30 hops:
1 2 ms 3 ms 2 ms OPNsense.localdomain [192.168.1.1] 2 20 ms 10 ms 13 ms 024-193-224-001.res.spectrum.com [24.193.224.1] 3 13 ms 12 ms 18 ms lag-53.nycrnydf01h.netops.charter.com [68.173.201.236] 4 24 ms 14 ms 21 ms lag-131.nyclnyrg01r.netops.charter.com [68.173.197.0] 5 18 ms 21 ms 23 ms lag-29.nwrknjmd67w-bcr00.netops.charter.com [107.14.19.24] 6 84 ms 93 ms 85 ms lag-20.nycmny837aw-bcr00.netops.charter.com [66.109.5.138] 7 * 82 ms * lag-12.chcgildt87w-bcr00.netops.charter.com [66.109.6.25] 8 92 ms 77 ms * lag-11.snvacaid17w-bcr00.netops.charter.com [66.109.6.14] 9 91 ms 91 ms 96 ms lag-11.snjucacl67w-bcr00.netops.charter.com [66.109.6.8] 10 76 ms 143 ms 91 ms lag-0.pr1.sjc10.netops.charter.com [66.109.5.133] 11 84 ms 81 ms 78 ms eqix-sv5.cenic.com [206.223.117.118] 12 85 ms 90 ms 84 ms dc-svl-agg8--svl-agg10-300g.cenic.net [137.164.11.81] 13 96 ms 99 ms 86 ms dc-lax-agg8--svl-agg8--100ge--2.cenic.net [137.164.11.20] 14 99 ms 86 ms 92 ms dc-tus-agg8--lax-agg8-300g.cenic.net [137.164.11.83] 15 91 ms 93 ms 88 ms sand1-agg-01--tus-agg8--300g--01.cenic.net [137.164.11.85] 16 114 ms 93 ms 89 ms ucsd--sand1-agg-01--100g--01.cenic.net [137.164.23.177] 17 93 ms 87 ms 173 ms nodem-core-6807-vlan2767-gw.ucsd.edu [132.239.254.61] 18 87 ms 97 ms 173 ms sdsc-7710-7--mcore-vl2995-p2p.ucsd.edu [132.239.255.50] 19 * * * Request timed out. 20 * * * Request timed out. 21 * * * Request timed out. 22 * * * Request timed out. 23 * * * Request timed out. 24 * * * Request timed out. 25 * * * Request timed out. 26 * * * Request timed out. 27 * * * Request timed out. 28 * * * Request timed out. 29 * * * Request timed out. 30 * * * Request timed out.
Trace complete.
C:\Users\n2nov>
44net mailing list --44net@mailman.ampr.org To unsubscribe send an email to44net-leave@mailman.ampr.org
This trace to my subnet is totally within the IPIP encap routing. What Mark and I are saying is that inbound or outbound trace to a non-44net address that would go through the UCSD gateway have stopped as of the day that the initial "upgrade" to the new portal on Wednesday April 3rd.
On 4/5/2024 4:17 PM, Leon Zetekoff via 44net wrote:
here's traceroutes from my 44.63.18.113
C:>tracert 44.68.41.1
Tracing route to n2nov.ampr.org [44.68.41.1] over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms t40.wa4zlw.org [10.195.10.3] 2 1 ms <1 ms <1 ms core100.wa4zlw.ampr.org [44.63.18.113] 3 41 ms 42 ms 41 ms gw.n2nov.ampr.org [44.68.41.2] 4 42 ms 42 ms 46 ms n2nov.ampr.org [44.68.41.1]
Thank you all for making us aware and providing your trace routes. We will get this sorted when we're back on line next week.
73,
Rebecca KO4KVG
On 4/5/24 4:21 PM, Charles Hargrove via 44net wrote:
This trace to my subnet is totally within the IPIP encap routing. What Mark and I are saying is that inbound or outbound trace to a non-44net address that would go through the UCSD gateway have stopped as of the day that the initial "upgrade" to the new portal on Wednesday April 3rd.
On 4/5/2024 4:17 PM, Leon Zetekoff via 44net wrote:
here's traceroutes from my 44.63.18.113
C:>tracert 44.68.41.1
Tracing route to n2nov.ampr.org [44.68.41.1] over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms t40.wa4zlw.org [10.195.10.3] 2 1 ms <1 ms <1 ms core100.wa4zlw.ampr.org [44.63.18.113] 3 41 ms 42 ms 41 ms gw.n2nov.ampr.org [44.68.41.2] 4 42 ms 42 ms 46 ms n2nov.ampr.org [44.68.41.1]
I think we need this to be handled by volunteers as opposed to employees.
On 4/5/2024 5:19 PM, Rebecca Key via 44net wrote:
when we're back on line next week
I mentioned a similar issue here a few weeks ago with respect to passing traffic to the public network across amprgw.
Behavior I've been experiencing is that after rebooting my gateway, re-establishing the tunnel from my end & starting up rip44d, I can ping 44net IPs & get a 44net ip from whatismyip.ampr.org pretty much immediately;
Public IP connectivity (e.g. pinging 8.8.8.8 or a curl to ifconfig.me over my tunnel interface) doesn't start working until after everything's been up and running for about 45-60 minutes.
Just replicated the above behavior on my gateway (Raspbian OS on a Pi 3+) & curious if giving it a bit of time solves anyone else's issues.
Best, -Steve
________________________________ From: Charles Hargrove via 44net 44net@mailman.ampr.org Sent: Friday, April 5, 2024 7:41:24 PM To: 44net@mailman.ampr.org 44net@mailman.ampr.org Subject: [44net] Re: 44net IPIP gateway issues, was: Re: Re: New 44Net Portal coming 4/3!
I think we need this to be handled by volunteers as opposed to employees.
On 4/5/2024 5:19 PM, Rebecca Key via 44net wrote:
when we're back on line next week
-- Charles J. Hargrove - N2NOV NYC-ARECS/RACES Citywide Radio Officer/Skywarn Coord.
44net Coordinator - Northeast USA
NY-NBEMS Net Saturdays @ 10AM & USeast-NBEMS Net Wednesdays @ 7PM on 7.036 Mhz USB (alt 3.536)/1500 hz waterfall spot; MFSK-16 or 32
"Information is the oxygen of the modern age. It seeps through the walls topped by barbed wire, it wafts across the electrified borders." - Ronald Reagan
"The more corrupt the state, the more it legislates." - Tacitus
"Molann an obair an fear" - Irish Saying (The work praises the man.)
"No matter how big and powerful government gets, and the many services it provides, it can never take the place of volunteers." - Ronald Reagan _______________________________________________ 44net mailing list -- 44net@mailman.ampr.org To unsubscribe send an email to 44net-leave@mailman.ampr.org
My "gateway" is in a commercial site and has been totally rebooted today.
On 4/5/2024 8:07 PM, kc8qba wrote:
I mentioned a similar issue here a few weeks ago with respect to passing traffic to the public network across amprgw.
Behavior I've been experiencing is that after rebooting my gateway, re-establishing the tunnel from my end & starting up rip44d, I can ping 44net IPs & get a 44net ip from whatismyip.ampr.org pretty much immediately;
Public IP connectivity (e.g. pinging 8.8.8.8 or a curl to ifconfig.me over my tunnel interface) doesn't start working until after everything's been up and running for about 45-60 minutes.
Just replicated the above behavior on my gateway (Raspbian OS on a Pi 3+) & curious if giving it a bit of time solves anyone else's issues.
Best, -Steve
*From:* Charles Hargrove via 44net 44net@mailman.ampr.org *Sent:* Friday, April 5, 2024 7:41:24 PM *To:* 44net@mailman.ampr.org 44net@mailman.ampr.org *Subject:* [44net] Re: 44net IPIP gateway issues, was: Re: Re: New 44Net Portal coming 4/3! I think we need this to be handled by volunteers as opposed to employees.
On 4/5/2024 5:19 PM, Rebecca Key via 44net wrote:
when we're back on line next week
-- Charles J. Hargrove - N2NOV NYC-ARECS/RACES Citywide Radio Officer/Skywarn Coord.
44net Coordinator - Northeast USA
NY-NBEMS Net Saturdays @ 10AM & USeast-NBEMS Net Wednesdays @ 7PM on 7.036 Mhz USB (alt 3.536)/1500 hz waterfall spot; MFSK-16 or 32
"Information is the oxygen of the modern age. It seeps through the walls topped by barbed wire, it wafts across the electrified borders." - Ronald Reagan
"The more corrupt the state, the more it legislates." - Tacitus
"Molann an obair an fear" - Irish Saying (The work praises the man.)
"No matter how big and powerful government gets, and the many services it provides, it can never take the place of volunteers." - Ronald Reagan _______________________________________________ 44net mailing list -- 44net@mailman.ampr.org To unsubscribe send an email to 44net-leave@mailman.ampr.org
All,
I observed something interesting. I'm still able to access my web server 44.60.44.10 from a client on the Public Internet.
- http://whatismyip.ampr.org - http://kb3vwg-010.ampr.org
Despite that, like others I also cannot initiate traffic from my AMPRLAN to the Internet - the trace stops at my AMPR router. Another user mentioned an issue the other day, I tested and was still able to use a normal client PC/laptop to browse the Internet - I cannot do so any longer. Using the software My Traceroute (mtr) and selecting port 80/tcp yielded results. The following trace is from the ISP Cogent Communications (the first hops removed for privacy). `mtr 44.60.44.10 -T -P 80`
7. be4109.agr22.dca01.atlas.cogentco.com be4108.agr21.dca01.atlas.cogentco.com8. be3311.ccr42.dca01.atlas.cogentco.com be3309.ccr41.dca01.atlas.cogentco.com be3308.ccr41.dca01.atlas.cogentco.com be3310.ccr42.dca01.atlas.cogentco.com9. be3084.ccr41.iad02.atlas.cogentco.com be3083.ccr41.iad02.atlas.cogentco.com10. ae-6.edge1.WashingtonDC111.Level3.net11. (waiting for reply)12. CENIC.ear1.LosAngeles1.Level3.net13. dc-lax-agg8--lax-agg10-300g.cenic.net14. dc-tus-agg8--lax-agg8-300g.cenic.net15. sand1-agg-01--tus-agg8--300g--01.cenic.net16. ucsd--sand1-agg-01--100g--01.cenic.net17. nodem-core-6807-vlan2767-gw.ucsd.edu18. sdsc-7710-7--mcore-vl2995-p2p.ucsd.edu19. amprgw.ucsd.edu20. (waiting for reply) #this hop should be my router-firewalled21. kb3vwg-010.ampr.org
--- 73,
LynwoodKB3VWG
Nope. It dies before amprgw.ucsd.edu.
Microsoft Windows [Version 10.0.19045.4170] (c) Microsoft Corporation. All rights reserved.
C:\Users\n2nov>tracert 44.68.41.1
Tracing route to n2nov.ampr.org [44.68.41.1] over a maximum of 30 hops:
3 lag-53.nycrnydf01h.netops.charter.com [68.173.201.236] 4 lag-131.nyclnyrg01r.netops.charter.com [68.173.197.0] 5 lag-29.nwrknjmd67w-bcr00.netops.charter.com [107.14.19.24] 6 lag-20.nycmny837aw-bcr00.netops.charter.com [66.109.5.138] 7 lag-12.chcgildt87w-bcr00.netops.charter.com [66.109.6.25] 8 lag-11.snvacaid17w-bcr00.netops.charter.com [66.109.6.14] 9 lag-11.snjucacl67w-bcr00.netops.charter.com [66.109.6.8] 10 lag-0.pr1.sjc10.netops.charter.com [66.109.5.133] 11 eqix-sv5.cenic.com [206.223.117.118] 12 dc-svl-agg8--svl-agg10-300g.cenic.net [137.164.11.81] 13 dc-lax-agg8--svl-agg8--100ge--2.cenic.net [137.164.11.20] 14 dc-tus-agg8--lax-agg8-300g.cenic.net [137.164.11.83] 15 sand1-agg-01--tus-agg8--300g--01.cenic.net [137.164.11.85] 16 ucsd--sand1-agg-01--100g--01.cenic.net [137.164.23.177] 17 nodem-core-6807-vlan2767-gw.ucsd.edu [132.239.254.61] 18 sdsc-7710-7--mcore-vl2995-p2p.ucsd.edu [132.239.255.50] 19 Request timed out. 20 Request timed out. 21 Request timed out. 22 Request timed out. 23 Request timed out. 24 Request timed out. 25 Request timed out. 26 Request timed out. 27 Request timed out. 28 Request timed out. 29 Request timed out. 30 Request timed out.
Trace complete.
C:\Users\n2nov>
On 4/5/2024 10:06 PM, lleachii@aol.com wrote:
All,
I observed something interesting. I'm still able to access my web server 44.60.44.10 from a client on the Public Internet.
- http://whatismyip.ampr.org http://whatismyip.ampr.org/
- http://kb3vwg-010.ampr.org http://kb3vwg-010.ampr.org
- http://44.60.44.10 http://44.60.44.10
Despite that, like others I also cannot initiate traffic from my AMPRLAN to the Internet - the trace stops at my AMPR router. Another user mentioned an issue the other day, I tested and was still able to use a normal client PC/laptop to browse the Internet - I cannot do so any longer.
Using the software My Traceroute (mtr) and selecting port 80/tcp yielded results. The following trace is from the ISP Cogent Communications (the first hops removed for privacy).
`mtr 44.60.44.10 -T -P 80`
7. be4109.agr22.dca01.atlas.cogentco.com be4108.agr21.dca01.atlas.cogentco.com 8. be3311.ccr42.dca01.atlas.cogentco.com be3309.ccr41.dca01.atlas.cogentco.com be3308.ccr41.dca01.atlas.cogentco.com be3310.ccr42.dca01.atlas.cogentco.com 9. be3084.ccr41.iad02.atlas.cogentco.com be3083.ccr41.iad02.atlas.cogentco.com 10. ae-6.edge1.WashingtonDC111.Level3.net 11. (waiting for reply) 12. CENIC.ear1.LosAngeles1.Level3.net 13. dc-lax-agg8--lax-agg10-300g.cenic.net 14. dc-tus-agg8--lax-agg8-300g.cenic.net 15. sand1-agg-01--tus-agg8--300g--01.cenic.net 16. ucsd--sand1-agg-01--100g--01.cenic.net 17. nodem-core-6807-vlan2767-gw.ucsd.edu 18. sdsc-7710-7--mcore-vl2995-p2p.ucsd.edu 19. amprgw.ucsd.edu 20. (waiting for reply) #this hop should be my router-firewalled 21. kb3vwg-010.ampr.org
73,
Lynwood KB3VWG
Charles,
It's unclear what you mean by your response "Nope. It dies before amprgw.ucsd.edu". Your trace is not using port 80/tcp. As my trace shows - using 80/tcp and not ICMP or UDP as other tools such as 'tracert', I'm able to reach AMPRGW thru to my HTTP server 44.60.44.10 from numerous ISP and cell networks.
I agree that it seems ingressing ICMP and UDP are having issues (and all egressing traffic), but I'm attempting to note that 80/tcp is working. Have you tested the HTTP links to 44.60.44.10 a normal cellular phone data connection, your, home ISP, etc.?
--- - Lynwood
On Friday, April 5, 2024 at 10:21:12 PM EDT, Charles Hargrove via 44net 44net@mailman.ampr.org wrote:
Nope. It dies before amprgw.ucsd.edu.
Microsoft Windows [Version 10.0.19045.4170] (c) Microsoft Corporation. All rights reserved.
C:\Users\n2nov>tracert 44.68.41.1
Tracing route to n2nov.ampr.org [44.68.41.1] over a maximum of 30 hops:
3 lag-53.nycrnydf01h.netops.charter.com [68.173.201.236] 4 lag-131.nyclnyrg01r.netops.charter.com [68.173.197.0] 5 lag-29.nwrknjmd67w-bcr00.netops.charter.com [107.14.19.24] 6 lag-20.nycmny837aw-bcr00.netops.charter.com [66.109.5.138] 7 lag-12.chcgildt87w-bcr00.netops.charter.com [66.109.6.25] 8 lag-11.snvacaid17w-bcr00.netops.charter.com [66.109.6.14] 9 lag-11.snjucacl67w-bcr00.netops.charter.com [66.109.6.8] 10 lag-0.pr1.sjc10.netops.charter.com [66.109.5.133] 11 eqix-sv5.cenic.com [206.223.117.118] 12 dc-svl-agg8--svl-agg10-300g.cenic.net [137.164.11.81] 13 dc-lax-agg8--svl-agg8--100ge--2.cenic.net [137.164.11.20] 14 dc-tus-agg8--lax-agg8-300g.cenic.net [137.164.11.83] 15 sand1-agg-01--tus-agg8--300g--01.cenic.net [137.164.11.85] 16 ucsd--sand1-agg-01--100g--01.cenic.net [137.164.23.177] 17 nodem-core-6807-vlan2767-gw.ucsd.edu [132.239.254.61] 18 sdsc-7710-7--mcore-vl2995-p2p.ucsd.edu [132.239.255.50] 19 Request timed out. 20 Request timed out. 21 Request timed out. 22 Request timed out. 23 Request timed out. 24 Request timed out. 25 Request timed out. 26 Request timed out. 27 Request timed out. 28 Request timed out. 29 Request timed out. 30 Request timed out.
Trace complete.
C:\Users\n2nov>
On 4/5/2024 10:06 PM, lleachii@aol.com wrote:
All,
I observed something interesting. I'm still able to access my web server 44.60.44.10 from a client on the Public Internet.
* http://whatismyip.ampr.org http://whatismyip.ampr.org/ * http://kb3vwg-010.ampr.org http://kb3vwg-010.ampr.org * http://44.60.44.10 http://44.60.44.10
Despite that, like others I also cannot initiate traffic from my AMPRLAN to the Internet - the trace stops at my AMPR router. Another user mentioned an issue the other day, I tested and was still able to use a normal client PC/laptop to browse the Internet - I cannot do so any longer.
Using the software My Traceroute (mtr) and selecting port 80/tcp yielded results. The following trace is from the ISP Cogent Communications (the first hops removed for privacy).
`mtr 44.60.44.10 -T -P 80`
7. be4109.agr22.dca01.atlas.cogentco.com be4108.agr21.dca01.atlas.cogentco.com 8. be3311.ccr42.dca01.atlas.cogentco.com be3309.ccr41.dca01.atlas.cogentco.com be3308.ccr41.dca01.atlas.cogentco.com be3310.ccr42.dca01.atlas.cogentco.com 9. be3084.ccr41.iad02.atlas.cogentco.com be3083.ccr41.iad02.atlas.cogentco.com 10. ae-6.edge1.WashingtonDC111.Level3.net 11. (waiting for reply) 12. CENIC.ear1.LosAngeles1.Level3.net 13. dc-lax-agg8--lax-agg10-300g.cenic.net 14. dc-tus-agg8--lax-agg8-300g.cenic.net 15. sand1-agg-01--tus-agg8--300g--01.cenic.net 16. ucsd--sand1-agg-01--100g--01.cenic.net 17. nodem-core-6807-vlan2767-gw.ucsd.edu 18. sdsc-7710-7--mcore-vl2995-p2p.ucsd.edu 19. amprgw.ucsd.edu 20. (waiting for reply) #this hop should be my router-firewalled 21. kb3vwg-010.ampr.org
73,
Lynwood KB3VWG
All,
A copy of the output from my router to http://44.0.0.1%C2%A0- `mtr 44.0.0.1 -T -P 80`
My traceroute [v0.95]user (192.168.xxx.xxx) -> 44.0.0.1 (44.0.0.1) 2024-04-05T22:50:46-0400Keys: Help Display mode Restart statistics Order of fields quit Packets Pings Host Loss% Snt Last Avg Best Wrst StDev 1. OpenWrt.lan 0.0% 6 0.8 1.0 0.8 1.1 0.1 2. lo0-100.WASHDC-VFTTP-352.verizon-gni.net 0.0% 5 4.4 7.7 1.5 29.3 12.1 3. 100.41.27.188 0.0% 5 3.1 3.1 2.8 3.3 0.2 4. (waiting for reply) 5. (waiting for reply) 6. (waiting for reply) 7. CENIC.ear1.LosAngeles1.Level3.net 0.0% 5 77.8 71.9 63.8 90.3 11.9 8. dc-lax-agg8--lax-agg10-300g.cenic.net 0.0% 5 68.6 78.8 67.5 101.5 15.5 9. dc-tus-agg8--lax-agg8-300g.cenic.net 0.0% 5 67.4 66.9 64.8 67.7 1.210. sand1-agg-01--tus-agg8--300g--01.cenic.net 0.0% 5 69.1 67.4 66.5 69.1 1.011. ucsd--sand1-agg-01--100g--01.cenic.net 0.0% 5 66.7 67.2 66.4 70.1 1.612. nodem-core-6807-vlan2767-gw.ucsd.edu 0.0% 5 65.9 66.5 65.2 67.2 0.913. sdsc-7710-7--mcore-vl2995-p2p.ucsd.edu 0.0% 5 67.4 67.3 67.0 67.7 0.314. gw.ampr.org 0.0% 5 68.0 66.9 66.3 68.0 0.6
On Friday, April 5, 2024 at 10:38:35 PM EDT, lleachii--- via 44net 44net@mailman.ampr.org wrote:
Charles,
It's unclear what you mean by your response "Nope. It dies before amprgw.ucsd.edu". Your trace is not using port 80/tcp. As my trace shows - using 80/tcp and not ICMP or UDP as other tools such as 'tracert', I'm able to reach AMPRGW thru to my HTTP server 44.60.44.10 from numerous ISP and cell networks.
I agree that it seems ingressing ICMP and UDP are having issues (and all egressing traffic), but I'm attempting to note that 80/tcp is working. Have you tested the HTTP links to 44.60.44.10 a normal cellular phone data connection, your, home ISP, etc.?
--- - Lynwood
On Friday, April 5, 2024 at 10:21:12 PM EDT, Charles Hargrove via 44net 44net@mailman.ampr.org wrote:
Nope. It dies before amprgw.ucsd.edu.
Microsoft Windows [Version 10.0.19045.4170] (c) Microsoft Corporation. All rights reserved.
C:\Users\n2nov>tracert 44.68.41.1
Tracing route to n2nov.ampr.org [44.68.41.1] over a maximum of 30 hops:
3 lag-53.nycrnydf01h.netops.charter.com [68.173.201.236] 4 lag-131.nyclnyrg01r.netops.charter.com [68.173.197.0] 5 lag-29.nwrknjmd67w-bcr00.netops.charter.com [107.14.19.24] 6 lag-20.nycmny837aw-bcr00.netops.charter.com [66.109.5.138] 7 lag-12.chcgildt87w-bcr00.netops.charter.com [66.109.6.25] 8 lag-11.snvacaid17w-bcr00.netops.charter.com [66.109.6.14] 9 lag-11.snjucacl67w-bcr00.netops.charter.com [66.109.6.8] 10 lag-0.pr1.sjc10.netops.charter.com [66.109.5.133] 11 eqix-sv5.cenic.com [206.223.117.118] 12 dc-svl-agg8--svl-agg10-300g.cenic.net [137.164.11.81] 13 dc-lax-agg8--svl-agg8--100ge--2.cenic.net [137.164.11.20] 14 dc-tus-agg8--lax-agg8-300g.cenic.net [137.164.11.83] 15 sand1-agg-01--tus-agg8--300g--01.cenic.net [137.164.11.85] 16 ucsd--sand1-agg-01--100g--01.cenic.net [137.164.23.177] 17 nodem-core-6807-vlan2767-gw.ucsd.edu [132.239.254.61] 18 sdsc-7710-7--mcore-vl2995-p2p.ucsd.edu [132.239.255.50] 19 Request timed out. 20 Request timed out. 21 Request timed out. 22 Request timed out. 23 Request timed out. 24 Request timed out. 25 Request timed out. 26 Request timed out. 27 Request timed out. 28 Request timed out. 29 Request timed out. 30 Request timed out.
Trace complete.
C:\Users\n2nov>
On 4/5/2024 10:06 PM, lleachii@aol.com wrote:
All,
I observed something interesting. I'm still able to access my web server 44.60.44.10 from a client on the Public Internet.
* http://whatismyip.ampr.org http://whatismyip.ampr.org/ * http://kb3vwg-010.ampr.org http://kb3vwg-010.ampr.org * http://44.60.44.10 http://44.60.44.10
Despite that, like others I also cannot initiate traffic from my AMPRLAN to the Internet - the trace stops at my AMPR router. Another user mentioned an issue the other day, I tested and was still able to use a normal client PC/laptop to browse the Internet - I cannot do so any longer.
Using the software My Traceroute (mtr) and selecting port 80/tcp yielded results. The following trace is from the ISP Cogent Communications (the first hops removed for privacy).
`mtr 44.60.44.10 -T -P 80`
7. be4109.agr22.dca01.atlas.cogentco.com be4108.agr21.dca01.atlas.cogentco.com 8. be3311.ccr42.dca01.atlas.cogentco.com be3309.ccr41.dca01.atlas.cogentco.com be3308.ccr41.dca01.atlas.cogentco.com be3310.ccr42.dca01.atlas.cogentco.com 9. be3084.ccr41.iad02.atlas.cogentco.com be3083.ccr41.iad02.atlas.cogentco.com 10. ae-6.edge1.WashingtonDC111.Level3.net 11. (waiting for reply) 12. CENIC.ear1.LosAngeles1.Level3.net 13. dc-lax-agg8--lax-agg10-300g.cenic.net 14. dc-tus-agg8--lax-agg8-300g.cenic.net 15. sand1-agg-01--tus-agg8--300g--01.cenic.net 16. ucsd--sand1-agg-01--100g--01.cenic.net 17. nodem-core-6807-vlan2767-gw.ucsd.edu 18. sdsc-7710-7--mcore-vl2995-p2p.ucsd.edu 19. amprgw.ucsd.edu 20. (waiting for reply) #this hop should be my router-firewalled 21. kb3vwg-010.ampr.org
73,
Lynwood KB3VWG
All,
I am able to reach other AMPR users HTTP servers. http://vk6hgr.ampr.org/ - http://44.136.204.77/ (the server responds and provides a redirect to the public server)
It seems TCP is OK. Also, AMPRGW properly responds to TCP traffic messages. Does anyone have other public TCP services on AMPRNet that can be tested?
73,
LynwoodKB3VWG
I have just tested ICMP from inside the IPIP mesh to the Internet and it’s working for me:
ping -I 44.63.7.215 1.1.1.1 PING 1.1.1.1 (1.1.1.1) from 44.63.7.215 : 56(84) bytes of data. 64 bytes from 1.1.1.1: icmp_seq=1 ttl=55 time=142 ms 64 bytes from 1.1.1.1: icmp_seq=2 ttl=55 time=141 ms 64 bytes from 1.1.1.1: icmp_seq=3 ttl=55 time=142 ms 64 bytes from 1.1.1.1: icmp_seq=4 ttl=55 time=142 ms 64 bytes from 1.1.1.1: icmp_seq=5 ttl=55 time=142 ms 64 bytes from 1.1.1.1: icmp_seq=6 ttl=55 time=142 ms 64 bytes from 1.1.1.1: icmp_seq=7 ttl=55 time=142 ms
Can someone confirm if this is still an issue so I can diagnose further
Thanks Chris - G1FEF
On 6 Apr 2024, at 04:18, lleachii--- via 44net 44net@mailman.ampr.org wrote:
All,
I am able to reach other AMPR users HTTP servers.
http://vk6hgr.ampr.org/ - http://44.136.204.77/ (the server responds and provides a redirect to the public server)
It seems TCP is OK. Also, AMPRGW properly responds to TCP traffic messages. Does anyone have other public TCP services on AMPRNet that can be tested?
73,
Lynwood KB3VWG _______________________________________________ 44net mailing list -- 44net@mailman.ampr.org To unsubscribe send an email to 44net-leave@mailman.ampr.org
The same ping test fails for me - IPIP mesh again. I can ping other 44net IPs but not anything external.
Jeremy M0RVB
On 6 Apr 2024, at 09:10, Chris via 44net 44net@mailman.ampr.org wrote:
I have just tested ICMP from inside the IPIP mesh to the Internet and it’s working for me:
ping -I 44.63.7.215 1.1.1.1 PING 1.1.1.1 (1.1.1.1) from 44.63.7.215 : 56(84) bytes of data. 64 bytes from 1.1.1.1: icmp_seq=1 ttl=55 time=142 ms 64 bytes from 1.1.1.1: icmp_seq=2 ttl=55 time=141 ms 64 bytes from 1.1.1.1: icmp_seq=3 ttl=55 time=142 ms 64 bytes from 1.1.1.1: icmp_seq=4 ttl=55 time=142 ms 64 bytes from 1.1.1.1: icmp_seq=5 ttl=55 time=142 ms 64 bytes from 1.1.1.1: icmp_seq=6 ttl=55 time=142 ms 64 bytes from 1.1.1.1: icmp_seq=7 ttl=55 time=142 ms
Can someone confirm if this is still an issue so I can diagnose further
Thanks Chris - G1FEF
Chris,
Another interesting observation occurred when testing egress from my LAN and router with various SRC IPs. My LAN is configured with a SNAT and IP/Rules to use 44.60.44.128 for traffic from a certain LAN SRC IP is set on the client.
* With my usual SNAT setting of SRC 44.60.44.128 - ping DOESN'T WORK* When pining from the router with 44.60.44.1 and changing the LAN SNAT rule to also use SRC 44.60.44.1 - ping WORKS
root@OpenWrt:~# ping -c 5 1.1.1.1 -I 44.60.44.1PING 1.1.1.1 (1.1.1.1) from 44.60.44.1: 56 data bytes64 bytes from 1.1.1.1: seq=0 ttl=55 time=67.178 ms64 bytes from 1.1.1.1: seq=1 ttl=55 time=65.657 ms64 bytes from 1.1.1.1: seq=2 ttl=55 time=65.435 ms64 bytes from 1.1.1.1: seq=3 ttl=55 time=65.314 ms64 bytes from 1.1.1.1: seq=4 ttl=55 time=65.462 ms --- 1.1.1.1 ping statistics ---5 packets transmitted, 5 packets received, 0% packet lossround-trip min/avg/max = 65.314/65.809/67.178 ms
--- - LynwoodKB3VWG
Chris,
I should also note, that after changing my traffic's SRC IP 44.60.44.1, I can again use the Internet as previously on the AMPRLAN client as well.
- LynwoodKB3VWG
Chris,
I recall something similar occurring during the lifetime of the late Brian Kantor. Is AMPRGW still a 10 Gbps BSD kernel?
- Lynwood
If it helps - from the late Brian Kantor, SK - Fri, Jun 2, 2017 at 5:12 PM I found a possible source of memory corruption - a hash routinemight have returned a negative number, causing the flow statsgathering to index off the beginning of a large array thatappears in memory adjacent to the routing table. This mighthave resulted in an entry being stomped on. I don't know. But the hash routine won't return negative or too large numbersanymore. I did fix that. We'll see if that prevents the problemfrom recurring. I'd hate to have to go through 16 million routeentries in a core dump. - Brian On Fri, Jun 02, 2017 at 11:12:16AM -0700, Brian Kantor wrote:> On Fri, Jun 02, 2017 at 02:03:56PM -0400, lleachii--- via 44Net wrote:> > From my perspective, I stop seeing all inbound Internet traffic from AMPRGW> > to 44.60.44.0/24, except for the intermittent data to another subnet (now> > 44.62.1.81). I transmit, and never receive replies.> > Although, I'm still able to send and receive traffic to/from the other 44> > GWs.>> Thanks, that helps. I checked, and the on-disk copy of the routing> table is still correct even when this is happening, so I'm beginning> to suspect memory corruption in the router software itself.>> As you know, that's difficult to find, but I'm looking through the> code to make sure I haven't done any of the usual errors. The next> time it happens, I'll take a core dump of the running process and> see if that tells me anything. Be sure to let me know.> - Brian
Chris,
I suspect some failure in the location that maintains what AMPR IPs have DNS entries - hence allowing FORWARD on AMPRGW. Rationale:
* My ingress TCP traces are blocked for 44.60.44.128, yet work for 44.60.44.1, 44.60.44.3 and 44.60.44.10
- On a side note, I also observe that on my DNS server (44.60.44.3) - that the 44.in-addr.arpa Zone seems to be failing (checking logs). I can no longer get authoritative answers, but I can still query 44.0.0.1 and get Zone Transfers (port 53/TCP) for AMPR.ORG. Was the Reverse Zone edited somehow?
- Lynwood
On Saturday, April 6, 2024 at 05:47:53 AM EDT, lleachii@aol.com lleachii@aol.com wrote:
Chris,
Another interesting observation occurred when testing egress from my LAN and router with various SRC IPs. My LAN is configured with a SNAT and IP/Rules to use 44.60.44.128 for traffic from a certain LAN SRC IP is set on the client.
* With my usual SNAT setting of SRC 44.60.44.128 - ping DOESN'T WORK* When pining from the router with 44.60.44.1 and changing the LAN SNAT rule to also use SRC 44.60.44.1 - ping WORKS
root@OpenWrt:~# ping -c 5 1.1.1.1 -I 44.60.44.1PING 1.1.1.1 (1.1.1.1) from 44.60.44.1: 56 data bytes64 bytes from 1.1.1.1: seq=0 ttl=55 time=67.178 ms64 bytes from 1.1.1.1: seq=1 ttl=55 time=65.657 ms64 bytes from 1.1.1.1: seq=2 ttl=55 time=65.435 ms64 bytes from 1.1.1.1: seq=3 ttl=55 time=65.314 ms64 bytes from 1.1.1.1: seq=4 ttl=55 time=65.462 ms --- 1.1.1.1 ping statistics ---5 packets transmitted, 5 packets received, 0% packet lossround-trip min/avg/max = 65.314/65.809/67.178 ms
--- - LynwoodKB3VWG
So, we are in the process of moving the primary nameserver away from the UCSD gateway server so all it will be left with is acting as the IPIP encap/de-encap gateway function + rip44d, so don’t rely on doing zone transfers from that server for much longer.
As to your egress problem, I checked on the gateway and your 44.60.44.128 IP is not in the filter list but your 44.60.44.1 IP is, that’s why it’s not working for 44.60.44.128. What is the A record hostname for that IP supposed to be? I can check if it’s in the zonefile or not - likely not - was it added only recently?
73, Chris - G1FEF — ARDC Administrator
Web: https://www.ardc.net
On 6 Apr 2024, at 12:02, lleachii--- via 44net 44net@mailman.ampr.org wrote:
Chris,
I suspect some failure in the location that maintains what AMPR IPs have DNS entries - hence allowing FORWARD on AMPRGW.
Rationale:
- My ingress TCP traces are blocked for 44.60.44.128, yet work for 44.60.44.1, 44.60.44.3 and 44.60.44.10
On a side note, I also observe that on my DNS server (44.60.44.3) - that the 44.in-addr.arpa Zone seems to be failing (checking logs). I can no longer get authoritative answers, but I can still query 44.0.0.1 and get Zone Transfers (port 53/TCP) for AMPR.ORG. Was the Reverse Zone edited somehow?
Lynwood
On Saturday, April 6, 2024 at 05:47:53 AM EDT, lleachii@aol.com lleachii@aol.com wrote:
Chris,
Another interesting observation occurred when testing egress from my LAN and router with various SRC IPs. My LAN is configured with a SNAT and IP/Rules to use 44.60.44.128 for traffic from a certain LAN SRC IP is set on the client.
- With my usual SNAT setting of SRC 44.60.44.128 - ping DOESN'T WORK
- When pining from the router with 44.60.44.1 and changing the LAN SNAT rule to also use SRC 44.60.44.1 - ping WORKS
root@OpenWrt:~# ping -c 5 1.1.1.1 -I 44.60.44.1 PING 1.1.1.1 (1.1.1.1) from 44.60.44.1: 56 data bytes 64 bytes from 1.1.1.1: seq=0 ttl=55 time=67.178 ms 64 bytes from 1.1.1.1: seq=1 ttl=55 time=65.657 ms 64 bytes from 1.1.1.1: seq=2 ttl=55 time=65.435 ms 64 bytes from 1.1.1.1: seq=3 ttl=55 time=65.314 ms 64 bytes from 1.1.1.1: seq=4 ttl=55 time=65.462 ms
--- 1.1.1.1 ping statistics --- 5 packets transmitted, 5 packets received, 0% packet loss round-trip min/avg/max = 65.314/65.809/67.178 ms
- Lynwood
KB3VWG _______________________________________________ 44net mailing list -- 44net@mailman.ampr.org To unsubscribe send an email to 44net-leave@mailman.ampr.org
Chris,
"What is the A record hostname for that IP supposed to be? I can check if it’s in the zonefile or not - likely not - was it added only recently?"
That's the issue, it was not added recently- it's been there for years, since I first devised my internal network plan years ago:
kb3vwg-128.ampr.org
user@machine:~$ nslookup 44.60.44.128 44.0.0.1128.44.60.44.in-addr.arpa name = kb3vwg-128.ampr.org. It is in the zone file.
- Lynwood On Saturday, April 6, 2024 at 12:41:29 PM EDT, Chris via 44net 44net@mailman.ampr.org wrote:
So, we are in the process of moving the primary nameserver away from the UCSD gateway server so all it will be left with is acting as the IPIP encap/de-encap gateway function + rip44d, so don’t rely on doing zone transfers from that server for much longer. As to your egress problem, I checked on the gateway and your 44.60.44.128 IP is not in the filter list but your 44.60.44.1 IP is, that’s why it’s not working for 44.60.44.128. What is the A record hostname for that IP supposed to be? I can check if it’s in the zonefile or not - likely not - was it added only recently? 73, Chris - G1FEF — ARDC Administrator
Web: https://www.ardc.net
On 6 Apr 2024, at 12:02, lleachii--- via 44net 44net@mailman.ampr.org wrote: Chris,
I suspect some failure in the location that maintains what AMPR IPs have DNS entries - hence allowing FORWARD on AMPRGW. Rationale:
* My ingress TCP traces are blocked for 44.60.44.128, yet work for 44.60.44.1, 44.60.44.3 and 44.60.44.10
- On a side note, I also observe that on my DNS server (44.60.44.3) - that the 44.in-addr.arpa Zone seems to be failing (checking logs). I can no longer get authoritative answers, but I can still query 44.0.0.1 and get Zone Transfers (port 53/TCP) for AMPR.ORG. Was the Reverse Zone edited somehow?
- Lynwood
On Saturday, April 6, 2024 at 05:47:53 AM EDT, lleachii@aol.com lleachii@aol.com wrote:
Chris,
Another interesting observation occurred when testing egress from my LAN and router with various SRC IPs. My LAN is configured with a SNAT and IP/Rules to use 44.60.44.128 for traffic from a certain LAN SRC IP is set on the client.
* With my usual SNAT setting of SRC 44.60.44.128 - ping DOESN'T WORK* When pining from the router with 44.60.44.1 and changing the LAN SNAT rule to also use SRC 44.60.44.1 - ping WORKS
root@OpenWrt:~# ping -c 5 1.1.1.1 -I 44.60.44.1PING 1.1.1.1 (1.1.1.1) from 44.60.44.1: 56 data bytes64 bytes from 1.1.1.1: seq=0 ttl=55 time=67.178 ms64 bytes from 1.1.1.1: seq=1 ttl=55 time=65.657 ms64 bytes from 1.1.1.1: seq=2 ttl=55 time=65.435 ms64 bytes from 1.1.1.1: seq=3 ttl=55 time=65.314 ms64 bytes from 1.1.1.1: seq=4 ttl=55 time=65.462 ms --- 1.1.1.1 ping statistics ---5 packets transmitted, 5 packets received, 0% packet lossround-trip min/avg/max = 65.314/65.809/67.178 ms
--- - LynwoodKB3VWG _______________________________________________ 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
Chris, Also, you noted:
"don’t rely on doing zone transfers from that server for much longer."
Please provide an Authoritative Public DNS server that accepts Zone Transfers either on AMPRNet or Public. To my knowledge gw.ampr.org was the only one.
---
73,
LynwoodKB3VWG
On Saturday, April 6, 2024 at 12:48:41 PM EDT, lleachii@aol.com lleachii@aol.com wrote:
Chris,
"What is the A record hostname for that IP supposed to be? I can check if it’s in the zonefile or not - likely not - was it added only recently?"
That's the issue, it was not added recently- it's been there for years, since I first devised my internal network plan years ago:
kb3vwg-128.ampr.org
user@machine:~$ nslookup 44.60.44.128 44.0.0.1128.44.60.44.in-addr.arpa name = kb3vwg-128.ampr.org. It is in the zone file.
- Lynwood On Saturday, April 6, 2024 at 12:41:29 PM EDT, Chris via 44net 44net@mailman.ampr.org wrote:
So, we are in the process of moving the primary nameserver away from the UCSD gateway server so all it will be left with is acting as the IPIP encap/de-encap gateway function + rip44d, so don’t rely on doing zone transfers from that server for much longer. As to your egress problem, I checked on the gateway and your 44.60.44.128 IP is not in the filter list but your 44.60.44.1 IP is, that’s why it’s not working for 44.60.44.128. What is the A record hostname for that IP supposed to be? I can check if it’s in the zonefile or not - likely not - was it added only recently? 73, Chris - G1FEF — ARDC Administrator
Web: https://www.ardc.net
On 6 Apr 2024, at 12:02, lleachii--- via 44net 44net@mailman.ampr.org wrote: Chris,
I suspect some failure in the location that maintains what AMPR IPs have DNS entries - hence allowing FORWARD on AMPRGW. Rationale:
* My ingress TCP traces are blocked for 44.60.44.128, yet work for 44.60.44.1, 44.60.44.3 and 44.60.44.10
- On a side note, I also observe that on my DNS server (44.60.44.3) - that the 44.in-addr.arpa Zone seems to be failing (checking logs). I can no longer get authoritative answers, but I can still query 44.0.0.1 and get Zone Transfers (port 53/TCP) for AMPR.ORG. Was the Reverse Zone edited somehow?
- Lynwood
On Saturday, April 6, 2024 at 05:47:53 AM EDT, lleachii@aol.com lleachii@aol.com wrote:
Chris,
Another interesting observation occurred when testing egress from my LAN and router with various SRC IPs. My LAN is configured with a SNAT and IP/Rules to use 44.60.44.128 for traffic from a certain LAN SRC IP is set on the client.
* With my usual SNAT setting of SRC 44.60.44.128 - ping DOESN'T WORK* When pining from the router with 44.60.44.1 and changing the LAN SNAT rule to also use SRC 44.60.44.1 - ping WORKS
root@OpenWrt:~# ping -c 5 1.1.1.1 -I 44.60.44.1PING 1.1.1.1 (1.1.1.1) from 44.60.44.1: 56 data bytes64 bytes from 1.1.1.1: seq=0 ttl=55 time=67.178 ms64 bytes from 1.1.1.1: seq=1 ttl=55 time=65.657 ms64 bytes from 1.1.1.1: seq=2 ttl=55 time=65.435 ms64 bytes from 1.1.1.1: seq=3 ttl=55 time=65.314 ms64 bytes from 1.1.1.1: seq=4 ttl=55 time=65.462 ms --- 1.1.1.1 ping statistics ---5 packets transmitted, 5 packets received, 0% packet lossround-trip min/avg/max = 65.314/65.809/67.178 ms
--- - LynwoodKB3VWG _______________________________________________ 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
Chris,
I also sync NTP from gw.ampr.org, is that gone as well?
- Lynwood On Saturday, April 6, 2024 at 12:58:40 PM EDT, lleachii@aol.com lleachii@aol.com wrote:
Chris, Also, you noted:
"don’t rely on doing zone transfers from that server for much longer."
Please provide an Authoritative Public DNS server that accepts Zone Transfers either on AMPRNet or Public. To my knowledge gw.ampr.org was the only one.
---
73,
LynwoodKB3VWG
On Saturday, April 6, 2024 at 12:48:41 PM EDT, lleachii@aol.com lleachii@aol.com wrote:
Chris,
"What is the A record hostname for that IP supposed to be? I can check if it’s in the zonefile or not - likely not - was it added only recently?"
That's the issue, it was not added recently- it's been there for years, since I first devised my internal network plan years ago:
kb3vwg-128.ampr.org
user@machine:~$ nslookup 44.60.44.128 44.0.0.1128.44.60.44.in-addr.arpa name = kb3vwg-128.ampr.org. It is in the zone file.
- Lynwood On Saturday, April 6, 2024 at 12:41:29 PM EDT, Chris via 44net 44net@mailman.ampr.org wrote:
So, we are in the process of moving the primary nameserver away from the UCSD gateway server so all it will be left with is acting as the IPIP encap/de-encap gateway function + rip44d, so don’t rely on doing zone transfers from that server for much longer. As to your egress problem, I checked on the gateway and your 44.60.44.128 IP is not in the filter list but your 44.60.44.1 IP is, that’s why it’s not working for 44.60.44.128. What is the A record hostname for that IP supposed to be? I can check if it’s in the zonefile or not - likely not - was it added only recently? 73, Chris - G1FEF — ARDC Administrator
Web: https://www.ardc.net
On 6 Apr 2024, at 12:02, lleachii--- via 44net 44net@mailman.ampr.org wrote: Chris,
I suspect some failure in the location that maintains what AMPR IPs have DNS entries - hence allowing FORWARD on AMPRGW. Rationale:
* My ingress TCP traces are blocked for 44.60.44.128, yet work for 44.60.44.1, 44.60.44.3 and 44.60.44.10
- On a side note, I also observe that on my DNS server (44.60.44.3) - that the 44.in-addr.arpa Zone seems to be failing (checking logs). I can no longer get authoritative answers, but I can still query 44.0.0.1 and get Zone Transfers (port 53/TCP) for AMPR.ORG. Was the Reverse Zone edited somehow?
- Lynwood
On Saturday, April 6, 2024 at 05:47:53 AM EDT, lleachii@aol.com lleachii@aol.com wrote:
Chris,
Another interesting observation occurred when testing egress from my LAN and router with various SRC IPs. My LAN is configured with a SNAT and IP/Rules to use 44.60.44.128 for traffic from a certain LAN SRC IP is set on the client.
* With my usual SNAT setting of SRC 44.60.44.128 - ping DOESN'T WORK* When pining from the router with 44.60.44.1 and changing the LAN SNAT rule to also use SRC 44.60.44.1 - ping WORKS
root@OpenWrt:~# ping -c 5 1.1.1.1 -I 44.60.44.1PING 1.1.1.1 (1.1.1.1) from 44.60.44.1: 56 data bytes64 bytes from 1.1.1.1: seq=0 ttl=55 time=67.178 ms64 bytes from 1.1.1.1: seq=1 ttl=55 time=65.657 ms64 bytes from 1.1.1.1: seq=2 ttl=55 time=65.435 ms64 bytes from 1.1.1.1: seq=3 ttl=55 time=65.314 ms64 bytes from 1.1.1.1: seq=4 ttl=55 time=65.462 ms --- 1.1.1.1 ping statistics ---5 packets transmitted, 5 packets received, 0% packet lossround-trip min/avg/max = 65.314/65.809/67.178 ms
--- - LynwoodKB3VWG _______________________________________________ 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
Not for now
On 6 Apr 2024, at 18:09, lleachii@aol.com wrote:
Chris,
I also sync NTP from gw.ampr.org, is that gone as well?
- Lynwood
On Saturday, April 6, 2024 at 12:58:40 PM EDT, lleachii@aol.com lleachii@aol.com wrote:
Chris,
Also, you noted:
"don’t rely on doing zone transfers from that server for much longer."
Please provide an Authoritative Public DNS server that accepts Zone Transfers either on AMPRNet or Public. To my knowledge gw.ampr.org was the only one.
73,
Lynwood KB3VWG
On Saturday, April 6, 2024 at 12:48:41 PM EDT, lleachii@aol.com lleachii@aol.com wrote:
Chris,
"What is the A record hostname for that IP supposed to be? I can check if it’s in the zonefile or not - likely not - was it added only recently?"
That's the issue, it was not added recently- it's been there for years, since I first devised my internal network plan years ago:
kb3vwg-128.ampr.org
user@machine:~$ nslookup 44.60.44.128 44.0.0.1 128.44.60.44.in-addr.arpa name = kb3vwg-128.ampr.org.
It is in the zone file.
- Lynwood
On Saturday, April 6, 2024 at 12:41:29 PM EDT, Chris via 44net 44net@mailman.ampr.org wrote:
So, we are in the process of moving the primary nameserver away from the UCSD gateway server so all it will be left with is acting as the IPIP encap/de-encap gateway function + rip44d, so don’t rely on doing zone transfers from that server for much longer.
As to your egress problem, I checked on the gateway and your 44.60.44.128 IP is not in the filter list but your 44.60.44.1 IP is, that’s why it’s not working for 44.60.44.128. What is the A record hostname for that IP supposed to be? I can check if it’s in the zonefile or not - likely not - was it added only recently?
73, Chris - G1FEF — ARDC Administrator
Web: https://www.ardc.net
On 6 Apr 2024, at 12:02, lleachii--- via 44net 44net@mailman.ampr.org wrote:
Chris,
I suspect some failure in the location that maintains what AMPR IPs have DNS entries - hence allowing FORWARD on AMPRGW.
Rationale:
- My ingress TCP traces are blocked for 44.60.44.128, yet work for 44.60.44.1, 44.60.44.3 and 44.60.44.10
On a side note, I also observe that on my DNS server (44.60.44.3) - that the 44.in-addr.arpa Zone seems to be failing (checking logs). I can no longer get authoritative answers, but I can still query 44.0.0.1 and get Zone Transfers (port 53/TCP) for AMPR.ORG. Was the Reverse Zone edited somehow?
Lynwood
On Saturday, April 6, 2024 at 05:47:53 AM EDT, lleachii@aol.com lleachii@aol.com wrote:
Chris,
Another interesting observation occurred when testing egress from my LAN and router with various SRC IPs. My LAN is configured with a SNAT and IP/Rules to use 44.60.44.128 for traffic from a certain LAN SRC IP is set on the client.
- With my usual SNAT setting of SRC 44.60.44.128 - ping DOESN'T WORK
- When pining from the router with 44.60.44.1 and changing the LAN SNAT rule to also use SRC 44.60.44.1 - ping WORKS
root@OpenWrt:~# ping -c 5 1.1.1.1 -I 44.60.44.1 PING 1.1.1.1 (1.1.1.1) from 44.60.44.1: 56 data bytes 64 bytes from 1.1.1.1: seq=0 ttl=55 time=67.178 ms 64 bytes from 1.1.1.1: seq=1 ttl=55 time=65.657 ms 64 bytes from 1.1.1.1: seq=2 ttl=55 time=65.435 ms 64 bytes from 1.1.1.1: seq=3 ttl=55 time=65.314 ms 64 bytes from 1.1.1.1: seq=4 ttl=55 time=65.462 ms
--- 1.1.1.1 ping statistics --- 5 packets transmitted, 5 packets received, 0% packet loss round-trip min/avg/max = 65.314/65.809/67.178 ms
- Lynwood
KB3VWG _______________________________________________ 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 mailto:44net@mailman.ampr.org To unsubscribe send an email to 44net-leave@mailman.ampr.org mailto:44net-leave@mailman.ampr.org
Hi Lynwood,
Please try again…?
73, Chris - G1FEF — ARDC Administrator
Web: https://www.ardc.net
On 6 Apr 2024, at 17:48, lleachii@aol.com wrote:
Chris,
"What is the A record hostname for that IP supposed to be? I can check if it’s in the zonefile or not - likely not - was it added only recently?"
That's the issue, it was not added recently- it's been there for years, since I first devised my internal network plan years ago:
kb3vwg-128.ampr.org
user@machine:~$ nslookup 44.60.44.128 44.0.0.1 128.44.60.44.in-addr.arpa name = kb3vwg-128.ampr.org.
It is in the zone file.
- Lynwood
On Saturday, April 6, 2024 at 12:41:29 PM EDT, Chris via 44net 44net@mailman.ampr.org wrote:
So, we are in the process of moving the primary nameserver away from the UCSD gateway server so all it will be left with is acting as the IPIP encap/de-encap gateway function + rip44d, so don’t rely on doing zone transfers from that server for much longer.
As to your egress problem, I checked on the gateway and your 44.60.44.128 IP is not in the filter list but your 44.60.44.1 IP is, that’s why it’s not working for 44.60.44.128. What is the A record hostname for that IP supposed to be? I can check if it’s in the zonefile or not - likely not - was it added only recently?
73, Chris - G1FEF — ARDC Administrator
Web: https://www.ardc.net
On 6 Apr 2024, at 12:02, lleachii--- via 44net 44net@mailman.ampr.org wrote:
Chris,
I suspect some failure in the location that maintains what AMPR IPs have DNS entries - hence allowing FORWARD on AMPRGW.
Rationale:
- My ingress TCP traces are blocked for 44.60.44.128, yet work for 44.60.44.1, 44.60.44.3 and 44.60.44.10
On a side note, I also observe that on my DNS server (44.60.44.3) - that the 44.in-addr.arpa Zone seems to be failing (checking logs). I can no longer get authoritative answers, but I can still query 44.0.0.1 and get Zone Transfers (port 53/TCP) for AMPR.ORG. Was the Reverse Zone edited somehow?
Lynwood
On Saturday, April 6, 2024 at 05:47:53 AM EDT, lleachii@aol.com lleachii@aol.com wrote:
Chris,
Another interesting observation occurred when testing egress from my LAN and router with various SRC IPs. My LAN is configured with a SNAT and IP/Rules to use 44.60.44.128 for traffic from a certain LAN SRC IP is set on the client.
- With my usual SNAT setting of SRC 44.60.44.128 - ping DOESN'T WORK
- When pining from the router with 44.60.44.1 and changing the LAN SNAT rule to also use SRC 44.60.44.1 - ping WORKS
root@OpenWrt:~# ping -c 5 1.1.1.1 -I 44.60.44.1 PING 1.1.1.1 (1.1.1.1) from 44.60.44.1: 56 data bytes 64 bytes from 1.1.1.1: seq=0 ttl=55 time=67.178 ms 64 bytes from 1.1.1.1: seq=1 ttl=55 time=65.657 ms 64 bytes from 1.1.1.1: seq=2 ttl=55 time=65.435 ms 64 bytes from 1.1.1.1: seq=3 ttl=55 time=65.314 ms 64 bytes from 1.1.1.1: seq=4 ttl=55 time=65.462 ms
--- 1.1.1.1 ping statistics --- 5 packets transmitted, 5 packets received, 0% packet loss round-trip min/avg/max = 65.314/65.809/67.178 ms
- Lynwood
KB3VWG _______________________________________________ 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 mailto:44net@mailman.ampr.org To unsubscribe send an email to 44net-leave@mailman.ampr.org mailto:44net-leave@mailman.ampr.org
Seems to be working now.
On 4/6/2024 1:33 PM, Chris via 44net wrote:
Hi Lynwood,
Please try again…?
73, Chris - G1FEF — ARDC Administrator
Web: https://www.ardc.net
On 6 Apr 2024, at 17:48, lleachii@aol.com wrote:
Chris,
/"What is the A record hostname for that IP supposed to be? I can check if it’s in the zonefile or not - likely not - was it added only recently?"/That's the issue, it was not added recently- it's been there for years, since I first devised my internal network plan years ago:
kb3vwg-128.ampr.org
user@machine:~$ nslookup 44.60.44.128 44.0.0.1 128.44.60.44.in-addr.arpa name = kb3vwg-128.ampr.org.
It is in the zone file.
- Lynwood
On Saturday, April 6, 2024 at 12:41:29 PM EDT, Chris via 44net 44net@mailman.ampr.org wrote:
So, we are in the process of moving the primary nameserver away from the UCSD gateway server so all it will be left with is acting as the IPIP encap/de-encap gateway function + rip44d, so don’t rely on doing zone transfers from that server for much longer.
As to your egress problem, I checked on the gateway and your 44.60.44.128 IP is not in the filter list but your 44.60.44.1 IP is, that’s why it’s not working for 44.60.44.128. What is the A record hostname for that IP supposed to be? I can check if it’s in the zonefile or not - likely not - was it added only recently?
73, Chris - G1FEF — ARDC Administrator
Web: https://www.ardc.net
On 6 Apr 2024, at 12:02, lleachii--- via 44net 44net@mailman.ampr.org wrote:
Chris,
I suspect some failure in the location that maintains what AMPR IPs have DNS entries - hence allowing FORWARD on AMPRGW.
Rationale:
- My ingress TCP traces are blocked for 44.60.44.128, yet work for
44.60.44.1, 44.60.44.3 and 44.60.44.10
- On a side note, I also observe that on my DNS server (44.60.44.3) -
that the 44.in-addr.arpa Zone seems to be failing (checking logs). I can no longer get authoritative answers, but I can still query 44.0.0.1 and get Zone Transfers (port 53/TCP) for AMPR.ORG. Was the Reverse Zone edited somehow?
- Lynwood
On Saturday, April 6, 2024 at 05:47:53 AM EDT, lleachii@aol.com lleachii@aol.com wrote:
Chris,
Another interesting observation occurred when testing egress from my LAN and router with various SRC IPs. My LAN is configured with a SNAT and IP/Rules to use 44.60.44.128 for traffic from a certain LAN SRC IP is set on the client.
- With my usual SNAT setting of SRC 44.60.44.128 - ping DOESN'T WORK
- When pining from the router with 44.60.44.1 and changing the LAN
SNAT rule to also use SRC 44.60.44.1 - ping WORKS
root@OpenWrt:~# ping -c 5 1.1.1.1 -I 44.60.44.1 PING 1.1.1.1 (1.1.1.1) from 44.60.44.1: 56 data bytes 64 bytes from 1.1.1.1: seq=0 ttl=55 time=67.178 ms 64 bytes from 1.1.1.1: seq=1 ttl=55 time=65.657 ms 64 bytes from 1.1.1.1: seq=2 ttl=55 time=65.435 ms 64 bytes from 1.1.1.1: seq=3 ttl=55 time=65.314 ms 64 bytes from 1.1.1.1: seq=4 ttl=55 time=65.462 ms
--- 1.1.1.1 ping statistics --- 5 packets transmitted, 5 packets received, 0% packet loss round-trip min/avg/max = 65.314/65.809/67.178 ms
- Lynwood
KB3VWG
Chris,
It's working now. What was the issue?
Thanks and 73,
LynwoodKB3VWG On Saturday, April 6, 2024 at 01:33:46 PM EDT, Chris via 44net 44net@mailman.ampr.org wrote:
Hi Lynwood, Please try again…? 73, Chris - G1FEF — ARDC Administrator
Web: https://www.ardc.net
On 6 Apr 2024, at 17:48, lleachii@aol.com wrote: Chris,
"What is the A record hostname for that IP supposed to be? I can check if it’s in the zonefile or not - likely not - was it added only recently?"
That's the issue, it was not added recently- it's been there for years, since I first devised my internal network plan years ago:
kb3vwg-128.ampr.org
user@machine:~$ nslookup 44.60.44.128 44.0.0.1128.44.60.44.in-addr.arpa name = kb3vwg-128.ampr.org. It is in the zone file.
- Lynwood On Saturday, April 6, 2024 at 12:41:29 PM EDT, Chris via 44net 44net@mailman.ampr.org wrote:
So, we are in the process of moving the primary nameserver away from the UCSD gateway server so all it will be left with is acting as the IPIP encap/de-encap gateway function + rip44d, so don’t rely on doing zone transfers from that server for much longer. As to your egress problem, I checked on the gateway and your 44.60.44.128 IP is not in the filter list but your 44.60.44.1 IP is, that’s why it’s not working for 44.60.44.128. What is the A record hostname for that IP supposed to be? I can check if it’s in the zonefile or not - likely not - was it added only recently? 73, Chris - G1FEF — ARDC Administrator
Web: https://www.ardc.net
On 6 Apr 2024, at 12:02, lleachii--- via 44net 44net@mailman.ampr.org wrote: Chris,
I suspect some failure in the location that maintains what AMPR IPs have DNS entries - hence allowing FORWARD on AMPRGW. Rationale:
* My ingress TCP traces are blocked for 44.60.44.128, yet work for 44.60.44.1, 44.60.44.3 and 44.60.44.10
- On a side note, I also observe that on my DNS server (44.60.44.3) - that the 44.in-addr.arpa Zone seems to be failing (checking logs). I can no longer get authoritative answers, but I can still query 44.0.0.1 and get Zone Transfers (port 53/TCP) for AMPR.ORG. Was the Reverse Zone edited somehow?
- Lynwood
On Saturday, April 6, 2024 at 05:47:53 AM EDT, lleachii@aol.com lleachii@aol.com wrote:
Chris,
Another interesting observation occurred when testing egress from my LAN and router with various SRC IPs. My LAN is configured with a SNAT and IP/Rules to use 44.60.44.128 for traffic from a certain LAN SRC IP is set on the client.
* With my usual SNAT setting of SRC 44.60.44.128 - ping DOESN'T WORK* When pining from the router with 44.60.44.1 and changing the LAN SNAT rule to also use SRC 44.60.44.1 - ping WORKS
root@OpenWrt:~# ping -c 5 1.1.1.1 -I 44.60.44.1PING 1.1.1.1 (1.1.1.1) from 44.60.44.1: 56 data bytes64 bytes from 1.1.1.1: seq=0 ttl=55 time=67.178 ms64 bytes from 1.1.1.1: seq=1 ttl=55 time=65.657 ms64 bytes from 1.1.1.1: seq=2 ttl=55 time=65.435 ms64 bytes from 1.1.1.1: seq=3 ttl=55 time=65.314 ms64 bytes from 1.1.1.1: seq=4 ttl=55 time=65.462 ms --- 1.1.1.1 ping statistics ---5 packets transmitted, 5 packets received, 0% packet lossround-trip min/avg/max = 65.314/65.809/67.178 ms
--- - LynwoodKB3VWG _______________________________________________ 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
_______________________________________________ 44net mailing list -- 44net@mailman.ampr.org To unsubscribe send an email to 44net-leave@mailman.ampr.org
Yep, hit me too!
73 - Bdale, KB0G
On April 3, 2024 4:15:24 PM MDT, Nathan Brookfield via 44net 44net@mailman.ampr.org wrote:
I've received the same, when trying to log-in I got an eULA that I can't actually click to accept, has anyone else had the same issue?
Nathan Brookfield | VK2NAB Director
NAB Investment Holdings Pty Ltd T/A Managed Networks W: http://nabih.com.au | E: Nathan.Brookfield@nabih.com.au | P: 0412 266 008
-----Original Message----- From: Patrick Thompson via 44net 44net@mailman.ampr.org Sent: Thursday, April 4, 2024 8:58 AM To: Dan Cross crossd@gmail.com Cc: Amprnet 44 Net 44net@mailman.ampr.org Subject: [44net] Re: New 44Net Portal coming 4/3!
I saw two of those notifications about subdomains but as you stated, no rights to see the ticket.
Thank you, Patrick
-----Original Message----- From: Dan Cross crossd@gmail.com Sent: Wednesday, April 3, 2024 16:44 To: Patrick Thompson patrick@pwthompson.net Cc: Rosy Schechter - KJ7RYV rosy@ardc.net; Amprnet 44 Net 44net@mailman.ampr.org Subject: Re: [44net] Re: New 44Net Portal coming 4/3!
On Wed, Apr 3, 2024 at 5:26 PM Patrick Thompson via 44net 44net@mailman.ampr.org wrote:
It states below it will not change the address assignments but where are our address assignments in the new portal??
Logging into the portal, I saw a notification about a new ticket that had been created related to that; I assume that's for importing the allocation information into the new portal, but I don't have permissions to view the ticket.
- Dan C.Thank you, Patrick
-----Original Message----- From: Rosy Schechter - KJ7RYV via 44net 44net@mailman.ampr.org Sent: Thursday, March 28, 2024 14:09 To: Amprnet 44 Net 44net@mailman.ampr.org Cc: newportal@ardc.net Subject: [44net] New 44Net Portal coming 4/3!
Hello, 44Net / AMPRNet Community!
I’m pleased to share that on Wednesday, April 3rd, at approximately 9am PDT / 4pm UTC, Chris G1FEF will release a new 44Net portal. We’ll give you a heads-up once we make the switch; expect some downtime starting at about 1am PDT / 8am UTC until launch time.
Here are the features the new portal will include:
- A new ticketing system to improve support response time
- DNS management
- Modern secure framework
- Improved UI/UX
- Capability to facilitate a pool of administrators
Of course, the portal upgrade will not change your address space assignment.
Also, along with any new launch – though we have done thorough testing with the TAC and staff– we expect that folks will find some bugs. We appreciate your patience should you find them, as well as your feedback.
If you have any questions in the meantime, please ask here or direct them to newportal@ardc.net.
73, Rosy KJ7RYV
-- Rosy Schechter - KJ7RYV Executive Director Amateur Radio Digital Communications (ARDC) ardc.net _______________________________________________ 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
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
The EULA worked fine here, scrolled to the bottom, checked the two boxes and clicked Accept. Chrome Version 123.0.6312.86. Though unlike our friend Tom M0LTE, I did not read it. 😊
Thank you, Patrick N5UYI
From: Bdale Garbee bdale@gag.com Sent: Wednesday, April 3, 2024 20:24 To: Nathan Brookfield Nathan.Brookfield@nabih.com.au; Nathan Brookfield via 44net 44net@mailman.ampr.org; Patrick Thompson patrick@pwthompson.net; Dan Cross crossd@gmail.com Cc: Amprnet 44 Net 44net@mailman.ampr.org Subject: Re: [44net] Re: New 44Net Portal coming 4/3!
Yep, hit me too!
73 - Bdale, KB0G
On April 3, 2024 4:15:24 PM MDT, Nathan Brookfield via 44net <44net@mailman.ampr.orgmailto:44net@mailman.ampr.org> wrote:
I've received the same, when trying to log-in I got an eULA that I can't actually click to accept, has anyone else had the same issue?
Nathan Brookfield | VK2NAB Director
NAB Investment Holdings Pty Ltd T/A Managed Networks W: http://nabih.com.au | E: Nathan.Brookfield@nabih.com.aumailto:Nathan.Brookfield@nabih.com.au | P: 0412 266 008
-----Original Message----- From: Patrick Thompson via 44net <44net@mailman.ampr.orgmailto:44net@mailman.ampr.org> Sent: Thursday, April 4, 2024 8:58 AM To: Dan Cross <crossd@gmail.commailto:crossd@gmail.com> Cc: Amprnet 44 Net <44net@mailman.ampr.orgmailto:44net@mailman.ampr.org> Subject: [44net] Re: New 44Net Portal coming 4/3!
I saw two of those notifications about subdomains but as you stated, no rights to see the ticket.
Thank you, Patrick
-----Original Message----- From: Dan Cross <crossd@gmail.commailto:crossd@gmail.com> Sent: Wednesday, April 3, 2024 16:44 To: Patrick Thompson <patrick@pwthompson.netmailto:patrick@pwthompson.net> Cc: Rosy Schechter - KJ7RYV <rosy@ardc.netmailto:rosy@ardc.net>; Amprnet 44 Net <44net@mailman.ampr.orgmailto:44net@mailman.ampr.org> Subject: Re: [44net] Re: New 44Net Portal coming 4/3!
On Wed, Apr 3, 2024 at 5:26 PM Patrick Thompson via 44net <44net@mailman.ampr.orgmailto:44net@mailman.ampr.org> wrote:
It states below it will not change the address assignments but where are our address assignments in the new portal??
Logging into the portal, I saw a notification about a new ticket that had been created related to that; I assume that's for importing the allocation information into the new portal, but I don't have permissions to view the ticket.
- Dan C.
Thank you, Patrick
-----Original Message----- From: Rosy Schechter - KJ7RYV via 44net <44net@mailman.ampr.orgmailto:44net@mailman.ampr.org> Sent: Thursday, March 28, 2024 14:09 To: Amprnet 44 Net <44net@mailman.ampr.orgmailto:44net@mailman.ampr.org> Cc: newportal@ardc.netmailto:newportal@ardc.net Subject: [44net] New 44Net Portal coming 4/3!
Hello, 44Net / AMPRNet Community!
I’m pleased to share that on Wednesday, April 3rd, at approximately 9am PDT / 4pm UTC, Chris G1FEF will release a new 44Net portal. We’ll give you a heads-up once we make the switch; expect some downtime starting at about 1am PDT / 8am UTC until launch time.
Here are the features the new portal will include:
* A new ticketing system to improve support response time * DNS management * Modern secure framework * Improved UI/UX * Capability to facilitate a pool of administrators
Of course, the portal upgrade will not change your address space assignment.
Also, along with any new launch – though we have done thorough testing with the TAC and staff– we expect that folks will find some bugs. We appreciate your patience should you find them, as well as your feedback.
If you have any questions in the meantime, please ask here or direct them to newportal@ardc.netmailto:newportal@ardc.net.
73, Rosy KJ7RYV
-- Rosy Schechter - KJ7RYV Executive Director Amateur Radio Digital Communications (ARDC) ardc.net
________________________________
44net mailing list -- 44net@mailman.ampr.orgmailto:44net@mailman.ampr.org To unsubscribe send an email to 44net-leave@mailman.ampr.orgmailto:44net-leave@mailman.ampr.org
________________________________
44net mailing list -- 44net@mailman.ampr.orgmailto:44net@mailman.ampr.org To unsubscribe send an email to 44net-leave@mailman.ampr.orgmailto:44net-leave@mailman.ampr.org
________________________________
44net mailing list -- 44net@mailman.ampr.orgmailto:44net@mailman.ampr.org To unsubscribe send an email to 44net-leave@mailman.ampr.orgmailto:44net-leave@mailman.ampr.org
________________________________
44net mailing list -- 44net@mailman.ampr.orgmailto:44net@mailman.ampr.org To unsubscribe send an email to 44net-leave@mailman.ampr.orgmailto:44net-leave@mailman.ampr.org
Got a response from Rebecca but my response was rejected by the mail server. Anyway, I was told my assignments would be in the Network menu but I do not have a Network menu available.
Thank you, Patrick
-----Original Message----- From: Rosy Schechter - KJ7RYV via 44net 44net@mailman.ampr.org Sent: Thursday, March 28, 2024 14:09 To: Amprnet 44 Net 44net@mailman.ampr.org Cc: newportal@ardc.net Subject: [44net] New 44Net Portal coming 4/3!
Hello, 44Net / AMPRNet Community!
I’m pleased to share that on Wednesday, April 3rd, at approximately 9am PDT / 4pm UTC, Chris G1FEF will release a new 44Net portal. We’ll give you a heads-up once we make the switch; expect some downtime starting at about 1am PDT / 8am UTC until launch time.
Here are the features the new portal will include:
* A new ticketing system to improve support response time * DNS management * Modern secure framework * Improved UI/UX * Capability to facilitate a pool of administrators
Of course, the portal upgrade will not change your address space assignment.
Also, along with any new launch – though we have done thorough testing with the TAC and staff– we expect that folks will find some bugs. We appreciate your patience should you find them, as well as your feedback.
If you have any questions in the meantime, please ask here or direct them to newportal@ardc.net.
73, Rosy KJ7RYV
-- Rosy Schechter - KJ7RYV Executive Director Amateur Radio Digital Communications (ARDC) ardc.net _______________________________________________ 44net mailing list -- 44net@mailman.ampr.org To unsubscribe send an email to 44net-leave@mailman.ampr.org
-
Bdale Garbee -
Charles Hargrove -
Charles Holliday -
Chris -
Damien Gardner -
Dan Cross -
David McAnally -
Jeff Parrish-Personal -
Jeremy Harmer -
kc8qba -
Leon Zetekoff -
lleachii＠aol.com -
Mark Van Daele -
Nathan Brookfield -
Patrick Thompson -
Rebecca Key -
Rosy Schechter - KJ7RYV -
Tom M0LTE