tank IPs are still 100.0.0.0/8 in K8s
Closed this issue · 3 comments
pinheadmz commented
these IPs are not accurate:
--> warcli network start --force
Warnet:
┏━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓
┃ Temp dir ┃ Bitcoin network ┃ Docker network ┃ Subnet ┃ Graph ┃
┡━━━━━━━━━━━━━━━━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━━╇━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┩
│ /root/.warnet/warnet/warnet │ regtest │ warnet │ 100.0.0.0/8 │ DiGraph with 12 nodes and 11 edges │
└─────────────────────────────┴─────────────────┴────────────────┴─────────────┴────────────────────────────────────┘
Tanks:
┏━━━━━━━┳━━━━━━━━━┳━━━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━━┳━━━━━━━━━━┓
┃ Index ┃ Version ┃ IPv4 ┃ bitcoin conf ┃ tc_netem ┃
┡━━━━━━━╇━━━━━━━━━╇━━━━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━━╇━━━━━━━━━━┩
│ 0 │ 26.0 │ 100.157.38.141 │ -uacomment=w0 │ None │
│ 1 │ 26.0 │ 100.240.177.228 │ -uacomment=w1 │ None │
│ 2 │ 25.1 │ 100.3.110.4 │ -uacomment=w2 │ None │
│ 3 │ 26.0 │ 100.170.225.26 │ -uacomment=w3 │ None │
│ 4 │ 26.0 │ 100.213.234.13 │ -uacomment=w4 │ None │
│ 5 │ 26.0 │ 100.183.221.239 │ -uacomment=w5 │ None │
│ 6 │ 26.0 │ 100.43.160.138 │ -uacomment=w6 │ None │
│ 7 │ 26.0 │ 100.17.43.236 │ -uacomment=w7 │ None │
│ 8 │ 26.0 │ 100.192.174.3 │ -uacomment=w8 │ None │
│ 9 │ 26.0 │ 100.49.199.126 │ -uacomment=w9 │ None │
│ 10 │ 26.0 │ 100.135.210.163 │ -uacomment=w10 │ None │
│ 11 │ 26.0 │ 100.208.150.101 │ -uacomment=w11 │ None │
└───────┴─────────┴─────────────────┴────────────────┴──────────┘
willcl-ark commented
Right.
To fix (properly) IMO we should rip out the IP generating code, and have docker use patched images too, as I've confirmed it works now.
I think we should omit this column from the table, as the ip addresses are unknown until after assignment. Perhaps we can optionally add it to the warcli network status command, if the tanks are running and the ip address is queryable?
willcl-ark commented
pinheadmz commented
fixed