TCNetClientを初期化する
Optionalconfig: TCNetConfigurationTCNetアクセスの設定。省略時はデフォルト値を使用
Protected_Protected_ProtectedauthProtectedbridgeProtectedbroadcastProtectedconfigProtectedserverProtectedsession接続状態を返す
接続中の場合はtrue
Optional[captureThe Symbol.for('nodejs.rejection') method is called in case a
promise rejection happens when emitting an event and
captureRejections is enabled on the emitter.
It is possible to use events.captureRejectionSymbol in
place of Symbol.for('nodejs.rejection').
import { EventEmitter, captureRejectionSymbol } from 'node:events';
class MyClass extends EventEmitter {
constructor() {
super({ captureRejections: true });
}
[captureRejectionSymbol](err, event, ...args) {
console.log('rejection happened for', event, 'with', err, ...args);
this.destroy(err);
}
destroy(err) {
// Tear the resource down here.
}
}
全non-internal IPv4アダプタにソケットを作成し、即座にresolveする Master OptIn検出時にアダプタ収束を行う
ProtecteddetectBridgeのOSがWindowsであるかをpingのTTL値から検出する
Bridge IPが自分のIPと一致する場合はos.platform()で判定する。 リモートの場合はpingを1回実行しTTL値をパースする (TTL > 64 → Windows)。 WindowsのデフォルトTTLは128、macOS/LinuxのデフォルトTTLは64であるため、 同一LAN (0-1ホップ) ではこの閾値で正確に判定できる。 結果はインスタンス変数にキャッシュし、セッション中1回だけ検出する。
連続 cmd=1 flood 等で並行呼び出しが起きた場合は、in-flight Promise を
共有する single-flight パターンにより ping の重複起動を防ぐ。ただし
Bridge 切り替え (server.address 変化) 後は古い Promise を共有せず、
新しい Bridge 向けに別の ping を発行する。
Windowsならtrue、それ以外ならfalse
TCNetネットワークから切断する ソケットを閉じ、全リスナーを削除する
Synchronously calls each of the listeners registered for the event named
eventName, in the order they were registered, passing the supplied arguments
to each.
Returns true if the event had listeners, false otherwise.
import { EventEmitter } from 'node:events';
const myEmitter = new EventEmitter();
// First listener
myEmitter.on('event', function firstListener() {
console.log('Helloooo! first listener');
});
// Second listener
myEmitter.on('event', function secondListener(arg1, arg2) {
console.log(`event with parameters ${arg1}, ${arg2} in second listener`);
});
// Third listener
myEmitter.on('event', function thirdListener(...args) {
const parameters = args.join(', ');
console.log(`event with parameters ${parameters} in third listener`);
});
console.log(myEmitter.listeners('event'));
myEmitter.emit('event', 1, 2, 3, 4, 5);
// Prints:
// [
// [Function: firstListener],
// [Function: secondListener],
// [Function: thirdListener]
// ]
// Helloooo! first listener
// event with parameters 1, 2 in second listener
// event with parameters 1, 2, 3, 4, 5 in third listener
Returns an array listing the events for which the emitter has registered listeners.
import { EventEmitter } from 'node:events';
const myEE = new EventEmitter();
myEE.on('foo', () => {});
myEE.on('bar', () => {});
const sym = Symbol('symbol');
myEE.on(sym, () => {});
console.log(myEE.eventNames());
// Prints: [ 'foo', 'bar', Symbol(symbol) ]
Protectedhandle受信パケットから認証ハンドシェイクを処理する AppData cmd=1でトークンを取得し、Error応答で認証成否を判定する
受信したパケット
送信元情報
Returns the number of listeners listening for the event named eventName.
If listener is provided, it will return how many times the listener is found
in the list of the listeners of the event.
The name of the event being listened for
Optionallistener: (...args: any[]) => voidThe event handler function
Returns a copy of the array of listeners for the event named eventName.
server.on('connection', (stream) => {
console.log('someone connected!');
});
console.log(util.inspect(server.listeners('connection')));
// Prints: [ [Function] ]
Adds the listener function to the end of the listeners array for the
event named eventName. No checks are made to see if the listener has
already been added. Multiple calls passing the same combination of eventName
and listener will result in the listener being added, and called, multiple
times.
server.on('connection', (stream) => {
console.log('someone connected!');
});
Returns a reference to the EventEmitter, so that calls can be chained.
By default, event listeners are invoked in the order they are added. The
emitter.prependListener() method can be used as an alternative to add the
event listener to the beginning of the listeners array.
import { EventEmitter } from 'node:events';
const myEE = new EventEmitter();
myEE.on('foo', () => console.log('a'));
myEE.prependListener('foo', () => console.log('b'));
myEE.emit('foo');
// Prints:
// b
// a
The name of the event.
The callback function
Adds a one-time listener function for the event named eventName. The
next time eventName is triggered, this listener is removed and then invoked.
server.once('connection', (stream) => {
console.log('Ah, we have our first user!');
});
Returns a reference to the EventEmitter, so that calls can be chained.
By default, event listeners are invoked in the order they are added. The
emitter.prependOnceListener() method can be used as an alternative to add the
event listener to the beginning of the listeners array.
import { EventEmitter } from 'node:events';
const myEE = new EventEmitter();
myEE.once('foo', () => console.log('a'));
myEE.prependOnceListener('foo', () => console.log('b'));
myEE.emit('foo');
// Prints:
// b
// a
The name of the event.
The callback function
Protectedpreparecmd=2 (auth) パケットの payload を生成する
sendAuthSequence と sendAuthCommandOnly の共通ロジックを抽出したものである。 ガード失敗時は null を返し、呼び出し元が失敗時の扱い (リセット or 無視) を決める。
送信用の payload Buffer、または null (ガード失敗時)
Adds the listener function to the beginning of the listeners array for the
event named eventName. No checks are made to see if the listener has
already been added. Multiple calls passing the same combination of eventName
and listener will result in the listener being added, and called, multiple
times.
server.prependListener('connection', (stream) => {
console.log('someone connected!');
});
Returns a reference to the EventEmitter, so that calls can be chained.
The name of the event.
The callback function
Adds a one-time listener function for the event named eventName to the
beginning of the listeners array. The next time eventName is triggered, this
listener is removed, and then invoked.
server.prependOnceListener('connection', (stream) => {
console.log('Ah, we have our first user!');
});
Returns a reference to the EventEmitter, so that calls can be chained.
The name of the event.
The callback function
Returns a copy of the array of listeners for the event named eventName,
including any wrappers (such as those created by .once()).
import { EventEmitter } from 'node:events';
const emitter = new EventEmitter();
emitter.once('log', () => console.log('log once'));
// Returns a new Array with a function `onceWrapper` which has a property
// `listener` which contains the original listener bound above
const listeners = emitter.rawListeners('log');
const logFnWrapper = listeners[0];
// Logs "log once" to the console and does not unbind the `once` event
logFnWrapper.listener();
// Logs "log once" to the console and removes the listener
logFnWrapper();
emitter.on('log', () => console.log('log persistently'));
// Will return a new Array with a single function bound by `.on()` above
const newListeners = emitter.rawListeners('log');
// Logs "log persistently" twice
newListeners[0]();
emitter.emit('log');
Removes all listeners, or those of the specified eventName.
It is bad practice to remove listeners added elsewhere in the code,
particularly when the EventEmitter instance was created by some other
component or module (e.g. sockets or file streams).
Returns a reference to the EventEmitter, so that calls can be chained.
OptionaleventName: string | symbolRemoves the specified listener from the listener array for the event named
eventName.
const callback = (stream) => {
console.log('someone connected!');
};
server.on('connection', callback);
// ...
server.removeListener('connection', callback);
removeListener() will remove, at most, one instance of a listener from the
listener array. If any single listener has been added multiple times to the
listener array for the specified eventName, then removeListener() must be
called multiple times to remove each instance.
Once an event is emitted, all listeners attached to it at the
time of emitting are called in order. This implies that any
removeListener() or removeAllListeners() calls after emitting and
before the last listener finishes execution will not remove them from
emit() in progress. Subsequent events behave as expected.
import { EventEmitter } from 'node:events';
class MyEmitter extends EventEmitter {}
const myEmitter = new MyEmitter();
const callbackA = () => {
console.log('A');
myEmitter.removeListener('event', callbackB);
};
const callbackB = () => {
console.log('B');
};
myEmitter.on('event', callbackA);
myEmitter.on('event', callbackB);
// callbackA removes listener callbackB but it will still be called.
// Internal listener array at time of emit [callbackA, callbackB]
myEmitter.emit('event');
// Prints:
// A
// B
// callbackB is now removed.
// Internal listener array [callbackA]
myEmitter.emit('event');
// Prints:
// A
Because listeners are managed using an internal array, calling this will
change the position indexes of any listener registered after the listener
being removed. This will not impact the order in which listeners are called,
but it means that any copies of the listener array as returned by
the emitter.listeners() method will need to be recreated.
When a single function has been added as a handler multiple times for a single
event (as in the example below), removeListener() will remove the most
recently added instance. In the example the once('ping')
listener is removed:
import { EventEmitter } from 'node:events';
const ee = new EventEmitter();
function pong() {
console.log('pong');
}
ee.on('ping', pong);
ee.once('ping', pong);
ee.removeListener('ping', pong);
ee.emit('ping');
ee.emit('ping');
Returns a reference to the EventEmitter, so that calls can be chained.
データリクエストをブロードキャストで送信する
実機テストの結果、RequestパケットはbroadcastSocket(60000)経由で ブロードキャストアドレス:60000に送信しnodeOptions=0x0000を使用する必要がある。
要求するデータタイプ
要求するレイヤー (0-7)
リクエスト応答のPromise
Protectedreset認証セッションを初期状態にリセットする
_authState/sessionToken/authResponseFailureCount/authTimeoutId を 初期値に戻し、Bridge からの次の cmd=1 で再度初回認証フローに入れる 状態へ戻す。bridgeIsWindows は既定でリセットされるが、Bridge の 物理端末が変わらないと判断できる場合 (連続送信失敗の閾値到達等) は preserveBridgeOs=true で保持することで無駄な再 ping を避けられる。
true の場合は bridgeIsWindows キャッシュを保持する
ProtectedsendBridge からの cmd=1 (再認証要求) に対して cmd=2 (auth) のみを送り返す
ShowKontrol の実測挙動 (sk-ext-capture.pcapng) をエミュレートする: Bridge が cmd=1 を送ってきたら SK は 1-10ms 以内に cmd=2 だけを返す。 223秒間のキャプチャで 8 回の再認証サイクルが観測され、全て同一tokenで 完結している (初回ハンドシェイクのみ cmd=0 hello を伴う)。
sendAuthSequence との違い:
実際に cmd=2 を送信した場合は true、ガード失敗で送信しなかった場合は false
Protectedsend認証シーケンス (cmd=0 hello → 50ms wait → cmd=2 auth) を送信する
呼び出し時点の sessionToken を内部で expectedToken としてキャプチャし、
各非同期境界で this.sessionToken !== expectedToken を確認する。
旧世代になっていたら resetAuthSession を呼ばずに return する
(新世代の state を壊さないため)。
By default EventEmitters will print a warning if more than 10 listeners are
added for a particular event. This is a useful default that helps finding
memory leaks. The emitter.setMaxListeners() method allows the limit to be
modified for this specific EventEmitter instance. The value can be set to
Infinity (or 0) to indicate an unlimited number of listeners.
Returns a reference to the EventEmitter, so that calls can be chained.
アダプタを切り替える。 pendingリクエストをrejectし、ソケットを再接続する
切り替え先のネットワークインターフェース名
TCNetプロトコルの低レベル実装