* [ath9k-devel] ath9k virtual interfaces
@ 2010-04-26 13:34 Rodolphe Marques
2010-04-26 16:34 ` Peter Stuge
0 siblings, 1 reply; 5+ messages in thread
From: Rodolphe Marques @ 2010-04-26 13:34 UTC (permalink / raw)
To: ath9k-devel
hi all,
My question is not directly related to the drivers itself but anyway
here it goes.
I have been playing with the virtual interfaces feature of this drivers
and I have a small problem.
I am able to create multiple virtual interfaces and have them configured
by network manager with all of them obtaining an IP address. The only
problem is that only the first interface gets the default gateway
configured. For the others I have to add a default gateway manually.
As anyone encountered this problem before? is there anyway I can make
this process automatic?
Best Regards,
Rodolphe Marques
^ permalink raw reply [flat|nested] 5+ messages in thread
* [ath9k-devel] ath9k virtual interfaces
2010-04-26 13:34 [ath9k-devel] ath9k virtual interfaces Rodolphe Marques
@ 2010-04-26 16:34 ` Peter Stuge
2010-04-26 16:54 ` Rodolphe Marques
0 siblings, 1 reply; 5+ messages in thread
From: Peter Stuge @ 2010-04-26 16:34 UTC (permalink / raw)
To: ath9k-devel
This is completely off-topic for this mailing list.
Rodolphe Marques wrote:
> The only problem is that only the first interface gets the default
> gateway configured.
In a normal system there is only one default gateway.
Please consider if you really must handle multiple default gateways.
In any case - how will your system know when to use which gateway?
Study the ip rule command. I recommend http://lartc.org/ for more
information.
//Peter
^ permalink raw reply [flat|nested] 5+ messages in thread
* [ath9k-devel] ath9k virtual interfaces
2010-04-26 16:34 ` Peter Stuge
@ 2010-04-26 16:54 ` Rodolphe Marques
2010-04-26 17:16 ` Peter Stuge
0 siblings, 1 reply; 5+ messages in thread
From: Rodolphe Marques @ 2010-04-26 16:54 UTC (permalink / raw)
To: ath9k-devel
Hi Peter,
I do an overload to the socket system call so that I can choose to which
interface a given application should bind.
The problem I think is that linux is not expecting to have several
interfaces connected to the same network so only the first interface as
a default gateway configured. So applications that I bind to interfaces
other than the first have no network connectivity.
Rodolphe
On 04/26/2010 05:34 PM, Peter Stuge wrote:
> This is completely off-topic for this mailing list.
>
> Rodolphe Marques wrote:
>
>> The only problem is that only the first interface gets the default
>> gateway configured.
>>
> In a normal system there is only one default gateway.
>
> Please consider if you really must handle multiple default gateways.
>
> In any case - how will your system know when to use which gateway?
> Study the ip rule command. I recommend http://lartc.org/ for more
> information.
>
>
> //Peter
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>
^ permalink raw reply [flat|nested] 5+ messages in thread
* [ath9k-devel] ath9k virtual interfaces
2010-04-26 16:54 ` Rodolphe Marques
@ 2010-04-26 17:16 ` Peter Stuge
2010-04-27 6:03 ` Benoit PAPILLAULT
0 siblings, 1 reply; 5+ messages in thread
From: Peter Stuge @ 2010-04-26 17:16 UTC (permalink / raw)
To: ath9k-devel
Rodolphe Marques wrote:
> The problem I think is that linux is not expecting to have several
> interfaces connected to the same network
The problem is not with Linux, but with you seeming to misunderstand
sockets and IP networks. (You'll get same results on all other OSes.)
I think you need a different solution, regardless of what actual
problem you are solving. Please don't post about this on this mailing
list, and please look for a new approach to solving your problem, if
what I suggested before did not help. (Did you already read all of
lartc.org?)
//Peter
^ permalink raw reply [flat|nested] 5+ messages in thread
* [ath9k-devel] ath9k virtual interfaces
2010-04-26 17:16 ` Peter Stuge
@ 2010-04-27 6:03 ` Benoit PAPILLAULT
0 siblings, 0 replies; 5+ messages in thread
From: Benoit PAPILLAULT @ 2010-04-27 6:03 UTC (permalink / raw)
To: ath9k-devel
Peter Stuge a ?crit :
> Rodolphe Marques wrote:
>
>> The problem I think is that linux is not expecting to have several
>> interfaces connected to the same network
>>
>
> The problem is not with Linux, but with you seeming to misunderstand
> sockets and IP networks. (You'll get same results on all other OSes.)
>
> I think you need a different solution, regardless of what actual
> problem you are solving. Please don't post about this on this mailing
> list, and please look for a new approach to solving your problem, if
> what I suggested before did not help. (Did you already read all of
> lartc.org?)
>
>
> //Peter
>
You can have anything you want in the routing table, including multiple
gateways. However, like Peter mentioned, you should be aware that the
kernel will probably use only one gateway at the end.
I think network-manager takes indeed care to not configure multiple
gateways (and it changes default metric from 1 to 2 on wireless
interfaces as well). Using dhclient on the command line will probably
fix that part.
Regards,
Benoit
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2010-04-27 6:03 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-04-26 13:34 [ath9k-devel] ath9k virtual interfaces Rodolphe Marques
2010-04-26 16:34 ` Peter Stuge
2010-04-26 16:54 ` Rodolphe Marques
2010-04-26 17:16 ` Peter Stuge
2010-04-27 6:03 ` Benoit PAPILLAULT
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.