Greetings!
I have a /22 block of AMPRNet space. I've configured it for tunnel access, and defined the gateway in my portal. Following the instructions on the wiki, here is my router config:
interface GigabitEthernet0/0
ip address 44.48.8.1 255.255.252.0 secondary
ip address 96.82.54.108 255.255.255.240
duplex auto
speed auto
media-type rj45
end
interface Tunnel0
no ip address
tunnel source 96.82.54.108
tunnel mode ipip
tunnel destination 169.228.66.251
end
results of 'sh int tunnel0'
amprnet-router#sh int tunnel0
Tunnel0 is up, line protocol is up
Hardware is Tunnel
MTU 17920 bytes, BW 100 Kbit/sec, DLY 50000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation TUNNEL, loopback not set
Keepalive not set
Tunnel source 96.82.54.108, destination 169.228.66.251
Tunnel protocol/transport IP/IP
Tunnel TTL 255, Fast tunneling enabled
Tunnel transport MTU 1480 bytes
Tunnel transmit bandwidth 8000 (kbps)
Tunnel receive bandwidth 8000 (kbps)
Last input 00:02:16, output never, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/0 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
7024 packets input, 3500920 bytes, 0 no buffer
Received 0 broadcasts (0 IP multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
0 packets output, 0 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 unknown protocol drops
0 output buffer failures, 0 output buffers swapped out
At this point, I believe I need to get RIP running with the right options. However, this is where the wiki falls short. The only rip configs examples are for the linux daemons. Here is the output of 'sh ip prot'
amprnet-router#sh ip protocols
*** IP Routing is NSF aware ***
Routing Protocol is "rip"
Outgoing update filter list for all interfaces is not set
Incoming update filter list for all interfaces is not set
Sending updates every 30 seconds, next due in 13 seconds
Invalid after 180 seconds, hold down 180, flushed after 240
Redistributing: rip
Neighbor(s):
169.228.66.251
Default version control: send version 2, receive version 2
Automatic network summarization is in effect
Maximum path: 4
Routing for Networks:
44.0.0.0
Passive Interface(s):
GigabitEthernet0/0
GigabitEthernet0/1
VoIP-Null0
Routing Information Sources:
Gateway Distance Last Update
Distance: (default is 120)
As is standard practice, I've put all interfaces in passive-default, and then explicitly defined tunnel0 as non-passive. I have not been able to establish any sort of RIP adjacency:
amprnet-router#sh ip route rip
Codes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
o - ODR, P - periodic downloaded static route, H - NHRP, l - LISP
+ - replicated route, % - next hop override
Gateway of last resort is not set
amprnet-router#sh ip rip database
44.0.0.0/8 auto-summary
44.48.8.0/22 directly connected, GigabitEthernet0/0
Thanks in advance to anyone who can offer any guidance.
---
73,
Bill Atkinson, NF9K
ARRL Technical Specialist
ARRL VE/OO
Laurel VE
PODXS 070 Club #1595
30MDG #6014
www.nf9k.netwww.crossroadsdmr.org
> I received a 44 net allocation and am successfully advertising it to the internet via my ISP.
> I have been reading on the AMPRNet Wiki about IPIP tunnelling and Startampr. Are there best practices or anything else I need to be aware of before venturing into building the gateway?
It is advisable to make your system an IPIP tunnel gateway for the same subnet as you advertise via BGP.
Make sure you use a non-44 public IP for the tunnel.
> On a related note, I have been using OpenVPN to provide publicly routable /32 IP addresses to individual Windows PC. I don’t see support for IPIP on Windows, are there any other tunnelling methods worth looking at, for Windows7 specifically, or is OpenVPN my best bet?
We offer OpenVPN but beware: it allows an easy entry into the AMPRnet that has nothing to do with
amateur radio anymore. You just become a VPN provider like there already are so many on internet.
To do something amateur-radio related with AMPRnet you really should offer radio access and encourage
the users to use it, and OpenVPN works counter-productive in that regard.
Rob
Hi,
I am interested in accessing 44 Net number via BGP. What would be the best avenue to discuss this? I already sent a message using the “Contact Us” link on the portal. How would I go about it?
Thanks,
Adi
VA3ADI
On 1/12/17 1:19 PM, Jonathan Smith wrote:
> Anyone have the UT coordinator email, or know where I can find it?
I am the Utah coordinator. Based on the inquiry I checked my spam mail and
found what I believe is the subject request. This will be processed shortly.
Sorry for any inconvenience.
Ken - KD6OAT
On Thu, Jan 12, 2017 at 1:00 PM, <44net-request(a)hamradio.ucsd.edu> wrote:
> Send 44Net mailing list submissions to
> 44net(a)hamradio.ucsd.edu
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://hamradio.ucsd.edu/mailman/listinfo/44net
> or, via email, send a message with subject or body 'help' to
> 44net-request(a)hamradio.ucsd.edu
>
> You can reach the person managing the list at
> 44net-owner(a)hamradio.ucsd.edu
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of 44Net digest..."
>
>
> Today's Topics:
>
> 1. TrivnetDB (Brian)
> 2. Re: Allocation time (Jonathan Smith)
> 3. Re: Allocation time (Bryan Fields)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 12 Jan 2017 12:15:22 -0500
> From: Brian <n1uro(a)n1uro.ampr.org>
> To: 44net(a)hamradio.ucsd.edu
> Subject: [44net] TrivnetDB
> Message-ID: <1484241322.23614.13.camel@n1uro>
> Content-Type: text/plain; charset="utf-8"
>
> Is there someone from there on this list? If so please contact me
> offlist. Thanks.
> --
> I don't have to worry about body fitness in 2017. All I do is
> show my body to itself in the mirror and it throws plenty of
> fits.
> --------
> 73 de Brian - N1URO
> email: (see above)
> Web: http://www.n1uro.net/
> Ampr1: http://n1uro.ampr.org/
> Ampr2: http://nos.n1uro.ampr.org
> Linux Amateur Radio Services
> axMail-Fax & URONode
> http://uronode.sourceforge.net
> http://axmail.sourceforge.net
> AmprNet coordinator for:
> Connecticut, Delaware, Maine,
> Maryland, Massachusetts,
> New Hampshire, New Jersey, Pennsylvania,
> Rhode Island, and Vermont.
>
>
>
How long does it usually take for the coordinator to approve requests? I know the holidays will get in the way. I'm just wondering. I'm looking for some space in Utah.
Thanks.
Is there someone from there on this list? If so please contact me
offlist. Thanks.
--
I don't have to worry about body fitness in 2017. All I do is
show my body to itself in the mirror and it throws plenty of
fits.
--------
73 de Brian - N1URO
email: (see above)
Web: http://www.n1uro.net/
Ampr1: http://n1uro.ampr.org/
Ampr2: http://nos.n1uro.ampr.org
Linux Amateur Radio Services
axMail-Fax & URONode
http://uronode.sourceforge.nethttp://axmail.sourceforge.net
AmprNet coordinator for:
Connecticut, Delaware, Maine,
Maryland, Massachusetts,
New Hampshire, New Jersey, Pennsylvania,
Rhode Island, and Vermont.
I found the talk that was just released, by Brian, W9CR very informative.
Very good historical overview of IPv4 as well, highly recommend watching it.
https://www.youtube.com/watch?v=mkKOX5q1XJ4#t=04m20s
Steve, KB9MWR
Hello Paul G4APL.
Could you please contact me off the list
as I lost your e-mail address. Weird...
Thank you very much in advance.
Best regards.
---
Tom - SP2L
Sent from Xperia Z1 with AquaMail
http://www.aqua-mail.com
> If I don't hear from them in a week or two, I put a comment "awaiting
> response to email" in their coordination request and return it to them.
> Returned requests will expire in 3 months if no further action is taken
> and do not generate coordinator reminders.
In that case it is not so bad. However, my experience is that most users who do
not understand the portal (and of course there are more of those in my country,
because they have the language barrier in addition to the already complicated matter)
and get a request returned to them (previously this was called rejected, now it
is called returned) will always manage to click on the re-submit link. So
the ball is again in my park, and when I don't play it back to them, I get
the reminders. I have once got it returned 3 times this way.
Normally it is not a real problem when a requester does not come back after
requesting additional information, because (here) the original request usually
wasn't what they wanted anyway (we use the portal only for IPIP gateways).
Rob
> You're welcome. Yes, I don't get many requests during a year and I go
> through a learning curve every time I use the portal site.
I still have the problem that users (who have to use a non-native language) do not
understand the portal, make a request for something they do not want, and when I
reject it with an explanation what the need to do next (read our website, mail me)
they just click on all links in that reply mail causing the request to be re-submitted
with the comments that I have put in there myself.
We really need some button to just delete a request without notification to the
submitter, so that I can contact them out-of-band. When I just leave the bad
requests there will be "reminder" mails from the portal later.
Rob
