[Xastir] ax25 devices

[victor alger]

Thanks for the info below!!!  I think I see what happens.  If I treat the ax 
device as another network "card, node, or whatever" I can communicate between 
computers and applications on another "network" completetly seperate from the 
one I use as the main "public one" so to speak.  The whole range of ports on 
this device or devices are available as long as there are applications 
listening on these devices.  I think....  Is that a true statement.... 
because if it is, it opends a whole another way to do some of the things I 
want to do here....  I did not realize that I could use the "ifup" to start 
the device.....   And yes, Suse all the way, I have abandoned all other 
distros I have tried, for good!!

Thanks again,  I am going to have some more fun...

On Wednesday 25 February 2004 12:54, N1OFZ wrote:
> First off what distro are you running?  And do you have AX.25 compiled
> into the kernel (not necessary for SuSE, hence the distro question)?
>
> If you do then all you have to do is add the device to the axports
> file.  If you want to add a serial device such as a KISS tnc you have
> to do a kissattach first.  Something like the DRSI card you just do an
> ifup.  Here are some examples from my system:
>
> from my rc.local:
> /sbin/ifconfig scc0 hw ax25 N1OFZ-5       --- my DRSI card
> /sbin/ifconfig scc0 192.168.17.71 netmask 255.255.255.0 mtu 512 up
> /usr/sbin/kissattach -l /dev/ttyD000 ax0 192.168.17.73   --- my MFJ
> 1270B in KISS mode
>
> from my axports file:
> scc0    N1OFZ-5 0       	255     2       drsi port 1
> scc1    N1OFZ-7 0       	255     2       drsi port 2
> ax0     N1OFZ-6 4800    	255     4       mfj 1270B on APRS
>
> ifconfig:
> ax0       Link encap:AMPR AX.25  HWaddr N1OFZ-6
>            inet addr:192.168.17.73  Bcast:192.168.17.255
> Mask:255.255.255.0
>            UP BROADCAST RUNNING  MTU:255  Metric:1
>            RX packets:3300 errors:0 dropped:0 overruns:0 frame:0
>            TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>            collisions:0 txqueuelen:10
>            RX bytes:272575 (266.1 Kb)  TX bytes:0 (0.0 b)
>
>
> eth0      Link encap:Ethernet  HWaddr 00:00:94:A9:83:02
>            inet addr:192.168.17.70  Bcast:192.168.17.255
> Mask:255.255.255.0
>            inet6 addr: fe80::200:94ff:fea9:8302/64 Scope:Link
>            UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>            RX packets:2289015 errors:1 dropped:0 overruns:0 frame:0
>            TX packets:1487272 errors:0 dropped:0 overruns:0 carrier:0
>            collisions:0 txqueuelen:100
>            RX bytes:365836617 (348.8 Mb)  TX bytes:305787386 (291.6 Mb)
>            Interrupt:12 Base address:0xe400
>
> lo        Link encap:Local Loopback
>            inet addr:127.0.0.1  Mask:255.0.0.0
>            inet6 addr: ::1/128 Scope:Host
>            UP LOOPBACK RUNNING  MTU:16436  Metric:1
>            RX packets:27813 errors:0 dropped:0 overruns:0 frame:0
>            TX packets:27813 errors:0 dropped:0 overruns:0 carrier:0
>            collisions:0 txqueuelen:0
>            RX bytes:2878159 (2.7 Mb)  TX bytes:2878159 (2.7 Mb)
>
> scc0      Link encap:AMPR AX.25  HWaddr N1OFZ-5
>            inet addr:192.168.17.71  Mask:255.255.255.0
>            UP RUNNING  MTU:512  Metric:1
>            RX packets:2443 errors:303226 dropped:0 overruns:0 frame:0
>            TX packets:2904 errors:6 dropped:0 overruns:0 carrier:0
>            collisions:0 txqueuelen:16
>            RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
>
> Let me know if this helps,
> Dana
> N1OFZ
>
> On Feb 25, 2004, at 12:06 PM, victor alger wrote:
> > AM I correct than an ax25 device such as ax0 or ax1 can be given a
> > tcpip
> > address and used like a network device.  If so how does one assign the
> > address and port, and what ports can one use?