AS does not indicate location.
Live BGP AS does not necessarily indicate ownership
at registrar, though any proxying effectively pools them.
A relay IP shouldn't be in more than one AS at
once, though it may shift around many over time.
dig doesn't really work via tor :(
__
On Wed, Jul 29, 2015 at 02:59:05AM +0200, nusenu wrote:
> Roger Dingledine:
> > I wonder how many guards shift location significantly across the
> > Internet, and how often?
>
> So nothing to worry about to much I guess.
Or to turn it around, it makes it a lot easier to dump the WFU
(weighted fra
At 22:05 7/28/2015 -0400, you wrote:
>
>A couple of minor notes regarding ASNs:
>
Also the AS number assigned to an IP
address may legitimately vary depending
on the source/observer. This is due to
the relativistic nature of BGP routing.
For example a Comcast address 74.95.187.105
is listed in AS
>(where a lot of IPs changed their AS from
>IANA to Digital Ocean)
A couple of minor notes regarding ASNs:
1) many IPs fall under a hierarchy of
ASs where a large core-network provider
(e.g. Level3) advertises a block and a
second client leaf-AS advertises a sub-
block. Sometimes the core AS adv
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Roger Dingledine:
> I wonder how many guards shift location significantly across the
> Internet, and how often?
For simplicity lets define 'significantly' as 'guard changed its AS'.
Taking into account data starting from first of July. There were 5
On Sun, Jul 26, 2015 at 04:48:37PM +, Yawning Angel wrote:
> If the relay's IP is constantly changing significantly faster than the
> Guard rotation interval (needs more numbers here), I'm not sure if they
> make great Guards, but this is an arma/asn type question since they
> think more about
On 26 July 2015 at 22:42, Yawning Angel wrote:
> On Sun, 26 Jul 2015 22:32:18 +0100
> Pascal Terjan wrote:
> [snip]
>> > I question the usefulness of most of the relays running on
>> > residential lines in the first place for other reasons (Eg: most
>> > consumer routers are crap, and will probab
On Sun, 26 Jul 2015 22:32:18 +0100
Pascal Terjan wrote:
[snip]
> > I question the usefulness of most of the relays running on
> > residential lines in the first place for other reasons (Eg: most
> > consumer routers are crap, and will probably not be able to
> > simultaneously maintain a connectio
On 26 July 2015 at 17:48, Yawning Angel wrote:
> On Sun, 26 Jul 2015 16:11:56 +0200
> nusenu wrote:
>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA512
>>
>> [split from 'Giving away some "pre-warmed" relay keys for adoption']
>
> Ok.
>
>> > I'm of the opinion that it may be worth adding code
On Sun, 26 Jul 2015 21:09:13 +0300
s7r wrote:
> We need to confirm this: is a relay holding TLS connections to the
> majority of the other relays?
This is another metrics needed thing. In general, at any given
time, any relay should be prepared to be able to open or accept a
connection to any o
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello Yawning,
We need to confirm this: is a relay holding TLS connections to the
majority of the other relays?
On a relay with over 100 days of uptime (middle relay) Stable, HSDir,
etc. I have (# netstat -a | wc -l) 1942 connections. Another one,
On Sun, 26 Jul 2015 16:11:56 +0200
nusenu wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> [split from 'Giving away some "pre-warmed" relay keys for adoption']
Ok.
> > I'm of the opinion that it may be worth adding code to pin relay
> > identities to IP addresses on the DirAuth
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
teor:
>
>> On 27 Jul 2015, at 01:30 , starlight.201...@binnacle.cx wrote:
>>
>> Perhaps a way to do it is reset the consensus for a relay if its
>> IP address moves to a different Autonomous System.
>>
>> Is rare that dynamic IP causes relays to h
> On 27 Jul 2015, at 01:30 , starlight.201...@binnacle.cx wrote:
>
> Perhaps a way to do it is reset the
> consensus for a relay if its IP address
> moves to a different Autonomous System.
>
> Is rare that dynamic IP causes relays
> to hop ASs (e.g. possibly SBC/ATT),
> and list of exceptions co
Perhaps a way to do it is reset the
consensus for a relay if its IP address
moves to a different Autonomous System.
Is rare that dynamic IP causes relays
to hop ASs (e.g. possibly SBC/ATT),
and list of exceptions could be created
for the few cases where it causes trouble.
CYMRU has a dynamic serv
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
[split from 'Giving away some "pre-warmed" relay keys for adoption']
> I'm of the opinion that it may be worth adding code to pin relay
> identities to IP addresses on the DirAuth side so that consensus
> weight and flag assignment gets totally re
16 matches
Mail list logo
