[Kamailio-Devel] [ openser-Bugs-1958839 ] nathelper does not detect RFC 3330 ranges
SourceForge.net
noreply at sourceforge.net
Tue Aug 5 17:13:26 CEST 2008
Bugs item #1958839, was opened at 2008-05-06 15:55
Message generated for change (Comment added) made by henningw
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=743020&aid=1958839&group_id=139143
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: modules
>Group: ver devel
>Status: Closed
Resolution: None
Priority: 5
Private: No
Submitted By: Nobody/Anonymous (nobody)
>Assigned to: Henning Westerholt (henningw)
Summary: nathelper does not detect RFC 3330 ranges
Initial Comment:
http://www.rfc-editor.org/rfc/rfc3330.txt
RFC 3330 defines a number of range which can not be found on the internet and if used are being nated.
nathelper does not detect those range like it does for RFC1918 ones.
Some of the ranges defined are marked as possible for allocation so I performed the whois request to check which one had been (and only one was found).
$ whois -h whois.radb.net 39.0.0.0
route: 39.0.0.0/8
descr: Exchange Point Networks
PO 12317
Marina del Rey, CA. 90295
US
origin: AS4554
mnt-by: MNT-EPNET
changed: bmanning at karoshi.com 20020401
source: ARIN
$ whois -h whois.radb.net 128.0.0.0
% No entries found for the selected source(s).
$ whois -h whois.radb.net 191.255.0.0
% No entries found for the selected source(s).
$ whois -h whois.radb.net 192.0.0.0
% No entries found for the selected source(s).
$ whois -h whois.radb.net 223.255.255.0
% No entries found for the selected source(s).
Those are not relevant :)
224.0.0.0/4 Multicast [RFC3171]
240.0.0.0/4 Reserved for Future Use [RFC1700, page 4]
----------------------------------------------------------------------
>Comment By: Henning Westerholt (henningw)
Date: 2008-08-05 15:13
Message:
Logged In: YES
user_id=337916
Originator: NO
I've looked up the ranges the original poster specified in the RFC.
128.0.0.0, 191.255.0.0, 192.0.0.0 and 223.255.255.0 will be probably
allocated sometimes. There a some special cases (like performance tests,
example code) in this RFC that make no sense at all. So i don't think this
is a real issue.
Please reopen if you have another range(s) in mind.
Henning
----------------------------------------------------------------------
Comment By: Bogdan-Andrei Iancu (bogdan_iancu)
Date: 2008-05-07 15:47
Message:
Logged In: YES
user_id=1275325
Originator: NO
Hi,
the RFC3330 defines groups of IP for special purposes, but not necessary
for private networks. What are the ranges you think that can be used only
in private nets?
Regards,
Bogdan
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=743020&aid=1958839&group_id=139143
More information about the Devel
mailing list