I can successfully hide my othernets on single node/zones with the
following...

hide-aka 21:1/148.0 !21:@fsxnet

FSXNet will only be presented to FSXNet addys... however if I want to
hid fidonet from all other nodes... I enter this and no luck get a

C:\binkd>binkd binkd.cfg
00:47 [2380] binkd.cfg: line 62: error in configuration files
? 00:47 [2380] 2 argument(s) required
! 00:47 [2380] error in configuration, aborting

below is the config...

hide-aka 1:2320/0.0 !1:*@fidonet 2:*@fidonet 3:*@fidonet 4:*@fidonet

How to I tell binkd to hide my fidonet node for only zones in fidonet.
I've tried it as !*@fidonet and that does not work either.

Allen
--- SBBSecho 3.00-Win32
* Origin: LiveWire BBS - Synchronet - LiveWireBBS.com (1:2320/100)

On 02/27/17, Allen Prunty said the following...

Allen,

I'm not 100% sure on this, but considering the error message given:

? 00:47 [2380] 2 argument(s) required

...you may need to break up the zones onto their own lines.

hide-aka 1:2320/0.0 !1:*@fidonet 2:*@fidonet 3:*@fidonet 4:*@fidonet

I would try:

hide-aka 1:2320/0.0 !1:*@fidonet
hide-aka 1:2320/0.0 !2:*@fidonet
hide-aka 1:2320/0.0 !3:*@fidonet
hide-aka 1:2320/0.0 !4:*@fidonet

Like I said, I'm not sure if that will work, but considering it's stating two arguments are required, perhaps breaking it down into two arguments per line might do the trick. I haven't run binkd since I started running Mystic, so I can't even test it on my end.


Dan Richter
aka Black Panther
Sysop - Castle Rock BBS
telnet://castlerockbbs.com
The sparrows are flying again...

--- Mystic BBS v1.12 A31 (Windows)
* Origin: Castle Rock BBS - castlerockbbs.com (1:317/3)

Like I said, I'm not sure if that will work, but considering it's
stating tw arguments are required, perhaps breaking it down into
two arguments per line might do the trick. I haven't run binkd
since I started running Mystic, so I can't even test it on my end.

I think I got it figured out... just need someone to poll my system
and see what is presented. I think it's working...

+ 02:24 [828] call to 8:8/3@fmlynet
02:24 [828] trying binkp.kofobbs.dk [80.63.101.234]...
02:24 [828] connected
+ 02:24 [828] outgoing session with binkp.kofobbs.dk:24554
[80.63.101.234]
- 02:24 [828] hiding aka 21:1/148@fsxnet
- 02:24 [828] hiding aka 1:2320/0@fidonet
- 02:24 [828] hiding aka 1:2320/100@fidonet
- 02:24 [828] hiding aka 1:227/0@fidonet
- 02:24 [828] hiding aka 24:110/3@sportnet
- 02:24 [828] hiding aka 44:502/0@dorenet
- 02:24 [828] hiding aka 80:774/9@retronet
- 02:24 [828] hiding aka 115:1502/224@pascal-net
- 02:24 [828] hiding aka 316:270/2@whispnet
- 02:24 [828] hiding aka 901:1/12@dixienet
- 02:24 [828] hiding aka 9:467/7@winsnet
- 02:24 [828] SYS The KofoBBS
- 02:24 [828] ZYZ Gert Andersen
- 02:24 [828] LOC Broendby Copenhagen Denmark
- 02:24 [828] NDL CM,MO,XX,TCP,BINKP,IBN,TELN,IFC,115200
- 02:24 [828] TIME Mon, 27 Feb 2017 08:24:44 +0100
--- SBBSecho 3.00-Win32
* Origin: LiveWire BBS - Synchronet - LiveWireBBS.com (1:2320/100)

Hi Allen,

On 2017-02-27 02:25:46, you wrote to Dan Richter:

Like I said, I'm not sure if that will work, but considering it's
stating tw arguments are required, perhaps breaking it down into
two arguments per line might do the trick. I haven't run binkd
since I started running Mystic, so I can't even test it on my end.

I think I got it figured out... just need someone to poll my system
and see what is presented. I think it's working...

It looks good:

+ 27 Feb 08:35:46 [21782] call to 1:2320/100@fidonet
27 Feb 08:35:46 [21782] trying livewirebbs.com [104.60.26.113]...
27 Feb 08:35:47 [21782] connected
+ 27 Feb 08:35:47 [21782] outgoing session with livewirebbs.com:24554 [104.60.26.113]
- 27 Feb 08:35:47 [21782] OPT CRAM-MD5-aa851363a267fcef6119eb96b2e094ee
+ 27 Feb 08:35:47 [21782] Remote requests MD mode
- 27 Feb 08:35:47 [21782] SYS LiveWire BBS
- 27 Feb 08:35:47 [21782] ZYZ Allen Prunty
- 27 Feb 08:35:47 [21782] LOC Parts Unknown, KY, USA
- 27 Feb 08:35:47 [21782] NDL 115200,TCP,BINKP
- 27 Feb 08:35:47 [21782] TIME Mon, 27 Feb 2017 02:35:42 -0500
- 27 Feb 08:35:47 [21782] VER binkd/1.1a-95/Win32 binkp/1.1
+ 27 Feb 08:35:47 [21782] addr: 1:2320/100@fidonet
+ 27 Feb 08:35:47 [21782] addr: 1:2320/0@fidonet
+ 27 Feb 08:35:47 [21782] addr: 1:227/0@fidonet
...
27 Feb 08:35:48 [21782] session closed, quitting...

So how did you do it? ;)


Bye, Wilfred.

--- FMail-W32 1.73.17.78-B20170215
* Origin: FMail development HQ (2:280/464)

Hi Dan,

On 2017-02-26 23:48:00, you wrote to Allen Prunty:

I would try:

hide-aka 1:2320/0.0 !1:*@fidonet
hide-aka 1:2320/0.0 !2:*@fidonet
hide-aka 1:2320/0.0 !3:*@fidonet
hide-aka 1:2320/0.0 !4:*@fidonet

That won't work, because the domains overlap. Maybe:

hide-aka 1:2320/0 *
present-aka 1:2320/0 1:*@fidonet
present-aka 1:2320/0 2:*@fidonet
present-aka 1:2320/0 3:*@fidonet
present-aka 1:2320/0 4:*@fidonet

Bye, Wilfred.

--- FMail-W32 1.73.17.78-B20170215
* Origin: FMail development HQ (2:280/464)

So how did you do it? ;)

I was able to pull up my binkd.cfg remotely. I put ALL of my AKA's in
like this...

hide-aka 21:1/148.0 !21:@fsxnet
hide-aka 1:2320/0.0 !*@fidonet
hide-aka 1:2320/100.0 !*@fidonet
hide-aka 1:227/0 !*@fidonet
hide-aka 24:110/3 !24:*@sportnet
hide-aka 44:502/0 !44:*@dorenet
hide-aka 80:774/9 !80:*@retronet
hide-aka 115:1502/224 !115:*@pascal-net
hide-aka 316:270/2 !316:*@whispnet
hide-aka 901:1/12 !901:*@dixienet
hide-aka 9:467/7 !9:*@winsnet
hide-aka 8:7366/1 !8:*@fmlynet

And it started working. Granted it is going to require that I poll
each net individulaly if one hub has two nets on it (not a problem at
this time) it does streamline my polls. I'm finding some mystic
systems don't fare well when I present all my AKAs to them from zones
/ domains they don't have.

Plus it is much kinder to other system's log files :-)

Allen
--- SBBSecho 3.00-Win32
* Origin: LiveWire BBS - Synchronet - LiveWireBBS.com (1:2320/100)

Hello Allen!

27 Feb 17 12:23, you wrote to Wilfred van Velzen:

this time) it does streamline my polls. I'm finding some mystic
systems don't fare well when I present all my AKAs to them from zones
/ domains they don't have.

Plus it is much kinder to other system's log files :-)

nolog "*or busy)"

This is what is frendly to my logfiles.

I have done what you are trying in the past, when I was in one othernet. My reason was, that not everybody needed to know, in what nets I was participating.

Kees

--- GoldED+/LNX 1.1.5
* Origin: As for me, all I know is that, I know nothing. (2:280/5003.4)

Hi,

On 2017-02-27 12:23:59, Allen Prunty wrote to Wilfred van Velzen:
about: "Re: Hiding of AKA's...":

I was able to pull up my binkd.cfg remotely. I put ALL of my AKA's in like this...

hide-aka 21:1/148.0 !21:@fsxnet
hide-aka 1:2320/0.0 !*@fidonet
hide-aka 1:2320/100.0 !*@fidonet
hide-aka 1:227/0 !*@fidonet
hide-aka 24:110/3 !24:*@sportnet
hide-aka 44:502/0 !44:*@dorenet
hide-aka 80:774/9 !80:*@retronet
hide-aka 115:1502/224 !115:*@pascal-net
hide-aka 316:270/2 !316:*@whispnet
hide-aka 901:1/12 !901:*@dixienet
hide-aka 9:467/7 !9:*@winsnet
hide-aka 8:7366/1 !8:*@fmlynet

And it started working. Granted it is going to require that I poll
each net individulaly if one hub has two nets on it (not a problem at
this time) it does streamline my polls. I'm finding some mystic
systems don't fare well when I present all my AKAs to them from zones
/ domains they don't have.

Plus it is much kinder to other system's log files :-)

Indeed! Thanks! ;)

Bye, Wilfred.


--- FMail-W32 1.73.17.78-B20170215
* Origin: Native IPv6 connectable node (2:280/464)

I have done what you are trying in the past, when I was in one
othernet. My reason was, that not everybody needed to know, in
what nets I was participating.

I'm not trying to be secretive or subversive... just think that some
nodes I connect to bombard me with AKA's ... I'm just trying to be a
bit friendlier.

Allen
--- SBBSecho 3.00-Win32
* Origin: LiveWire BBS - Synchronet - LiveWireBBS.com (1:2320/100)

Hello Allen!

27 Feb 17 15:33, you wrote to me:

I'm not trying to be secretive or subversive... just think that some
nodes I connect to bombard me with AKA's ... I'm just trying to be a
bit friendlier.

Commendable. ;)

Kees

--- GoldED+/LNX 1.1.5
* Origin: As for me, all I know is that, I know nothing. (2:280/5003.4)

On 2017 Feb 27 02:25:46, you wrote to Dan Richter:

Like I said, I'm not sure if that will work, but considering it's
stating tw arguments are required, perhaps breaking it down into two
arguments per line might do the trick. I haven't run binkd since I
started running Mystic, so I can't even test it on my end.

I think I got it figured out... just need someone to poll my system
and see what is presented. I think it's working...

i'm curious as to why do you want to do this? what problem is it solving?

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... URA Redneck if your mailbox is in the shape of any farm animal.
---
* Origin: (1:3634/12.73)

Re: Hiding of AKA's...
By: mark lewis to Allen Prunty on Mon Feb 27 2017 09:56 pm

i'm curious as to why do you want to do this? what problem is it solving?

It keeps the logs neater on the systems that I connect with Just being nice.

Plus it helps with the "cognitive therapy" when I can figure out a feature of something.

Allen
--- SBBSecho 3.00-Win32
* Origin: LiveWire BBS - Synchronet - LiveWireBBS.com (1:2320/100)

Hi Allen,

On 27 Feb 17 12:23, Allen Prunty wrote to Wilfred van Velzen:
about: "Re: Hiding of AKA's...":

So how did you do it? ;)

I was able to pull up my binkd.cfg remotely. I put ALL of my AKA's in like this...

hide-aka 21:1/148.0 !21:@fsxnet
hide-aka 1:2320/0.0 !*@fidonet
hide-aka 1:2320/100.0 !*@fidonet
hide-aka 1:227/0 !*@fidonet

Btw: before you said:

How to I tell binkd to hide my fidonet node for only zones in fidonet. I've tried it as !*@fidonet and that does not work either.

I'm glad that wasn't true! ;)


Wilfred.

--- FMail-W32 2.0.0.0
* Origin: point@work (2:280/464.112)