Menu

#45 problem after 24h disconnect

open
nobody
None
2
2004-09-27
2004-07-04
Anonymous
No

hey there!

there are some problems withinhin these version 1.5
beta 2

first.. not all users could connect... sometimes they
must open and close it a few times for running em right.

i think it's a problem with the ip detection.

second: there is a problem in the transfer window... it
stand for complete ( no changin') these "bug" is
everytime and takes some minutes.... only the network
status window let you know that the transfer is
working... how about a prozentage screener ?

third: there some things like 24 h disconnect... what
about a funktion for a adress (dyn dns for example) list
who re-connects automaticly on one of these ( after
disconnect )

i think there is a kind of trouble with the connection too-
cause the "speed" toggles very much up n down ( no
running appz in the backround )

feel free for more : Sammy2000@freenet.de

Discussion

  • Chris

    Chris - 2004-09-27

    Logged In: YES
    user_id=573676

    Can anyone translate this? Mr. Anonymous, if you're out
    there, I'd like to hear more about these bugs as you've
    given me nothing I can reproduce. Lowering priority until I
    can figure out what the bug report is saying.

     
  • Chris

    Chris - 2004-09-27
    • priority: 5 --> 2
     
  • Nobody/Anonymous

    Logged In: NO

    The problem is, after a forced disconnect from e.g. dsl
    networks, waste is unable to re-resolve the dyndns to the
    new address this clients gets after reconnecting. So, waste
    keeps trying to reconnect to the "old" ip of the client. You
    must re-open waste or do a manual nslookup and connect to
    the ip.

     

Log in to post a comment.

MongoDB Logo MongoDB