Re: Stupid NAT tricks and how to stop them.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Cullen Jennings wrote:
On 4/11/06 12:33 AM, "John Loughney" <john.loughney@xxxxxxxxxxx> wrote:


In practice, I've needed to power-cycle these NAT boxes every few weeks, to
clear out the garbage.


I'm curios to understand more of what you mean by this? Are you running out
of ports? Do you have any ideas what is causing this? (I have a strong
interest in the many ways NATs fail :-)


Linux: http://www.eisfair.org/
host_type("echnaton","(none)","Linux echnaton 2.2.19 #15").

No problems, but from time to complains about not so clean seesion
termination by dtag.de

_____


Fritz_Box_Eumex300IP
cpu model               : MIPS 4KEc V4.8
BogoMIPS                : 149.91
Linux version 2.4.17_mvl21-malta-mips_fp_le

No problem either, but from time to time I find in my telnet session:

Apr 11 05:22:04 dsld[381]: Channel 0 closed (physical)
Apr 11 05:22:04 dsld[381]: EVENT(36): Zeitüberschreitung bei der PPP-Aushandlung. (PPP_LCP)
Apr 11 05:22:04 dsld[381]: internet: PPP_LCP TIMEOUT
Apr 11 05:22:04 dsld[381]: starting autodetection
Apr 11 05:22:04 voipd[402]: connstatus 4 -> 2
Apr 11 05:22:07 dsld[381]: autodetect: failed
Apr 11 05:22:07 dsld[381]: atm socket rmem 65534
Apr 11 05:22:07 dsld[381]: PPPoEFW: set_snd_mtu: 1492
Apr 11 05:22:07 dsld[381]: PPPoEFW: set_rcv_mtu: 1492
Apr 11 05:22:07 dsld[381]: PPPoE forwarding for lan enabled.
Apr 11 05:22:07 dsld[381]: internet: set_rcv_ipaddr: 192.168.179.1
Apr 11 05:22:07 dsld[381]: internet: connecting
Apr 11 05:22:07 dsld[381]: internet: 00:04:0e:6d:8a:43
Apr 11 05:22:07 dsld[381]: internet: 00:04:0e:6d:8a:43
...
repeating

_____


Grandstream ATA-486
Red lite blinking, saying VoIP is dead.
HTML does not connect at all.
No Ping either.

Only unplugging power get the box back.


_____


dtag.de forces session termination every 24 hours. Sometimes
they are nasty and terminate the session several times within
a short time or they simply go dead. Happens rarely.

Everytime I get a new ip-address after reconnecting. That is
all what this silly session termination is about. Just to
anger the VoIP people. They are selling VoIP themselves those
silly buggers :)

The Grandstream goes bonkers when session terminations is
forced but the session is not terminated propperly but simply
broken.

There is another problem with the GrandStream: It does not
handle ICMP properly. It breaks MTU discovery and traceroute.


Cheers
Peter and Karin


--
Peter and Karin Dambier
The Public-Root Consortium
Graeffstrasse 14
D-64646 Heppenheim
+49(6252)671-788 (Telekom)
+49(179)108-3978 (O2 Genion)
+49(6252)750-308 (VoIP: sipgate.de)
mail: peter@xxxxxxxxxxxxxxxx
mail: peter@xxxxxxxxxxxxxxxxxxxxx
http://iason.site.voila.fr/
https://sourceforge.net/projects/iason/


_______________________________________________

Ietf@xxxxxxxx
https://www1.ietf.org/mailman/listinfo/ietf

[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Fedora Users]