1. Forum
  2. FidoNet
  3. ALT.OS.LINUX.MAGEIA

  • Problems with Pan ?

    From Jim Beard@2:250/1 to All on Sun Nov 29 19:04:17 2020
    Is anyone else using pan having problems?

    I am getting lots of error messages complaining of getting corrupted data
    when the connection is to reader463.eternal-september.org. If I change
    the port to 563, that sometimes works but other times nothing seems to
    get a connection.

    Cheers!

    jim b.

    --
    UNIX is not user-unfriendly, it merely expects users to be computer-
    friendly.

    --- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Mike Easter@2:250/1 to All on Sun Nov 29 19:38:16 2020
    Jim Beard wrote:
    I am getting lots of error messages complaining of getting corrupted data when the connection is to reader463.eternal-september.org. If I change
    the port to 563, that sometimes works but other times nothing seems to
    get a connection.

    Do you use 'always trust this server's certificate'?

    --
    Mike Easter

    --- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
    * Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1@fidonet)
  • From Bit Twister@2:250/1 to All on Sun Nov 29 20:33:00 2020
    On Sun, 29 Nov 2020 19:04:17 -0000 (UTC), Jim Beard wrote:
    Is anyone else using pan having problems?

    I am getting lots of error messages complaining of getting corrupted data when the connection is to reader463.eternal-september.org.

    Where did you get that 463 id. Suggest reading
    http://www.eternal-september.org/index.php?showpage=techinfo


    If I change
    the port to 563, that sometimes works but other times nothing seems to
    get a connection.


    Then I suggest an internet connection problem.

    I did see an article last week about some network screw up hitting about a third of some traffic. Can not remember who/where.

    Have see a few people complain in eternal-september.support.
    I have not seen any problems in months using slrn at
    $ echo $NNTPSERVER
    snews://reader443.eternal-september.org
    here in Dallas Tx.


    --- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From faeychild@2:250/1 to All on Mon Nov 30 11:22:53 2020
    On 30/11/20 7:33 am, Bit Twister wrote:
    On Sun, 29 Nov 2020 19:04:17 -0000 (UTC), Jim Beard wrote:
    Is anyone else using pan having problems?

    I am getting lots of error messages complaining of getting corrupted data
    when the connection is to reader463.eternal-september.org.

    Where did you get that 463 id. Suggest reading
    http://www.eternal-september.org/index.php?showpage=techinfo


    If I change
    the port to 563, that sometimes works but other times nothing seems to
    get a connection.


    Then I suggest an internet connection problem.

    I did see an article last week about some network screw up hitting about a third of some traffic. Can not remember who/where.

    Have see a few people complain in eternal-september.support.
    I have not seen any problems in months using slrn at
    $ echo $NNTPSERVER
    snews://reader443.eternal-september.org
    here in Dallas Tx.



    I may be confusing things a lot more, but

    Thunderbird is set as suggested by eternal-september

    Server name: news.eternal-september.org
    Port : 119 (NNTP)
    Port : 563 (encrypted connection NNTPS)

    I have port 563

    connection security SSL/TLS

    --
    faeychild
    Running plasmashell 5.15.4 on 5.7.19-desktop-3.mga7 kernel.
    Mageia release 7 (Official) for x86_64 installed via Mageia-7-x86_64-DVD.iso


    --- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Jim Beard@2:250/1 to All on Mon Nov 30 14:27:04 2020
    On Sun, 29 Nov 2020 11:38:16 -0800, Mike Easter wrote:

    Jim Beard wrote:
    I am getting lots of error messages complaining of getting corrupted
    data when the connection is to reader463.eternal-september.org. If I
    change the port to 563, that sometimes works but other times nothing
    seems to get a connection.

    Do you use 'always trust this server's certificate'?

    Yes.

    Cheers!

    jim b.

    --
    UNIX is not user-unfriendly, it merely expects users to be computer-
    friendly.

    --- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Jim Beard@2:250/1 to All on Mon Nov 30 14:39:36 2020
    On Sun, 29 Nov 2020 14:33:00 -0600, Bit Twister wrote:

    On Sun, 29 Nov 2020 19:04:17 -0000 (UTC), Jim Beard wrote:
    Is anyone else using pan having problems?

    I am getting lots of error messages complaining of getting corrupted
    data when the connection is to reader463.eternal-september.org.

    Where did you get that 463 id. Suggest reading
    http://www.eternal-september.org/index.php?showpage=techinfo

    From the page just above:
    Client Settings
    Server name: news.eternal-september.org
    Port : 119 (NNTP)
    Port : 563 (encrypted connection NNTPS)
    Servername: reader80.eternal-september.org
    Port : 80
    Servername: reader443.eternal-september.org
    Port : 443 (encrypted connection NNTPS)


    If I change
    the port to 563, that sometimes works but other times nothing seems to
    get a connection.

    The third Servername reader443.* was my backup. I simply changed the
    port number from 443 to 563 used by my primary.


    Then I suggest an internet connection problem.

    That may well be.

    I eventually went to a backup done months ago and copied over all files,
    and that worked. Then later a bit of flakiness. Then working.
    And still working today.

    An internet connection problem would be a plausible cause for my
    problems.

    I did see an article last week about some network screw up hitting about
    a third of some traffic. Can not remember who/where.

    Have see a few people complain in eternal-september.support.
    I have not seen any problems in months using slrn at
    $ echo $NNTPSERVER snews://reader443.eternal-september.org
    here in Dallas Tx.

    Cheers!

    jim b.

    --
    UNIX is not user-unfriendly, it merely expects users to be computer-
    friendly.

    --- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Jim Beard@2:250/1 to All on Mon Nov 30 14:46:45 2020
    On Mon, 30 Nov 2020 22:22:53 +1100, faeychild wrote:

    I may be confusing things a lot more, but

    Thunderbird is set as suggested by eternal-september

    Server name: news.eternal-september.org Port : 119 (NNTP)
    Port : 563 (encrypted connection NNTPS)

    I have port 563

    connection security SSL/TLS

    Pan has setups for two servers, one primary and the other
    the followup. I have long used the one on port 563 for
    primary and the one on 443 for backup.

    news.eternal-september.org uses port 563
    reader443.eternal-september.org uses port 443

    There was a time years ago when I used port 119 unencrypted
    but for some reason Verizon FIOS did not like that.

    Cheers!

    jim b.

    --
    UNIX is not user-unfriendly, it merely expects users to be computer-
    friendly.

    --- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Bit Twister@2:250/1 to All on Mon Nov 30 17:23:22 2020
    On Mon, 30 Nov 2020 14:39:36 -0000 (UTC), Jim Beard wrote:
    On Sun, 29 Nov 2020 14:33:00 -0600, Bit Twister wrote:

    On Sun, 29 Nov 2020 19:04:17 -0000 (UTC), Jim Beard wrote:
    Is anyone else using pan having problems?

    I am getting lots of error messages complaining of getting corrupted
    data when the connection is to reader463.eternal-september.org.

    Where did you get that 463 id. Suggest reading
    http://www.eternal-september.org/index.php?showpage=techinfo

    From the page just above:
    Client Settings
    Server name: news.eternal-september.org
    Port : 119 (NNTP)
    Port : 563 (encrypted connection NNTPS)
    Servername: reader80.eternal-september.org
    Port : 80
    Servername: reader443.eternal-september.org
    Port : 443 (encrypted connection NNTPS)

    Still not seeing 463 in the above.



    The third Servername reader443.* was my backup. I simply changed the
    port number from 443 to 563 used by my primary.


    Then I suggest an internet connection problem.

    That may well be.

    I forgot to mention checking that Pan is not attempting more than
    four concurrent connections at a time.


    --- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Jim Beard@2:250/1 to All on Mon Nov 30 19:06:39 2020
    On Mon, 30 Nov 2020 11:23:22 -0600, Bit Twister wrote:

    On Mon, 30 Nov 2020 14:39:36 -0000 (UTC), Jim Beard wrote:
    On Sun, 29 Nov 2020 14:33:00 -0600, Bit Twister wrote:

    On Sun, 29 Nov 2020 19:04:17 -0000 (UTC), Jim Beard wrote:
    Is anyone else using pan having problems?

    I am getting lots of error messages complaining of getting corrupted
    data when the connection is to reader463.eternal-september.org.

    Where did you get that 463 id. Suggest reading
    http://www.eternal-september.org/index.php?showpage=techinfo

    From the page just above:
    Client Settings Server name: news.eternal-september.org Port : 119
    (NNTP)
    Port : 563 (encrypted connection NNTPS)
    Servername: reader80.eternal-september.org Port : 80 Servername:
    reader443.eternal-september.org Port : 443 (encrypted connection NNTPS)

    Still not seeing 463 in the above.

    Typo. My bad.

    The third Servername reader443.* was my backup. I simply changed the
    port number from 443 to 563 used by my primary.


    Then I suggest an internet connection problem.

    That may well be.

    I forgot to mention checking that Pan is not attempting more than four concurrent connections at a time.

    Cheers!

    jim b.

    --
    UNIX is not user-unfriendly, it merely expects users to be computer-
    friendly.

    --- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)