Thats the crux of the problem. When @Lee_Travis tries to join the network sees the IP address 22.214.171.124 which is the external facing IP address of the wifi he is currently on.
I know one of our mobile networks can change ones mobile phone/dongle’s IP address every access. Its like they have a huge NAT with multiple IP addresses facing the internet and its rather random which IP address is used for any connection.
You might be right, but why can whaismyip.com see my true ip and so can my personal site. But it is read like that ^. I do know that exchanges also have a problem connecting with me sometimes. it is like having a vpn only even more secure. i can’t even get on the safe network. sometimes it changes frequently and sometimes it won’t change for a few days. But I almost always have to do extra verification on any routine site I go to. During my safe browser authenticator session, it seemed fairly stable.
I really wish sites could use something other than ip to identify you ip just isn’t reliable enough. and it takes too much control out of the hands of users. that above address is a DigitalOcean address, like maybe that is a server that hosts some of the maid browser.
@maidsafe is there some way that we could embed the invitation token in the client config. The person still only gets their 1000 PUTs so there shouldn’t be a spamming problem if they copy the config over to another device.
This way it is dependent on the invite code only and not the IP address?
Problem there is that we know some people will just give this out. Its already been attempted and this is why all the hassle. So we have spammers and well meaning people that will give this out to deal with. Its a PITA but till safecoin its gonna be like that, apart from alpha 3 mind you.
Does this mean I am SOL, or is there some work around for me? Without access I won’t be able to do any kind of development as promised. I’d really like to solve this problem of my access, I am sure it may be a problem for someone else as well. i have no other option for Internet access as I am very remote. My log is posted above, which makes me uneasy, not sure if there is any tracking info in there that someone could use against me.
This sounds like what I’m using (not sure if you really mean ‘rooted’).
I have mobile broadband, enable the hotspot on my (Android) mobile and use that. Yes I often have to update my IP, but it takes a second (I just keep a tab open with the invite URL in it and I can see if it needs updating whenever my PC boots).
EDIT: these days I usually use a VPN too, but it also works without that.
For dev really a local test is what you want then deploy to the alpha network when you are happy. You can use the mock-routing versions of the libs, or indeed build your own small tenet (can be done on a single pc, a couple is best) for a full network experience. However mock routing binaries are on the site and these will work for you.
I had to find another way around the twenty gig limitation. if i download two or three hp Linux machines then the twenty gigs is gone in a few days. I don’t see how anyone could survive with twenty gigs and I rarely watch videos.
If you can’t figure anything else out, I suppose you could fire up a VPS and access Alpha2 network via your VPS. You normally even have the option of setting a static IP for a VPS, so you’d never have to worry about IP changing in that case.
The network should also be able to revert to a previous state in the case of degraded performance. Some sort performance and behavior log that sections maintain after every “upgrade”. This behavior and performance history log should grow to no larger than a few megs. Once that limit is reached from weeks of gathered performance data, the the log is reset until the next upgrade event. This in effect means the network believes itself to be stable.
In the case that instabilities are detected by groups, each group will submit a reversion vote. Using a similar consensus algorithm applied to sections the network then authorizes the roll back. Sections report the successful roll back to each other then once again reach a consensus on the validity of their current state. Data chains will likely bake this in. How close am I to the planned mechanics for upgrade and roll back?