Ubuntu Linux Gateway Example - Revision history

KI5QKX: mw push

2026-04-30T18:52:28Z

mw push

← Older revision		Revision as of 18:52, 30 April 2026
Line 472:		Line 472:
	At this point you should be able to connect "ham" devices to the "ham" network interface <tt>eth2</tt> and be able to reach the internet.		At this point you should be able to connect "ham" devices to the "ham" network interface <tt>eth2</tt> and be able to reach the internet.

			[[Category:How-To]]
	[[Category:How-To Guides]]		[[Category:How-To Guides]]
	[[Category:Infrastructure]]		[[Category:Infrastructure]]
	[[Category:Gateways]]		[[Category:Gateways]]

KI5QKX: mw push

2026-03-01T00:14:21Z

mw push

← Older revision		Revision as of 00:14, 1 March 2026
Line 474:		Line 474:

	[[Category:How-To Guides]]		[[Category:How-To Guides]]
			[[Category:Infrastructure]]
			[[Category:Gateways]]

KI5QKX: mw push

2026-02-28T23:20:07Z

mw push

← Older revision		Revision as of 23:20, 28 February 2026
Line 39:		Line 39:
	On the Dell I've installed [http://www.ubuntu.com/ Ubuntu 12.04 LTS] (the 32-bit server version). With one exception all of the software you will need for the gateway you can get with the server.		On the Dell I've installed [http://www.ubuntu.com/ Ubuntu 12.04 LTS] (the 32-bit server version). With one exception all of the software you will need for the gateway you can get with the server.

	====Installing ~~Required~~ Linux ~~Software~~====		==== Installing required Linux software ====
	Install the Ubuntu Linux Distribution on your gateway hardware following the instructions on Ubuntu's web site.		Install the Ubuntu Linux Distribution on your gateway hardware following the instructions on Ubuntu's web site.

Line 75:		Line 75:

	====Obtain a "Static" IPv4 from your ISP====		====Obtain a "Static" IPv4 from your ISP====
	=====What is a "~~Static~~" IP ?=====		===== What is a "static" IP ? =====
	Normally your ISP assigns your router a public IPv4 address dynamically from a pool of IPv4 addresses shared by many customers.		Normally your ISP assigns your router a public IPv4 address dynamically from a pool of IPv4 addresses shared by many customers.
	This means that your Public IPv4 address can change periodically and without notice. Usually this isn't a big issue for most normal users, however it can cause problems when trying implement an AMPRNet gateway.		This means that your Public IPv4 address can change periodically and without notice. Usually this isn't a big issue for most normal users, however it can cause problems when trying implement an AMPRNet gateway.
Line 93:		Line 93:
	Please make sure you copy this information down carefully and verify it with your ISP. Your gateway will not work correctly without it!		Please make sure you copy this information down carefully and verify it with your ISP. Your gateway will not work correctly without it!

	====Decide on ~~Private~~ IPv4 ~~Addresses~~ for "~~Non~~-Ham" ~~Devices~~====		==== Decide on private IPv4 addresses for "non-Ham" devices ====
	Your "non-ham" devices will need their own IP Addresses, separate from AMPRNet. Normally these addresses are assigned from what is known as [http://en.wikipedia.org/wiki/RFC1918#Private_IPv4_address_spaces private address space]. Your gateway will take care of routing traffic to and from this private address space to the public Internet.		Your "non-ham" devices will need their own IP Addresses, separate from AMPRNet. Normally these addresses are assigned from what is known as [http://en.wikipedia.org/wiki/RFC1918#Private_IPv4_address_spaces private address space]. Your gateway will take care of routing traffic to and from this private address space to the public Internet.

Line 114:		Line 114:
	* DNS Name Servers : 8.8.8.8, 8.8.4.4 (I use Google's DNS Servers because my ISP doesn't allow queries from subnets other than their own)		* DNS Name Servers : 8.8.8.8, 8.8.4.4 (I use Google's DNS Servers because my ISP doesn't allow queries from subnets other than their own)

	==Setting up the ISP (~~Internet~~) ~~Interface~~==		== Setting up the ISP (internet) interface ==
	===Configuring the interface===		===Configuring the interface===
	To configure the ISP Interface, type the following command to edit the file <tt>/etc/networking/interfaces</tt>:		To configure the ISP Interface, type the following command to edit the file <tt>/etc/networking/interfaces</tt>:
Line 164:		Line 164:
	Don't continue to the next steps until you are successfully able to get the gateway connected to the Internet.		Don't continue to the next steps until you are successfully able to get the gateway connected to the Internet.

	==Setting up the "~~Non~~-Ham" ~~Network Interface~~==		== Setting up the "non-Ham" network interface ==
	Now we need to configure things so that you can connect your "non-ham" devices to the Internet.		Now we need to configure things so that you can connect your "non-ham" devices to the Internet.

	===Configuring the ~~Interface~~===		=== Configuring the interface ===
	Once again you will need to edit the file <tt>/etc/network/interfaces</tt> by type the following:		Once again you will need to edit the file <tt>/etc/network/interfaces</tt> by type the following:
	<code><pre>sudo nano /etc/network/interfaces</pre></code>		<code><pre>sudo nano /etc/network/interfaces</pre></code>
Line 184:		Line 184:
	</pre></code>		</pre></code>

	===Setting up DHCP===		=== Setting up DHCP ===
	DHCP stands for Dynamic Host Configuration Protocol and is used to assign IP addresses to hosts dynamically.		DHCP stands for Dynamic Host Configuration Protocol and is used to assign IP addresses to hosts dynamically.
	To configure DHCP for our "non-ham" devices you will need to edit the file <tt>/etc/dhcp/dhcpd.conf</tt>.		To configure DHCP for our "non-ham" devices you will need to edit the file <tt>/etc/dhcp/dhcpd.conf</tt>.
Line 229:		Line 229:
	Save the file and restart your gateway with <tt>sudo shutdown -r now</tt>.		Save the file and restart your gateway with <tt>sudo shutdown -r now</tt>.

	==Setting up the ~~Firewall~~ (~~Part~~ 1)==		== Setting up the firewall (part 1) ==
	Now will we need to setup the Firewall using <tt>iptables</tt>.		Now will we need to setup the Firewall using <tt>iptables</tt>.
	The [http://www.cyberciti.biz/tips/linux-iptables-examples.html following article]gives a good overview of <tt>iptables</tt>.		The [http://www.cyberciti.biz/tips/linux-iptables-examples.html following article]gives a good overview of <tt>iptables</tt>.
Line 236:		Line 236:
	# Help protect your gateway and "non-ham" devices.		# Help protect your gateway and "non-ham" devices.

	===What is NAT?===		=== What is NAT? ===
	NAT stands for Network Address Translation.		NAT stands for Network Address Translation.

Line 248:		Line 248:
	from the Internet gets back to the right device.		from the Internet gets back to the right device.

	===Setting up NAT===		=== Setting up NAT ===
	Setting up NAT for our "non-ham" devices requires the following command:		Setting up NAT for our "non-ham" devices requires the following command:
	'''(Be sure to substitute your "static" IP address in the <tt>--to-source</tt> option)'''		'''(Be sure to substitute your "static" IP address in the <tt>--to-source</tt> option)'''
Line 256:		Line 256:
	</pre></code>		</pre></code>

	===Protecting the ~~Gateway~~===		=== Protecting the gateway ===
	First, we need to define our default Firewall Policies:		First, we need to define our default Firewall Policies:
	* DROP all traffic headed for our gateway		* DROP all traffic headed for our gateway
Line 280:		Line 280:
	</pre></code>		</pre></code>

	===Protecting the "~~Non~~-Ham" ~~Network~~===		=== Protecting the "non-Ham" network ===
	Now we need to allow connections from the "non-ham" network to the Internet and allow the returning traffic from the Internet back to the "non-ham" network.		Now we need to allow connections from the "non-ham" network to the Internet and allow the returning traffic from the Internet back to the "non-ham" network.
	<code><pre>		<code><pre>
Line 299:		Line 299:

	==Setting up the Local "Ham" Network (AMPRNet) Interface==		==Setting up the Local "Ham" Network (AMPRNet) Interface==
	===Configuring the ~~Interface~~===		=== Configuring the interface ===
	Once again you will need to edit the file <tt>/etc/network/interfaces</tt> by typing the following:		Once again you will need to edit the file <tt>/etc/network/interfaces</tt> by typing the following:
	<code><pre>sudo nano /etc/network/interfaces</pre></code>		<code><pre>sudo nano /etc/network/interfaces</pre></code>
Line 317:		Line 317:
	</pre></code>		</pre></code>

	===More DHCP===		=== More DHCP ===
	To configure DHCP for our "ham" devices you will need to edit the file <tt>/etc/dhcp/dhcpd.conf</tt> again.		To configure DHCP for our "ham" devices you will need to edit the file <tt>/etc/dhcp/dhcpd.conf</tt> again.
	<code><pre>		<code><pre>
Line 431:		Line 431:
	</pre></code>		</pre></code>

	==Setting up the ~~Firewall~~ (~~Part~~ 2)==		== Setting up the firewall (part 2) ==
	===Forwarding ~~Traffic~~ to "~~Ham~~" ~~Devices~~===		=== Forwarding traffic to "ham" devices ===
	You will need to add the following <tt>iptables</tt> rules to allow traffic to and from your local AMPRNet subnet and the global AMPRNet and allow your "ham" devices to obtain IP addresses via DHCP.		You will need to add the following <tt>iptables</tt> rules to allow traffic to and from your local AMPRNet subnet and the global AMPRNet and allow your "ham" devices to obtain IP addresses via DHCP.

KI5QKX at 20:21, 12 December 2024

2024-12-12T20:21:33Z

← Older revision		Revision as of 20:21, 12 December 2024
Line 471:		Line 471:
	==Testing==		==Testing==
	At this point you should be able to connect "ham" devices to the "ham" network interface <tt>eth2</tt> and be able to reach the internet.		At this point you should be able to connect "ham" devices to the "ham" network interface <tt>eth2</tt> and be able to reach the internet.


			[[Category:How-To Guides]]

Kb3vwg: new AMPRGW IP

2017-05-26T20:19:12Z

new AMPRGW IP

← Older revision		Revision as of 20:19, 26 May 2017
Line 418:		Line 418:
	## Configure static routes		## Configure static routes
	# Default route for table 44 is to send traffic to amprnet gateway at UCSD		# Default route for table 44 is to send traffic to amprnet gateway at UCSD
	ip route add default dev ampr0 via 169.228.66.~~251~~ onlink table 44		ip route add default dev ampr0 via 169.228.34.84 onlink table 44

	# Route packets for our net to local interface (put your AMPRNet Subnet here)		# Route packets for our net to local interface (put your AMPRNet Subnet here)

Kb3vwg at 08:46, 3 August 2015

2015-08-03T08:46:17Z

← Older revision		Revision as of 08:46, 3 August 2015
Line 1:		Line 1:
	The following are the steps necessary to create a general purpose gateway to AMPRNet using an Ubuntu Linux Server.		The following are the steps necessary to create a general purpose gateway to AMPRNet using an Ubuntu Linux Server.
	'''(NOTE: A script has been developed to ~~automate many~~ of ~~these tasks~~, see: [[startampr]])'''		'''(NOTE: A script has been developed to streamline setup of a [[Gateway]], see: [[startampr]])'''

	==Cautions==		==Cautions==

Kb3vwg at 08:45, 3 August 2015

2015-08-03T08:45:43Z

← Older revision		Revision as of 08:45, 3 August 2015
Line 1:		Line 1:
	The following are the steps necessary to create a general purpose gateway to AMPRNet using an Ubuntu Linux Server.		The following are the steps necessary to create a general purpose gateway to AMPRNet using an Ubuntu Linux Server.
			'''(NOTE: A script has been developed to automate many of these tasks, see: [[startampr]])'''

	==Cautions==		==Cautions==

Njohnson at 02:51, 5 April 2014

2014-04-05T02:51:27Z

← Older revision		Revision as of 02:51, 5 April 2014
Line 26:		Line 26:
	(Click on the image to enlarge).		(Click on the image to enlarge).

	[[File:AMPRNetGatewayDiagram.png\| ~~200~~ px]]		[[File:AMPRNetGatewayDiagram.png\| 500 px]]

	==Prerequisites (What do I need to get started?)==		==Prerequisites (What do I need to get started?)==

Njohnson at 02:49, 5 April 2014

2014-04-05T02:49:31Z

← Older revision		Revision as of 02:49, 5 April 2014
Line 1:		Line 1:
	~~'''''THIS IS A ROUGH DRAFT'''''~~

	~~'''Please send comments, additions, corrections, and suggestions to <tt>n0sfh at erudicon.com</tt>'''~~

	The following are the steps necessary to create a general purpose gateway to AMPRNet using an Ubuntu Linux Server.		The following are the steps necessary to create a general purpose gateway to AMPRNet using an Ubuntu Linux Server.

Njohnson: /* Cautions */

2014-04-02T02:42:56Z

Cautions

← Older revision		Revision as of 02:42, 2 April 2014
Line 11:		Line 11:
	* '''Be sure to be aware of the security implications of performing these steps. While the steps here try to maximize security for your "non-ham" devices, be aware that these steps may expose those devices to hackers, criminals, and script-kiddies'''.		* '''Be sure to be aware of the security implications of performing these steps. While the steps here try to maximize security for your "non-ham" devices, be aware that these steps may expose those devices to hackers, criminals, and script-kiddies'''.

	To paraphrase from the Broadband-Hamnet(tm) folks:		Finally, to paraphrase from the Broadband-Hamnet(tm) folks:

	'''As with ANY piece of Ham radio gear, AMPRNet COULD be used illegally, and it is the control operator's duty to make sure it is being used in accordance with your local Amateur Radio rules.'''		'''As with ANY piece of Ham radio gear, AMPRNet COULD be used illegally, and it is the control operator's duty to make sure it is being used in accordance with your local Amateur Radio rules.'''