# \#webtransport

**URL:** https://discuss.ipfs.tech/tag/webtransport/126.md

[Latest](https://discuss.ipfs.tech/latest.md) · [Categories](https://discuss.ipfs.tech/categories.md) · [Tags](https://discuss.ipfs.tech/tags.md)

---

## [Local webtransport in firefox](https://discuss.ipfs.tech/t/local-webtransport-in-firefox/17767)

<div class="topic-metadata">

**Author:** [@h30x](https://discuss.ipfs.tech/u/h30x)\
**Replies:** 1\
**Last updated:** [April 1, 2024, 4:55am UTC](https://discuss.ipfs.tech/t/local-webtransport-in-firefox/17767 "2024-04-01T04:55:46Z")

</div>

TL;DR Webtransport does work in chromium but not in firefox. I started a kubo node locally, it exposes these multiaddresses: /ip4/127.0.0.1/tcp/4001/p2p/12D3KooWF44SaSomGuUSNycgpkRwQcxcsMYeNbtn6XCHPR2ojodv /ip4/127.0.…

---

## [PubSub between Kubo and js-ipfs in the browser with WebRTC and WSS/WebTransport](https://discuss.ipfs.tech/t/pubsub-between-kubo-and-js-ipfs-in-the-browser-with-webrtc-and-wss-webtransport/15542)

<div class="topic-metadata">

**Author:** [@danieln](https://discuss.ipfs.tech/u/danieln)\
**Replies:** 1\
**Last updated:** [November 23, 2022, 7:55pm UTC](https://discuss.ipfs.tech/t/pubsub-between-kubo-and-js-ipfs-in-the-browser-with-webrtc-and-wss-webtransport/15542 "2022-11-23T19:55:05Z")

</div>

Assuming that I’m building an app that relies on PubSub and I roughly have the following topology: Assuming that the chrome browsers are behind NAT, will they still be able to establish a WebRTC connection with one …