Hi,
I’m following the instructions at the below link to use OpenWRT as a 44Net gateway. I’m confused about some of the instructions. What should <AMPRGW> be replace with in the route.
This has me confused as well:
“an interface instance for a new VLAN and bridge (the example above uses AMPRNET), add it to its own firewall zone using Input: Accept (if you wish for you AMPRLAN devices to reach the router), Output: Accept and Forward: Drop (or Reject). Assign an IP from your allocation to this interface, you will configure this IP on your devices as the Default Route/Gateway address.”
I created the AMPRNET interface but i put the 44Net allocation ip in the gateway of that interface, reboot after doing everything else, I get an error from Ampr-ripd that the interface doesn’t exist.
If anyone has done this on a OpenWRT router, would you be willing to share your firewall and network config files so that I can learn what I’m doing wrong.
http://wiki.ampr.org/wiki/Setting_up_a_gateway_on_OpenWRT
Thanks
Roger
VA7LBB
Also - from your post, did you follow the steps to install IP-full so the startup script would create the tunnel interface?
In addition, did you compile ampr-ripd?
null
Roger,
AMPRGW should be replaced with the IP of AMPRGW.See: http://wiki.ampr.org/wiki/Services for those details.
You don't need a "Gateway" to the tunnel, as it's a Layer 3. You do need to assign an IP from your range to a VLAN/bridge if you will make a: VLAN, port/ SSID, etc. for your allocation to "live."
What issues are you having with network and firewall configs?You never actually said what's wrong.
Feel free to ask me any more questions, or private email me for landline.
73,
- Lynwood
KB3VWG
-----Original Message-----
From: 44net-request <44net-request(a)mailman.ampr.org>
To: 44net <44net(a)mailman.ampr.org>
Sent: Tue, Jan 8, 2019 3:00 pm
Subject: 44Net Digest, Vol 8, Issue 3
Send 44Net mailing list submissions to
44net(a)mailman.ampr.org
To subscribe or unsubscribe via the World Wide Web, visit
https://mailman.ampr.org/mailman/listinfo/44net
or, via email, send a message with subject or body 'help' to
44net-request(a)mailman.ampr.org
You can reach the person managing the list at
44net-owner(a)mailman.ampr.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of 44Net digest..."
Today's Topics:
1. OpenWRT AMPRNet config (Roger)
----------------------------------------------------------------------
Message: 1
Date: Mon, 7 Jan 2019 12:32:53 -0800
From: Roger <va7lbb(a)rezgas.com>
To: 44net(a)mailman.ampr.org
Subject: [44net] OpenWRT AMPRNet config
Message-ID: <CC7E3091-3982-478B-A5C2-7F83E5D0AE30(a)rezgas.com>
Content-Type: text/plain; charset=utf-8
Hi,
I?m following the instructions at the below link to use OpenWRT as a 44Net gateway. I?m confused about some of the instructions. What should <AMPRGW> be replace with in the route.
This has me confused as well:
?an interface instance for a new VLAN and bridge (the example above uses AMPRNET), add it to its own firewall zone using Input: Accept (if you wish for you AMPRLAN devices to reach the router), Output: Accept and Forward: Drop (or Reject). Assign an IP from your allocation to this interface, you will configure this IP on your devices as the Default Route/Gateway address.?
I created the AMPRNET interface but i put the 44Net allocation ip in the gateway of that interface, reboot after doing everything else, I get an error from Ampr-ripd that the interface doesn?t exist.
If anyone has done this on a OpenWRT router, would you be willing to share your firewall and network config files so that I can learn what I?m doing wrong.
http://wiki.ampr.org/wiki/Setting_up_a_gateway_on_OpenWRT
Thanks
Roger
VA7LBB
------------------------------
Subject: Digest Footer
_______________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
------------------------------
End of 44Net Digest, Vol 8, Issue 3
***********************************
Hi,
I’m following the instructions at the below link to use OpenWRT as a 44Net gateway. I’m confused about some of the instructions. What should <AMPRGW> be replace with in the route.
This has me confused as well:
“an interface instance for a new VLAN and bridge (the example above uses AMPRNET), add it to its own firewall zone using Input: Accept (if you wish for you AMPRLAN devices to reach the router), Output: Accept and Forward: Drop (or Reject). Assign an IP from your allocation to this interface, you will configure this IP on your devices as the Default Route/Gateway address.”
I created the AMPRNET interface but i put the 44Net allocation ip in the gateway of that interface, reboot after doing everything else, I get an error from Ampr-ripd that the interface doesn’t exist.
If anyone has done this on a OpenWRT router, would you be willing to share your firewall and network config files so that I can learn what I’m doing wrong.
http://wiki.ampr.org/wiki/Setting_up_a_gateway_on_OpenWRT
Thanks
Roger
VA7LBB
> AWS instances have private IPs that are mapped (elsewhere) to a public
IP, at no point does the public IP/Network exist on the AWS instance.
That was true for legacy EC2. Now days, instances are launched in VPCs
where you can choose to use your own public or private IPs directly on the
network interfaces. You can also now have multiple interfaces on an
instance.
On Mon, Jan 7, 2019, 07:14 Jim Popovitch via 44Net <44net(a)mailman.ampr.org
wrote:
> On Mon, 2019-01-07 at 16:06 +0100, Toussaint OTTAVI wrote:
> > The right question would be :
> > On an AWS instance, is it possible to have another public (non-
> > AMPRNet) IP, so that we can build a tunnel to where we want, and route
> > our AMPRNet subnet through it ?
> >
> > Moreover, I never tried Amazon cloud services, but Microsoft Azure has
> > a built-in VPN system. It's possible to established IPSec tunnels
> > between Azure VMs and a local router. I saw Amazon has a feature
> > called "VPC" (Virtual Private Cloud). I don't know it it's the same
> > thing, and if it's suitable to connect AWS instances with local
> > resources via a VPN.
> >
>
> I think the general problems with doing any forwarding/routing on an AWS
> instance is their layer 3 abstraction foo. AWS instances have private
> IPs that are mapped (elsewhere) to a public IP, at no point does the
> public IP/Network exist on the AWS instance.
>
> -Jim P.
>
> _________________________________________
> 44Net mailing list
> 44Net(a)mailman.ampr.org
> https://mailman.ampr.org/mailman/listinfo/44net
>
Hi all,
We are already announcing a subnet with BGP via a low-cost virtual
instance at Vultr. It works fine. As we'll soon deploy our second data
center, and we'll start migrating from our old-style 10.44.0.0/16
private addressing to full AMPRNet addressing, I was wondering if I
could find a second low-cost BGP provider for redundancy.
I saw that Amazon now provides "Bring your Own IP" features :
https://aws.amazon.com/fr/blogs/networking-and-content-delivery/introducing…
Did someone already tried it ? Would it be suitable for AMPRNet
announcement ? Is this feature available outside of the U.S ? Amazon
seems to provide free account during one year. Are there any volunteers
to try out ?
73 QRO & Happy New Year de TK1BI
I am trying to setup a Cisco 2921/K9 router. The router has 3 gigabit ethernet ports and a CISCO EHWIC-4ESG 4-Port Gigabit WAN Interface Card<https://www.ebay.com/itm/CISCO-EHWIC-4ESG-4-Port-Gigabit-WAN-Interface-Card…>. I can not get a static IP address from Spectrum so I need to set up a tunnel. Does anyone has have any dealing with this type of setup. I am looking for a way to where to start from.
73's
David A. Pechon Sr. KA5TTZ
U.S. Army Retired (SSG/SS)
Cell # (985)520-1748
HAMSHACK HOTLINE #4525
Since taking on a BGP routed /24 several weeks ago I've occasionally
watched my gateway firewall logs in realtime to get a sense of how much
traffic I get from the Internet at large for my little section of the
AMPRNet.
I get an average of 2.7 packets a second in random scanning traffic.
Scaling this up to the /8 that comprises AMPRNet, I surmise that the UCSD
gateway must get something like 176k packets a second. Assuming an average
SYN packet of 20 bytes, this is something like 283 gigabytes per day.
Is that about right, Brian?
-J
