notcarl

Members
  • Posts

    3
  • Joined

  • Last visited

notcarl's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Piggybacking on this. I am having the same exact issue with mullvad. It will start if I remove ,::0/0. This will forward all ipv4 connections but leaves all ipv6 exposed. This isn't an issue while running in the bridge network but for containers using the host container they will still use ipv6. Is there going to be a patch that allows us to forward both ipv4 and ipv6 soon?
  2. In response to my previous issue dealing with this error Caught internal_error: 'Read past initial payload after incoming encrypted handshake.'. ---DUMP--- /usr/lib/libtorrent.so.19(_ZN7torrent14internal_error10initializeERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE+0x25a) [0x7f1c8345489a] /usr/bin/rtorrent(_ZN7torrent14internal_errorC1EPKc+0xb1) [0x55c68615adb1] /usr/lib/libtorrent.so.19(+0x3cfe2) [0x7f1c83449fe2] /usr/lib/libtorrent.so.19(_ZN7torrent9PollEPoll7performEv+0xca) [0x7f1c8346f91a] /usr/lib/libtorrent.so.19(_ZN7torrent9PollEPoll7do_pollEli+0x79) [0x7f1c8346fa39] /usr/lib/libtorrent.so.19(_ZN7torrent11thread_base10event_loopEPS0_+0x123) [0x7f1c834a0583] /usr/bin/rtorrent(+0x4542c) [0x55c6860fd42c] /usr/lib/libc.so.6(__libc_start_main+0xf2) [0x7f1c83028002] /usr/bin/rtorrent(+0x45c6e) [0x55c6860fdc6e] I have been using the version of this docker that came out 2 years ago running rTorrent 0.9.7 and this error seems to have been fixed with this version onward. Would there be any issue with me using the current version of this docker so I would be able to use ruTorrent 3.9 instead of 3.8 as well as pyrocore and just using pacman to install the current version from the aur which is rTorrent 0.9.8/0.13.8? I am not sure how that would play with how you have the container set up. I have already reported this to pyroscope in hopes that it could get fixed and not have to use a jank setup.
  3. I've been getting this error that is causing fatal errors and requiring rtorrent to have a restart. The only bandaid fix for this I've found was disabling encryption entirely. Is there any plans to updating rtorrent to something beyond 0.9.6 it doesn't seem to appear in the newer versions and I would like to have the option to accept encrypted connections. Error log from a recent crash below: 1595149504 C Caught internal_error: 'Read past initial payload after incoming encrypted handshake.'. ---DUMP--- /usr/lib/libtorrent.so.19(_ZN7torrent14internal_error10initializeERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE+0x25a) [0x7fa11ec7d89a] /usr/bin/rtorrent(_ZN7torrent14internal_errorC1EPKc+0xb1) [0x55aa2cf27db1] /usr/lib/libtorrent.so.19(+0x3cfe2) [0x7fa11ec72fe2] /usr/lib/libtorrent.so.19(_ZN7torrent9PollEPoll7performEv+0xca) [0x7fa11ec9891a] /usr/lib/libtorrent.so.19(_ZN7torrent9PollEPoll7do_pollEli+0x79) [0x7fa11ec98a39] /usr/lib/libtorrent.so.19(_ZN7torrent11thread_base10event_loopEPS0_+0x123) [0x7fa11ecc9583] /usr/bin/rtorrent(+0x4542c) [0x55aa2ceca42c] /usr/lib/libc.so.6(__libc_start_main+0xf2) [0x7fa11e851002] /usr/bin/rtorrent(+0x45c6e) [0x55aa2cecac6e]