Re: [gentoo-user] wpa_supplicant not starting dhcpcd

[Tamer Higazi]

Hi,
I had the same issue.

1st you have to check how the ipaddresses are managed ?
Are you sure that you make use of gentoo network addressing and not th 
systemd network manage ?

Be tripple sure of it, and have a look there:
/etc/systemd/network/

2nd. Your WLAN board should give ip-addresses away, not receive them.
The config_wlp3s0="dhcp" is totally wrong.

you must assign this wlan device an address, and configure  it.


2nd, DHCPD gives IP-Adresses away through one address.
Config is here /etc/dhcp/dhcpd.conf

for example, if the network card is 192.168.0.1 and you configured dhcpd 
that everything that is wired to it, will receive an ip-address not the 
wlan board.


dhcpd would look like this (for 2 networks on 2 boards)
You cannot have the same network on 2 boards.

#Wired Board

subnet 192.168.0.0 netmask 255.255.255.0 {
     pool {
         range 192.168.0.100 192.168.0.200;
         default-lease-time 259200;
         max-lease-time 518400;
         option subnet-mask 255.255.255.0;
         option broadcast-address 192.168.0.255;
         option routers 192.168.0.1;
         option domain-name-servers 1.1.1.1;
     }
}

#WLAN Config

subnet 192.168.1.0 netmask 255.255.255.0 {
     pool {
         range 192.168.1.100 192.168.1.200;
         default-lease-time 259200;
         max-lease-time 518400;
         option subnet-mask 255.255.255.0;
         option broadcast-address 192.168.0.255;
         option routers 192.168.1.1;
         option domain-name-servers 1.1.1.1;
     }
}

What I would advise, is to setup a network bridge, and add the wlan and 
lan device to it.
Then there is only one network.....



best, Tamer


On 2019-12-21 18:15, n952162 wrote:
>
> Okay, I have an update on this.
>
> Note that wlp3s0 is the WireLess adapter and enp0s2 is the wired
> Ethernet adapter.
>
> Given the /etc/conf.d/net as shown below (i.e. only config_wlp3s0="dhcp")
>
>  1. If there is *no* /etc/init.d/net.enp0s2 link (or any adapter
>     link), then the wireless connection comes up with a dhcp-derived
>     address
>  2. if there *is* an /etc/init.d/net.enp0s2 link, and the same
>     /etc/conf.d/net file:
>      1. the wireless comes up with no address (and no dhcp attempt in
>         /var/log/syslog)
>      2. The wired adapter has a (dhcp-derived) zero-conf address or
>         something, at 169.
>  3. if a fixed ip address is additionally specified for the wired
>     adapter in /etc/conf.d/net
>      1. it is assigned as specified
>      2. No attempt is made to run dhcp on the wireless anymore
>         (although dhcp *is* specified for it in /etc/conf.d/net)
>
> The thing is, before my root filesystem got crashed by a negligent
> ext4 recovery, the system came up multi-homed, with a static and a
> dhcp-derived address.
> Coming from 4.9.? to 4.19.72.
>
> Could it be that something changed?
>
>
> On 12/19/19 08:46, n952162 wrote:
>> I have this line in /etc/conf.d/net:
>>
>> config_wlp3s0="dhcp"
>>
>> given:
>>
>> $ifconfig wlp3s0
>> wlp3s0    Link encap:Ethernet  HWaddr xx:xx:xx:xx:xx:xx
>>           inet addr:192.168.178.42 Bcast:192.168.178.255
>> Mask:255.255.255.0
>>           UP BROADCAST RUNNING MULTICAST  MTU:1500 Metric:1
>>           RX packets:2008 errors:0 dropped:0 overruns:0 frame:0
>>           TX packets:335 errors:0 dropped:0 overruns:0 carrier:0
>>           collisions:0 txqueuelen:1000
>>           RX bytes:619501  TX bytes:40551
>>
>> but I still have to manually start dhcpcd (now, after installing kernel
>> 4.19.72).
>>
>> Another problem - wpa_supplicant then defines a default gateway, even
>> though one already existed for the wired connection:
>>
>> config_enp2s0="192.168.179.20 netmask 255.255.255.0 brd 192.168.179.255"
>> routes_enp2s0="default via 192.168.179.24"
>>
>> I have to then manually delete that when I'm on wireless.  That all
>> happened automatically before.  I wonder how I broke that all.
>>
>>
>