diff options
Diffstat (limited to 'ax25ipd/README.ax25ipd')
| -rw-r--r-- | ax25ipd/README.ax25ipd | 42 |
1 files changed, 21 insertions, 21 deletions
diff --git a/ax25ipd/README.ax25ipd b/ax25ipd/README.ax25ipd index 0af2cce..bfc12d8 100644 --- a/ax25ipd/README.ax25ipd +++ b/ax25ipd/README.ax25ipd @@ -1,7 +1,7 @@ -** +** ** This file is a cobbling together of the various notes on ax25ipd. -** +** ax25ipd ======= @@ -30,10 +30,10 @@ run on BSD should not present too many issues, there has been no attempt to retain BSD(Sun) operability since it was updated in an environment where there was no access to BSD. - ax25ipd requires a serial port, and uses a raw socket to gain access -to the IP layer of the host's TCP/IP implementation (this requires that -ax25ipd be started by root). ax25ipd also supports using a standard UDP -socket in place of the raw socket, although this does not adhere to + ax25ipd requires a serial port, and uses a raw socket to gain access +to the IP layer of the host's TCP/IP implementation (this requires that +ax25ipd be started by root). ax25ipd also supports using a standard UDP +socket in place of the raw socket, although this does not adhere to RFC1226. @@ -96,7 +96,7 @@ myalias ILSUN beacon every 540 btext ax25ipd -- digi ka9wsb-7 -- Experimental IP encapsulator loglevel 2 -route W1AW-13 handbook.arrl.com +route W1AW-13 handbook.arrl.com route WZ9ZZZ last.one.edu param 1 20 @@ -160,7 +160,7 @@ using ax25ipd to carry AX.25 traffic. device /dev/ttya device /dev/ttya speed 9600 speed 1200 route W1AW-5 fish.sea.com route KA9WSB-3 one.two.com - + Using this setup, a user could run AX.25 connections between the two PCs. Note that while NOS can digipeat, NOS will not automatically allow users near W1AW-5 to digipeat through it to reach KA9WSB-3 (i.e. the command @@ -203,7 +203,7 @@ Sample Configuration - digi-to-digi device /dev/ttya device /dev/ttya speed 9600 speed 9600 route W1AW-5 fish.sea.com route KA9WSB-3 one.two.com - param 1 20 param 1 33 + param 1 20 param 1 33 In this setup, the UNIX hosts are "on the air". No PCs or additional hardware are required. A user near W1AW-5 could read a user near KA9WSB-3 @@ -214,9 +214,9 @@ would work just fine. --------- We have added dual port capibility in DIGI MODE ONLY to allow us to use it -with a Dataengine. Very little needed changing, but we did not document the +with a Dataengine. Very little needed changing, but we did not document the changes. If you really need to know, diff the package against the original, -which was/is at sunsite.unc.edu. To specify the second port, do something +which was/is at sunsite.unc.edu. To specify the second port, do something like this... #to use the second port, we need to be in digi mode @@ -226,19 +226,19 @@ mode digi mycall ve3djf-12 myalias vhfdjf # -#port 1 on my tnc goes to uhf. -#The callsign and alias must be different for this to work right... +#port 1 on my tnc goes to uhf. +#The callsign and alias must be different for this to work right... mycall2 ve3djf-13 myalias2 uhfdjf # -Everything else is the same. Note that if you leave out the mycall2 and +Everything else is the same. Note that if you leave out the mycall2 and myalias2 defines, it works just like the original in single port mode. For recieving on the KISS (dual) port, packets are checked against both callsigns -and aliases. Whoever is on the other end of the AXIP link can find out what -port it came from by looking at the who it got digi'd through, although -I can't think of any reason to do that... For transmiting, you go out the -port with the callsign matching the digi address. For example, to go out +and aliases. Whoever is on the other end of the AXIP link can find out what +port it came from by looking at the who it got digi'd through, although +I can't think of any reason to do that... For transmiting, you go out the +port with the callsign matching the digi address. For example, to go out port 0 in the above example, digi through ve3djf-12 or vhfdjf. To go out port 1, digi through ve3djf-13 or uhfdjf. @@ -246,11 +246,11 @@ Deficencies: If you specify the same callsign on both ports, no error is generated, but the way the logic in the code works you always go out the upper port (port 1), not port 0. In TNC mode, there is really no way to specify which port to transmit on that I can think of, so -there is no multiplexing there. Everything goes out port 0 in TNC mode +there is no multiplexing there. Everything goes out port 0 in TNC mode still. Lastly, none of the dump routines know anything about ports on the KISS interface, so they look the same, with both ports lumped into one. -Let us know if you like this hack, BTW. In retrospect, we should have +Let us know if you like this hack, BTW. In retrospect, we should have written a KISSPlexor (tm:-) HIHI. I think we will do that next. @@ -260,7 +260,7 @@ VE3DJF@bbs.VE3RPI.ampr.org AXIP (IP encapsulation of AX.25 frames) daemon by Michael Westerhof. - + |