26 Mar
2010
26 Mar
'10
3:46 p.m.
Hi guys,
Does anyone have a REGEX syntax to match a private IP on the 192.168.x.x
range?
I'm trying with:
if($avp(s:ip_origen)=~"192.168(\.([1]?\d{1,2}|2[0-4]{1}\d{1}|25[0-5]{1})){2}"
)
But all IPs pass as private, even public ones.
Thanks!
Uriel
26 Mar
26 Mar
3:56 p.m.
172.16.0.0/12 does not line up on octet boundaries. You will need to
do something other than a regular expression. Fortunately, 'src_ip'
is a composite that supports comparisons against subnets in shorthand
CIDR notation.
It might also be that whatever you are trying to accomplish can be
done better some other way, but since you did not pose the question in
terms of the objective, I cannot speak to that.
--
Sent from mobile device
On Mar 26, 2010, at 9:46 AM, Uriel Rozenbaum
<uriel.rozenbaum(a)gmail.com> wrote:
Hi guys,
Does anyone have a REGEX syntax to match a private IP on the
192.168.x.x range?
I'm trying with:
if($avp(s:ip_origen)=~"192.168(\.([1]?\d{1,2}|2[0-4]{1}\d{1}|25[0-5]
{1})){2}" )
But all IPs pass as private, even public ones.
Thanks!
Uriel
_______________________________________________
Kamailio (OpenSER) - Users mailing list
Users(a)lists.kamailio.org
http://lists.kamailio.org/cgi-bin/mailman/listinfo/users
http://lists.openser-project.org/cgi-bin/mailman/listinfo/users
4:29 p.m.
Hi Alex,
Actually what I'm trying to do is check the IPs on a request on a
Kamailio+RTPProxy acting as border of our network.
So I have the ingress IP and egress IP and need to check if I have to bridge
ii, ei, ie or ee.
I managed to obtain all IPs in AVPs, but now I have to check if they are
public or private.
So far our network uses only 192.168.x.x class for private servers.
Thanks for the quick reply
Uriel
On Fri, Mar 26, 2010 at 10:56 AM, Alex Balashov
<abalashov(a)evaristesys.com>wrote;wrote:
172.16.0.0/12 does not line up on octet boundaries.
You will need to do
something other than a regular expression. Fortunately, 'src_ip' is a
composite that supports comparisons against subnets in shorthand CIDR
notation.
It might also be that whatever you are trying to accomplish can be done
better some other way, but since you did not pose the question in terms of
the objective, I cannot speak to that.
--
Sent from mobile device
On Mar 26, 2010, at 9:46 AM, Uriel Rozenbaum <uriel.rozenbaum(a)gmail.com>
wrote:
Hi guys,
Does anyone have a REGEX syntax to match a private IP on the 192.168.x.x
range?
I'm trying with:
if($avp(s:ip_origen)=~"192.168(\.([1]?\d{1,2}|2[0-4]{1}\d{1}|25[0-5]{1})){2}"
)
But all IPs pass as private, even public ones.
Thanks!
Uriel
_______________________________________________
Kamailio (OpenSER) - Users mailing list
Users(a)lists.kamailio.org
http://lists.kamailio.org/cgi-bin/mailman/listinfo/users
http://lists.openser-project.org/cgi-bin/mailman/listinfo/users
5:25 p.m.
Done,
I had a lot of errors so I'll just show the final version that works OK.
=~ "192\.168\.([0-9]{1,3})\.([0-9]{1,3})
The only drawback is that I could pass as valid 192.168.999.999 but as these
IPs come from a DNS query, I assume they'll be fine.
Cheers,
Uriel
On Fri, Mar 26, 2010 at 11:29 AM, Uriel Rozenbaum <uriel.rozenbaum(a)gmail.com
wrote:
> Hi Alex,
>
> Actually what I'm trying to do is check the IPs on a request on a
> Kamailio+RTPProxy acting as border of our network.
>
> So I have the ingress IP and egress IP and need to check if I have to
> bridge ii, ei, ie or ee.
> I managed to obtain all IPs in AVPs, but now I have to check if they are
> public or private.
>
> So far our network uses only 192.168.x.x class for private servers.
>
> Thanks for the quick reply
> Uriel
>
>
> On Fri, Mar 26, 2010 at 10:56 AM, Alex Balashov <abalashov(a)evaristesys.com
> wrote:
>
>> 172.16.0.0/12 does not line up on octet boundaries. You will need to do
>> something other than a regular expression. Fortunately, 'src_ip' is a
>> composite that supports comparisons against subnets in shorthand CIDR
>> notation.
>>
>> It might also be that whatever you are trying to accomplish can be done
>> better some other way, but since you did not pose the question in terms of
>> the objective, I cannot speak to that.
>>
>> --
>> Sent from mobile device
>>
>>
>> On Mar 26, 2010, at 9:46 AM, Uriel Rozenbaum <uriel.rozenbaum(a)gmail.com>
> wrote:
>>
>> Hi guys,
>>>
>>> Does anyone have a REGEX syntax to match a private IP on the 192.168.x.x
>>> range?
>>>
>>> I'm trying with:
>>>
if($avp(s:ip_origen)=~"192.168(\.([1]?\d{1,2}|2[0-4]{1}\d{1}|25[0-5]{1})){2}"
>>> )
>>>
>>> But all IPs pass as private, even public ones.
>>>
>>> Thanks!
>>> Uriel
>>> _______________________________________________
>>> Kamailio (OpenSER) - Users mailing list
>>> Users(a)lists.kamailio.org
>>> http://lists.kamailio.org/cgi-bin/mailman/listinfo/users
>>> http://lists.openser-project.org/cgi-bin/mailman/listinfo/users
>>>
>>
>
30 Mar
30 Mar
12:30 p.m.
On 3/26/10 4:25 PM, Uriel Rozenbaum wrote:
Done,
I had a lot of errors so I'll just show the final version that works OK.
=~ "192\.168\.([0-9]{1,3})\.([0-9]{1,3})
The only drawback is that I could pass as valid 192.168.999.999 but as
these IPs come from a DNS query, I assume they'll be fine.
I think you can reduce it to be just: "^192\.168\."
Since it comes from dns server or socket attributes, then you are safe.
The other option is to convert it to integer (with transformations) and
check it as net mask via bit wise operators.
Cheers,
Daniel
Cheers,
Uriel
On Fri, Mar 26, 2010 at 11:29 AM, Uriel Rozenbaum
<uriel.rozenbaum(a)gmail.com <mailto:uriel.rozenbaum@gmail.com>> wrote:
Hi Alex,
Actually what I'm trying to do is check the IPs on a request on a
Kamailio+RTPProxy acting as border of our network.
So I have the ingress IP and egress IP and need to check if I have
to bridge ii, ei, ie or ee.
I managed to obtain all IPs in AVPs, but now I have to check if
they are public or private.
So far our network uses only 192.168.x.x class for private servers.
Thanks for the quick reply
Uriel
On Fri, Mar 26, 2010 at 10:56 AM, Alex Balashov
<abalashov(a)evaristesys.com <mailto:abalashov@evaristesys.com>> wrote:
172.16.0.0/12 <http://172.16.0.0/12> does not line up on octet
boundaries. You will need to do something other than a
regular expression. Fortunately, 'src_ip' is a composite that
supports comparisons against subnets in shorthand CIDR notation.
It might also be that whatever you are trying to accomplish
can be done better some other way, but since you did not pose
the question in terms of the objective, I cannot speak to that.
--
Sent from mobile device
On Mar 26, 2010, at 9:46 AM, Uriel Rozenbaum
<uriel.rozenbaum(a)gmail.com <mailto:uriel.rozenbaum@gmail.com>>
wrote:
Hi guys,
Does anyone have a REGEX syntax to match a private IP on
the 192.168.x.x range?
I'm trying with:
if($avp(s:ip_origen)=~"192.168(\.([1]?\d{1,2}|2[0-4]{1}\d{1}|25[0-5]{1})){2}"
)
But all IPs pass as private, even public ones.
Thanks!
Uriel
_______________________________________________
Kamailio (OpenSER) - Users mailing list
Users(a)lists.kamailio.org <mailto:Users@lists.kamailio.org>
http://lists.kamailio.org/cgi-bin/mailman/listinfo/users
http://lists.openser-project.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Kamailio (OpenSER) - Users mailing list
Users(a)lists.kamailio.org
http://lists.kamailio.org/cgi-bin/mailman/listinfo/users
http://lists.openser-project.org/cgi-bin/mailman/listinfo/users
--
Daniel-Constantin Mierla * http://www.asipto.com/ *
http://twitter.com/miconda *
http://www.linkedin.com/in/danielconstantinmierla
5:34 p.m.
On Friday 26 March 2010, Uriel Rozenbaum wrote:
I had a lot of errors so I'll just show the final
version that works OK.
=~ "192\.168\.([0-9]{1,3})\.([0-9]{1,3})
The only drawback is that I could pass as valid 192.168.999.999 but as
these IPs come from a DNS query, I assume they'll be fine.
Hi Uriel,
thank you for sharing this. As Alex mentioned, the easier (and also probably
more faster) way is to use the src_ip construct, which 'understand' network
ranges.
Cheers,
Henning
5:51 p.m.
Daniel and Henning, thanks for your input. In some cases I have to compare
IPs that are not PV. In those cases I'll have to use the regex operator.
Cheers,
Uriel
On Tue, Mar 30, 2010 at 11:34 AM, Henning Westerholt <
henning.westerholt(a)1und1.de> wrote:
On Friday 26 March 2010, Uriel Rozenbaum wrote:
I had a lot of errors so I'll just show the
final version that works OK.
=~ "192\.168\.([0-9]{1,3})\.([0-9]{1,3})
The only drawback is that I could pass as valid 192.168.999.999 but as
these IPs come from a DNS query, I assume they'll be fine.
Hi Uriel,
thank you for sharing this. As Alex mentioned, the easier (and also
probably
more faster) way is to use the src_ip construct, which 'understand' network
ranges.
Cheers,
Henning
5353
days inactive
5357
days old
6 comments
4 participants
participants (4)
-
Alex Balashov -
Daniel-Constantin Mierla -
Henning Westerholt -
Uriel Rozenbaum