Differences

This shows you the differences between two versions of the page.

--- packet:ip [2024/09/27 18:16] – IP routing/gateway over packet gm5aug
+++ packet:ip [2024/09/27 18:21] (current) – [Linux kernel AX.25 support + kissattach] gm5aug
@@ Line 54: / Line 54: @@
 Specify a unique IP in the same subnet at each end, e.g. 10.0.0.1 and 10.0.0.2. You can use private (RFC1918) addresses, or any others you have allocated, eg from 44net.
+Note that if you already have a 44net IP address on an interface (for example a Wireguard tunnel), you will need to follow a slightly different method to configure the IP and subnet on ax0 (swapping the IP and subnet for your own):
+<code>
+sudo kissattach /dev/ttyACM0 myport
+sudo ip addr add 44.10.0.1/28 dev ax0
+</code>
 ''/dev/ttyACM0'' is the device path for a single NinoTNC, adjust as required.
@@ Line 238: / Line 246: @@
 This how-to presupposes you are able to SSH into the remote node. This node will serve as the gateway for routing Internet traffic over packet.
-While there may well be other ways, this is the script that Michael GM5AUG uses to switch the MB7NKL packet node between regular packet work, and IP traffic (with thanks to Martin M0NXP for his assistance in getting this running) to start the IP server up:
+While there may well be other ways, this is the script that Michael GM5AUG uses to switch the MB7NKL packet node between regular packet work, and start the server up for IP traffic (with thanks to Martin M0NXP for his assistance in getting this running):
-(you will need to modify the parts shown in *asterisks*)
+You will need to modify the parts shown in *asterisks*
 <code>