Wrong source address with TUN/TAP interface
|Reported by:||jdesfossez||Owned by:||vadim|
|Component:||3rd party libs||Version:||2.5|
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.
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