Le 02/10/13 13:57, Konrad Karl a
crit:
On Wed, Oct 02, 2013 at 10:48:41AM +0200, Damien Sandras wrote:
On Linux the ip command seems to be able to determine the outgoing network
interface and also the source address being used. It
On Thu, Oct 03, 2013 at 09:29:38AM +0200, Damien Sandras wrote:
Le 02/10/13 13:57, Konrad Karl a ?crit :
Naive question: why cannot Ekiga do something similar?
Good news... It will be implemented in next release.
I'm finishing the GTK 3 port (including migration to the portable
GSettings)
Le 01/10/13 20:17, Konrad Karl a
crit:
Hi,
On Sun, Sep 29, 2013 at 05:53:58PM +0200, Damien Sandras wrote:
What Ekiga is supposed to do, is to send one message per interface
with the interface IP address as source. If your routing is well
On Wed, Oct 02, 2013 at 09:43:33AM +0200, Damien Sandras wrote:
Le 01/10/13 20:17, Konrad Karl a ?crit :
Hi,
On Sun, Sep 29, 2013 at 05:53:58PM +0200, Damien Sandras wrote:
What Ekiga is supposed to do, is to send one message per interface
with the interface IP address as source. If your
Le 02/10/13 10:15, Konrad Karl a
crit:
Not specifically required. The standard
says nothing about multiple
interfaces handling.
It is just a question of routing after that point. You can see
this
as a kind of fork of SIP
On Wed, 2 Oct 2013, Damien Sandras wrote:
If user B has two local interfaces (eth0: 192.x and tun: 10.x), when EkigaB
will send a SIP message to userA, it will send it twice (because it can not
determine how routing will work, that's the kernel responsibility) :
- one SIP message to userA
On Wed, Oct 02, 2013 at 10:48:41AM +0200, Damien Sandras wrote:
Le 02/10/13 10:15, Konrad Karl a ?crit :
.
A question still remains for me: why is this done the way it is?
If I e.g telnet some.ip.add.ress then routing rule apply and all
traffic will go over the vpn interface (tun0 or
Le 02/10/13 11:56, Mikael Abrahamsson a
crit:
On Wed, 2 Oct 2013, Damien Sandras wrote:
If user B has two local interfaces (eth0:
192.x and tun: 10.x), when EkigaB will send a SIP message to
userA, it will send it twice (because it can
Hi,
On Sun, Sep 29, 2013 at 05:53:58PM +0200, Damien Sandras wrote:
What Ekiga is supposed to do, is to send one message per interface
with the interface IP address as source. If your routing is well
configured, then only one of the various SIP messages should reach
the remote user.
is this
I want to use Ekiga without a central server by manually entering IP
addresses to connect directly to others. This works fine on a LAN. But
on VPN it doesn't work because of a bug, and this bug actually exists
with the LAN but it's not noticed. I am using Ekiga version
3.3.2-0ubuntu3 on Ubuntu
What Ekiga is supposed to do, is to
send one message per interface with the interface IP address as
source. If your routing is well configured, then only one of the
various SIP messages should reach the remote user.
Please note that Ekiga 3.3.2 is an old
Every other service I use on VPN only uses the interface for the VPN
address that I enter. I don't know why Ekiga would send it out to
every interface. Plus, part of the reason for using Ekiga over VPN is
to have a private conversation, so sending signals out to every
interface makes noise that I
12 matches
Mail list logo
