何も分からんけどエロ担当できます！やらせてください！

だいたいXとmixi2でダブって同じ話を投げてる人が多いので年末年始で飽きられそうな

mixi2じゃないと見れないものがあまりなくてな……

巨峰になりたい

「ピザって10回言って？」
「ピザピザピザピザピザピザピザピザピザピザ！」

　　 ∩
　　( ⌒)　　∩__
　　/ ,ノ　　 i E)
　 / /　　　 / /””
　/ /_、_ ／ノ
`/ /,_ノ`)／／
(　　　／
ヽ　　｜　　　お疲れ
　＼　　 ＼

TailscaleはL3 VPNなのでIPアドレス単位で通信先を見てます

・通信先が100かts.net配下
　→TailscaleのVPNトンネルに突っ込む、直接疎通できる相手ならP2Pで直接トンネル接続してパケットを直送する
　　つながらない相手ならInternet上の中継ノードやUDP Hole Punchingなどでトンネルを確立

・通信先がそれ以外
　→通信先がサブネットルーティング対象→サブネットルーター経由でのVPN接続
　→それ以外
　　→Exit NodeがON→Exit Nodeとトンネルしてデフォルトルートのように使う
　　→Exit NodeがOFF→通常のパケットとしてNICから放出

みたいなVPN付きルーターみたいなのをソフトウェア的にやってます。

この辺はL2TPとかEtherIP over IPsecとかとは用途が全然違う領域。(こっちはネットワークサブネットをくっつけてしまえ的なS2SとかP2Sね)

I am writing to seek your assistance with an issue that has occurred in the Nostream GitHub repository. Unfortunately, I made an error that requires administrative intervention to resolve.

Accidental Push: I inadvertently pushed local changes to the Nostream GitHub repository. This was not intended, and I realized the mistake immediately after the push.

Problematic Commits: The two most recent commits (af4d2953 and 246eb61) were mistakenly included in the push. I attempted to revert these changes myself but was unsuccessful in rectifying the situation.

Desired Resolution: Ideally, I would like to reset the HEAD to commit b6133a18, which is the last correct state before the erroneous commits were made.

Apology and Acknowledgment: I sincerely apologize for this mistake and the inconvenience it may have caused. I understand the importance of maintaining the integrity of the repository and regret any disruption this has caused to the team's workflow.

I appreciate your understanding and assistance in this matter. If there are any procedures I should follow in the future to prevent such occurrences, please advise.

Thank you for your time and attention to this request.

Best regards, @npub1qqqqq...