starred/trackerslist-ngosang
1
0
Fork 0
mirror of https://github.com/ngosang/trackerslist.git synced 2026-04-25 09:25:59 +03:00
Code Issues 7 Projects Releases Packages Wiki Activity

[GH-ISSUE #81] Why should there be 127.0.0.1 in trackers ip list? #72

New issue
Closed
opened 2026-02-26 05:32:22 +03:00 by kerem · 2 comments
kerem commented 2026-02-26 05:32:22 +03:00
Owner
Copy link

Originally created by @Cabbagec on GitHub (Apr 13, 2018).
Original GitHub issue: https://github.com/ngosang/trackerslist/issues/81

Updated 2018-04-13 00:00:03
trackers_best_ip (20 trackers):

...
udp://123.249.16.65:2710/announce
udp://127.0.0.1:6969/announce
udp://210.244.71.25:6969/announce
...

There are also two 127.0.0.1 addresses on that day's trackers_all_ip (90 trackers) list.

Originally created by @Cabbagec on GitHub (Apr 13, 2018). Original GitHub issue: https://github.com/ngosang/trackerslist/issues/81 **Updated 2018-04-13 00:00:03** `trackers_best_ip (20 trackers)`: ``` ... udp://123.249.16.65:2710/announce udp://127.0.0.1:6969/announce udp://210.244.71.25:6969/announce ... ``` There are also two `127.0.0.1` addresses on that day's `trackers_all_ip (90 trackers)` list.
kerem closed this issue 2026-02-26 05:32:23 +03:00
kerem commented 2026-02-26 05:32:23 +03:00
Author
Owner
Copy link

@aurora-anon commented on GitHub (Apr 16, 2018):

@Cabbagec In cases where there's a local BitTorrent tracker server on a system.
The most likely address for such a server is udp://127.0.0.1:6969/announce

If there's such a server on a system, it may run on a different protocol or port and it can even be binded to another IP adddress, and after all, it may not have any data available for a requested torrent.
It may not be of much usefulness, but it's certainly of no harm.

<!-- gh-comment-id:381750179 --> @aurora-anon commented on GitHub (Apr 16, 2018): @Cabbagec In cases where there's a local BitTorrent tracker server on a system. The most likely address for such a server is udp://127.0.0.1:6969/announce If there's such a server on a system, it may run on a different protocol or port and it can even be binded to another IP adddress, and after all, it may not have any data available for a requested torrent. It may not be of much usefulness, but it's certainly of no harm.
kerem commented 2026-02-26 05:32:23 +03:00
Author
Owner
Copy link

@ngosang commented on GitHub (Apr 19, 2018):

The DNS domain of the tracker "christianbro.pw" is pointing to 127.0.0.1. It's bad configured so I'm removing from the list.
Anyway, this is not a security issue because your bittorrent client will try to connect to your own computer.

<!-- gh-comment-id:382839286 --> @ngosang commented on GitHub (Apr 19, 2018): The DNS domain of the tracker "christianbro.pw" is pointing to 127.0.0.1. It's bad configured so I'm removing from the list. Anyway, this is not a security issue because your bittorrent client will try to connect to your own computer.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
No results found.
Labels
Clear labels   
bug

   
enhancement

   
help wanted

   
pull-request

Mirrored from GitHub Pull Request

  
question

   
waiting

   
wontfix
No labels
bug
enhancement
help wanted
pull-request
question
waiting
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/trackerslist-ngosang#72
No description provided.