Добро пожаловать, Гость. Пожалуйста авторизуйтесь здесь.
FGHIGate на GaNJa NeTWoRK ST@Ti0N - Просмотр сообщения в эхоконференции ENET.SYSOP
Введите FGHI ссылку:


Присутствуют сообщения из эхоконференции ENET.SYSOP с датами от 10 Jul 13 21:42:12 до 08 Nov 24 13:03:04, всего сообщений: 12576
Ответить на сообщение К списку сообщений Предыдущее сообщение Следующее сообщение
= Сообщение: 1560 из 12576 ====================================== ENET.SYSOP =
От   : Benny Pedersen                   2:230/0            28 Nov 14 21:43:28
Кому : BjЎrn Felten                                        28 Nov 14 21:43:28
Тема : qico -b -i 2:203/0 fails
FGHI : area://ENET.SYSOP?msgid=2:230/0+5478ec56
На   : area://ENET.SYSOP?msgid=2:203/2+5478a394
= Кодировка сообщения определена как: LATIN-1 ================================
Ответ: area://ENET.SYSOP?msgid=2:203/2+547902ee
==============================================================================
Hello BjЎrn!

28 Nov 2014 17:32, BjЎrn Felten wrote to Benny Pedersen:

BF> Sigh! Can you please go back in this thread? I posted the log
BF> snippet there.

note this was your binkp.cfg, not your working radius

BF> I... <nah, I'll bit my tongue...>

good as http://www.expert.se/ black friday :)

BF> What part of "I move your mail manually to the Radius outbound" did
BF> you not understand? Radius is old, it doesn't handle modern encryption
BF> as well as binkd does. Binkd get "security violation", Radius doesn't.

so you move radius incomming dirs mail over to ?

why is argus/radius/binkp at your server using diffrence dirs on incomming ?

BP>> are you like Gert that needs 4 or five programs to handle something as
BP>> simple as binkp ?

BF> Let me paraphrase Gert here (from a comment to you):

Gert can make it work :=)

BF> "Proev lige at checke din mailer log om hvordan den ser ud nu for
BF> connect fra 203/0."

he have a log to

BF> Obviously with connection attempts from binkd and not the ones from
BF> Radius. DUH!

i have binkp aswell but since qico works with your radius setup all works here

   ----- binkd_bjorn.log begins -----

  22 Nov 00:55:21 [21068] BEGIN, binkd/1.0a-559/Linux -v -p -c -P 2:203/0 bjorn.cfg
  22 Nov 00:55:21 [21068] creating a poll for 2:203/0@fidonet (`d' flavour)
  22 Nov 00:55:21 [21068] clientmgr started
+ 22 Nov 00:55:21 [21069] call to 2:203/0@fidonet
  22 Nov 00:55:21 [21069] trying 90.231.158.147...
  22 Nov 00:55:21 [21069] connected
+ 22 Nov 00:55:21 [21069] session with f0.n203.z2.binkp.net (90.231.158.147)
- 22 Nov 00:55:21 [21069] OPT CRAM-MD5-1665eca905d01c2cf846299a4591c9a2
+ 22 Nov 00:55:21 [21069] Remote requests MD mode
- 22 Nov 00:55:21 [21069] SYS West Swedish Net
- 22 Nov 00:55:21 [21069] ZYZ BjЎrn Felten
- 22 Nov 00:55:21 [21069] LOC Gothenburg
- 22 Nov 00:55:21 [21069] PHN 90.231.158.147
- 22 Nov 00:55:21 [21069] NDL MO,CM,TCP,IFC,TEL,VMP,BND
- 22 Nov 00:55:21 [21069] TIME Sat, 22 Nov 2014 00:54:36 +0100
- 22 Nov 00:55:21 [21069] VER Radius/4.010/21.01.2005,13:56(Final-Release)/Win32 binkp/1.1
+ 22 Nov 00:55:21 [21069] addr: 2:203/0@fidonet
+ 22 Nov 00:55:21 [21069] addr: 2:203/2@fidonet
+ 22 Nov 00:55:21 [21069] addr: 2:20/0@fidonet
+ 22 Nov 00:55:21 [21069] addr: 2:2/2@fidonet
+ 22 Nov 00:55:22 [21069] pwd protected session (MD5)
+ 22 Nov 00:55:22 [21069] sending /home/xpoint/fido/out/00cb0000.out as a850ca57.pkt (611)
+ 22 Nov 00:55:22 [21069] sent: /home/xpoint/fido/out/00cb0000.out (611, 611.00 CPS, 2:203/0@fidonet)
+ 22 Nov 00:55:22 [21069] done (to 2:203/0@fidonet, OK, S/R: 1/0 (611/0 bytes))
  22 Nov 00:55:22 [21069] session closed, quitting...
  22 Nov 00:55:22 [21068] rc(21069)=0
  22 Nov 00:55:22 [21068] the queue is empty, quitting...
   ----- binkd_bjorn.log ends -----

since that date i have connected with qico to you

note its your radius, not your argus / binkp problem :=)

BF> I can't see what goes wrong in my log, only you can in your.

maybe use irex so ? it have a working logs, but lost source keeps the problem in irex

BF> My guess is that you don't know how to set up your mailer to do
BF> encryption properly.

sure see logs above

BF> Just as you didn't know how to give the proper
BF> command to your gico (see origin and compare it to what Semen Panevin
BF> explained to you).

man qico was at fault here with the syntax

   ----- pollall-qico begins -----
#!/bin/sh
#
# qctl is the queue manager
#
/usr/bin/qctl -pn 1:261/38
/usr/bin/qctl -pn 2:230/150
/usr/bin/qctl -pn 2:240/1120
/usr/bin/qctl -pn 2:280/1027
/usr/bin/qctl -pn 2:292/854
/usr/bin/qctl -pn 2:5030/786
/usr/bin/qctl -pn 2:203/0
   ----- pollall-qico ends -----

such geeks out there :)


 Regards Benny

... there can only be one way of life, and it works :)

--- Msged/LNX 6.2.0 (Linux/3.17.3-gentoo (i686))
* Origin: duggi.junc.org where qico is waiting (2:230/0)

К главной странице гейта
Powered by NoSFeRaTU`s FGHIGate
Открытие страницы: 0.066272 секунды