First login?
Lost password?
 
 
sctp-discussion AT lists.franken.de 
SCTP Discussions

Text archives Help


Re: [SCTP-Discussion] RE: INIT from private IP address to public IP address never received


Chronological Thread 
  • From: Andreas Jungmaier <ajung AT exp-math.uni-essen.de>
  • To: Michael Tüxen <Michael.Tuexen AT micmac.franken.de>, "Eng Se-Hsieng" <g0202512 AT nus.edu.sg>
  • Cc: "La Monte Henry Piggy Yarroll" <piggy AT baqaqi.chi.il.us>, <sctp_impl AT external.cisco.com>, <discussion AT sctp.de>
  • Subject: Re: [SCTP-Discussion] RE: INIT from private IP address to public IP address never received
  • Date: Mon May 5 12:57:00 2003
  • List-id: SCTP Discussions <discussion.sctp.de>
  • Organization: University Duisburg-Essen
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Dear all,

please find my comments below:

On Saturday 03 May 2003 22:18, Michael Tüxen wrote:
> Are you using the hostname parameters? Which machine is the source of
> the ICMP packets.
>
> I do not believe that the NAT engine handles the SCTP packets...
>
> Best regards
> Michael
>
> On Friday, May 2, 2003, at 16:31 Europe/Berlin, Eng Se-Hsieng wrote:
> >>> Dear all,
> >>>
> >>> I have tried the following scenario using the Reference
> >>> Implementation
> >>> with actual existing networks. Host A is on a GPRS network and Host
> >>> B is
> >>> on a university network and is assigned a fixed IP.
> >>>
> >>> Results using the University of Essen's implementatino were very
> >>> similar.
> >>>
> >>> Host A (private IP 172.18.56.36) towards Host B (fixed IP
> >>> 137.132.165.205)
> >>
> >> That means you are using NAT. The NAT firewall almost certainly
> >> does NOT support SCTP. I don't know of ANY SCTP NAT firewalls
> >> available yet.

This is exactly as I would think. The SCTP packets are simply discarded,
and ICMP, destination unreachable are sent back from the NAT box
(as indicated by additional TCPDUMP files that were sent to me).

Also, I do not think that the DNS request are related to the SCTP/NAT
problem at all. These probably come from a different process, and just
happen to appear on the tcpdump trace.
This does not have to do with the hostname parameter in SCTP (as I think,
so far NO implementation supports this).

Best regards,
Andreas

> > 14:30:39.826588 I 172.22.83.100 > 137.132.165.146: ip-proto-132 48
> > 14:30:39.947056 I 172.22.83.100 > 137.132.165.146: ip-proto-132 48
> > 14:30:45.826561 I 172.22.83.100 > 137.132.165.146: ip-proto-132 48
> > 14:30:57.126663 I 172.22.83.100 > 137.132.165.146: ip-proto-132 48
> > 14:31:21.266795 I 172.22.83.100 > 137.132.165.146: ip-proto-132 48
> > 14:32:12.178799 I 172.22.83.100 > 137.132.165.146: ip-proto-132 48
> > 14:33:04.639663 I 172.22.83.100.32770 > 137.132.123.4.53: 53768+ A?
> > CYRILLE.nus.edu.sg. (36) (DF)
> > 14:33:04.659178 O 137.132.123.4.53 > 172.22.83.100.32770: 53768
> > NXDomain* 0/1/0 (83)
> > 14:33:05.719556 I 172.22.83.100.32770 > 137.132.123.4.53: 53769+ A?
> > CYRILLE. (25) (DF)
> > 14:33:05.724976 O 137.132.123.4.53 > 172.22.83.100.32770: 53769
> > Refused 0/0/0 (25)
> > 14:33:06.399734 I 172.22.83.100.32770 > 137.132.5.2.53: 53769+ A?
> > CYRILLE. (25) (DF)
> > 14:33:06.405689 O 137.132.5.2.53 > 172.22.83.100.32770: 53769 Refused
> > 0/0/0 (25)
> > 14:33:07.279830 I 172.22.83.100.32770 > 137.132.123.4.53: 53769+ A?
> > CYRILLE. (25) (DF)
> > 14:33:07.285648 O 137.132.123.4.53 > 172.22.83.100.32770: 53769
> > Refused 0/0/0 (25)
> > 14:33:07.999634 I 172.22.83.100.32770 > 137.132.5.2.53: 53769+ A?
> > CYRILLE. (25) (DF)
> > 14:33:08.859617 I 172.22.83.100 > 137.132.165.146: ip-proto-132 48

- --
Dipl.-Ing. Andreas Jungmaier
Computer Networking Technology Group
University of Duisburg-Essen
http://www.exp-math.uni-essen.de/~ajung
My PGP Key-ID: D3824AC0

My PGP Key-Fingerprint: 228C 7C2C 3381 2DD4 9998 2812 5C0B 0B04 D382 4AC0
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+tkAoXAsLBNOCSsARAo13AJwLJAHgtIJYzoqUR5TKQ2Orb4BNawCgzJZ3
rhkkkFmVgQuDgKlrWPGwn44=
=o61N
-----END PGP SIGNATURE-----



Archive powered by MHonArc 2.6.19+.

Top of page