Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

pfsd: Unnecessary logging of picked UPnP ports #5

Open
VoyTechnology opened this issue Jun 14, 2022 · 1 comment
Open

pfsd: Unnecessary logging of picked UPnP ports #5

VoyTechnology opened this issue Jun 14, 2022 · 1 comment

Comments

@VoyTechnology
Copy link
Member

Output of meta/logs/pfsd.log:

2016/02/10 19:46:13 [INFO]  main: UPnP devices available
2016/02/10 19:46:13 [INFO]  upnp: Picked port: 40949
2016/02/10 19:46:13 [INFO]  upnp: Picked port: 58583
2016/02/10 19:46:13 [INFO]  upnp: Picked port: 41288
2016/02/10 19:46:13 [INFO]  upnp: Picked port: 36086
2016/02/10 19:46:13 [INFO]  upnp: Picked port: 518
2016/02/10 19:46:13 [INFO]  upnp: Picked port: 14587
2016/02/10 19:46:13 [INFO]  upnp: Picked port: 1547
2016/02/10 19:46:13 [INFO]  upnp: Picked port: 24300
2016/02/10 19:46:13 [INFO]  upnp: Picked port: 54828
2016/02/10 19:46:13 [INFO]  upnp: Picked port: 21832
2016/02/10 19:46:13 [INFO]  main: Peer address: 192.168.192.26:34529
2016/02/10 19:46:14 [INFO]  dnetclient: Currently Connected: 192.168.192.26:38659,
2016/02/10 19:46:14 [INFO]  dnetclient: Successfully joined discovery network
2016/02/10 19:46:14 [INFO]  main: Starting ParanoidNetwork server with TLS.

Steps to reproduce this issue:

paranoid-cli mount test test

Update: This looks like its only logging it unnecessarly and not actually picking the ports

@VoyTechnology
Copy link
Member Author

Looks like we can kill pfsd/upnp package completely with https://github.com/NebulousLabs/go-upnp

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant