It’s just me @Josh.
I have a high preference for ipv6.
I don’t like ipv4 and currently ipv6 is actually the only thing that works for me.
P.S. The newer node/cli version isn’t working for me either.
5 Likes
4/20 here - I am (effectively) with TalkTalk
1 Like
Thats good to hear, as is
4 Likes
1 Like
I don’t seem to have ipv6 from my ISP either: 4 / 20
3 Likes
4/20 ipv6 not suported
1 Like
18/20 and ipv6 (sorry…)
It works for me right now with latest versions on a local IPv6 network.
sn_api: commit 723b52f
sn_node: commit d763b63
3 Likes
I’ve got both networks up and running.
Since I need to compile every time I switch versions, it’s taking me hours for it to finish, but when I do, I will have sn_node 0.26.7 running on both machines.
[update]
I’m currently running into an issue with node joining, so only one machine is running.
12 Likes
@folaht, your network is running fine.
Client side: I could create an account, a file container and a nrs map (tfa):
$ ./safe cat tfa
Files of FilesContainer (version 0) at "tfa":
+-------------------------+-----------------+------+----------------------+----------------------+--------------------------------------------------------------------+
| Name | Type | Size | Created | Modified | Link |
+-------------------------+-----------------+------+----------------------+----------------------+--------------------------------------------------------------------+
| /empty_dir | inode/directory | 0 | 2021-02-06T15:26:29Z | 2021-02-06T15:26:29Z | |
+-------------------------+-----------------+------+----------------------+----------------------+--------------------------------------------------------------------+
| /img | inode/directory | 0 | 2021-02-06T15:26:29Z | 2021-02-06T15:26:29Z | |
+-------------------------+-----------------+------+----------------------+----------------------+--------------------------------------------------------------------+
| /img/safe_logo_blue.svg | image/svg+xml | 5852 | 2021-02-06T15:26:29Z | 2021-02-06T15:26:29Z | safe://hygoykyeqx3yp6upna9wxan8tuwg8q59ma88f9mnwy84m3mbhh755jmothy |
+-------------------------+-----------------+------+----------------------+----------------------+--------------------------------------------------------------------+
| /index.html | text/html | 639 | 2021-02-06T15:26:29Z | 2021-02-06T15:26:29Z | safe://hy8oyryeurq5hcoqzyp5quj19azf3s5xtx5mfm4beu3at3gj6b5c3iwu4pc |
+-------------------------+-----------------+------+----------------------+----------------------+--------------------------------------------------------------------+
$ ./safe cat tfa/index.html
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<meta http-equiv="X-UA-Compatible" content="ie=edge">
<title>My simple safe site</title>
</head>
<body>
<h1>My simple safe site</h1>
<h2>Relative link:</h2>
<img src="img/safe_logo_blue.svg">
<h2>Absolute link:</h2>
<img src="/img/safe_logo_blue.svg">
<h2>Versioned safe link:</h2>
<img src="safe://test/img/safe_logo_blue.svg?v=0">
<h2>Unversioned safe link (shouldn't be displayed):</h2>
<img src="safe://test/img/safe_logo_blue.svg">
</body>
</html>
Node side: I launched a node. No error, but log is currently the following:
$ cat ~/.safe/node/root_dir/v.log
[sn_node] INFO 2021-02-06T16:14:25.245508257+01:00 [src/bin/sn_node.rs:90] Node PID is: 308314
[sn_node] INFO 2021-02-06T16:14:25.245656538+01:00 [src/bin/sn_node.rs:113]
Running sn_node v0.26.7
=======================
I guess my node is an infant waiting for acceptance. @maidsafe, I think the log should be explicit about this.
For anyone interested the command I used to launch my node was:
rm -rf ~/.safe/node/root_dir
mkdir -p ~/.safe/node/root_dir
./sn_node -m 2000000000 --ip my:ipv6:address --clean -p 5483 -h '["[2001:983:8610:1:854:efb1:52e6:85a3]:12000"]' -vvv > ~/.safe/node/root_dir/v.log 2>&1 &
Notes:
- Replace --ip parameter with your own IPv6 address and -p parameter with a port you have open on your machine
- 2 GB disk space dedicated to the node
- log with debug verbosity stored in ~/.safe/node/root_dir/v.log
-
--cleanflag doesn’t seem to remove previous node data, so I explicitly delete storage directory. @maidsafe, I think that--cleanshould do that.
11 Likes
That’s a bug for @lionel.faber
3 Likes
For information: when I kill a network brutally (executing pkill sn_node in each node) and restart all the nodes with --clean flag I observe that:
- blobs are not preserved (which is expected)
- accounts, file containers and nrs maps are preserved (which is a bug)
If, additionally, I delete ~/.safe/node/root_dir on each VM before restarting the nodes then nothing is preserved (which is normal).
EDIT:
I understand now that --clean is meant to delete current config file (but I am not sure how this is useful). Anyway, current situation where part of data are deleted is not good. It should be all or nothing, possibly controlled by a new flag (like --clear-data).
4 Likes
All this …patter about IPv6 made me finally subscribe to my ISP IPv6 beta program, which I eyed some time ago now…glad once more to have chosen aussiebroadband (I know what a name…)
If I manage to find iIdiot proof instructions scrolling the thread, I might try to crash your party, @folaht !
8 Likes
eheh I think I just got the welcome drink
MacBook-Pro-2:safe Home$ ./safe cat safe://hy8oycycfzs8a4y4x4p31tso5ajo38xk7j1sqtfkzw6zaf3ifutnkriyh9y
Bonjour chacun !
Does this mean we have an IPv6 community test-net ?!
10 Likes
feel free to send some test-coins @tfa @folaht !!
8b08a1a4baefc503e59a6783b96206d57fdcd794d89bc0e9f6ede71d3e6fcf52
SafeKey's current balance: 15.342000000
7 Likes
I intend to keep it running as long as possible,
although I do want to kill off the extra nodes,
until we end up with 11 machines running 1 node each.
2 Likes
Left it running on my wife’s laptop, but not sure what happenes when you move out from a IPv6 network? Would the node rejoin automatically when back on the IPv6 network?
On a side note, I’m new to IPv6, so if anybody has suggestions on how to secure the network I’d appreciate. Probably out of ignorance, but the lack of NAT makes me nervous: does that mean people can access the devices directly? My nergear r7000 doesn’t seem to have a firewall to secure the ipv6 network, and activating a firewall on each device is not an option the way I see it…
4 Likes
I’m in Indonesia (260 Mio people) , many ISP packages propose an IP Dynamic Private… meaning
- Ipv4 only
- you don’t even have public IP at all
(… and receive a captcha on Google search sometimes 
)
so I’m obviously 0/10
2 Likes
Turned the laptop back on, after it run out of power, fire the terminal and can cat tfa/index straight away?!
What is this, sorcery @maidsafe!?
4 Likes
I so far have not thought of security at all.
So far my security has been “using Linux” since the XP days, but I understand that since Windows 7, Microsoft has been a bit more careful on this issue.
Browsing for answers, I have read that NAT was not meant to secure the network, only to extend the IPv4 lifetime and that stateful firewalls is what people complaining about the loss of NAT firewalls should be looking for.
And yes, people can access IPv6 devices directly. That’s the intention.
My log is this:
[folaht@Rezosur-dy node-active-1]$ cat sn_node.log
[folaht@Rezosur-dy node-active-1]$
1 Like