Just a sample of the Echomail archive
[ << oldest | < older | list | newer > | newest >> ]
|  Message 3693  |
|  Tommi Koivula to Paul Hayton  |
|  UFW and he.net  |
|  12 Oct 21 21:06:58  |
 REPLY: 3:770/100 a02371d9 MSGID: 2:221/360 6165d0f1 CHRS: CP437 2 TZUTC: 0300 Hi Paul. 12 Oct 21 15:43:00, you wrote to me: TK>> I think your problem is somehere in your router PI, you should open ports TK>> 24554-24555 there as well. But as I'm no linux expert, I dont think I TK>> can help much more. PH> So look at the Raspberry Pi that acts as the end point of the tunnel? At that PI you should open and/or forward ports. Which OS are you running there? PH> The main router connected to the internet does have 24554-24555 open PH> already, and IPv4 traffic coming in via my ISP works OK At the main router it is needed only to open protocol 41 from he.net to your PI so that the tunnel works. Anything else on the IPV4 side is irrelevant. In my Ubuntu: tommi@pin:~$ sudo ufw status|grep ipv6 Anywhere ALLOW 216.66.84.46/ipv6 But all this seems to be working at your setup... 'Tommi --- * Origin: rbb.fidonet.fi (2:221/360) SEEN-BY: 1/123 30/0 80/1 90/1 105/81 120/340 123/131 154/10 221/1 SEEN-BY: 221/6 226/30 227/702 229/424 426 428 550 664 700 240/1120 SEEN-BY: 240/5832 249/206 317 400 261/38 280/464 5555 282/464 1038 SEEN-BY: 301/0 1 101 113 812 317/3 322/757 335/364 342/200 460/58 SEEN-BY: 633/280 712/848 920/1 4500/1 5020/1042 5058/104 PATH: 221/6 301/1 229/426 |
[ << oldest | < older | list | newer > | newest >> ]