Displaying 2 results from an estimated 2 matches for "hp821".
2010 Feb 11
4
multiple addresses and multiple ports in Switch mode
...icated it may have mixed up the ports.
It doesn't appear to use the 28655 port that would be needed for remote
access. Before i changed to switch mode, the remote tincd nodes would have
28655 associated with the external ip address.
1265921476 tinc.vpn[5734]: Received packet of 92 bytes from hp821
(37.70.156.168 port 655)
1265921476 tinc.vpn[5734]: Broadcasting packet of 92 bytes from hp821
(37.70.156.168 port 655)
1265921476 tinc.vpn[5734]: Got unauthenticated packet from hp821
(37.70.156.168 port 655)
1265921476 tinc.vpn[5734]: Received packet of 60 bytes from hp821
(37.70.156.168 port 655...
2010 May 21
1
tinc confused on remote nodes behind NAT?
...tells me this was covered recently, but i didn't find it again in
gmail. The nodes see each other but if i have something misconfigured that
is decreasing my speed.
All my nodes are behind NATs.
i have a remote node that connects to a central node via port forwarding
from public port 7777 to hp821 running on port 655.
remoteNode ----> public ip 1.2.3.4:7777 ----> hp821:655
There are other nodes behind the central NAT that could be making outgoing
connections on port 655.