Why don't handle source port and destination port?

[fwqaaq]

edgetunnel/src/worker-vless.js

Lines 540 to 548 in 4221293

	for (let index = 0; index < chunk.byteLength;) {
	const lengthBuffer = chunk.slice(index, index + 2);
	const udpPakcetLength = new DataView(lengthBuffer).getUint16(0);
	const udpData = new Uint8Array(
	chunk.slice(index + 2, index + 2 + udpPakcetLength)
	);
	index = index + 2 + udpPakcetLength;
	controller.enqueue(udpData);
	}

Complete UDP messge also includes source port and destination port(total 8 bytes), but it seems they are being ignored in here.

[zizifn]

Port and destination is in vless header. And worker runtime not support udp yet.

[fwqaaq]

Port and destination is in vless header. And worker runtime not support udp yet.

So vless sends UDP datas after processing, thus it also lacks a checksum?

[xqdoo00o]

and no need to use DOH, because some public dns like google 8.8.8.8 open a tcp port 53 to handle dns request, so handleTCPOutBound could handle dns.

[zizifn]

I think in vless format, every udp chunk has a vless header, like tcp chunk. source code. so maybe it's not necessory to set udpStreamWrite. and no need to use DOH, because some public dns like google 8.8.8.8 open a tcp port 53 to handle dns request, so handleTCPOutBound could handle dns.

You are right. In the init implementation, I used 8.8.8.8 for dns, but change to cf doh for speed.