Verify configuration for public IPs

[ParkerS]

Ah yes, I couldn’t do it in the portal either, exciting to see more gateways popping in, I’m working on getting my little home dc setup to handle 64 address block here in the next couple weeks

[Dany]

@weynandkuijpers could you please check one more time? It should work now.

Server is pingable!. see…

trace route looks good too.

[Dany]

Hey parkers,

can you give me some details on your cabling? Do you have a second NIC port in use for the public IPs on the nodes? I did some more testing and have now different scenarios configured.

have you ever tested routing to the public IPs assigned to your nodes? I mean not from the inside of you network but from the web?

[ParkerS]

I’m only using a single nic connection, it seems to be creating virtual interfaces because the nodes are using Mac’s that don’t physically exist in boxes,

I have a primary gateway that has a run to each node that handles all the subnetting, it really was pretty minimal on the configuration side once I realized that the node creates another interface with a static address using the information from the public config you put in on the polka dot Ui.

I’ve never had a test run but I had the impression they were working properly, would be news to me if they weren’t

So I just have my gateway hand out private subnet addresses at boot, then when I added the public config it created the static interface with the address inside of the public subnet range

[RobertL]

As i plan to bring some nodes to a local datacenter I’m following this thread. Seems we really could use a guide for dummies (me that is) on how to setup your node in a datacenter correctly.

[ParkerS]

theres definitely not alot of info on the gateway side, I have a few threads going with bits and pieces here

Building a Gigabit/Multi-gig public subnet on ATT Superfast Fiber (their name not mine)

To start this is going to be a long project, and there is going to be lots of episodes but the intent is to create a series of guides that would allow the average user to go from a standard network all the way to a 5 public node configuration on ATT fiber. This is a functional exercise for education, testing and development on the threefold network for your own personal gain. Over all Intend to the cover the topics installing or modifying ethernet drops, pulling wire, configuring a bgw-320 to ca…

Public Node Setup for the home user.

I’m incredibly lucky when it comes to isp, the head for my neighborhoods fiber happens to also be in my back yard, right now I can pull 1100-1250 down through my second node that has a 10g nic. Average pings about 12ms. There’s only 12 feet of 6a between the fiber and the node aswell. Att is telling me I’ll have their new 2.5/5gb service available by the end of this year, definitely a lot of opportunities to be had. Currently have a helium miner, these, gonna be running presearch, I’m less inte…

bit im workin on some bigger picture more general stuff now that will be more widely applicable as i figure it out myself. im active on discord telegram and here, let me know if i can help!

[ParkerS]

could you make sure my public ip config is working correctly on 2914,3049 or 3081, dany pointed out ive never tested it and ive been answering lots of questions assuming my setup was correct…

[ParkerS]

Dany, Congrats on being the first German gateway nodes!

theres only gateways in four countries right now and as far as I know, You and I are the only DIY gateways.

[weynandkuijpers]

Hi @Dany,

All looks good!

➜  terraform-dany git:(main) ✗ ssh root@178.250.167.69
ssh: connect to host 178.250.167.69 port 22: Connection refused
➜  terraform-dany git:(main) ✗ ping 178.250.167.69
PING 178.250.167.69 (178.250.167.69) 56(84) bytes of data.
64 bytes from 178.250.167.69: icmp_seq=1 ttl=51 time=135 ms
64 bytes from 178.250.167.69: icmp_seq=2 ttl=51 time=126 ms
64 bytes from 178.250.167.69: icmp_seq=3 ttl=51 time=137 ms
64 bytes from 178.250.167.69: icmp_seq=4 ttl=51 time=120 ms
64 bytes from 178.250.167.69: icmp_seq=5 ttl=51 time=128 ms
^C
--- 178.250.167.69 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4002ms
rtt min/avg/max/mdev = 119.557/129.110/136.627/6.248 ms
➜  terraform-dany git:(main) ✗ ssh root@178.250.167.69   
The authenticity of host '178.250.167.69 (178.250.167.69)' can't be established.
ED25519 key fingerprint is SHA256:GZduV+dbPnaRHqRwNzoO1JRVXS5eH+E7ZKeTcfzLrX8.
This host key is known by the following other names/addresses:
    ~/.ssh/known_hosts:33: 301:d12e:3351:4208:c32b:a725:4b6c:aa03
    ~/.ssh/known_hosts:35: 301:d12e:3351:4208:9a7c:cf44:d2d4:f788
    ~/.ssh/known_hosts:36: 301:d12e:3351:4208:6243:5c48:b899:8932
    ~/.ssh/known_hosts:37: 301:5393:bfab:9bfd:35f:140b:5736:7042
Are you sure you want to continue connecting (yes/no/[fingerprint])? yes
Warning: Permanently added '178.250.167.69' (ED25519) to the list of known hosts.
Welcome to Ubuntu 20.04.4 LTS (GNU/Linux 5.12.9 x86_64)

 * Documentation:  https://help.ubuntu.com
 * Management:     https://landscape.canonical.com
 * Support:        https://ubuntu.com/advantage

This system has been minimized by removing packages and content that are
not required on a system that users do not log into.

To restore this content, you can run the 'unminimize' command.

The programs included with the Ubuntu system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Ubuntu comes with ABSOLUTELY NO WARRANTY, to the extent permitted by
applicable law.

root@proxy1:~# 

Congratulations! The connection refused in the beginning is because this flist start a few daemons and this takes some time. Last step in theprocess is to start sshd As you can see, it got there and works.

Let’s cable the other nodes as well

[weynandkuijpers]

I’ll test it now…

[weynandkuijpers]

3081

Hi @parker, some thing does not sit wright with this setup:

  Enter a value: yes

grid_network.proxy01: Creating...
grid_network.proxy01: Still creating... [10s elapsed]
grid_network.proxy01: Still creating... [20s elapsed]
grid_network.proxy01: Still creating... [30s elapsed]
grid_network.proxy01: Creation complete after 34s [id=637b3ef2-a634-49cd-ac6e-0cdb19f4e987]
grid_deployment.p1: Creating...
grid_deployment.p1: Still creating... [10s elapsed]
grid_deployment.p1: Still creating... [20s elapsed]
╷
│ Error: error waiting deployment: workload 0 failed within deployment 3608 with error could not get public ip config: public ip workload is not okay
│ 
│   with grid_deployment.p1,
│   on main.tf line 21, in resource "grid_deployment" "p1":
│   21: resource "grid_deployment" "p1" {
│ 

I used the same terraform deployment script as for @Dany test, just replaced his 1983 node for your 3081. Please have a look at the farm setup in the https://portal.grid.tf in the farm / public ip section (you should have a /something defined there which is not a /32.

@Dany, any more suggestions to check?

[Dany]

Yeah…Great!! Thank you very much @weynandkuijpers.

We will connect the other nodes as soon as possible. I’ll let you know when it’s done!

Thanks again!

[ParkerS]

this is my config under the node specifically,

this is under the farm

[weynandkuijpers]

I am not a network expert, but know my way around networks (a bit…). The first thing that stands out to me is that you specify to have a /29 which is 8 IP addresses. As far as I remember the convention, usually the lowest (IPv4) address is the network address, the highest IPv4 address is the broadcasrt address of the subnet. Usually the GW is the one address above the network address (in your case 108.242.38.188. You have chosen....190 to be the gateway, right in the middle of the usable range.

I have not ready the code that distributes address but I can imagine that is uses that convention and therefore it might create a conflict. Let me ask one of the network gurus.

[ParkerS]

Some of that is because though I have an 8 address block Att controls the gateway address, so my network address is 108.242.38.184, the gateways 190 and the usable range is 185-189 and broadcast is 191. So I have 5 usable addresses currently

Does this test require I have additional ips setup beyond the one ip directly associated with the node public config?

[ParkerS]

Hey Dany I get the vibe your more of business model host with your rack plans, do you plan to be looking for people to have hosting agreements with in the future?

[Dany]

hey parkers, well… with this DC farming project we wanted to find out if this is technically and economically feasilbe and also sustainable. Also we wanted this to be done in a most professional way. That might look like we are going for a business here but for now we’re not particularly looking out for some kind of co-farming services to offer (if thats what you are refering to). But we are open for any kind of cooperations. The grid has to grow further and from my point of view DC farms are essential for the grid. Apart from… since we are now close to finishing this setup… I feel that I’m still hungry

[FLnelson]

I’ve noticed Flux has some sort of node renting program. I haven’t really looked into it, but it could be a starting point for you to look into, and myself.

[weynandkuijpers]

So the expert (on holliday) responded: In order to do this the server needs to have 2 nic’s connected. Do you have 2 nic’s connected? If not, add a network cable to the switch and it should work after a reboot.

[Dany]

@Dany, any more suggestions to check?

No suggestions at the moment. I have to dig deeper. I found out that there are differenent ways to assign public IPs (f. e. via TFchain-Portal or via polkadot UI). Also it looks like there are different hardware setups like using only one NIC port which can share LAN and public IP. I set up different szenarios and try to make them work. Will come up with the results asap.