? 00:47 [2380] 2 argument(s) required
hide-aka 1:2320/0.0 !1:*@fidonet 2:*@fidonet 3:*@fidonet 4:*@fidonet
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.
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 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
So how did you do it? ;)
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 :-)
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 :-)
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.
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?
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
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.
Sysop: | digital man |
---|---|
Location: | Riverside County, California |
Users: | 1,035 |
Nodes: | 15 (0 / 15) |
Uptime: | 06:14:24 |
Calls: | 761 |
Calls today: | 1 |
Files: | 95,171 |
D/L today: |
894 files (98,775K bytes) |
Messages: | 299,179 |