Nп/п : 2 из 100
От : deon 3:633/509 07 янв 25 09:00:26
К : Dennis Slagers 07 янв 25 02:07:02
Тема : FidoNews 42:01 [02/08]: General Articles
----------------------------------------------------------------------------------
@MSGID: 9372.fdn_fidonews@3:633/509 2be1ad16
@REPLY: 2:280/2060 677c4784
@TZUTC: 1100
@PID: Synchronet 3.20a-Linux master/4bb08eded Dec 23
2024 GCC 10.2.1
@TID: SBBSecho 3.23-Linux master/4bb08eded Dec 23
2024 GCC 10.2.1
@COLS: 80
@BBSID: ALTERANT
@CHRS: CP437 2
@NOTE: FSEditor.js v1.105
Re: FidoNews 42:01 [02/08]: General Articles
By: Dennis Slagers to deon on Mon Jan 06 2025 10:13 pm
Howdy,
> How and what service/tools do you use? I am intrigued about it.
To use NAT64, you also need (to be using) a DNS server that is capable of DNS64.
The process is this:
* You resolve a hostname that has an IP4 (only) address. (If the
hostname also returns an AAAA record for IP6, then NAT64 wouldnt be need
anyway.)
A DNS server that is setup for DNS64, would return an AAAA record,
instead of an A record for the IP4 address, like:
eg: for tfb-bbs.org (180.150.99.174)
# host tfb-bbs.org
tfb-bbs.org has address 64:ff9b::b496:63ae
(bind supports DNS64).
* Your internal routing would then route 64:ff9b::/96 via a machine
running jool (the nat64 part). In theory you could use any IP6 net, but I
think most use 64:ff9b::/96.
Jool then proxies the connection to the IP4 address (hence it needs
to have a working internet IP4 stack) to the destination, and sends
the replies to the originator over IP6.
The jool machine doesnt need a public internet IP4 address, it can
still be an internal private address (192.168...), and if that was the
case, then your outgoing router would need to be doing SRC NAT to its
public IP4 address. (Like it probably would be anyway.)
In my case, I have an alpine virtual machine running on a PI4,
with 512MB memory. Alpine provides the jool app and kernel module.
nat64:/# apk list|grep jool
jool-modules-lts-6.6.56-r0 aarch64 {jool-modules-lts} (GPL-2.0-or-later)
[installed]
jool-modules-rpi-6.6.49-r0 aarch64 {jool-modules-rpi} (GPL-2.0-or-later)
jool-tools-4.1.11-r1 aarch64 {jool-tools} (GPL-2.0-only) [installed]
jool-tools-bash-completion-4.1.11-r1 aarch64 {jool-tools} (GPL-2.0-only)
jool-tools-doc-4.1.11-r1 aarch64 {jool-tools} (GPL-2.0-only)
jool-tools-openrc-4.1.11-r1 aarch64 {jool-tools} (GPL-2.0-only) [installed]
I ran it exclusively for a week on IP6, and it worked well. It
doesnt help you if you have some devices inside your network (like I do)
that dont have an IP6 stack. You`ll need to have them use a DNS server
that doesnt do the DNS64 bit (since they dont understand IP6), or
configure your bind server to not do DNS64 replies to those devices, via
ACLs.
...ыюхя
--- SBBSecho 3.23-Linux
* Origin: I`m playing with ANSI+videotex - wanna play too? (3:633/509)
SEEN-BY: 2/1000 50/109 105/81 106/201 128/187
129/305 153/7715 218/700 221/1
SEEN-BY: 226/30 227/114 229/110 114 200 206 300
312 317 400 426 428 470 616
SEEN-BY: 229/664 700 705 230/0 240/5832 266/512
280/464 282/1038 291/111
SEEN-BY: 292/140 789 854 8125 301/1 320/219
322/757 335/364 342/200 396/45
SEEN-BY: 410/9 450/1024 452/166 463/68 633/267 280
384 408 410 418 420 509
SEEN-BY: 633/2744 712/848 902/26 5000/111 5001/100
5015/46 5020/715 830 846
SEEN-BY: 5020/1042 4441 12000 5023/24 5030/49 1081
1474 5053/51 55 5060/900
SEEN-BY: 5061/133 5068/45 5075/128 5083/1 444
@PATH: 633/509 280 229/426 292/854 5020/1042 4441