If your router can be configured to forward IPIP (IP protocol 4) to your 44ENCAP address then that is the better solution, but if not you should be able to put the address specified in the 44ENCAP line into the DMZ.

73, John

-----Original Message----- From: 44Net [mailto:44net-bounces+john.wiseman=cantab.net@hamradio.ucsd.edu] On Behalf Of Dale Yanz Sent: 05 January 2016 05:41 To: 'AMPRNet working group' Subject: Re: [44net] locked

(Please trim inclusions from previous messages) _______________________________________________ Thanks

I'm currently using a D-Link DIR-615 Which one would fit the bill ??

Dale KJ6IX

-----Original Message----- From: 44Net [mailto:44net-bounces+kj6ix=arrl.net@hamradio.ucsd.edu] On Behalf Of Don Poaps Sent: Monday, January 04, 2016 9:36 PM To: AMPRNet working group Subject: Re: [44net] locked

(Please trim inclusions from previous messages) _______________________________________________ Dale

I got the same message in BPQ32 console. My Router would not let IPIP in or Out. N9PMO routing AMPR net via BPQ to my system. Util I can get a Router that with route IPIP. I'm stuck.

Don va7dgp

On Monday, 4 January 2016, Dale Yanz kj6ix_n6spk@charter.net wrote:

(Please trim inclusions from previous messages) _______________________________________________ Hi All

Question is that am I being locked out ?

44.125.10.0/24 0 0.0.0.0 E 0 0 Locked

Dale KJ6IX

-------------- next part -------------- An HTML attachment was scrubbed... URL: < http://hamradio.ucsd.edu/mailman/private/44net/attachments/20160104/ec 252401/attachment.html

...

---

44Net mailing list 44Net@hamradio.ucsd.edu javascript:; http://hamradio.ucsd.edu/mailman/listinfo/44net

-- *Don Poaps* *New Westminster, BC* *VA7DGP*

I did reset my router dmz to 44ENCAP ip 192.168.1.10

OK THIS IS WHERE IM AT !!!

My BPQ32 Console is NOW SHOWING ROUTE TO 44/8FOUND !!! :) :)

MAKING HEADWAY !!!!

Going to take a brake for a bit and go from here !!!

73's Dale KJ6IX

-----Original Message----- From: 44Net [mailto:44net-bounces+kj6ix=arrl.net@hamradio.ucsd.edu] On Behalf Of Dale Yanz Sent: Tuesday, January 05, 2016 9:22 AM To: 'AMPRNet working group' Subject: Re: [44net] locked

(Please trim inclusions from previous messages) _______________________________________________ Thanks John

I'm going to be working on that this morning. I was having problems with trying to do this last nite as I'm going to give it another try this morning. I'll let you know how it turns out.

Dale KJ6IX

-----Original Message----- From: 44Net [mailto:44net-bounces+kj6ix=arrl.net@hamradio.ucsd.edu] On Behalf Of John Wiseman Sent: Tuesday, January 05, 2016 1:34 AM To: 'AMPRNet working group' Subject: Re: [44net] locked

(Please trim inclusions from previous messages) _______________________________________________ If your router can be configured to forward IPIP (IP protocol 4) to your 44ENCAP address then that is the better solution, but if not you should be able to put the address specified in the 44ENCAP line into the DMZ.

73, John

-----Original Message----- From: 44Net [mailto:44net-bounces+john.wiseman=cantab.net@hamradio.ucsd.edu] On Behalf Of Dale Yanz Sent: 05 January 2016 05:41 To: 'AMPRNet working group' Subject: Re: [44net] locked

(Please trim inclusions from previous messages) _______________________________________________ Thanks

I'm currently using a D-Link DIR-615 Which one would fit the bill ??

Dale KJ6IX

-----Original Message----- From: 44Net [mailto:44net-bounces+kj6ix=arrl.net@hamradio.ucsd.edu] On Behalf Of Don Poaps Sent: Monday, January 04, 2016 9:36 PM To: AMPRNet working group Subject: Re: [44net] locked

(Please trim inclusions from previous messages) _______________________________________________ Dale

I got the same message in BPQ32 console. My Router would not let IPIP in or Out. N9PMO routing AMPR net via BPQ to my system. Util I can get a Router that with route IPIP. I'm stuck.

Don va7dgp

On Monday, 4 January 2016, Dale Yanz kj6ix_n6spk@charter.net wrote:

(Please trim inclusions from previous messages) _______________________________________________ Hi All

Question is that am I being locked out ?

44.125.10.0/24 0 0.0.0.0 E 0 0 Locked

Dale KJ6IX

-------------- next part -------------- An HTML attachment was scrubbed... URL: < http://hamradio.ucsd.edu/mailman/private/44net/attachments/20160104/ec 252401/attachment.html

...

---

44Net mailing list 44Net@hamradio.ucsd.edu javascript:; http://hamradio.ucsd.edu/mailman/listinfo/44net

-- *Don Poaps* *New Westminster, BC* *VA7DGP*

Hi Ronen,

Your message to “contact us” was forwarded to your co-ordinator. I will ask Brian to look into the whereabouts of your co-ordinator.

Regards, Chris

On 7 Jan 2016, at 20:52, Drorap drorap@netvision.net.il wrote:

(Please trim inclusions from previous messages) _______________________________________________ Hi there Im waiting 3 month for network allocation (i used to be a coordinator long ago and did handle it myself) I have sent a request and got no reply I have followed the info in the portal and aftew a month send mail to the "contact us" and got no reply is someone read the contact us ? Please advice I want to try and re alive our Wireless network that used to work 15 years ago THanks Forward Ronen - 4Z4ZQ http://www.ronen.org

---

This email is free from viruses and malware because avast! Antivirus protection is active. https://www.avast.com/antivirus

---

44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net

Your message to “contact us” was forwarded to your co-ordinator. I will ask Brian to look into the whereabouts of your co-ordinator.

Delays of months and years by coordinators continues to be heard of - why aren't there coordinator teams instead of individuals. Then if one is busy somebody else can immediately take care of it. Or better yet - automate the whole process. In these days - tasks like this should take milliseconds, not months..

Bill

On Fri, Jan 08, 2016 at 09:34:16AM -0800, Bill Vodall wrote:

Delays of months and years by coordinators continues to be heard of - why aren't there coordinator teams instead of individuals. Then if one is busy somebody else can immediately take care of it. Or better yet - automate the whole process. In these days - tasks like this should take milliseconds, not months..

On the contrary Bill, it may be too automated already. We have a continuing problem with ineligible people requesting addresses and registering gateways; we currently need to keep knowledgeable people in the loop to reduce the probability of our network being abused or used for abuse.

We have a constant problem with finding volunteers to do coordination.

The question of automating address assignment has been looked into; about the only way it could be done would be if we had a secure method of making sure that the applicant is a bona fide ham radio operator. At the moment, the only known automated way of doing this is to use Logbook of the World certificates, which greatly restricts the number of people who could prove their eligibility and has its own set of problems.

Teams are a good idea. I think there are a few already. - Brian