I'm trying to set a static ipv6 address in the Debian box I am running the
BBS on. I've been using the GUI to set it but I can't ping the box
externally. If I let the box pick up a IPv6 from the Rpi tunnel I am running
I can ping that ipc6 address externally. This tells me it's the static
settings and/or gui I am using that is not working

I tried mucking around with /cat/network/interfaces but also no joy.

At present I see this when I run ip a

[sigh]

first hurdle... how do I now copy/paste text from a text editor into this terminal window running Mystic?

I used to (using Windows OS) just be able to copy and paste text between open windows... but now it seems not.

I can select and copy text in a terminal window running sublime text... but
how to paste here?

--- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

On 18 Jun 2021 at 04:10p, Avon pondered and said...

first hurdle... how do I now copy/paste text from a text editor into this terminal window running Mystic?

Solved, ctrl-shift-v ... who knew? Not me :)

I see this

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state
UP group default qlen 1000
link/ether 1c:6f:65:d7:70:04 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.131/24 brd 192.168.1.255 scope global noprefixroute enp4s0
valid_lft forever preferred_lft forever
inet6 2001:470:c:123::200/64 scope global noprefixroute
valid_lft forever preferred_lft forever
inet6 fe80::1e6f:65ff:fed7:7004/64 scope link noprefixroute
valid_lft forever preferred_lft forever

My intended IPv6 address on this box is 2001:470:c:123::200 and you will see
it uses 192.168.1.131 as the local LAN IP.

The network card seems to be called enp4s0 and I think the system auto
creates that. There's no mention of it in the 'interfaces' file at all.

I tried setting this

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

# some test settings to set ipv4

auto eth0
iface eth0 inet static
address 192.168.1.131
netmask 225.255.255.0
gateway 192.168.1.254

# some test settings to set ipv6

iface eth0 inet6 static
address 2001:470:c:123::200
netmask 64
gateway 2001:470:c:123::5


You'll note I tried eth0 but this did not work... when i changed eth0
to enp4s0 the OS booted but at the desktop it said I had no network
connection

It seems nutty how hard it is to set a static IPv6 address and desired gateway and keep everything else working :(

Any thoughts appreciated.

--- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

Am 18.06.21 schrieb Avon@21:1/101 in FSX_NET:

Hallo Avon,

Two ideas:

First, if you prefer "eth0" over "enp4sdfsd523", you can change this behaviour in the kernel commandline by adding these parameters:
net.ifnames=0 biosdevname=0

For the RasPi, it should be a file on the /boot partition.

The enps432 devices get its name during bootup with the intention to be predictible, so that eth0 won't be eth1 on the next boot.
This could happen as the eth-devices get its numbers in the order of activation by the drivers which is not garuanteed to be always in the same order. But if you only have one eth device, it's okay this way :)
(and eth0 is much better to memorize...)

It seems nutty how hard it is to set a static IPv6 address and desired gateway and keep everything else working :(

On my BBS machine, I use the following lines in /etc/network/interfaces:

==== cut here for new monitor ====
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet static
address 192.168.14.85
netmask 255.255.255.0
gateway 192.168.14.1
dns-search narnia.lan
dns-nameservers 192.168.14.5 192.168.14.1

iface eth0 inet6 static
privext 0
address 2001:470:540b::f1d0:2:240:5824/64
==== cut here for new monitor ====

This results in this "ip a" output for eth0:

==== cut here for new monitor ====
2: eth0: ...
link/ether 00:e0:c5:3b:eb:0c brd ff:ff:ff:ff:ff:ff
inet 192.168.14.85/24 brd 192.168.14.255 scope global eth0
valid_lft forever preferred_lft forever
inet6 2001:470:540b:0:f1d0:2:240:5824/64 scope global
valid_lft forever preferred_lft forever
inet6 fe80::2e0:c5ff:fe3b:eb0c/64 scope link
valid_lft forever preferred_lft forever
==== cut here for new monitor ====

I just noticed that in your "ip a" output, your inet6 entries have the
option "noprefixroute" set.
As far as I understand it, this means that no default route for this
address has been (automatically) added.

So, if your problem persists, try looking at your IPv6 routing table using "route -n6" and search for your IPv6 default route, in my case it is:

::/0 fe80::464e:6dff:fe22:35c UGDAe 1024 2 0 eth0

But I don't remember doing anything special to have this route be
created...

How are you advertising your prefix in your LAN?
In my case, my tunnel endpoint is on my DSL router (AVM FritzBox) and
"router advertisement" is active here.
As far as I know, via router advertisement also the default gateway can be sent to the clients. Is this configured?

I hope that helps you a little.

Regards,
Anna

--- OpenXP 5.0.50
* Origin: Imzadi Box Point (21:3/127.1)

On 18 Jun 2021 at 10:15a, acn pondered and said...

Hallo Avon,

Hi, and thanks for the reply :)

First, if you prefer "eth0" over "enp4sdfsd523", you can change this behaviour in the kernel commandline by adding these parameters:
net.ifnames=0 biosdevname=0

I don't know how/where to do that in debian 10 sorry

The enps432 devices get its name during bootup with the intention to be predictible, so that eth0 won't be eth1 on the next boot.

I don't mind using the name defined on boot, it's just getting it talking to
my rpi that's running the he.net tunnel that I think?? is the issue.

On my BBS machine, I use the following lines in /etc/network/interfaces:

==== cut here for new monitor ====
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet static
address 192.168.14.85
netmask 255.255.255.0
gateway 192.168.14.1
dns-search narnia.lan
dns-nameservers 192.168.14.5 192.168.14.1

iface eth0 inet6 static
privext 0
address 2001:470:540b::f1d0:2:240:5824/64

At the moment I have left mine as

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

# some test settings to set ipv4

# auto eth0
# iface eth0 inet static
# address 192.168.1.131
# netmask 225.255.255.0
# gateway 192.168.1.254

# some test settings to set ipv6

# iface eth0 inet6 static
# address 2001:470:c:123::200
# netmask 64
# gateway 2001:470:c:123::5

you can see my commented out attempts...

This results in this "ip a" output for eth0:

Mine is

avon@orac:/$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state
UP group default qlen 1000
link/ether 1c:6f:65:d7:70:04 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.131/24 brd 192.168.1.255 scope global noprefixroute enp4s0
valid_lft forever preferred_lft forever
inet6 2001:470:c:123::200/64 scope global
valid_lft forever preferred_lft forever
inet6 fe80::1e6f:65ff:fed7:7004/64 scope link noprefixroute
valid_lft forever preferred_lft forever

I just noticed that in your "ip a" output, your inet6 entries have the option "noprefixroute" set.
As far as I understand it, this means that no default route for this address has been (automatically) added.

This I think is my problem, and I've been trying to google and test possible fixes all night, but so far no joy.

So, if your problem persists, try looking at your IPv6 routing table
using "route -n6" and search for your IPv6 default route, in my case it

Here's mine

avon@orac:/$ sudo route -n6
Kernel IPv6 routing table
Destination Next Hop Flag Met Ref Use If ::1/128 :: U 256 2 0 lo 2001:470:c:123::/64 :: U 100 2 0 enp4s0
2001:470:c:123::/64 :: U 256 1 0 enp4s0
fe80::/64 :: U 100 1 0 enp4s0
::/0 2001:470:c:123::5 UG 100 5 0 enp4s0
::1/128 :: Un 0 7 0 lo 2001:470:c:123::200/128 :: Un 0 5 0 enp4s0
fe80::1e6f:65ff:fed7:7004/128 :: Un 0 3 0 enp4s0
ff00::/8 :: U 256 6 0 enp4s0
::/0 :: !n -1 1 0 lo

::/0 fe80::464e:6dff:fe22:35c UGDAe 1024 2 0 eth0

::/0 2001:470:c:123::5 UG 100 5 0 enp4s0

perhaps something is amiss here?

How are you advertising your prefix in your LAN?

It's using Radvd on my Rpi which is on the LAN and is set up as the end point for the he.net tunnel.

In my case, my tunnel endpoint is on my DSL router (AVM FritzBox) and "router advertisement" is active here.

Rpi for me. in all my mucking about I must have once found a way for the
debian box to see the Rpi as it did pick up a dynamic IPv6 once and I could ping that from outside my LAN... stuffed if I recall how now :(

As far as I know, via router advertisement also the default gateway can
be sent to the clients. Is this configured?

Don't know it's been years since I set the Pi up... the windows boxes work
fine I am cautious about touching the pi gateway/endpoint of the tunnel.

I hope that helps you a little.

It does :)

--- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

On 18 Jun 2021 at 10:15a, acn pondered and said...

Success.

I ended up checking and rechecking some IPv6 address settings and I think I have got things running. I needed a 'd' instead of a 'c' in my address setup
on the debian box.

At this stage I can now ping6 out and I think incoming ipv6 traffic to the
box may work too. I think.

If you can ping6 agency.bbs.nz and get a reply it's a good sign.

Al (and others) if you could test binkp polling over IPv6 that would be good too... :)

--- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

On 06-18-21 16:10, Avon wrote to All <=-

I'm trying to set a static ipv6 address in the Debian box I am running
the BBS on. I've been using the GUI to set it but I can't ping the box externally. If I let the box pick up a IPv6 from the Rpi tunnel I am running I can ping that ipc6 address externally. This tells me it's the static settings and/or gui I am using that is not working

I tried mucking around with /cat/network/interfaces but also no joy.

Onme thing I've found is that if you're setting a static IP, the default gateway needs to be the _link local_ address of your IPv6 router, if you're on a LAN. By router, I mean either dedicated box (like I'm using) or a host acting as a router (e.g Linux based tunnel router).

At present I see this when I run ip a

[sigh]

first hurdle... how do I now copy/paste text from a text editor into
this terminal window running Mystic?

Don't know (system specific)

I used to (using Windows OS) just be able to copy and paste text
between open windows... but now it seems not.

Linux has so many different desktops that it's hard to know.

I do often cheat - SSH via PuTTY from a Windows desktop does allow for easy copy and paste. :)

... What did the cannibal call two hunters in a jeep? Meals on wheels!
=== MultiMail/Win v0.52
--- SBBSecho 3.10-Linux
* Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (21:1/109)

On 06-18-21 16:19, Avon wrote to All <=-

On 18 Jun 2021 at 04:10p, Avon pondered and said...

first hurdle... how do I now copy/paste text from a text editor into this terminal window running Mystic?

Solved, ctrl-shift-v ... who knew? Not me :)

Cool. :)

I see this

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 1c:6f:65:d7:70:04 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.131/24 brd 192.168.1.255 scope global noprefixroute enp4s0
valid_lft forever preferred_lft forever
inet6 2001:470:c:123::200/64 scope global noprefixroute
valid_lft forever preferred_lft forever
inet6 fe80::1e6f:65ff:fed7:7004/64 scope link noprefixroute
valid_lft forever preferred_lft forever

My intended IPv6 address on this box is 2001:470:c:123::200 and you
will see it uses 192.168.1.131 as the local LAN IP.

The network card seems to be called enp4s0 and I think the system auto creates that. There's no mention of it in the 'interfaces' file at all.

I tried setting this

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

# some test settings to set ipv4

auto eth0
iface eth0 inet static
address 192.168.1.131
netmask 225.255.255.0
gateway 192.168.1.254

# some test settings to set ipv6

iface eth0 inet6 static
address 2001:470:c:123::200
netmask 64
gateway 2001:470:c:123::5

You'll note I tried eth0 but this did not work... when i changed eth0
to enp4s0 the OS booted but at the desktop it said I had no network connection

It seems nutty how hard it is to set a static IPv6 address and desired gateway and keep everything else working :(

Here's the /etc/network/interfaces on my BBS machine. Multiple static IPs, the works. ;) Note the fe80: address for the default gateway.

auto lo

iface lo inet loopback

iface eth0 inet static
address 10.69.181.7
netmask 255.255.255.0
broadcast 10.69.181.255

auto eth0

iface eth0 inet6 static
address 2001:44b8:4176:f101::7
netmask 64
gateway fe80::e228:6dff:fe92:8799

iface eth0:0 inet static
address 202.12.89.164
netmask 255.255.255.240
gateway 202.12.89.161
broadcast 202.12.89.175
auto eth0:0

iface eth0 inet6 static
address 2001:44b8:4176:f101::7
netmask 64
gateway fe80::e228:6dff:fe92:8799

iface eth0:0 inet static
address 202.12.89.164
netmask 255.255.255.240
gateway 202.12.89.161
broadcast 202.12.89.175
auto eth0:0

iface eth0:1 inet static
address 44.136.76.3
netmask 255.255.255.0
#gateway 44.136.76.1
broadcast 44.136.76.255
up route add -net 44.0.0.0 netmask 255.0.0.0 gw 44.136.76.1 dev eth0:1
auto eth0:1

iface eth0:2 inet static
address 10.69.181.6
netmask 255.255.255.0
broadcast 10.69.181.255

auto eth0:2

iface eth0:2 inet6 static
address 2001:44b8:4176:f101::6
netmask 64
gateway fe80::e228:6dff:fe92:8799

iface eth0:3 inet static
address 202.12.89.162
netmask 255.255.255.240
gateway 202.12.89.161
broadcast 202.12.89.179
auto eth0:3


iface eth1 inet dhcp
auto eth1

allow-hotplug wlan0
iface wlan0 inet manual
wpa-roam /etc/wpa_supplicant/wpa_supplicant.conf
iface default inet dhcp

Any thoughts appreciated.

--- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

... Always address your elders with respect; they could leave you a fortune. === MultiMail/Win v0.52
--- SBBSecho 3.10-Linux
* Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (21:1/109)

Hello Avon!

On 18 Jun 2021, Avon said the following...

Success.

That's great!

If you can ping6 agency.bbs.nz and get a reply it's a good sign.

Tried from work, and it's working just fine:

PING agency.bbs.nz(2001:470:d:123::200 (2001:470:d:123::200)) 56 data bytes
64 bytes from 2001:470:d:123::200 (2001:470:d:123::200): icmp_seq=1 ttl=43 time=357 ms
64 bytes from 2001:470:d:123::200 (2001:470:d:123::200): icmp_seq=2 ttl=43 time=357 ms
64 bytes from 2001:470:d:123::200 (2001:470:d:123::200): icmp_seq=3 ttl=43 time=385 ms
64 bytes from 2001:470:d:123::200 (2001:470:d:123::200): icmp_seq=4 ttl=43 time=357 ms
64 bytes from 2001:470:d:123::200 (2001:470:d:123::200): icmp_seq=5 ttl=43 time=357 ms
64 bytes from 2001:470:d:123::200 (2001:470:d:123::200): icmp_seq=6 ttl=43 time=359 ms
64 bytes from 2001:470:d:123::200 (2001:470:d:123::200): icmp_seq=7 ttl=43 time=357 ms
64 bytes from 2001:470:d:123::200 (2001:470:d:123::200): icmp_seq=8 ttl=43 time=357 ms
64 bytes from 2001:470:d:123::200 (2001:470:d:123::200): icmp_seq=9 ttl=43 time=357 ms
64 bytes from 2001:470:d:123::200 (2001:470:d:123::200): icmp_seq=10 ttl=43 time=357 ms

--- agency.bbs.nz ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9011ms
rtt min/avg/max/mdev = 357.396/360.659/385.654/8.358 ms

Best regards
Zip

--- Mystic BBS v1.12 A47 2021/06/07 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (21:1/202)

I can select and copy text in a terminal window running sublime text... but how to paste here?

That depends on your terminal and whether or not you are using the clipboard or something else. I find a middle click, the mousewheel in my case will often paste the clipboard for me.

--- BBBS/Li6 v4.10 Toy-5
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106.2)

The network card seems to be called enp4s0 and I think the system auto creates that. There's no mention of it in the 'interfaces' file at all.

That looks like a systemd thing. My debian box shows something similar and my slackware box still uses eth0.

It seems nutty how hard it is to set a static IPv6 address and desired gateway
and keep everything else working :(

Yes, I prefer the old eth0 method, and still use it when I can.. :)

I can ping your agency.bbs.nz and net1.fsxnet.nz from my BBBS box just fine with IPv4 or IPv6.. :)

--- BBBS/Li6 v4.10 Toy-5
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106.2)

Avon wrote to All <=-

[snip]

My intended IPv6 address on this box is 2001:470:c:123::200 and you
will see it uses 192.168.1.131 as the local LAN IP.

I see you're getting your IPv6 block from HE.net as I do. Since you're configuring your bbs' IPv6 as a static, you also need to define a default
block route so the frames know how/where to route to/from. I do all mine
via a bash script. My primary network interface is a Realtek wifi (ra0)
and I have to do at least 2 things:
- define the IP in the interface:
ip -6 address add 2001:470:8a1e::3/48 dev ra0
- define a default IPv6 route:
ip -6 route add default via 2001:470:8a1e::1 dev ra0
- define an IPv6 IP for your router's ethernet device since your lan will
NOT require a 6-to-4 tunnel

Since I also broker IPv6 IPs for packet radio and they're not on my lan
but 6-to-4 tunnels I have to also add routes through my primary IPv6
router as well:
ip -6 route add 2001:470:8a1e::/48 dev ra0
ip -6 route add 2001:470:8a1e::5 via 2001:470:8a1e::1 dev ra0
ip -6 route add 2001:470:8a1e::6 via 2001:470:8a1e::1 dev ra0
ip -6 route add 2001:470:8a1e::7 via 2001:470:8a1e::1 dev ra0
ip -6 route add 2001:470:8a1e::8 via 2001:470:8a1e::1 dev ra0
ip -6 route add 2001:470:8a1e::13 via 2001:470:8a1e::1 dev ra0
ip -6 route add 2001:470:8a1e::14 via 2001:470:8a1e::1 dev ra0
ip -6 route add 2001:470:8a1e::15 via 2001:470:8a1e::1 dev ra0
ip -6 route add 2001:470:8a1e::16 via 2001:470:8a1e::1 dev ra0
ip -6 route add 2001:470:8a1e::17 via 2001:470:8a1e::1 dev ra0
ip -6 route add 2001:470:8a1e::2 via 2001:470:8a1e::1 dev ra0
ip -6 route add 2001:470:8a1e::20 via 2001:470:8a1e::1 dev ra0
ip -6 route add 2001:470:8a1e::21 via 2001:470:8a1e::1 dev ra0

Keep in mind also, you *must* build a parallel firewall for your IPv6
as you have for your IPv4 since it's treated separately. Instead of using "iptables" use "ip6tables". The rest is pretty much the same. Ex:
ip6tables -P INPUT DROP
ip6tables -A INPUT -p icmp -j ACCEPT
ip6tables -A INPUT -p icmpv6 -j ACCEPT

So looking at the above, the lan block route will use NDP (neighbor
discovery protocol) for devices on my lan while the rest that are
packet nodes will get forced to the primary gateway which also has
6-to-4 tunnels and routes per each packet node.

For packet, I'm using amprnet's IPv4 IPs to bind to since packet requires
the use of ARP for IP routing and IPv6 has eliminated ARP in favor of NDP,
so the 6-to-4 tunnels encapsulated under the 44net IPv4 IPs works slick as
it uses IP protocol 41 for it's transport.

As for your polling via bink, DNS resolution will give both IPv4 AND IPv6, with IPv6 taking the priority route. If you poll me and watch your interface you should see the connection establish via IPv6. What I see from you here so far:

n1uro@n1uro:~$ fping6 2001:470:d:123::200
2001:470:d:123::200 is alive

n1uro@n1uro:~$ host agency.bbs.nz
agency.bbs.nz has address 219.89.83.33
agency.bbs.nz has IPv6 address 2001:470:d:123::200

using UDP:
n1uro@n1uro:~$ traceroute6 !$
traceroute6 2001:470:d:123::200
traceroute to 2001:470:d:123::200 (2001:470:d:123::200), 30 hops max, 80 byte packets
1 gw-ipv6.n1uro.com (2001:470:8a1e::1) 5.823 ms 6.267 ms 6.249 ms
2 tunnel326296.tunnel.tserv4.nyc4.ipv6.he.net (2001:470:1f06:295::1) 34.577 ms 35.318 ms 32.164 ms
3 ve422.core1.nyc4.he.net (2001:470:0:5d::1) 38.265 ms 36.364 ms 38.595 ms
4 100ge9-1.core2.chi1.he.net (2001:470:0:298::1) 55.759 ms 56.304 ms 100ge2-1.core2.chi1.he.net (2001:470:0:4b8::1) 55.073 ms
5 100ge15-2.core1.chi1.he.net (2001:470:0:483::1) 57.875 ms 57.234 ms 56.855 ms
6 100ge5-2.core1.oma1.he.net (2001:470:0:43f::2) 68.091 ms 57.648 ms 60.818 ms
7 100ge10-2.core1.den1.he.net (2001:470:0:42e::1) 67.923 ms 123.434 ms 67.198 ms
8 100ge4-2.core1.cys1.he.net (2001:470:0:4b4::2) 67.511 ms 67.478 ms 66.712 ms
9 100ge2-2.core1.slc1.he.net (2001:470:0:4b6::1) 73.698 ms 87.282 ms 86.522 ms
10 e0-54.core2.las1.he.net (2001:470:0:4e4::2) 89.503 ms 91.497 ms 90.600 ms
11 e0-34.core2.lax2.he.net (2001:470:0:4ba::1) 100.460 ms 98.834 ms 98.444 ms
12 100ge10-2.core1.lax2.he.net (2001:470:0:1b6::1) 97.306 ms 95.469 ms 96.159 ms
13 100ge2-2.core1.lax1.he.net (2001:470:0:72::1) 97.748 ms 137.828 ms 148.936 ms
14 tserv1.lax1.he.net (2001:470:0:9d::2) 120.893 ms 96.913 ms 93.755 ms
15 tunnel398066-pt.tunnel.tserv15.lax1.ipv6.he.net (2001:470:c:123::2) 279.889 ms 281.073 ms 280.690 ms
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 *^C
(this tells me of a possible firewall issue)

Using ICMP:
n1uro@n1uro:~$ sudo traceroute6 -I 2001:470:d:123::200
traceroute to 2001:470:d:123::200 (2001:470:d:123::200), 30 hops max, 80 byte packets
1 gw-ipv6.n1uro.com (2001:470:8a1e::1) 1.835 ms 2.437 ms 2.419 ms
2 tunnel326296.tunnel.tserv4.nyc4.ipv6.he.net (2001:470:1f06:295::1) 27.775 ms 33.021 ms 34.525 ms
3 ve422.core1.nyc4.he.net (2001:470:0:5d::1) 34.141 ms 37.018 ms 36.000 ms
4 100ge2-1.core2.chi1.he.net (2001:470:0:4b8::1) 47.897 ms 52.759 ms 49.733 ms
5 100ge15-2.core1.chi1.he.net (2001:470:0:483::1) 53.101 ms 48.599 ms 51.356 ms
6 100ge5-2.core1.oma1.he.net (2001:470:0:43f::2) 61.340 ms 62.032 ms 62.984 ms
7 100ge10-2.core1.den1.he.net (2001:470:0:42e::1) 86.350 ms 66.550 ms 66.964 ms
8 100ge4-2.core1.cys1.he.net (2001:470:0:4b4::2) 70.579 ms 68.719 ms 67.331 ms
9 100ge2-2.core1.slc1.he.net (2001:470:0:4b6::1) 73.821 ms 74.111 ms 73.349 ms
10 e0-54.core2.las1.he.net (2001:470:0:4e4::2) 82.124 ms 87.489 ms 87.210 ms
11 e0-34.core2.lax2.he.net (2001:470:0:4ba::1) 92.430 ms 91.158 ms 99.455 ms
12 100ge10-2.core1.lax2.he.net (2001:470:0:1b6::1) 92.434 ms 87.474 ms 89.101 ms
13 100ge2-2.core1.lax1.he.net (2001:470:0:72::1) 91.201 ms 88.182 ms 93.716 ms
14 tserv1.lax1.he.net (2001:470:0:9d::2) 94.006 ms 93.264 ms 98.099 ms
15 tunnel398066-pt.tunnel.tserv15.lax1.ipv6.he.net (2001:470:c:123::2) 364.078 ms 354.166 ms 348.063 ms
16 2001:470:d:123::200 (2001:470:d:123::200) 338.341 ms 334.199 ms 326.155 ms

No reverse dns? :) Otherwise a traceroute using ICMP works.

Hope this helps ya out!

... Joseph to Mary: "What do you mean, 'It's a GIRL?'"
--- MultiMail/Linux v0.52
* Origin: Carnage - risen from the dead now on SBBS (21:4/107)

Hello Avon.

18 Jun 21 20:55, you wrote to acn:

@TID: Mystic BBS 1.12 A46
@MSGID: 21:1/101 990aa3a1
@REPLY: 21:3/127.1@fsxnet f18862e9
@TZUTC: 1200
On 18 Jun 2021 at 10:15a, acn pondered and said...

Hallo Avon,

Hi, and thanks for the reply :)

First, if you prefer "eth0" over "enp4sdfsd523", you can change
this behaviour in the kernel commandline by adding these
parameters: net.ifnames=0 biosdevname=0

I don't know how/where to do that in debian 10 sorry

https://wiki.debian.org/NetworkInterfaceNames

The enps432 devices get its name during bootup with the intention
to be predictible, so that eth0 won't be eth1 on the next boot.

I don't mind using the name defined on boot, it's just getting it
talking to my rpi that's running the he.net tunnel that I think?? is
the issue.

On my BBS machine, I use the following lines in
/etc/network/interfaces:

==== cut here for new monitor ====
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet static
address 192.168.14.85
netmask 255.255.255.0
gateway 192.168.14.1
dns-search narnia.lan
dns-nameservers 192.168.14.5 192.168.14.1

iface eth0 inet6 static
privext 0
address 2001:470:540b::f1d0:2:240:5824/64

At the moment I have left mine as

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

# some test settings to set ipv4

# auto eth0
# iface eth0 inet static
# address 192.168.1.131
# netmask 225.255.255.0
# gateway 192.168.1.254

# some test settings to set ipv6

# iface eth0 inet6 static
# address 2001:470:c:123::200
# netmask 64
# gateway 2001:470:c:123::5

you can see my commented out attempts...

This results in this "ip a" output for eth0:

Mine is

avon@orac:/$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 1c:6f:65:d7:70:04 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.131/24 brd 192.168.1.255 scope global noprefixroute enp4s0
valid_lft forever preferred_lft forever
inet6 2001:470:c:123::200/64 scope global
valid_lft forever preferred_lft forever
inet6 fe80::1e6f:65ff:fed7:7004/64 scope link noprefixroute
valid_lft forever preferred_lft forever

I just noticed that in your "ip a" output, your inet6 entries
have the option "noprefixroute" set. As far as I understand it,
this means that no default route for this address has been
(automatically) added.

This I think is my problem, and I've been trying to google and test possible fixes all night, but so far no joy.

So, if your problem persists, try looking at your IPv6 routing
table using "route -n6" and search for your IPv6 default route,
in my case it

Here's mine

avon@orac:/$ sudo route -n6
Kernel IPv6 routing table
Destination Next Hop Flag Met Ref
Use If ::1/128 :: U
256 2 0 lo 2001:470:c:123::/64 ::
U 100 2 0 enp4s0 2001:470:c:123::/64 ::
U 256 1 0 enp4s0 fe80::/64 ::
U 100 1 0 enp4s0 ::/0
2001:470:c:123::5 UG 100 5 0 enp4s0 ::1/128
:: Un 0 7 0 lo
2001:470:c:123::200/128 :: Un 0 5
0 enp4s0 fe80::1e6f:65ff:fed7:7004/128 :: Un
0 3 0 enp4s0 ff00::/8 ::
U 256 6 0 enp4s0 ::/0 ::
!n -1 1 0 lo

::/0 fe80::464e:6dff:fe22:35c UGDAe 1024 2 0 eth0

::/0 2001:470:c:123::5 UG 100 5 0 enp4s0

perhaps something is amiss here?

How are you advertising your prefix in your LAN?

It's using Radvd on my Rpi which is on the LAN and is set up as the
end point for the he.net tunnel.

In my case, my tunnel endpoint is on my DSL router (AVM FritzBox)
and "router advertisement" is active here.

Rpi for me. in all my mucking about I must have once found a way for
the debian box to see the Rpi as it did pick up a dynamic IPv6 once
and I could ping that from outside my LAN... stuffed if I recall how
now :(

As far as I know, via router advertisement also the default
gateway can be sent to the clients. Is this configured?

Don't know it's been years since I set the Pi up... the windows boxes
work fine I am cautious about touching the pi gateway/endpoint of the tunnel.

I hope that helps you a little.

It does :)

--- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz
(21:1/101)
SEEN-BY: 1/100 101 102 103 104 105 106 107 108 109 110 111 112 113 114
115 116
SEEN-BY: 1/117 118 119 120 121 122 123 124 125 126 127 128 129 130 131
133 134
SEEN-BY: 1/135 137 138 139 140 141 142 143 144 145 146 147 148 149 150
151 152
SEEN-BY: 1/153 154 155 156 157 158 159 160 161 162 163 164 165 166 167
168 169
SEEN-BY: 1/171 172 173 174 175 176 177 178 180 181 182 183 184 185 186
187 188
SEEN-BY: 1/189 190 191 192 193 194 195 197 198 199 200 201 202 203 204
205 206
SEEN-BY: 1/207 208 209 211 212 213 214 215 216 217 218 219 220 221 222
223 224
SEEN-BY: 1/225 226 227 228 616 995 2/100 1202 3/100 4/10 100 103 105
106 107
SEEN-BY: 4/108 110 113 114 115 117 122 123 124 127 129 130 131 132 134
136 139
SEEN-BY: 4/140 141 142 143 144 145 146 147 148 149 151 156 157 165 166
167 168
SEEN-BY: 4/171 172 5/100
@PATH: 1/101 100 4/100

sorry i can't delete lines remotely :)

Daniel

... BBS: Uptime is 02d 20h 02m 36s (BT-Uptime/OS2, V1.5)
--- GoldED+/EMX 1.1.4.7
* Origin: Roon's BBS - Budapest, HUNGARY (21:4/148)

On 18 Jun 2021 at 03:24p, Zip pondered and said...

That's great!

I know a bit of a relief if I'm honest.

If you can ping6 agency.bbs.nz and get a reply it's a good sign.

Tried from work, and it's working just fine:

PING agency.bbs.nz(2001:470:d:123::200 (2001:470:d:123::200)) 56 data

Cool thanks!

--- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

On 18 Jun 2021 at 06:51a, Al pondered and said...

I can ping your agency.bbs.nz and net1.fsxnet.nz from my BBBS box just fine with IPv4 or IPv6.. :)

Can you hit 24555 at Agency BBS using IPv6 or port 23? Thanks!

--- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

On 18 Jun 2021 at 02:35p, N1uro pondered and said...

I see you're getting your IPv6 block from HE.net as I do. Since you're

Thanks for all the info. I'll take some time to digest it now.

--- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

I can ping your agency.bbs.nz and net1.fsxnet.nz from my BBBS box just
fine with IPv4 or IPv6.. :)

Can you hit 24555 at Agency BBS using IPv6 or port 23? Thanks!

Yes, it's a little slow to respond, but I was just on your BBS and port 24555 is good also.

--- BBBS/Li6 v4.10 Toy-5
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106.2)

Hello Paul;

Avon wrote to N1uro <=-

I see you're getting your IPv6 block from HE.net as I do. Since you're

Thanks for all the info. I'll take some time to digest it now.

Print it up and enjoy sitting on the throne while you read it. Think of it
as a "tech newspaper" hahahaha <G>

... Old hypochondriacs never die, they just lose their grippe.
--- MultiMail/Linux v0.52
* Origin: Carnage - risen from the dead now on SBBS (21:4/107)

Avon wrote (2021-06-19):

On 18 Jun 2021 at 06:51a, Al pondered and said...

I can ping your agency.bbs.nz and net1.fsxnet.nz from my BBBS box
just fine with IPv4 or IPv6.. :)

Can you hit 24555 at Agency BBS using IPv6 or port 23? Thanks!

nothing...

nmap -6 2001:470:d:123::200
Starting Nmap 7.80 ( https://nmap.org ) at 2021-06-20 13:11 UTC
Nmap scan report for 2001:470:d:123::200
Host is up (0.21s latency).
All 1000 scanned ports on 2001:470:d:123::200 are filtered

Nmap done: 1 IP address (1 host up) scanned in 64.44 seconds


nmap -6 -p24553-24556 2001:470:d:123::200
Starting Nmap 7.80 ( https://nmap.org ) at 2021-06-20 13:15 UTC
Nmap scan report for 2001:470:d:123::200
Host is up (0.32s latency).

PORT STATE SERVICE
24553/tcp filtered unknown
24554/tcp filtered binkp
24555/tcp filtered unknown
24556/tcp filtered unknown

Nmap done: 1 IP address (1 host up) scanned in 4.56 seconds

---
* Origin: . (21:3/102)

acn wrote to Avon <=-

Two ideas:

First, if you prefer "eth0" over "enp4sdfsd523", you can change this behaviour in the kernel commandline by adding these parameters:
net.ifnames=0 biosdevname=0

oh thank you!


... Abandon desire
--- MultiMail/DOS v0.52
* Origin: realitycheckBBS.org -- information is power. (21:4/122)