Opened 4 years ago
Closed 2 years ago
#146 closed defect (fixed)
Wrong source address with TUN/TAP interface
| Reported by: | jdesfossez | Owned by: | vadim |
|---|---|---|---|
| Priority: | major | Milestone: | QuteCom 3.0 |
| Component: | 3rd party libs | Version: | 2.5 |
| Keywords: | Cc: |
Description
Hello,
On Windows, when using Qutecom with a VPN which creates a TUN/TAP interface (for example OpenVPN), the source address used is not the address of the TUN interface but the address of the physical interface.
For example, the ethernet is 10.0.0.1 and VPN 172.16.0.1, if the traffic is set to go out from the VPN interface, the packet have 10.0.0.1 for source instead of 172.16.0.1 (I have used wireshark on the TUN interface to get this information, so I'm sure the packets exit by this interface with the wrong source address). Because of that, the connection cannot be established.
Qutecom is started after the VPN is established.
Thanks,
Julien
Change History (8)
comment:1 Changed 3 years ago by chris-mac
- Milestone changed from QuteCom 2.2-RC2 to QuteCom 2.2-RC4
- Priority changed from critical to major
- Version changed from 2.2-RC3 to 2.2
comment:2 Changed 3 years ago by laurent
- Version changed from 2.2 to 2.5
comment:3 Changed 3 years ago by chris-mac
- Milestone changed from QuteCom 2.2-RC4 to QuteCom 2.5
comment:4 Changed 3 years ago by Dmitriy.Trt
- field_os set to all
comment:6 Changed 2 years ago by ahgindia
- Milestone set to QuteCom 3.0
Can we know any estimate date, when can we expect resolution for this issue ?
This issue seems to be very major, as other softphones already have this functionality, so qutecom should be on the same stage as well.
comment:7 Changed 2 years ago by laurent
QuteCom 3.0 will use Bearer from Qt 4.7 to detect network devices ...
integration is not finished yet ... gui part is missing ( patch are welcomed ;)
You can try to hack network device identifier in config.xml with "network.interface" key.
comment:8 Changed 2 years ago by laurent
- Resolution set to fixed
- Status changed from new to closed
bug fix 79
I have same problems on Debian: tcpdump on OpenVPN server (bridged configuration) says that packets are sent with wrong source address (IP-address of my Wi-Fi connection on client) and QuteCom can't establish connection.