[gentoo-user] Re: configure wlan0 route metric

[gentoo-user] Re: configure wlan0 route metric

[deadeyes]

Kfir Lavi <lavi.kfir <at> gmail.com> writes:

> Hi,you can use net-analyzer/ifmetric.I found this solution not satisfying, but
> don't remember why. I guess some corner cases. I have bonded the interfaces on
> my laptop. The bonding driver will prefer using the wired when
> 
> it is connected. Here is my /etc/conf.d/net:# eth0config_eth0=( "null" )#
> wlanmodules=( "wpa_supplicant" )wpa_supplicant_wlan0="-Dwext"config_wlan0=( 
> "null" )
> 
> modules_wlan0=( "!plug" )ifplugd_wlan0="--api-mode=wlan"#
> bondslaves_bond0="eth0 wlan0"dhcpcd_bond0="--noipv4ll --nolink -t
> 15"config_bond0=( "dhcp" )Regards,Kfir
> 

Thanks for your response!
Bonding doesn't seem a good solution for me.
I can't find documentation on ifmetric.
Do I need ifplugd to call ifmetric? or can I configure this in /etc/conf.d/net?

Re: [gentoo-user] Re: configure wlan0 route metric

[Mick]

On 13 April 2011 11:06, deadeyes <gvm999@gmail.com> wrote:

> Thanks for your response!
> Bonding doesn't seem a good solution for me.
> I can't find documentation on ifmetric.
> Do I need ifplugd to call ifmetric? or can I configure this in /etc/conf.d/net?

You can define the priority in your /etc/conf.d/net

You can set this per wired/wireless interface; e.g.

metric_eth0="100"

Look at your /etc/conf.d/net.example for more details.

HTH.
-- 
Regards,
Mick

[gentoo-user] Re: configure wlan0 route metric

[deadeyes]

Mick <michaelkintzios <at> gmail.com> writes:

>
> You can define the priority in your /etc/conf.d/net
> 
> You can set this per wired/wireless interface; e.g.
> 
> metric_eth0="100"
> 
> Look at your /etc/conf.d/net.example for more details.
> 
> HTH.


No offense, I had found out about this option (and tried it already):
"I found out I can modify the metric for the default route using metric_wlan0."

This however only changes the default route. Not the route for the local network
route.
Also metric_eth0 would give less priority to my wired network, which is not what
I want.

I was searching around the gentoo forums for ifmetric and found this piece of
code that can be added in /etc/conf.d/net:
postup() {
   local metric=0

   case "${IFACE}" in
      eth0) metric=0 ;;
      eth1) metric=1 ;;
   esac
   ifmetric "${IFACE}" "${metric}"

   return 0
}

I'll try as soon as I can and add my experience with this.

Re: [gentoo-user] Re: configure wlan0 route metric

[Indi]

On Wed, Apr 13, 2011 at 01:50:02PM +0200, deadeyes wrote:
> 
> I was searching around the gentoo forums for ifmetric and found this piece of
> code that can be added in /etc/conf.d/net:
> postup() {
>    local metric=0
> 
>    case "${IFACE}" in
>       eth0) metric=0 ;;
>       eth1) metric=1 ;;
>    esac
>    ifmetric "${IFACE}" "${metric}"
> 
>    return 0
> }
> 

Hey, that works very well here -- thanks!
Been wanting that solution for some time now.
:)
-- 
 /\       /\ 
   <\   />    
      ^      caveat utilitor 
    'v-v'            

Re: [gentoo-user] Re: configure wlan0 route metric

[Mick]

On 13 April 2011 16:35, Indi <thebeelzebubtrigger@gmail.com> wrote:
> On Wed, Apr 13, 2011 at 01:50:02PM +0200, deadeyes wrote:
>>
>> I was searching around the gentoo forums for ifmetric and found this piece of
>> code that can be added in /etc/conf.d/net:
>> postup() {
>>    local metric=0
>>
>>    case "${IFACE}" in
>>       eth0) metric=0 ;;
>>       eth1) metric=1 ;;
>>    esac
>>    ifmetric "${IFACE}" "${metric}"
>>
>>    return 0
>> }
>>
>
> Hey, that works very well here -- thanks!
> Been wanting that solution for some time now.
> :)

My apologies!  It took some time between reading your message and
replying to it - by which time I had forgotten the finer points.

Whether you set NIC priority in the /etc/conf.d/net file or in a post
up script, the result is the same.  One NIC will have a higher
priority than another for ALL connections.  This is because NICs do
not do NATing.  They will send all packets out to the gateway
(192.168.1.1) and the router at the gateway will determine which
packet is forwarded to the Internet and which to the LAN.  So, if you
do not want to prioritise one NIC over another, it may be better to
use iptables to route LAN packets via a particular NIC instead.

-- 
Regards,
Mick

Re: [gentoo-user] Re: configure wlan0 route metric

[Indi]

On Wed, Apr 13, 2011 at 06:10:05PM +0200, Mick wrote:
> On 13 April 2011 16:35, Indi <thebeelzebubtrigger@gmail.com> wrote:
> > On Wed, Apr 13, 2011 at 01:50:02PM +0200, deadeyes wrote:
> >>
> >> I was searching around the gentoo forums for ifmetric and found this piece of
> >> code that can be added in /etc/conf.d/net:
> >> postup() {
> >>    local metric=0
> >>
> >>    case "${IFACE}" in
> >>       eth0) metric=0 ;;
> >>       eth1) metric=1 ;;
> >>    esac
> >>    ifmetric "${IFACE}" "${metric}"
> >>
> >>    return 0
> >> }
> >>
> >
> > Hey, that works very well here -- thanks!
> > Been wanting that solution for some time now.
> > :)
> 
> My apologies!  It took some time between reading your message and
> replying to it - by which time I had forgotten the finer points.
> 
> Whether you set NIC priority in the /etc/conf.d/net file or in a post
> up script, the result is the same.  One NIC will have a higher
> priority than another for ALL connections.  This is because NICs do
> not do NATing.  They will send all packets out to the gateway
> (192.168.1.1) and the router at the gateway will determine which
> packet is forwarded to the Internet and which to the LAN.  So, if you
> do not want to prioritise one NIC over another, it may be better to
> use iptables to route LAN packets via a particular NIC instead.
> 
> -- 
> Regards,
> Mick

Actually I do want to prioritise one over the other, when both are
connected. Using netplug with one wired and one wireless, and the
referenced script in /etc/conf.d/net.

Am I doing it wrong? :)

-- 
 /\       /\ 
   <\   />    
      ^      caveat utilitor 
    'v-v'            

Re: [gentoo-user] Re: configure wlan0 route metric

[Mick]

[-- Attachment #1: Type: Text/Plain, Size: 1860 bytes --]

On Wednesday 13 April 2011 18:07:30 Indi wrote:
> On Wed, Apr 13, 2011 at 06:10:05PM +0200, Mick wrote:
> > On 13 April 2011 16:35, Indi <thebeelzebubtrigger@gmail.com> wrote:
> > > On Wed, Apr 13, 2011 at 01:50:02PM +0200, deadeyes wrote:
> > >> I was searching around the gentoo forums for ifmetric and found this
> > >> piece of code that can be added in /etc/conf.d/net:
> > >> postup() {
> > >>    local metric=0
> > >> 
> > >>    case "${IFACE}" in
> > >>       eth0) metric=0 ;;
> > >>       eth1) metric=1 ;;
> > >>    esac
> > >>    ifmetric "${IFACE}" "${metric}"
> > >> 
> > >>    return 0
> > >> }
> > > 
> > > Hey, that works very well here -- thanks!
> > > Been wanting that solution for some time now.
> > > 
> > > :)
> > 
> > My apologies!  It took some time between reading your message and
> > replying to it - by which time I had forgotten the finer points.
> > 
> > Whether you set NIC priority in the /etc/conf.d/net file or in a post
> > up script, the result is the same.  One NIC will have a higher
> > priority than another for ALL connections.  This is because NICs do
> > not do NATing.  They will send all packets out to the gateway
> > (192.168.1.1) and the router at the gateway will determine which
> > packet is forwarded to the Internet and which to the LAN.  So, if you
> > do not want to prioritise one NIC over another, it may be better to
> > use iptables to route LAN packets via a particular NIC instead.
> 
> Actually I do want to prioritise one over the other, when both are
> connected. Using netplug with one wired and one wireless, and the
> referenced script in /etc/conf.d/net.
> 
> Am I doing it wrong? :)

No, not at all.  It's only that the OP wanted to prioritise the wired 
interface against the wireless, but *only* for connections to the LAN.
-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Re: configure wlan0 route metric

[Indi]

On Wed, Apr 13, 2011 at 09:10:01PM +0200, Mick wrote:
> On Wednesday 13 April 2011 18:07:30 Indi wrote:
> > On Wed, Apr 13, 2011 at 06:10:05PM +0200, Mick wrote:
> > > On 13 April 2011 16:35, Indi <thebeelzebubtrigger@gmail.com> wrote:
> > > > On Wed, Apr 13, 2011 at 01:50:02PM +0200, deadeyes wrote:
> > > >> I was searching around the gentoo forums for ifmetric and found this
> > > >> piece of code that can be added in /etc/conf.d/net:
> > > >> postup() {
> > > >>    local metric=0
> > > >> 
> > > >>    case "${IFACE}" in
> > > >>       eth0) metric=0 ;;
> > > >>       eth1) metric=1 ;;
> > > >>    esac
> > > >>    ifmetric "${IFACE}" "${metric}"
> > > >> 
> > > >>    return 0
> > > >> }
> > > > 
> > > > Hey, that works very well here -- thanks!
> > > > Been wanting that solution for some time now.
> > > > 
> > > > :)
> > > 
> > > My apologies!  It took some time between reading your message and
> > > replying to it - by which time I had forgotten the finer points.
> > > 
> > > Whether you set NIC priority in the /etc/conf.d/net file or in a post
> > > up script, the result is the same.  One NIC will have a higher
> > > priority than another for ALL connections.  This is because NICs do
> > > not do NATing.  They will send all packets out to the gateway
> > > (192.168.1.1) and the router at the gateway will determine which
> > > packet is forwarded to the Internet and which to the LAN.  So, if you
> > > do not want to prioritise one NIC over another, it may be better to
> > > use iptables to route LAN packets via a particular NIC instead.
> > 
> > Actually I do want to prioritise one over the other, when both are
> > connected. Using netplug with one wired and one wireless, and the
> > referenced script in /etc/conf.d/net.
> > 
> > Am I doing it wrong? :)
> 
> No, not at all.  It's only that the OP wanted to prioritise the wired 
> interface against the wireless, but *only* for connections to the LAN.
> -- 
> Regards,
> Mick


Ah, sorry I missed that part. It does seem to do just I wanted though.

-- 
 /\       /\ 
   <\   />    
      ^      caveat utilitor 
    'v-v'            

[gentoo-user] Re: configure wlan0 route metric

[deadeyes]

Mick <michaelkintzios <at> gmail.com> writes:

> >
> > Hey, that works very well here -- thanks!
> > Been wanting that solution for some time now.
> > :)
> 
> My apologies!  It took some time between reading your message and
> replying to it - by which time I had forgotten the finer points.
> 
> Whether you set NIC priority in the /etc/conf.d/net file or in a post
> up script, the result is the same.  One NIC will have a higher
> priority than another for ALL connections.  This is because NICs do
> not do NATing.  They will send all packets out to the gateway
> (192.168.1.1) and the router at the gateway will determine which
> packet is forwarded to the Internet and which to the LAN.  So, if you
> do not want to prioritise one NIC over another, it may be better to
> use iptables to route LAN packets via a particular NIC instead.
> 

Great to see this helps someone else as well :)

@Mick: I am not sure if I fully understand what you mean. Following the routing
table the most specific route will be used, which is not the default route, but
the route to the local lan. In this case the metric is important as there are
multiple interfaces with the same network.
And what do you mean by setting NIC priority (using the metric_eth0 config
option?) using /etc/conf.d/net or in a post script? Both have different outcomes
it looks to me.

Greetings

[gentoo-user] Re: configure wlan0 route metric

[deadeyes]

deadeyes <gvm999 <at> gmail.com> writes:

code that can be added in /etc/conf.d/net:
postup() {
   local metric=0

   case "${IFACE}" in
      eth0) metric=0 ;;
      eth1) metric=1 ;;
   esac
   ifmetric "${IFACE}" "${metric}"

   return 0
}

Seems like this works for me as well! :)

Thanks for your responses guys

Re: [gentoo-user] Re: configure wlan0 route metric

[Mick]

On 13 April 2011 20:52, deadeyes <gvm999@gmail.com> wrote:
> Mick <michaelkintzios <at> gmail.com> writes:

>> Whether you set NIC priority in the /etc/conf.d/net file or in a post
>> up script, the result is the same.  One NIC will have a higher
>> priority than another for ALL connections.  This is because NICs do
>> not do NATing.  They will send all packets out to the gateway
>> (192.168.1.1) and the router at the gateway will determine which
>> packet is forwarded to the Internet and which to the LAN.  So, if you
>> do not want to prioritise one NIC over another, it may be better to
>> use iptables to route LAN packets via a particular NIC instead.
>>
>
> Great to see this helps someone else as well :)
>
> @Mick: I am not sure if I fully understand what you mean. Following the routing
> table the most specific route will be used, which is not the default route, but
> the route to the local lan.

*All* routes have to go through the local LAN.  That's where you router is.

Both NICs are in the same subnet (192.168.1.0/24) and use the same
gateway (192.168.1.1).  Therefore, the only thing that determines
which NIC your packets will go out of is the NIC's metric setting.

In your first email you show eth0 with a higher priority than wlan0.
All connections will go out eth0, unless eth0 goes down for some
reason, or becomes saturated.


> In this case the metric is important as there are
> multiple interfaces with the same network.
> And what do you mean by setting NIC priority (using the metric_eth0 config
> option?) using /etc/conf.d/net or in a post script? Both have different outcomes
> it looks to me.

Both have the same outcome - set priority for your eth0 and wlan0 NICs,

use the same file - /etc/conf.d/net

and set up the same parameter - metric.

The post up script also sets the lo interface to 0 which is the
default anyway.  Unless I misunderstand the file's nomenclature local
stands for Local Loopback (127.0.0.1/255.0.0.0) and by default has
higher priority.

Anyway, that's how I understand this, no doubt some networking guru
will correct me if I got it wrong.
-- 
Regards,
Mick

Re: [gentoo-user] Re: configure wlan0 route metric

[Mick]

On 14 April 2011 09:13, deadeyes <gvm999@gmail.com> wrote:
> deadeyes <gvm999 <at> gmail.com> writes:
>
> code that can be added in /etc/conf.d/net:
> postup() {
>   local metric=0
>
>   case "${IFACE}" in
>      eth0) metric=0 ;;
>      eth1) metric=1 ;;
>   esac
>   ifmetric "${IFACE}" "${metric}"
>
>   return 0
> }
>
> Seems like this works for me as well! :)

It does?  I assume that eth1 above is wlan0 in your case.

If you restart both eth0 and wlan0 so as to zero the packet counters,
then start a download/upload from your a machine in your LAN, what
packet counts do you get in ifconfig for each NIC?

-- 
Regards,
Mick

[gentoo-user] Re: configure wlan0 route metric

[deadeyes]

Mick <michaelkintzios <at> gmail.com> writes:

> 
> It does?  I assume that eth1 above is wlan0 in your case.
> 


Yes indeed :) it is wlan0.

Re: [gentoo-user] Re: configure wlan0 route metric

[Indi]

On Thu, Apr 14, 2011 at 12:00:02PM +0200, Mick wrote:
> On 14 April 2011 09:13, deadeyes <gvm999@gmail.com> wrote:
> > deadeyes <gvm999 <at> gmail.com> writes:
> >
> > code that can be added in /etc/conf.d/net:
> > postup() {
> >   local metric=0
> >
> >   case "${IFACE}" in
> >      eth0) metric=0 ;;
> >      eth1) metric=1 ;;
> >   esac
> >   ifmetric "${IFACE}" "${metric}"
> >
> >   return 0
> > }
> >
> > Seems like this works for me as well! :)
> 
> It does?  I assume that eth1 above is wlan0 in your case.
>

On my thinkpad the wireless is eth0, wired is eth1.
Not sure why, but I've had a few machines that work that way.

-- 
 /\       /\ 
   <\   />    
      ^      caveat utilitor 
    'v-v'            

Re: [gentoo-user] Re: configure wlan0 route metric

[Indi]

On Fri, Apr 15, 2011 at 12:30:02AM +0200, Indi wrote:
> On Thu, Apr 14, 2011 at 12:00:02PM +0200, Mick wrote:
> > On 14 April 2011 09:13, deadeyes <gvm999@gmail.com> wrote:
> > > deadeyes <gvm999 <at> gmail.com> writes:
> > >
> > > code that can be added in /etc/conf.d/net:
> > > postup() {
> > >   local metric=0
> > >
> > >   case "${IFACE}" in
> > >      eth0) metric=0 ;;
> > >      eth1) metric=1 ;;
> > >   esac
> > >   ifmetric "${IFACE}" "${metric}"
> > >
> > >   return 0
> > > }
> > >
> > > Seems like this works for me as well! :)
> > 
> > It does?  I assume that eth1 above is wlan0 in your case.
> >
> 
> On my thinkpad the wireless is eth0, wired is eth1.

Oh, I got that backwards, sorry -- wireless is eth1.
:)
-- 
 /\       /\ 
   <\   />    
      ^      caveat utilitor 
    'v-v'            

Re: [gentoo-user] Re: configure wlan0 route metric

[Mick]

[-- Attachment #1: Type: Text/Plain, Size: 968 bytes --]

On Friday 15 April 2011 03:06:57 Indi wrote:
> On Fri, Apr 15, 2011 at 12:30:02AM +0200, Indi wrote:
> > On Thu, Apr 14, 2011 at 12:00:02PM +0200, Mick wrote:
> > > On 14 April 2011 09:13, deadeyes <gvm999@gmail.com> wrote:
> > > > deadeyes <gvm999 <at> gmail.com> writes:
> > > > 
> > > > code that can be added in /etc/conf.d/net:
> > > > postup() {
> > > >   local metric=0
> > > > 
> > > >   case "${IFACE}" in
> > > >      eth0) metric=0 ;;
> > > >      eth1) metric=1 ;;
> > > >   esac
> > > >   ifmetric "${IFACE}" "${metric}"
> > > > 
> > > >   return 0
> > > > }
> > > > 
> > > > Seems like this works for me as well! :)
> > > 
> > > It does?  I assume that eth1 above is wlan0 in your case.
> > 
> > On my thinkpad the wireless is eth0, wired is eth1.
> 
> Oh, I got that backwards, sorry -- wireless is eth1.

Different drivers name the wireless interface using different names (eth1, 
wlan0, ath0, etc.)

-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]