@eyedeekay
+R4SAS
+RN
+RN_
+Xeha
+not_bob
+orignal
FreeRider
Irc2PGuest75862
Onn4l7h
Onn4|7h
T3s|4_
aargh3
acetone_
anon4
cancername
eyedeekay_bnc
profetikla
shiver_1
u5657
weko_
x74a6
orignal
I'm wondering if we can have multiple SSU2 session to the same remote router
zzz
I try pretty hard to prevent it
orignal
that's my question
orignal
should I check endpoint even if connid is different
orignal
or it's valid
zzz
up to you. I do it at the end of the handshake, I close the old conn and copy over any pending outbound msgs
orignal
good to know
zzz
because one side could think the old one was closed and the other side thinks it's open, because the destroy got lost
orignal
maybe
orignal
I just need to add this check
orignal
so one session per address
orignal
then what is connid for?
orignal
yes, that's what I mean per RI
zzz
the conn id is so we can keep the connection up even when the IP changes
zzz
without needing complex heuristics
zzz
but we haven't implemented that yet...
orignal
agree
orignal
if we have ipv4 session can we introduce ipv6 address through it?
orignal
bascially I try to connect to Chralie through ipv6 but I have a ipv4 session to Bob already
orignal
since I'm not supposed to create another session I should use existing oner
zzz
The IP address is always included (unlike in SSU 1) and may be different than the IP used for the session.
zzz
^^ that's prop. 159
zzz
this is SSU 1:
zzz
Alice sends the request to Bob using an existing session over the transport (IPv4 or IPv6) that she wishes to test. When Bob receives a request from Alice via IPv4, Bob must select a Charlie that advertises an IPv4 address. When Bob receives a request from Alice via IPv6, Bob must select a Charlie that advertises an IPv6 address. The actual Bob-Charlie communication may be via IPv4 or IPv6 (i.e., independent of Alice's
zzz
address type).
zzz
so as of now, it's not clear