See NAT and VOIP for more information about the problems with IP-telephony and NAT.
Use STUN clients to test equipment and add your result here using either cone NAT,
restricted cone NAT, port restricted NAT or symmetric NAT (see here for definitions).
- W-Linx
- MB400-X2: cone NAT
- D-Link
- DI-604: cone NAT
- DI-624: cone NAT (if "Game mode" is enabled, else Symmetric NAT)
- 500G Adsl router: Symmetric NAT
- DSLink
- 220e Adsl router: Symmetric NAT
- ZOOM
- X4: port restricted cone NAT
- Acer
- WLAN 11b Broadband Router: port restricted cone NAT
- Linksys
- BEFW11S4 v3.2: Full Cone NAT
- WRT54G Port Restricted Cone NAT
- Zyxel
- 660 Series (Including HW61) : Symmetrical NAT and plus HW61 has SIP ALG which tryes to solve NAT problems (but does it wrongly)
- NetGear
- MR314: Full Cone NAT for UDP and Symetric NAT for TCP
Page Changes
Really port restricted cone NAT?
The latter is the default behavior of iptables and is detected as Port Restricted Cone NAT by STUN. However, as soon as two internal devices start to communicate with the same port to the same server/port (e.g. two internal phones to an external STUN-Server) the NAT-Router changes to symmetric mode (although Cone NAT would still be possible).
Stats on NAT in a residential context,
It is based on data available at: http://www.cafzone.net/ipb/lofiversion/index.php/t25279.html
Tested NAT: 18
PortRestrictedCone: 6 (33%)
FullCone: 5 (27%)
Symmetric: 6 (33%)
RestrictedCone: 1 (5%)
Any other results going in the same direction?
TomCat
Linksys Routers
LINKSYS BEFSR42 V1