Yes, I can ping... Something... :)
If you think the problem is in UFW, you can turn it off for a while. I think the problem is not there.
I think your problem is somehere in your router PI, you should open ports 24554-24555 there as well. But as I'm no linux expert, I dont think I
can help much more.
Your tunnel is working ok as you can poll out by ipv6.
His tunnel is working, he can make outbound connections. So the protocal 41 is open to the tunnel endpoint computer. (PI).
Yes, I can ping... Something... :)
Thanks, yes I can see IPv6 pings reaching the system running the BinkD server so traffic is getting to the machine concerned... just not it
seems to the port via IPv6
ping agency.bbs.nz
So far so good.
Paul Hayton wrote to Tommi Koivula <=-
On 11 Oct 2021 at 08:43p, Tommi Koivula pondered and said...
His tunnel is working, he can make outbound connections. So the protocal 41 is open to the tunnel endpoint computer. (PI).
I can also ping the Debian box via the Pi endpoint tunnel using IPv6...
so I figure things must almost be working as I can reach the system
from the internet via IPv6 and the tunnel using ping
I think your problem is somehere in your router PI, you should open ports
24554-24555 there as well. But as I'm no linux expert, I dont think I
can help much more.
So look at the Raspberry Pi that acts as the end point of the tunnel?
The main router connected to the internet does have 24554-24555 open already, and IPv4 traffic coming in via my ISP works OK
Question:
Is one native IPv6 and the other endpoint a 6-to-4 tunnel? This *may* be an issue. Using IPv4 as a test would help. I know natively on my access
At that PI you should open and/or forward ports. Which OS are you running there?
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.
If I can ping to the box that's not enough to know things are OK right?
OK will see what I can find.
Paul Hayton wrote to Brian Rogers <=-
No native IPv6 here :( I'm only able to access IPv6 because I run the he.net tunnel on the Raspberry Pi. It in turn assigns other devices on
my LAN their IPv6 addresses.
Before I moved to Linux for my HUB things worked fine on Windows for BinkD. So with the settings in the Edgerouter and the settings in the
RPi end point for the IPv6 tunnel unchanged, my hunch is that it's something not right in the Debian 10 box I built that now runs the HUB
and BBS
Paul Hayton wrote to All <=-
It turns out the Rpi endpoint of my he.net tunnel was missing some
FORWARD rules in the ip6tables setting. When I finally dug into that
and saw it was missing such a rule for the new static IPv6 I had set
for my new Linux box things finally started working.
If you would like to test
agency.bbs.nz
ipv6.agency.bbs.nz
ports 24554-24556
Paul Hayton wrote to Brian Rogers <=-
No native IPv6 here :( I'm only able to access IPv6 because I run the he.net tunnel on the Raspberry Pi. It in turn assigns other devices on
my LAN their IPv6 addresses.
Before I moved to Linux for my HUB things worked fine on Windows for BinkD. So with the settings in the Edgerouter and the settings in the
RPi end point for the IPv6 tunnel unchanged, my hunch is that it's something not right in the Debian 10 box I built that now runs the HUB
and BBS
n1uro@n1uro:~$ telnet6 ipv6.agency.bbs.nz 24554
Trying 2001:470:d:123::200...
Connected to ipv6.agency.bbs.nz.
Escape character is '^]'.
.OPT CRAM-MD5-63a15ca50d2db19365e6ebdec75a76eeSYS Agency + Risa HUBZYZ Paul HaytonLOC Dunedin, New Zealand)NDL 115200,TCP,CM,MO,IBN,BINKP,PING,IPv6%TIME Wed, 13 Oct 2021 17:14:26 +1300#VER binkd/1.1a-112/Linux binkp/1.1 3:57/0@fidonet
Ok, so by process of elimination, what happens when you shut off ALL your firewalling? Don't forget you probably have one firewall on your router,
If you would like to test
agency.bbs.nz
ipv6.agency.bbs.nz
ports 24554-24556
I'm hoping all is well now.
I think I figured it out (at last).
It turns out the Rpi endpoint of my he.net tunnel was missing some FORWARD rules in the ip6tables setting. When I finally dug into that and saw it was missing such a rule for the new static IPv6 I had set for my new Linux box things finally started working.
If you would like to test
agency.bbs.nz
ipv6.agency.bbs.nz
ports 24554-24556
Paul Hayton wrote to Brian Rogers <=-
Curious I ended up getting this message twice from you
It is! Now remove the "ipv4." in "ipv4.agency.bbs.nz" in the nodelist
and you are back as a full member of the Fidonet IPv6 club. ;-)
I wonder if it's because I had a desktop crash while drafting responses and a stale copy was in multimail?
Was it just this one?
Paul Hayton wrote to Brian Rogers <=-
Yep just one reply sent twice, but erm only seen this once ;-)
It had to have been the desktop crash then. I lost all my good taglines too *sigh*
I'm stuck as to know why I can't seem to get ports open for my IPv6 address when I have UFW seemingly enabled.
But it feels like I'm 90%+ sorted as I know the Debian box can happily poll outbound BinkD traffic without issue.
Any help appreciated.
It is! Now remove the "ipv4." in "ipv4.agency.bbs.nz" in the
nodelist and you are back as a full member of the Fidonet IPv6
club. ;-)
Doing this now. Cheers. :)
ifconfig
Doing this now. Cheers. :)
The change propagated to this friday's Z2 nodelist. :)
Hello Paul!
ifconfigDon't use this command for any purpose. Never.
Thanks for the ideas and tips. I have managed to solve my problem now.
A good nights sleep awaits.
ifconfig
Don't use this command for any purpose. Never.i like to know why ?
ifconfig
Don't use this command for any purpose. Never.
i like to know why ?
It uses deprecated API and may leave the kernel network stack in a
really unpredictable state.
ifconfig
Don't use this command for any purpose. Never.
i like to know why ?
It uses deprecated API and may leave the kernel network stack in a
really unpredictable state.
I guess you are using iptables instead of ipchains and ipfwadm. Or...
?
ifconfig
Don't use this command for any purpose. Never.
i like to know why ?
It uses deprecated API and may leave the kernel network stackwhat kernerl version do you refer to here ?
in a really unpredictable state.
and what ifconfig ?
that is usefull info imho
I guess you are using iptables instead of ipchains and ipfwadm.or maybe vim ? shorewall is my friend
Or... ?
2.6+
and what ifconfig ?Any.
that is usefull info imhoNot really, for over 10 years.
I guess you are using iptables instead of ipchains and ipfwadm.
Or... ?
or maybe vim ? shorewall is my friend
Very stupid.
| Sysop: | DaiTengu |
|---|---|
| Location: | Appleton, WI |
| Users: | 830 |
| Nodes: | 10 (1 / 9) |
| Uptime: | 76:29:40 |
| Calls: | 11,515 |
| Calls today: | 4 |
| Files: | 186,255 |
| Messages: | 1,821,393 |