12 Oct
2020
12 Oct
'20
10:11 a.m.
How about adding source addr param to pike_check_req()?
Motivation is that main proxy may be front-ended by another proxy that
passes the real source addr to the main proxy in a header.
-- Juha
12 Oct
12 Oct
10:44 a.m.
Hello,
I am fine to add it. So far I preferred to discard unwanted traffic at
the brorder of the core platform, so I didn't need such feature.
Cheers,
Daniel
On 12.10.20 16:11, Juha Heinanen wrote:
How about adding source addr param to
pike_check_req()?
Motivation is that main proxy may be front-ended by another proxy that
passes the real source addr to the main proxy in a header.
-- Juha
_______________________________________________
Kamailio (SER) - Development Mailing List
sr-dev(a)lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev
--
Daniel-Constantin Mierla -- www.asipto.com
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Funding: https://www.paypal.me/dcmierla
9:40 a.m.
On 13.10.20 10:54, Juha Heinanen wrote:
Daniel-Constantin Mierla writes:
The changes were not complex, so I just pushed the code implementing
this feature. It can be useful to trigger alerts using Via or Contact
headers, even at the edge proxy. More over, can be used to write logs
when forwarding too much traffic to a specific ip address, although in
this case pipelimit can provide more flexibility.
I also extended to be allowed to be used in on/reply_route. Now thinking
about it, probably makes sense to allow it inside onsend_route as well.
Cheers,
Daniel
--
Daniel-Constantin Mierla -- www.asipto.com
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Funding: https://www.paypal.me/dcmierla
I am fine to add it. So far I preferred to
discard unwanted traffic at
the brorder of the core platform, so I didn't need such feature.
I agree,
better to do blocking at the edge.
1548
days inactive
1549
days old
3 comments
2 participants
participants (2)
-
Daniel-Constantin Mierla -
Juha Heinanen