Re: [gentoo-user] re: alternating between wired and wireless interfaces

[Shawn Wilson]

Just thought I'd give the other popular alternative of the Redhat backed NetworkManager. 

Also, if you don't wait for the interface to come up I don't think the service can bind to the interface (and it obviously can't bind to an IP). Probably not an issue for ssh but possibly one for MySQL or Apache. 

Torben Hensgens Mailer <thens.mail@××××××××××.com> wrote:
>Am 21.09.2013 12:47, schrieb Alexander Kapshuk:
>> I have both wired and wireless network interfaces configured:
>> box0 log # rc-update show|egrep 'enp3s0|wlp2s0'
>>             net.enp3s0 |      default
>>             net.wlp2s0 |      default
>>
>> (1). Is there a way to instruct the system as to which network
>interface
>> to use, so it doesn't try to bring up the one not intended to be used
>at
>> boot time:
>> box0 log # egrep 'enp3s0|wlp2s0' messages
>> -------------------------------------------
>> Sep 21 12:30:18 localhost kernel: [   12.268209] r8169 0000:03:00.0
>> enp3s0: link down
>> Sep 21 12:30:18 localhost kernel: [   12.268236] IPv6:
>> ADDRCONF(NETDEV_UP): enp3s0: link is not ready
>> Sep 21 12:30:18 localhost /etc/init.d/net.enp3s0[1888]: No
>configuration
>> specified; defaulting to DHCP
>> Sep 21 12:30:18 localhost dhcpcd[1896]: enp3s0: waiting for carrier
>> Sep 21 12:30:56 localhost /etc/init.d/net.enp3s0[1801]: ERROR:
>> net.enp3s0 failed to start
>> Sep 21 12:30:56 localhost kernel: [   50.595278] IPv6:
>> ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
>> Sep 21 12:30:56 localhost /etc/init.d/net.wlp2s0[1917]: WARNING:
>> net.wlp2s0 has started, but is inactive
>> Sep 21 12:30:56 localhost /etc/init.d/netmount[2007]: ERROR: cannot
>> start netmount as net.enp3s0 would not start
>> Sep 21 12:30:56 localhost /etc/init.d/sshd[2008]: ERROR: cannot start
>> sshd as net.enp3s0 would not start
>> Sep 21 12:30:57 localhost kernel: [   51.817387] wlp2s0: authenticate
>> with f4:ec:38:b9:59:a7
>> Sep 21 12:30:57 localhost kernel: [   51.825344] wlp2s0: send auth to
>> f4:ec:38:b9:59:a7 (try 1/3)
>> Sep 21 12:30:57 localhost kernel: [   51.826811] wlp2s0:
>authenticated
>> Sep 21 12:30:57 localhost kernel: [   51.827059] wlp2s0: associate
>with
>> f4:ec:38:b9:59:a7 (try 1/3)
>> Sep 21 12:30:57 localhost kernel: [   51.829316] wlp2s0: RX AssocResp
>> from f4:ec:38:b9:59:a7 (capab=0x411 status=0 aid=2)
>> Sep 21 12:30:57 localhost kernel: [   51.829586] wlp2s0: associated
>> Sep 21 12:30:57 localhost kernel: [   51.829598] IPv6:
>> ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready
>> Sep 21 12:30:59 localhost wpa_cli: interface wlp2s0 CONNECTED
>> Sep 21 12:30:59 localhost /etc/init.d/net.wlp2s0[2130]: No
>configuration
>> specified; defaulting to DHCP
>> Sep 21 12:30:59 localhost dhcpcd[2138]: wlp2s0: sending IPv6 Router
>> Solicitation
>> Sep 21 12:30:59 localhost dhcpcd[2138]: wlp2s0: sendmsg: Cannot
>assign
>> requested address
>> Sep 21 12:30:59 localhost dhcpcd[2138]: wlp2s0: rebinding lease of
>> 192.168.1.5
>> Sep 21 12:30:59 localhost dhcpcd[2138]: wlp2s0: acknowledged
>192.168.1.5
>> from 192.168.1.1 `TP-LINK'
>> Sep 21 12:30:59 localhost dhcpcd[2138]: wlp2s0: checking for
>192.168.1.5
>> Sep 21 12:31:03 localhost dhcpcd[2138]: wlp2s0: sending IPv6 Router
>> Solicitation
>> Sep 21 12:31:03 localhost dhcpcd[2138]: wlp2s0: leased 192.168.1.5
>for
>> 259200 seconds
>> Sep 21 12:31:07 localhost dhcpcd[2167]: wlp2s0: sending IPv6 Router
>> Solicitation
>> Sep 21 12:31:11 localhost dhcpcd[2167]: wlp2s0: sending IPv6 Router
>> Solicitation
>> Sep 21 12:31:11 localhost dhcpcd[2167]: wlp2s0: no IPv6 Routers
>available
>> -------------------------------------------
>> (2). sshd seems to start only if the wired interface is up. How do I
>> tell it start when the wireless interface is running?
>> box0 log # rc-status|egrep 'enp3s0|wlp2s0|sshd'
>>   net.enp3s0                                                        [
>> stopped  ]
>>   net.wlp2s0                                                        [
>> started  ]
>>   sshd                                                              [
>> stopped  ]
>>
>>
>> Thanks.
>>
>>
>
>Yeh, same advice here, try wicd first. If you don't want a GUI (or you
>don't have corresponding UI toolkits installed), there's also the
>option
>to configure and use wicd via the ncurses interface.