Omit the iceServers list:

const pc = new RTCPeerConnection();

Either omit the iceServers list from the RTCPeerConnection constructor, or make it the empty list [].

From RTCPeerConnection docs:

iceServers | optional

An array of RTCIceServer objects, each describing one server which may be used by the ICE agent; these are typically STUN and/or TURN servers. If this isn’t specified, the connection attempt will be made with no STUN or TURN server available, which limits the connection to local peers.

webrtc/samples demo

The WebRTC project has a Trickle ICE sample that you can use to see how changes in iceServers effect the candidate address that are gathered. The specific sample you want to look at is.

1. Run it with defaults set by pressing the Gather candidates button at the bottom of the page. This will return a list of addresses which include the address of the public side of your NAT.

   

2. Now remove all the ICE servers from the list and press Gather candidates again, this time you should only see local network addresses.

   

Notice that, on my network, the 2 public IPv4 addresses (beginning with 98.) only appear when I’m using the default ICE servers. When I use an empty ICE server list, my public IPv4 addresses are no longer discovered. My IPv6 addresses, on the other hand, are the same in both tests because they aren’t subject to NAT.

Here is a link to the source code that sets up iceServers and PeerConnection.