### Description
When Kamailio listening IP address is assigned to a secondary network interface and this
card does not use for the default route, then at the L3-network level selected wrong IP
address and in the "Recrod-Route" and "Via" headers used correct
Kamailio IP.
For example in the attached file, frame 5 and fragments in frames 3,4.
[
invite-from-wrong-ip.pcap.gz](https://github.com/kamailio/kamailio/files/11…
![image](https://github.com/kamailio/kamailio/assets/2562241/68696b29-b37c-4d0a-b349-97054db14727)
#### Reproduction
Our use case.
1. create a new virtual machine with a random IP address in the AWS cloud;
2. create a new network interface card with a static IP address;
3. attach a new network interface to a virtual machine, in Linux should be configured only
one default route via the first network interface with a dynamic IP address;
4. start Kamailio daemon with configured listening TCP/socket with the IP address from the
secondary IP card.
5. make a call via Kamailio.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3486
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/3486(a)github.com>