interface is by my recollection at the same level as the 192.168…, and there is a 10…. I’ll follow up on the UPnP within MikroTik – I looked briefly yesterday, but had not knowingly relied on UPnP to control port opening. The MikroTik does have a Firewall>=NAT area, which is where I tried the port-forwarding. Yes, I used to get the port-binding errors quite frequently (n times a day) on B14 (and probably before, but not keep track of them, just changed the listening port). Yes, I rebooted the PC and power-down-wait-power-upped the PC and router. The timeline was: all fine, seeding ~65 torrents, B15 message came in, I said goferit, B15 (updater) restarted, B15 looked fine except for NAT problem (no incoming connections, seeding rate=0). Thanks parg! Yay on the not-BBT! Must be coincidence. I am happy to answer questions about data that I have failed to provide.īiglyBT2203-B15, Windows 10, MikroTik routerīBT listening port 61500 (TCP & UDP, not randomised on restart) I feel I have exhausted the possibilities to remedy the situation myself, and wonder if there is anyone who has fixed a similar problem, or can advise on port-forwarding. The plugins_mlDHT_2.2.9.zip (Sun 19-01-2020 22:11) has not downloaded anything and the Sources tab (Downloading view) reports 0 seeds and 0 peers for it. There was minor I2P uploading until I disabled I2P as part of trying to fix things. The Sources tab in Library view (Completed) reports peers available as per normal. I was not able to implement the 2203B14 torrent (worked perfectly) as there was already a copy of it downloaded. I have downloaded BiglyBT2202 (non-Beta), but the same problem persists. I have tried to implement port-forwarding, but this has failed, very possibly due to my lack of experience in port-forwarding (uncertain of Src, Dest perspective, but tried googled advice). Windows 10 Firewall has appropriate rules set to allow BiglyBt.exe including at Group level. Since there is no incoming, I cannot use that avenue to get help. Decentralised chats are blank, and contain only my nick (in Green, as per B15). The Network Status Test fails for incoming TCP and UDP. The NAT/Firewall-test reports time-outs for both TCP and UDP protocols. Since the updater-restart, there has been a “Firewalled” problem, and no two-way traffic possible.Īll other Internet functions (browser, WhatsApp, eMail) work normally, so the problem appears to be BBT specific, and across generations of BBT and days of attempted fixes.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |