diff options
Diffstat (limited to 'ax25rtd/README.ax25rtd')
| -rw-r--r-- | ax25rtd/README.ax25rtd | 28 |
1 files changed, 14 insertions, 14 deletions
diff --git a/ax25rtd/README.ax25rtd b/ax25rtd/README.ax25rtd index fe7a241..0c6a080 100644 --- a/ax25rtd/README.ax25rtd +++ b/ax25rtd/README.ax25rtd @@ -41,7 +41,7 @@ ipax0 dg1kjd-10 76800 256 7 IP-encap device * Klaus Kudielka (klaus.kudielka@ieee.org). * ***************************************************************** -Just a quick small README... +Just a quick small README... This will hopefully go into the man pages ASAP. Ax25routed @@ -53,7 +53,7 @@ This is a daemon that: - emulates the ceased "autorouter" of Linux Kernel AX.25 - sets up ARP entries automagically -- may adjust IP routes and encapsulation mode +- may adjust IP routes and encapsulation mode (although I really do not recomment to use this feature...) The "autorouter" is not really an autorouter. It just listens to the AX.25 @@ -90,7 +90,7 @@ ip-maxroutes 256 ax25-learn-routes no Set this to "yes", ax25rtd will add the routing information - for every heard frame (with complete digipeater path) to the + for every heard frame (with complete digipeater path) to the kernel AX.25 routing table. Note that ax25rtd's internal cache will be updated anyway, regardless of this option. @@ -120,16 +120,16 @@ ip-learn-routes no If set to "yes", ax25rtd will modify the IP routing table if it receives an IP frame (directed to us). This is dangerous! - It should not screw up your routing table, though. Ax25rtd - recognizes the netmask of the device and will adjust the route + It should not screw up your routing table, though. Ax25rtd + recognizes the netmask of the device and will adjust the route only if it fits the netmask and the old route points to one of the devices ax25rtd knows about (hence an AX.25 device). The problems begin if you have more than one port and a user - is able to hear your outgoing traffic on at least two of them. - Due to technical reasons ax25rtd adjusts the route _after_ the - kernel has sent the reply to the received TCP frame already. - This has technical reasons. + is able to hear your outgoing traffic on at least two of them. + Due to technical reasons ax25rtd adjusts the route _after_ the + kernel has sent the reply to the received TCP frame already. + This has technical reasons. If the remote does the same both are switching between the two ports. @@ -162,8 +162,8 @@ ip-adjust-mode no The problem with this option is that the kernel AX.25 sends a received IP frame to the IP layer regardless if it was - sent in UI frame encapsulation "mode datagram (dg)" or - in I frame encaps, hence in an AX.25 connection, "mode virtual + sent in UI frame encapsulation "mode datagram (dg)" or + in I frame encaps, hence in an AX.25 connection, "mode virtual connect (vc)". The Linux kernel will respond to this frame before ax25rtd can adjust the mode. If the remote does the same... You get the picture. @@ -172,7 +172,7 @@ ip-adjust-mode no arp-add no - This option, if set to "yes", changes the ARP table to the + This option, if set to "yes", changes the ARP table to the source callsign of the received frame. It should be harmless, just has the the effect that if it is a new entry, the Linux ARP code will send one ARP request before ax25rtd has adjust @@ -248,7 +248,7 @@ ax25rtctl -q ax25rtctl --version ax25rtctl -V - + Guess what... @@ -275,7 +275,7 @@ The commands recognized on this socket are: add ax25 <callsign> <dev> <time> [<digipeater>] Add an AX.25 route add ip <ip> <dev> <time> <call> <mode> - Add an IP route & mode + Add an IP route & mode del ax25 <callsign> <dev> Remove an AX.25 route from cache an kernel routing table |