Configuring an AX.25 port - Revision history

DL5RB: Try to polish the table look.

2006-04-18T22:40:31Z

Try to polish the table look.

← Older revision		Revision as of 22:40, 18 April 2006
Line 349:		Line 349:
	Sequence is very important in this section, but if you stick with the suggested sequence it should work okay. The keywords and arguments are:		Sequence is very important in this section, but if you stick with the suggested sequence it should work okay. The keywords and arguments are:

	{\|		<blockquote style="background: white; border: 1px solid black; padding: 1em;">
			{\| class="wikitable" style="text-align:left"
	\| device \|\| this keyword must be the first line of a port definition and specifies the name of the special device file that the rest of the configuration applies to. e.g. /dev/scc0		\| device \|\| this keyword must be the first line of a port definition and specifies the name of the special device file that the rest of the configuration applies to. e.g. /dev/scc0
	\|-		\|-
Line 399:		Line 400:
	\| slip \|\| the KISS slip flag, the argument is an integer.		\| slip \|\| the KISS slip flag, the argument is an integer.
	\|}		\|}
			</blockquote>

	==== Using the driver ====		==== Using the driver ====

DL5RB: /* Channel Configuration */

2006-04-18T22:15:02Z

Channel Configuration

← Older revision		Revision as of 22:15, 18 April 2006
Line 349:		Line 349:
	Sequence is very important in this section, but if you stick with the suggested sequence it should work okay. The keywords and arguments are:		Sequence is very important in this section, but if you stick with the suggested sequence it should work okay. The keywords and arguments are:

	device		{\|
			\| device \|\| this keyword must be the first line of a port definition and specifies the name of the special device file that the rest of the configuration applies to. e.g. /dev/scc0
	this keyword must be the first line of a port definition and specifies the name of the special device file that the rest of the configuration applies to. e.g. /dev/scc0		\|-
	speed		\| speed \|\| this keyword specifies the speed in bits per second of the interface. The argument is an integer: e.g. 1200
			\|-
	this keyword specifies the speed in bits per second of the interface. The argument is an integer: e.g. 1200		\| clock \|\| this keyword specifies where the clock for the data will be sourced. Allowable values are:
	clock		{\|
			\| dpll \|\| normal halfduplex operation
	this keyword specifies where the clock for the data will be sourced. Allowable values are:		\|-
			\| external \|\| MODEM supplies its own Rx/Tx clock
	dpll		\|-
			\| divider \|\| use fullduplex divider if installed.
	normal halfduplex operation		\|}
	external		\|-
			\| mode \|\| this keyword specifies the data coding to be used. Allowable arguments are: nrzi or nrz
	MODEM supplies its own Rx/Tx clock		\|-
	divider		\| rxbuffers \|\| this keyword specifies the number of receive buffers to allocate memory for. The argument is an integer, e.g. 8.
			\|-
	use fullduplex divider if installed.		\| txbuffers \|\| this keyword specifies the number of transmit buffers to allocate memory for. The argument is an integer, e.g. 8.
			\|-
	mode		\| bufsize \|\| this keyword specifies the size of the receive and transmit buffers. The arguments is in bytes and represents the total length of the frame, so it must also take into account the AX.25 headers and not just the length of the data field. This keyword is optional and default to 384
			\|-
	this keyword specifies the data coding to be used. Allowable arguments are: nrzi or nrz		\| txdelay \|\| the KISS transmit delay value, the argument is an integer in ms.
	rxbuffers		\|-
			\| persist \|\| the KISS persist value, the argument is an integer.
	this keyword specifies the number of receive buffers to allocate memory for. The argument is an integer, e.g. 8.		\|-
	txbuffers		\| slot \|\| the KISS slot time value, the argument is an integer in ms.
			\|-
	this keyword specifies the number of transmit buffers to allocate memory for. The argument is an integer, e.g. 8.		\| tail \|\| the KISS transmit tail value, the argument is an integer in ms.
	bufsize		\|-
			\| fulldup \|\| the KISS full duplex flag, the argument is an integer. 1==Full Duplex, 0==Half Duplex.
	this keyword specifies the size of the receive and transmit buffers. The arguments is in bytes and represents the total length of the frame, so it must also take into account the AX.25 headers and not just the length of the data field. This keyword is optional and default to 384		\|-
	txdelay		\| wait \|\| the KISS wait value, the argument is an integer in ms.
			\|-
	the KISS transmit delay value, the argument is an integer in mS.		\| min \|\| the KISS min value, the argument is an integer in s.
	persist		\|-
			\| maxkey \|\| the KISS maximum keyup time, the argument is an integer in s.
	the KISS persist value, the argument is an integer.		\|-
	slot		\| idle \|\| the KISS idle timer value, the argument is an integer in s.
			\|-
	the KISS slot time value, the argument is an integer in mS.		\| maxdef \|\| the KISS maxdef value, the argument is an integer.
	tail		\|-
			\| group \|\| the KISS group value, the argument is an integer.
	the KISS transmit tail value, the argument is an integer in mS.		\|-
	fulldup		\| txoff \|\| the KISS txoff value, the argument is an integer in ms.
			\|-
	the KISS full duplex flag, the argument is an integer. 1==Full Duplex, 0==Half Duplex.		\| softdcd \|\| the KISS softdcd value, the argument is an integer.
	wait		\|-
			\| slip \|\| the KISS slip flag, the argument is an integer.
	the KISS wait value, the argument is an integer in mS.		\|}
	min

	the KISS min value, the argument is an integer in S.
	maxkey

	the KISS maximum keyup time, the argument is an integer in S.
	idle

	the KISS idle timer value, the argument is an integer in S.
	maxdef

	the KISS maxdef value, the argument is an integer.
	group

	the KISS group value, the argument is an integer.
	txoff

	the KISS txoff value, the argument is an integer in mS.
	softdcd

	the KISS softdcd value, the argument is an integer.
	slip

	the KISS slip flag, the argument is an integer.

	==== Using the driver ====		==== Using the driver ====

DL5RB: /* The sccstat and sccparam tools */

2006-04-18T22:02:35Z

The sccstat and sccparam tools

← Older revision		Revision as of 22:02, 18 April 2006
Line 438:		Line 438:
	To assist in the diagnosis of problems you can use the sccstat program to display the current configuration of an SCC device. To use it try:		To assist in the diagnosis of problems you can use the sccstat program to display the current configuration of an SCC device. To use it try:

	# sccstat /dev/scc0		<pre>
			# sccstat /dev/scc0
			</pre>

	you will displayed a very large amount of information relating to the configuration and health of the /dev/scc0 SCC port.		you will displayed a very large amount of information relating to the configuration and health of the /dev/scc0 SCC port.
Line 444:		Line 446:
	The sccparam command allows you to change or modify a configuration after you have booted. Its syntax is very similar to the NOS param command, so to set the txtail setting of a device to 100mS you would use:		The sccparam command allows you to change or modify a configuration after you have booted. Its syntax is very similar to the NOS param command, so to set the txtail setting of a device to 100mS you would use:

			<pre>
	# sccparam /dev/scc0 txtail 0x8		# sccparam /dev/scc0 txtail 0x8
			</pre>

	=== Creating a BPQ ethernet device ===		=== Creating a BPQ ethernet device ===

DL5RB: /* Creating the /etc/ax25/axports file */

2006-04-18T21:59:53Z

Creating the /etc/ax25/axports file

← Older revision		Revision as of 21:59, 18 April 2006
Line 497:		Line 497:
	The /etc/ax25/axports is a simple text file that you create with a text editor. The format of the /etc/ax25/axports file is as follows:		The /etc/ax25/axports is a simple text file that you create with a text editor. The format of the /etc/ax25/axports file is as follows:

			<pre>
	portname callsign baudrate paclen window description		portname callsign baudrate paclen window description
			</pre>

	where:		where:

	portname		{\| portname \|\| is a text name that you will refer to the port by.
			\|-
	is a text name that you will refer to the port by.		\| callsign \|\| is the AX.25 callsign you want to assign to the port.
	callsign		\|-
			\| baudrate \|\| is the speed at which you wish the port to communicate with your TNC.
	is the AX.25 callsign you want to assign to the port.		\|-
	baudrate		\| paclen \|\| is the maximum packet length you want to configure the port to use for AX.25 connected mode connections.
			\|-
	is the speed at which you wish the port to communicate with your TNC.		\| window \|\| is the AX.25 window (K) parameter. This is the same as the MAXFRAME setting of many TNC's.
	paclen		\|-
			\| description \|\| is a textual description of the port.
	is the maximum packet length you want to configure the port to use for AX.25 connected mode connections.		\|}
	window

	is the AX.25 window (K) parameter. This is the same as the MAXFRAME setting of many TNC's.
	description

	is a textual description of the port.

	In my case, mine looks like:		In my case, mine looks like:

DL5RB: More wikifcation. The table still looks ugly.

2006-04-18T21:54:36Z

More wikifcation. The table still looks ugly.

Show changes

DL5RB: Move KISS into KISS page.

2006-04-18T21:40:50Z

Move KISS into KISS page.

← Older revision		Revision as of 21:40, 18 April 2006
Line 5:		Line 5:
	The network device is what is listed when you use the `ifconfig' command. This is the object that the Linux kernel sends and receives network data from. Nearly always the network device has a physical port associated with it, but there are occasions where this isn't necessary. The network device does relate directly to a device driver.		The network device is what is listed when you use the `ifconfig' command. This is the object that the Linux kernel sends and receives network data from. Nearly always the network device has a physical port associated with it, but there are occasions where this isn't necessary. The network device does relate directly to a device driver.

	In the Linux AX.25 code there are a number of device drivers. The most common is probably the KISS driver, but others are the SCC driver(s), the Baycom driver and the ~~Soundmodem~~ driver.		In the Linux AX.25 code there are a number of device drivers. The most common is probably the [[KISS]] driver, but others are the SCC driver(s), the Baycom driver and the [[soundmodem]] driver.

	Each of these device drivers will create a network device when it is started.		Each of these device drivers will create a network device when it is started.

	~~=== Creating a KISS device ===~~

	~~<pre>~~
	~~Kernel Compile Options:~~

	~~Amateur Radio support --->~~
	~~[*] Amateur Radio support~~
	~~--- Packet Radio protocols~~
	~~<*> Amateur Radio AX.25 Level 2 protocol~~
	~~...~~
	~~AX.25 network device drivers --->~~
	~~--- AX.25 network device drivers~~
	~~<*> Serial port KISS driver~~
	~~...~~
	~~</pre>~~

	Probably the most common configuration will be for a [[KISS]] [[TNC]] on a serial port. You will need to have the TNC preconfigured and connected to your serial port. You can use a communications program like minicom or seyon to configure the TNC into kiss mode.

	~~To create a KISS device you use the kissattach program. In it simplest form you can use the kissattach program as follows:~~

	~~<pre>~~
	~~# /usr/sbin/kissattach /dev/ttyS0 radio 44.135.96.242~~
	~~# kissparms -p radio -t 100 -s 100 -r 25~~
	~~</pre>~~

	The kissattach command will create a KISS network device. These devices are called `ax[0-9]'. The first time you use the kissattach command it creates `ax0', the second time it creates `ax1' etc. Each KISS device has an associated serial port.

	~~The kissparms command allows you to set various KISS parameters on a KISS device.~~

	Specifically the example presented would create a KISS network device using the serial device `/dev/ttyS0' and the entry from the /etc/ax25/axports with a port name of `radio'. It then configures it with a txdelay and slottime of 100 milliseconds and a ppersist value of 25.

	~~Please refer to the man pages for more information.~~

	It is possible and occasionally useful to manually reissue the kissparms command, with your desired parameters as shown above, if you occasionally need to reload the specific parameters into a TNC that has had to be restarted or power-cycled, and the parameters are those that are not default for what the TNC comes up with when brought up cold. It can also be useful to include such a kissparms command on a crontab line so this happens periodically if the station is unattended and something goes wrong with the TNC. Kissparms output to the TNC also is displayed by the listen(1) monitoring command, if running with the -a switch which displays outgoing as well as incoming packets. -WB5AOH-

	~~==== Configuring for Dual Port TNC's ====~~

	The mkiss utility included in the ax25-utils distribution allows you to make use of both modems on a dual port TNC. Configuration is fairly simple. It works by taking a single serial device connected to a single multiport TNC and making it look like a number of devices each connected to a single port TNC. You do this before you do any of the AX.25 configuration. The devices that you then do the AX.25 configuration on are pseudo-TTY interfaces, (/dev/ttyq), and not the actual serial device. Pseudo-TTY devices create a kind of pipe through which programs designed to talk to tty devices can talk to other programs designed to talk to tty devices. Each pipe has a master and a slave end. The master end is generally called `/dev/ptyq' and the slave ends are called `/dev/ttyq*'. There is a one to one relationship between masters and slaves, so /dev/ptyq0 is the master end of a pipe with /dev/ttyq0 as its slave. You must open the master end of a pipe before opening the slave end. mkiss exploits this mechanism to split a single serial device into separate devices.

	~~Example: if you have a dual port TNC and it is connected to your /dev/ttyS0 serial device at 9600 bps, the command:~~

	~~<pre>~~
	~~# /usr/sbin/mkiss -s 9600 /dev/ttyS0 /dev/ptyq0 /dev/ptyq1~~
	~~# /usr/sbin/kissattach /dev/ttyq0 port1 44.135.96.242~~
	~~# /usr/sbin/kissattach /dev/ttyq1 port2 44.135.96.242~~
	~~</pre>~~

	would create two pseudo-tty devices that each look like a normal single port TNC. You would then treat /dev/ttyq0 and /dev/ttyq1 just as you would a conventional serial device with TNC connected. This means you'd then use the kissattach command as described above, on each of those, in the example for AX.25 ports called port1 and port2. You shouldn't use kissattach on the actual serial device as the mkiss program uses it.

	~~The mkiss command has a number of optional arguments that you may wish to use. They are summarized as follows:~~

	~~; -c : enables the addition of a one byte checksum to each KISS frame. This is not supported by most KISS implementations, it is supported by the G8BPG KISS ROM.~~
	~~; -s <speed> : sets the speed of the serial port.~~
	~~; -h : enables hardware handshaking on the serial port, it is off by default. Most KISS implementation do not support this, but some do.~~
	~~; -l : enables logging of information to the syslog log file.~~

	=== Creating a 6PACK device ===		=== Creating a 6PACK device ===

DL5RB: /* 6.1.1. Creating a KISS device */

2006-04-18T19:19:02Z

6.1.1. Creating a KISS device

← Older revision		Revision as of 19:19, 18 April 2006
Line 9:		Line 9:
	Each of these device drivers will create a network device when it is started.		Each of these device drivers will create a network device when it is started.

	=== ~~6.1.1.~~ Creating a KISS device ===		=== Creating a KISS device ===

			<pre>
	Kernel Compile Options:		Kernel Compile Options:

	Amateur Radio support --->		Amateur Radio support --->
	[*] Amateur Radio support		[*] Amateur Radio support
	--- Packet Radio protocols		--- Packet Radio protocols
	<*> Amateur Radio AX.25 Level 2 protocol		<*> Amateur Radio AX.25 Level 2 protocol
	...		...
	AX.25 network device drivers --->		AX.25 network device drivers --->
	--- AX.25 network device drivers		--- AX.25 network device drivers
	<*> Serial port KISS driver		<*> Serial port KISS driver
	...		...
			</pre>

	Probably the most common configuration will be for a [[KISS]] [[TNC]] on a serial port. You will need to have the TNC preconfigured and connected to your serial port. You can use a communications program like minicom or seyon to configure the TNC into kiss mode.		Probably the most common configuration will be for a [[KISS]] [[TNC]] on a serial port. You will need to have the TNC preconfigured and connected to your serial port. You can use a communications program like minicom or seyon to configure the TNC into kiss mode.
Line 27:		Line 29:
	To create a KISS device you use the kissattach program. In it simplest form you can use the kissattach program as follows:		To create a KISS device you use the kissattach program. In it simplest form you can use the kissattach program as follows:

	# /usr/sbin/kissattach /dev/ttyS0 radio 44.135.96.242		<pre>
	# kissparms -p radio -t 100 -s 100 -r 25		# /usr/sbin/kissattach /dev/ttyS0 radio 44.135.96.242
			# kissparms -p radio -t 100 -s 100 -r 25
			</pre>

	The kissattach command will create a KISS network device. These devices are called `ax[0-9]'. The first time you use the kissattach command it creates `ax0', the second time it creates `ax1' etc. Each KISS device has an associated serial port.		The kissattach command will create a KISS network device. These devices are called `ax[0-9]'. The first time you use the kissattach command it creates `ax0', the second time it creates `ax1' etc. Each KISS device has an associated serial port.

DL5RB: Remove soundmodem bits; they now have their own page.

2006-04-18T18:45:49Z

Remove soundmodem bits; they now have their own page.

← Older revision		Revision as of 18:45, 18 April 2006
Line 162:		Line 162:

	You may then treat the new AX.25 device as you would any other. You can configure it for TCP/IP, add it to ax25d and run NET/ROM or ROSE over it as you please.		You may then treat the new AX.25 device as you would any other. You can configure it for TCP/IP, add it to ax25d and run NET/ROM or ROSE over it as you please.

	~~=== Creating a kernel Soundmodem device ===~~

	~~Kernel Compile Options:~~

	~~Amateur Radio support --->~~
	~~[*] Amateur Radio support~~
	~~--- Packet Radio protocols~~
	~~<*> Amateur Radio AX.25 Level 2 protocol~~
	~~...~~
	~~AX.25 network device drivers --->~~
	~~--- AX.25 network device drivers~~
	~~...~~
	~~<*> Soundcard modem driver~~
	~~[?] soundmodem support for Soundblaster and compatible cards~~
	~~[?] soundmodem support for WSS and Crystal cards~~
	~~[?] soundmodem support for 1200 baud AFSK modulation~~
	~~[?] soundmodem support for 2400 baud AFSK modulation (7.3728MHz crystal)~~
	~~[?] soundmodem support for 2400 baud AFSK modulation (8MHz crystal)~~
	~~[?] soundmodem support for 2666 baud AFSK modulation~~
	~~[?] soundmodem support for 4800 baud HAPN-1 modulation~~
	~~[?] soundmodem support for 4800 baud PSK modulation~~
	~~[?] soundmodem support for 9600 baud FSK G3RUH modulation~~
	~~...~~

	Thomas Sailer has built a driver for the kernel that allows you to use your soundcard as a modem. Connect your radio directly to your soundcard to play packet! Thomas recommends at least a 486DX2/66 if you want to use this software as all of the digital signal processing is done by the main CPU.

	The driver currently emulates 1200 bps AFSK, 4800 HAPN and 9600 FSK (G3RUH compatible) modem types. The only sound cards currently supported are SoundBlaster and Windows Sound System Compatible models. If you have a sound card of another type, you can try the user-mode soundmodem described later in this document.

	The sound cards require some circuitry to help them drive the Push-To-Talk circuitry, and information on this is available from Thomas's Soundmodem PTT circuit web page. There are quite a few possible options, they are: detect the sound output from the soundcard, or use output from a parallel port, serial port or MIDI port. Circuit examples for each of these are on Thomas's site.

	~~The Soundmodem driver creates network devices called: sm0, sm1, sm2 etc when it is configured.~~

	~~Note~~

	The Soundmodem driver competes for the same resources as the Linux sound driver, so if you wish to use the Soundmodem driver you must ensure that the Linux sound driver is not installed. You can, of course, compile them both as modules and insert and remove them as you wish.

	~~==== Configuring the sound card ====~~

	The Soundmodem driver does not initialize the sound card. The ax25-utils package includes a utility to do this called `setcrystal' that may be used for sound cards based on the Crystal chip set. If you have some other card then you will have to use some other software to initialize it. Its syntax is fairly straightforward:

	~~setcrystal [-w wssio] [-s sbio] [-f synthio] [-i irq] [-d dma] [-c dma2]~~

	~~So, for example, if you wished to configure a SoundBlaster card at i/o base address 0x388, irq 10 and DMA 1 you would use:~~

	~~# setcrystal -s 0x388 -i 10 -d 1~~

	~~To configure a Window Sound System card at i/o base address 0x534, irq 5, DMA 3 you would use:~~

	~~# setcrystal -w 0x534 -i 5 -d 3~~

	~~The [-f synthio] parameter is the set the synthesizer address, and the [-c dma2] parameter is to set the second DMA channel to allow full duplex operation.~~

	~~==== Configuring the Soundmodem driver ====~~

	~~When you have configured the soundcard you need to configure the driver telling it where the sound card is located and what sort of modem you wish it to emulate.~~

	The sethdlc utility allows you to configure the driver with these parameters, or, if you have only one soundcard installed you may specify the parameters on the insmod command line when you load the Soundmodem module.

	~~For example, a simple configuration, with one SoundBlaster soundcard configured as described above emulating a 1200 bps modem:~~

	~~# insmod hdlcdrv~~
	~~# insmod soundmodem mode="sbc:afsk1200" iobase=0x220 irq=5 dma=1~~

	~~This is not really the preferred way to do it. The sethdlc utility works just as easily with one device as with many.~~

	The sethdlc man page has the full details, but a couple of examples will illustrate the most important aspects of this configuration. The following examples assume you have already loaded the Soundmodem modules using:

	~~# insmod hdlcdrv~~
	~~# insmod soundmodem~~

	~~or that you compiled the kernel with the driver inbuilt.~~

	~~Configure the driver to support the Windows Sound System card we configured above to emulate a G3RUH 9600 compatible modem as device sm0 using a parallel port at 0x378 to key the Push-To-Talk:~~

	~~# sethdlc -p -i sm0 mode wss:fsk9600 io 0x534 irq 5 dma 3 pario 0x378~~

	~~Configure the driver to support the SoundBlaster card we configured above to emulate a 4800 bps HAPN modem as device sm1 using the serial port located at 0x2f8 to key the Push-To-Talk:~~

	~~# sethdlc -p -i sm1 mode sbc:hapn4800 io 0x388 irq 10 dma 1 serio 0x2f8~~

	~~Configure the driver to support the SoundBlaster card we configured above to emulate a 1200 bps AFSK modem as device sm1 using the serial port located at 0x2f8 to key the Push-To-Talk:~~

	~~# sethdlc -p -i sm1 mode sbc:afsk1200 io 0x388 irq 10 dma 1 serio 0x2f8~~

	~~==== Configuring the AX.25 channel access parameters ====~~

	~~The AX.25 channel access parameters are the equivalent of the KISS ppersist, txdelay and slottime type parameters. You use the sethdlc utility for this as well.~~

	~~Again the sethdlc man page is the source of the most complete information but another example of two won't hurt:~~

	~~Configure the sm0 device with TxDelay of 100 mS, SlotTime of 50mS, PPersist of 128 and full duplex:~~

	~~# sethdlc -i sm0 -a txd 100 slot 50 ppersist 128 full~~

	~~Note that the timing values are in milliseconds.~~

	~~==== Setting the audio levels and tuning the driver ====~~

	It is very important that the audio levels be set correctly for any radio based modem to work. This is equally true of the Soundmodem. Thomas has developed some utility programs that make this task easier. They are called smdiag and smmixer.

	~~smdiag~~

	~~provides two types of display, either an oscilloscope type display or an eye pattern type display.~~
	~~smmixer~~

	~~allows you to actually adjust the transmit and receive audio levels.~~

	~~To start the smdiag utility in 'eye' mode for the Soundmodem device sm0 you would use:~~

	~~# smdiag -i sm0 -e~~

	~~To start the smmixer utility for the Soundmodem device sm0 you would use:~~

	~~# smmixer -i sm0~~

	~~==== Configuring the Kernel AX.25 to use the Soundmodem ====~~

	~~The Soundmodem driver creates standard network devices that the AX.25 Kernel code can use. Configuration is much the same as that for a PI or PacketTwin card.~~

	~~The first step is to configure the device with an AX.25 callsign. The ifconfig utility may be used to perform this.~~

	~~# /sbin/ifconfig sm0 hw ax25 VK2KTJ-15 up~~

	~~will assign the Soundmodem device sm0 the AX.25 callsign VK2KTJ-15. Alternatively you can use the axparms command, but you still need the ifconfig utility to bring the device up:~~

	~~# ifconfig sm0 up~~
	~~# axparms -setcall sm0 vk2ktj-15~~

	The next step is to create an entry in the /etc/ax25/axports file as you would for any other device. The entry in the axports file is associated with the network device you've configured by the callsign you configure. The entry in the axports file that has the callsign that you configured the Soundmodem device with is the one that will be used to refer to it.

	~~You may then treat the new AX.25 device as you would any other. You can configure it for TCP/IP, add it to ax25d and run NET/ROM or ROSE over it as you please.~~

	~~=== Creating a user-mode Soundmodem device ===~~

	~~Kernel Compile Options: not applicable~~

	~~Thomas Sailer has written a sound modem driver that runs in user-mode using the kernel sound drivers, so it should work with any sound card supported under Linux.~~

	The driver is implemented as the user-mode program soundmodem. The graphical soundmodemconfig program allows configuring and testing the soundmodem driver. As well as kernel sound support you need the kernel AX.25 mkiss driver.

	~~The software and documentation can be downloaded from http://www.baycom.org/~tom/ham/soundmodem.~~

	=== Creating a YAM device ===		=== Creating a YAM device ===

DL5RB: /* Configuring the AX.25 channel access parameters = */

2006-04-18T18:33:57Z

Configuring the AX.25 channel access parameters =

← Older revision		Revision as of 18:33, 18 April 2006
Line 247:		Line 247:
	# sethdlc -p -i sm1 mode sbc:afsk1200 io 0x388 irq 10 dma 1 serio 0x2f8		# sethdlc -p -i sm1 mode sbc:afsk1200 io 0x388 irq 10 dma 1 serio 0x2f8

	==== Configuring the AX.25 channel access parameters =====		==== Configuring the AX.25 channel access parameters ====

	The AX.25 channel access parameters are the equivalent of the KISS ppersist, txdelay and slottime type parameters. You use the sethdlc utility for this as well.		The AX.25 channel access parameters are the equivalent of the KISS ppersist, txdelay and slottime type parameters. You use the sethdlc utility for this as well.

DL5RB: /* Creating a 6PACK device */

2006-04-18T18:33:03Z

Creating a 6PACK device

← Older revision		Revision as of 18:33, 18 April 2006
Line 76:		Line 76:
	...		...

	6PACK is a protocol that is supported by some TNCs as an alternative to KISS. It is used in a similar fashion to the KISS driver, using the slattach command instead of kissattach.		[[6PACK]] is a protocol that is supported by some TNCs as an alternative to KISS. It is used in a similar fashion to the KISS driver, using the slattach command instead of kissattach.

	A mini HOWTO on the 6PACK driver is included in the kernel source code as the file /usr/src/linux/Documentation/networking/6pack.txt.		A mini HOWTO on the 6PACK driver is included in the kernel source code as the file /usr/src/linux/Documentation/networking/6pack.txt.