1. Forum
  2. Fsxnet Message
  3. FSX MYS

  • troubleshooting FTN nodes

    From Satchmo@21:4/144 to All on Monday, December 17, 2018 18:36:03
    All,

    I need to troubleshoot a couple of FTN networks I have recently setup on my system.
    Before I dive into parsing the mutil/fidopoll logs, what could the reason be for not receiving a reply from the upstream nodes areafix/filefix?

    I've checked initial connectivity with a manual fidopoll and can see it
    sending the netmail packet. Just nothing comes back. I'm seeing this on 2 of
    my newly setup networks.

    Are there any statistics tools/utils to create reports from the
    fidopoll/mutil logs for Mystic?

    Thanks,

    Satchmo

    --- Mystic BBS/NNTP v1.12 A39 2018/04/21 (Raspberry Pi/32)
    * Origin: Sonic BBS | sonicbbs.ddns.net (21:4/144)
  • From Michael Borthwick@21:4/132 to Satchmo on Tuesday, December 18, 2018 09:44:15
    I need to troubleshoot a couple of FTN networks I have recently setup on my system.

    - Have you restarted mystic server after adding the new addresses?

    - Have you checked the netmail to the HUBs, are the addresses correct, ie
    does it show you are sending from the right address ie 21:4/132 on the fsx
    net?

    - What networks have you added? I have a couple here that simply don't
    respond to me. Everything is set up fine on my end, I don't think the NC has their systems set up correctly.

    --- Mystic BBS v1.12 A39 2018/04/21 (Raspberry Pi/32)
    * Origin: Fusion BBS ~ Newcastle, Australia (21:4/132)
  • From Satchmo@21:4/144 to All on Tuesday, December 18, 2018 00:01:27
    On Tue, 18 Dec 2018 08:44:00 GMT
    Michael Borthwick wrote:

    I need to troubleshoot a couple of FTN networks I have recently setup on my system.

    - Have you restarted mystic server after adding the new addresses?

    Yep - all restarted. Just trawling through the log files now.


    - Have you checked the netmail to the HUBs, are the addresses correct, ie does it show you are sending from the right address ie 21:4/132 on the fsx net?

    Yeah everything correct. it looks like a password issue. Hopefully easy
    enough to resolve.
    it's just weird & frustrating that polling the hub is fine and no packets are ever there for me so super hard to debug.

    I guess the only surefire way would be to log onto their system and create
    some netmail/echomail posts so I know there could be some packets to pick up. However it seems like there is a delay in the hub importing/exporting/tossing mail so it gets awkward.


    - What networks have you added? I have a couple here that simply don't respond to me. Everything is set up fine on my end, I don't think the NC has their systems set up correctly.

    Not going to name any names as it could well be an issue on my end!
    I'll keep plodding along :)

    Thanks for the opportunity to vent a bit! ;)

    --- Mystic BBS/NNTP v1.12 A39 2018/04/21 (Raspberry Pi/32)
    * Origin: Sonic BBS | sonicbbs.ddns.net (21:4/144)
  • From deon@21:2/116.1 to Satchmo on Tuesday, December 18, 2018 00:26:41
    On 12/17/18, Satchmo said the following...
    Before I dive into parsing the mutil/fidopoll logs, what could the
    reason be for not receiving a reply from the upstream nodes areafix/filefix?

    You really need your uplink to go through their logs.

    I common reason I've found, is that packet passwords are different.

    So while you can validate connectivity which validates that you both are
    using the right session password, packets can have a packet password, and if you sent one and the other end is not expecting it (or visa versa), the
    packet may be discard once received.

    That said, I too have some networks where the uplink doesnt respond so diagnosing why I dont receive a response is futile...

    ...deon

    _--_|\ | Deon George
    / \ | Chinwag BBS - A BBS on a PI in Docker!
    \_.__.*/ |
    V | Coming from the 'burbs of Melbourne, Australia

    --- Mystic BBS v1.12 A39 2018/04/21 (Raspberry Pi/32)
    * Origin: Chinwag | MysticBBS in Docker on a Pi! (21:2/116.1)
  • From vk3jed@21:1/109.1 to Satchmo on Tuesday, December 18, 2018 12:17:30
    On 18-Dec-2018 10:01, Satchmo wrote to All <=-

    Yeah everything correct. it looks like a password issue. Hopefully easy enough to resolve.
    it's just weird & frustrating that polling the hub is fine and no
    packets are ever there for me so super hard to debug.

    I've found it to be a typo that causes this most of the time, when it's happened to me. :)


    ... Laughter is the shortest distance between two people.
    --- MultiMail/Win
    * Origin: Bush Track BBS (21:1/109.1)
  • From vk3jed@21:1/109.1 to deon on Tuesday, December 18, 2018 12:18:12
    On 18-Dec-2018 10:26, deon wrote to Satchmo <=-

    I common reason I've found, is that packet passwords are different.

    That has happened too. :)


    ... Love is grand. Divorce is fifty grand.
    --- MultiMail/Win
    * Origin: Bush Track BBS (21:1/109.1)
  • From Satchmo@21:4/144 to vk3jed on Tuesday, December 18, 2018 14:27:21
    On 12/18/18, vk3jed said the following...

    On 18-Dec-2018 10:26, deon wrote to Satchmo <=-

    I common reason I've found, is that packet passwords are different.

    That has happened too. :)

    Yep. Packet password was to blame. woohoo!
    1 network down 1 to go!

    --- Mystic BBS v1.12 A39 2018/04/21 (Raspberry Pi/32)
    * Origin: Sonic BBS | sonicbbs.ddns.net (21:4/144)
  • From Vk3jed@21:1/109 to Satchmo on Wednesday, December 19, 2018 13:44:00
    On 12-18-18 13:27, Satchmo wrote to vk3jed <=-

    On 12/18/18, vk3jed said the following...

    On 18-Dec-2018 10:26, deon wrote to Satchmo <=-

    I common reason I've found, is that packet passwords are different.

    That has happened too. :)

    Yep. Packet password was to blame. woohoo!
    1 network down 1 to go!

    That'll do it. :D


    ... Too many pray for peace with their fists clenched.
    === MultiMail/Win v0.51
    --- SBBSecho 3.03-Linux
    * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (21:1/109)