Bug 142219 – dhcpcd_eth1 does not set the correct options for dhcp on wlan nic

• Product: Gentoo Linux
• Status: VERIFIED NEEDINFO

[Description the_mgt 2006-07-30 13:49:23 UTC]

Hi!
(Long introduction to the problem, but I think it helps uderstanding...)
I am using a laptop and thought up some tricks to automatically connect home via openvpn if i am not in my home lan. This setup needs a running nameserver on my machine and it must avoid that /etc/resolv.conf is overwritten when i get an ip address via dhcp. I need my resolv.conf untouched (because of nameserver pointing to localhost and the "search" entries) and i need the network's information sent via dhcp for local nameservers and stuff. So i found out, the -e option of dhcpcd points to a directory where i can store the resolv.conf without destroying mine. This works fine for my ethernet nic, but it fails completely on my wlan-nic. Both nics use an identical line for configuration:
dhcpcd_eth0="-t 20 -e /etc/dhcpc"
dhcpcd_eth1="-t 20 -e /etc/dhcpc"
It works for eth0, but not for eth1. Baselayout is version 1.12.0-r1, dhcpcd is 2.0.7.
Since wireless.example states that dhcpcd_ESSID overrides interface settings, i think it should recognize my eth1 setting.

[Comment 1 Roy Marples (RETIRED) 2006-07-30 16:23:11 UTC]

Why don't you emerge resolvconf-gentoo to manage /etc/resolv.conf for you?

I use that to manage wired, wireless and openvpn connections on my laptop.
You'll probably need baselayout-1.12.1 and definitely openvpn-2.1 beta for resolvconf support though.

As to the bug report, please attach your conf.d/net and conf.d/wireless files.

[Comment 2 the_mgt 2006-07-31 15:14:31 UTC]

(In reply to comment #1)
> Why don't you emerge resolvconf-gentoo to manage /etc/resolv.conf for you?
Because I never heard of it... Emerging right now, sounds very good!
 
> As to the bug report, please attach your conf.d/net and conf.d/wireless files.
> 
conf.d/net:
modules_eth0=( "dhcpcd" )
modules_eth1=( "!wpa_supplicant" "dhcpcd" )
modles_bnep0=( "!dhcpcd" )

dhcpcd_eth0="-t 20 -e /etc/dhcpc"
dhcpcd_eth1="-t 20 -e /etc/dhcpc"

config_eth0=( "dhcp" )

config_bnep0=( "10.42.1.2/24" )
routes_bnep0=( "default via 10.42.1.1" )

conf.d/wireless: 
config_Essone=( "dhcp" )
preferred_aps=( "WLAN" "TUBSWLAN" "Essone" )
config_Essone=( "dhcp" )
dns_servers_Essone=( "10.42.0.1" )
dns_domain_Essone="wunderland"
dns_search_domains_Essone="wunderland"

Since it defenitely happens with this ESSID, i posted only these settings for wireless. (And omitted the key ;)

[Comment 3 Roy Marples (RETIRED) 2006-08-01 08:27:07 UTC]

Please test with baselayout-1.12.2 and dhcpcd-2.0.8

BTW, the -e option will be dropped for dhcpcd-3 I think as it's a bit silly now we have resolvconf support.

[Comment 4 the_mgt 2006-08-05 12:47:39 UTC]

(In reply to comment #3)
> Please test with baselayout-1.12.2 and dhcpcd-2.0.8
I tested with baselayout-1.12.2 and dhcpcd-2.0.8-r2, but it didn't work either.

It does work as I inteded it to with baselayout-1.12.4!

> BTW, the -e option will be dropped for dhcpcd-3 I think as it's a bit silly now
> we have resolvconf support.
 Ok, so i guess i will switch to that solution.

All in all, i guess we can close the bug?