| |
VK7AX > FBBDIG 17.08.08 00:30l 275 Lines 8083 Bytes #999 (0) @ WW
BID : VK7AX-1708XX
Read: GUEST
Subj: xfbb Digest, Vol 41, Issue 3
Path: IZ3LSV<IK2XDE<DB0RES<DK0WUE<ON0BEL<VK7AX
Sent: 080816/2230Z @:VK7AX.#ULV.TAS.AUS.OC #:50982 [Ulverstone] FBB7.00g $:VK7A
From: VK7AX@VK7AX.#ULV.TAS.AUS.OC
To : FBBDIG@WW
Today's Topics:
1. Re: Unproto and beacon problem (Bo Skoglund)
2. Re: Unproto and beacon problem (Marco Di Martino (IW2OHX))
----------------------------------------------------------------------
Message: 1
Date: Fri, 15 Aug 2008 13:38:12 +0200
From: "Bo Skoglund" <bose63(AT)algonet.se>
Subject: Re: [xfbb] Unproto and beacon problem
To: "List for the LINUX version of FBB" <xfbb(AT)f6fbb.org>
Message-ID: <1980C1E8AB7140D1A45E325E71BFE2CD(AT)serimner>
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
reply-type=original
Hi Marco.
What I can see from your mail is that you are trying to send FBB-beacons
on FBB port3.
Port 3 is an AXIP-port attached to an other computer.
Files that needs configuration is fbb.conf, port.sys, beacon3.sys
and ax25ipd.conf.
[fbb.conf]
(Allow users to make unroto requests)
> ># First connection mask :
> ># 0 : Disable
> ># 1 : Excluded
> ># 2 : Local
> ># 4 : Expert
> ># 8 : Sysop
> ># 16 : BBS
> ># 32 : Pagination
> ># 64 : Guest
> ># 128: Modem
> ># 256: See-all-messages
> ># 512: Unproto list asking is allowed
> ># 1024: Liste des messages nouveaux.
> ># 2048:
> >#
> ># What new users can do wihout special permissions from sysop
> > 32 (Pagination) + 128 (Modem) + 512 (ask for unproto) + 1024
(list new msg) = 1696
> >mask = 1696
(How many messages, and type of messages, are sent to the user when
requesting unproto)
> ># Number of back messages in unproto lists
> ># Syntax: unprotoes <Back number> <delay> <type of messages in
unproto lists>
> ># A = ACK-messages
> ># P = Personal messages to local users
> ># V = Personal messages in transit
> ># M = Subject is replaced with stars in personal mail
> >#
> >unprotoes = 500 5 VPA
Your port.sys looks ok. It should work.
FBB port 3 is configured to send unproto when new messages arrive.
(The L in UXWYL)
Your beacon3.sys looks ok, but consider using FBB as unproto address
instead of MAIL in your beacon3.sys as most client programs that
listens for unproto, listens for FBB.
! FBB v IW2OHX IQ2LB
Most likely you forgot to configure your AXIP-port to allow
unproto beacons.
AXIP-ports does not allow unproto beacons at all by default.
You must enable beacon on the port you want to send beacons/unproto on.
You must also allow the destination address for the unproto/beacon
packets on the AXIP port
In ax25ipd.conf:
add the destination FBB-0 on the line that starts with "broadcast"
add the letter b at the end of the peer delaration to enable
broadcasts on that AXIP-tunnel.
[ax25ipd] (Example)
broadcast QST-0 NODES-0 FBB-0
route iw2ohx-0 192.168.0.1 b
Restart ax25ipd to make the changes take effect.
> >
> > inittnc3.sys
> > ----
> > #
> > # INITTNC for LINUX interface
> > #
I don't think this file is used at all in your system.
What I've learned is that inittncX.sys is only used to init a TNC
that FBB talks directly to.
(TNC with WA8DED-firmware, not when you are using ax25d + kiss/mkiss/6pack)
This is a heritage from DOS when FBB talked directly to the serial port
via a serial port driver.
I hope that this will help you solv your problem with unproto beacons.
73 de SM7KS, Bo
------------------------------
Message: 2
Date: Sat, 16 Aug 2008 10:37:14 +0200
From: "Marco Di Martino (IW2OHX)" <iw2ohx(AT)iw2ohx.net>
Subject: Re: [xfbb] Unproto and beacon problem
To: List for the LINUX version of FBB <xfbb(AT)f6fbb.org>
Message-ID: <48A691BA.2060309(AT)iw2ohx.net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Hi Bo,
thank you very much for your help.
I solved my problem with unproto and beacon.
There were two things mis-configured:
1) ax25ipd: broadcast wasn't allowed. Now it's configured as you suggested
2) xnet: the digipeating function was disabled. So I enabled "Cross
digipeating" option
to permit re-transmission of UI frames between two different port. This
function is enabled
in IW2OHX and in IQ2LB digis.
According to XNET manual's, at page 29:
*PA TNC R 2*
2 stands for "Cross Digipeating" between two ports. (for example between
ports 1-2, or ports 3-4, ecc..).
It works!!
For detailed info about digipeating in xnet ask me!
Bye
Marco
iw2ohx
Bo Skoglund ha scritto:
> > Hi Marco.
> >
> > What I can see from your mail is that you are trying to send
FBB-beacons on FBB port3.
> > Port 3 is an AXIP-port attached to an other computer.
> >
> > Files that needs configuration is fbb.conf, port.sys, beacon3.sys
and ax25ipd.conf.
> >
> > [fbb.conf]
> > (Allow users to make unroto requests)
> >
>> >> # First connection mask :
>> >> # 0 : Disable
>> >> # 1 : Excluded
>> >> # 2 : Local
>> >> # 4 : Expert
>> >> # 8 : Sysop
>> >> # 16 : BBS
>> >> # 32 : Pagination
>> >> # 64 : Guest
>> >> # 128: Modem
>> >> # 256: See-all-messages
>> >> # 512: Unproto list asking is allowed
>> >> # 1024: Liste des messages nouveaux.
>> >> # 2048:
>> >> #
>> >> # What new users can do wihout special permissions from sysop
>> >> 32 (Pagination) + 128 (Modem) + 512 (ask for unproto) + 1024
(list new msg) = 1696
>> >> mask = 1696
>> >>
> >
> > (How many messages, and type of messages, are sent to the user when
requesting unproto)
> >
>> >> # Number of back messages in unproto lists
>> >> # Syntax: unprotoes <Back number> <delay> <type of messages in
unproto lists>
>> >> # A = ACK-messages
>> >> # P = Personal messages to local users
>> >> # V = Personal messages in transit
>> >> # M = Subject is replaced with stars in personal mail
>> >> #
>> >> unprotoes = 500 5 VPA
>> >>
> >
> > Your port.sys looks ok. It should work.
> > FBB port 3 is configured to send unproto when new messages arrive.
(The L in UXWYL)
> >
> > Your beacon3.sys looks ok, but consider using FBB as unproto
address instead of
> > MAIL in your beacon3.sys as most client programs that listens for
unproto, listens for FBB.
> > ! FBB v IW2OHX IQ2LB
> >
> > Most likely you forgot to configure your AXIP-port to allow
unproto beacons.
> > AXIP-ports does not allow unproto beacons at all by default.
> > You must enable beacon on the port you want to send beacons/unproto on.
> > You must also allow the destination address for the unproto/beacon
packets on the AXIP port
> >
> > In ax25ipd.conf:
> > add the destination FBB-0 on the line that starts with "broadcast"
> > add the letter b at the end of the peer delaration to enable
broadcasts on that AXIP-tunnel.
> >
> > [ax25ipd] (Example)
> > broadcast QST-0 NODES-0 FBB-0
> > route iw2ohx-0 192.168.0.1 b
> >
> > Restart ax25ipd to make the changes take effect.
> >
> >
>> >> inittnc3.sys
>> >> ----
>> >> #
>> >> # INITTNC for LINUX interface
>> >> #
>> >>
> >
> > I don't think this file is used at all in your system.
> > What I've learned is that inittncX.sys is only used to init a TNC
that FBB talks directly to.
> > (TNC with WA8DED-firmware, not when you are using
ax25d + kiss/mkiss/6pack)
> > This is a heritage from DOS when FBB talked directly to the serial
port via a serial port driver.
> >
> > I hope that this will help you solv your problem with unproto beacons.
> >
> > 73 de SM7KS, Bo
> >
-- --- Marco Di Martino Via Attimo, 18 - Bollate (MI) Cell. +393285373364
e-mail: iw2ohx(AT)iw2ohx.net www.marcodimartino.it
- Amateur Radio: I W 2 O H X
Homepage: www.iw2ohx.net Ampr
Hostname: iw2ohx.ampr.org Ampr IP: 44.134.160.78 - 44.134.160.79
LinuxNode: telnet://gw.iw2ohx.net/
Jnos: telnet://gw.iw2ohx.net:4001/
(X)net: telnet://gw.iw2ohx.net:4002/
NET/ROM: BOLNET:IW2OHX; OHXNOS:IW2OHX-4
Packet Mail : IW2OHX (AT) IW2OHX.ILOM.ITA.EU
--- ------------------------------
End of xfbb Digest, Vol 41, Issue 3
***********************************
****************************************************************
ABOVE IS A CROSS POST TO THE PACKET RADIO NETWORK IN AN EFFORT
TO PROMOTE FURTHER INTEREST IN PACKET RADIO
Courtesy Tony VK7AX VK7AX(AT)VK7AX.#ULV.TAS.AUS.OC
****************************************************************
Read previous mail | Read next mail
| |
