Hi, I am testing pylon on my pc to see if how it works and if it could be used as a workaround in situations where outgoing UDP traffic is blocked by corporate firewall but TCP/443 is allowed.
I have noticed that pylon generates a new node id at every run:
root@e14:/home/toni# //home/toni/bin/pylon refract abfd... --listen-addr 0.0.0.0 --listen-port 1080
pylon.cpp:001173: main: Running pylon instance in P2P mode
pylon.cpp:001235: main: No udp port set, picking random
pylon.cpp:001268: main: Waiting for zt node to come online...
pylon.cpp:001274: main: zt node: e6332cf4c9
pylon.cpp:001278: main: Joining network abfd... ... (please authorize)
pylon.cpp:001283: main: Waiting for network join to complete
^C
root@e14:/home/toni# /home/toni/bin/pylon refract abfd... --listen-addr 0.0.0.0 --listen-port 1080
pylon.cpp:001173: main: Running pylon instance in P2P mode
pylon.cpp:001235: main: No udp port set, picking random
pylon.cpp:001268: main: Waiting for zt node to come online...
pylon.cpp:001274: main: zt node: 1e87102fc6
pylon.cpp:001278: main: Joining network abfd... ... (please authorize)
pylon.cpp:001283: main: Waiting for network join to complete
^C
Is it normal? Maybe I am doing something wrong. It is not very practical having to authorize a new node every time.
Apart from that, even authorizing the node every time I did not manage to make it work. Setting pylon as a socks5 proxy in Firefox and trying to access a resource in the ZT network, hangs and does not load the page. My pc running pylon is a ZT node working fine. The documentation on github does not help much.