Also we want to be able to assign to globals, e.g.
def run() -> int32:
global X
X = 34
return 0
And they should be stored in the data segment and persist across calls…
Can this be handled entirely in nac3artiq and without passing opts
all over the place?
Actually, processing __artiq_rpc_flags__
doesn't work easily with NAC3, contrary to what I said earlier in the chat, sorry for that mistake. Probably better to process the AST after all.
And why not just set the correct netmask in the first place?
Regarding the routing tables: You complain about strongswan, but you should note that it doesn't mess up the routing tables. Your…
And to where will you route? I repeat: with a /32 address you cannot reach any other host.
This IP is to acquire.
What does that mean anyway?
Also with a /31 the last digits should be .0 and .1, .2 is not going to work.
If you use /32 then you can't reach any other hosts.
You need to set up the policy-based routing for the interface choosing part. As has been done before with existing altnet and HKBN connections.
I think you'd want /31 and then route the default traffic on table 3 through 10.42.0.1 (which would be the VPS)?