Subj : Networking Questions To : Avon From : Daniel Path Date : Fri Jun 18 2021 08:50 pm Hello Avon. 18 Jun 21 20:55, you wrote to acn: A> @TID: Mystic BBS 1.12 A46 A> @MSGID: 21:1/101 990aa3a1 A> @REPLY: 21:3/127.1@fsxnet f18862e9 A> @TZUTC: 1200 A> On 18 Jun 2021 at 10:15a, acn pondered and said... ac>> Hallo Avon, A> Hi, and thanks for the reply :) ac>> First, if you prefer "eth0" over "enp4sdfsd523", you can change ac>> this behaviour in the kernel commandline by adding these ac>> parameters: net.ifnames=0 biosdevname=0 A> I don't know how/where to do that in debian 10 sorry https://wiki.debian.org/NetworkInterfaceNames ac>> The enps432 devices get its name during bootup with the intention ac>> to be predictible, so that eth0 won't be eth1 on the next boot. A> I don't mind using the name defined on boot, it's just getting it A> talking to my rpi that's running the he.net tunnel that I think?? is A> the issue. ac>> On my BBS machine, I use the following lines in ac>> /etc/network/interfaces: ac>> ac>> ==== cut here for new monitor ==== ac>> auto lo ac>> iface lo inet loopback ac>> ac>> auto eth0 ac>> iface eth0 inet static ac>> address 192.168.14.85 ac>> netmask 255.255.255.0 ac>> gateway 192.168.14.1 ac>> dns-search narnia.lan ac>> dns-nameservers 192.168.14.5 192.168.14.1 ac>> ac>> iface eth0 inet6 static ac>> privext 0 ac>> address 2001:470:540b::f1d0:2:240:5824/64 A> At the moment I have left mine as A> source /etc/network/interfaces.d/* A> # The loopback network interface A> auto lo A> iface lo inet loopback A> # some test settings to set ipv4 A> # auto eth0 A> # iface eth0 inet static A> # address 192.168.1.131 A> # netmask 225.255.255.0 A> # gateway 192.168.1.254 A> # some test settings to set ipv6 A> # iface eth0 inet6 static A> # address 2001:470:c:123::200 A> # netmask 64 A> # gateway 2001:470:c:123::5 A> you can see my commented out attempts... ac>> This results in this "ip a" output for eth0: A> Mine is A> avon@orac:/$ ip a A> 1: lo: mtu 65536 qdisc noqueue state UNKNOWN A> group default qlen 1000 A> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 A> inet 127.0.0.1/8 scope host lo A> valid_lft forever preferred_lft forever A> inet6 ::1/128 scope host A> valid_lft forever preferred_lft forever A> 2: enp4s0: mtu 1500 qdisc pfifo_fast A> state UP group default qlen 1000 A> link/ether 1c:6f:65:d7:70:04 brd ff:ff:ff:ff:ff:ff A> inet 192.168.1.131/24 brd 192.168.1.255 scope global noprefixroute A> enp4s0 A> valid_lft forever preferred_lft forever A> inet6 2001:470:c:123::200/64 scope global A> valid_lft forever preferred_lft forever A> inet6 fe80::1e6f:65ff:fed7:7004/64 scope link noprefixroute A> valid_lft forever preferred_lft forever ac>> I just noticed that in your "ip a" output, your inet6 entries ac>> have the option "noprefixroute" set. As far as I understand it, ac>> this means that no default route for this address has been ac>> (automatically) added. A> This I think is my problem, and I've been trying to google and test A> possible fixes all night, but so far no joy. ac>> So, if your problem persists, try looking at your IPv6 routing ac>> table using "route -n6" and search for your IPv6 default route, ac>> in my case it A> Here's mine A> avon@orac:/$ sudo route -n6 A> Kernel IPv6 routing table A> Destination Next Hop Flag Met Ref A> Use If ::1/128 :: U A> 256 2 0 lo 2001:470:c:123::/64 :: A> U 100 2 0 enp4s0 2001:470:c:123::/64 :: A> U 256 1 0 enp4s0 fe80::/64 :: A> U 100 1 0 enp4s0 ::/0 A> 2001:470:c:123::5 UG 100 5 0 enp4s0 ::1/128 A> :: Un 0 7 0 lo A> 2001:470:c:123::200/128 :: Un 0 5 A> 0 enp4s0 fe80::1e6f:65ff:fed7:7004/128 :: Un A> 0 3 0 enp4s0 ff00::/8 :: A> U 256 6 0 enp4s0 ::/0 :: A> !n -1 1 0 lo ac>> ::/0 fe80::464e:6dff:fe22:35c UGDAe 1024 2 0 eth0 A> ::/0 2001:470:c:123::5 UG 100 5 0 enp4s0 A> perhaps something is amiss here? ac>> How are you advertising your prefix in your LAN? A> It's using Radvd on my Rpi which is on the LAN and is set up as the A> end point for the he.net tunnel. ac>> In my case, my tunnel endpoint is on my DSL router (AVM FritzBox) ac>> and "router advertisement" is active here. A> Rpi for me. in all my mucking about I must have once found a way for A> the debian box to see the Rpi as it did pick up a dynamic IPv6 once A> and I could ping that from outside my LAN... stuffed if I recall how A> now :( ac>> As far as I know, via router advertisement also the default ac>> gateway can be sent to the clients. Is this configured? A> Don't know it's been years since I set the Pi up... the windows boxes A> work fine I am cautious about touching the pi gateway/endpoint of the A> tunnel. ac>> I hope that helps you a little. A> It does :) A> --- Mystic BBS v1.12 A46 2020/08/26 (Linux/64) A> * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz A> (21:1/101) A> SEEN-BY: 1/100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 A> 115 116 A> SEEN-BY: 1/117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 A> 133 134 A> SEEN-BY: 1/135 137 138 139 140 141 142 143 144 145 146 147 148 149 150 A> 151 152 A> SEEN-BY: 1/153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 A> 168 169 A> SEEN-BY: 1/171 172 173 174 175 176 177 178 180 181 182 183 184 185 186 A> 187 188 A> SEEN-BY: 1/189 190 191 192 193 194 195 197 198 199 200 201 202 203 204 A> 205 206 A> SEEN-BY: 1/207 208 209 211 212 213 214 215 216 217 218 219 220 221 222 A> 223 224 A> SEEN-BY: 1/225 226 227 228 616 995 2/100 1202 3/100 4/10 100 103 105 A> 106 107 A> SEEN-BY: 4/108 110 113 114 115 117 122 123 124 127 129 130 131 132 134 A> 136 139 A> SEEN-BY: 4/140 141 142 143 144 145 146 147 148 149 151 156 157 165 166 A> 167 168 A> SEEN-BY: 4/171 172 5/100 A> @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) .