[systemd-devel] Can't connect to WiFi when the wired and the wireless interfaces are bonded

[Doron Behar]

I agree. This is what I understood from the manual pages. I've even
tried to run `dhcpcd wlp2s0` manually after I've connected to the WiFi
network and it didn't help either. Here is `dhcpcd`'s output:

	DUID 00:01:00:01:22:58:f0:ec:34:13:e8:35:48:e6
	wlp2s0: IAID c4:ca:ef:aa
	wlp2s0: adding address fe80::bf80:8309:6514:f4ff
	wlp2s0: soliciting a DHCP lease
	wlp2s0: soliciting an IPv6 router
	wlp2s0: offered 192.168.43.146 from 192.168.43.1
	wlp2s0: probing address 192.168.43.146/24
	wlp2s0: leased 192.168.43.146 for 3600 seconds
	wlp2s0: adding route to 192.168.43.0/24
	wlp2s0: adding default route via 192.168.43.1
	forked to background, child pid 1142

It does seem to be working yet I'm not really connected to the internet,
`ping 8.8.8.8` doesn't work.

On Wed, May 16, 2018 at 09:14:01AM +0300, Mantas Mikulėnas wrote:
> On Wed, May 16, 2018 at 12:47 AM Bruce A. Johnson <
> bjohnson at blueridgenetworks.com> wrote:
> 
> > Doron,
> >
> > I don't see any mention of DHCP in  your wireless network definition, so
> > I'm dubious that your system has made any attempt at getting an IP address
> > on wlp2s0. Try adding *DHCP=yes* to the *[Network]* section of
> > 25-wireless.network.
> >
> > I haven't done a wireless setup with systemd yet, nor have I tried the
> > active-backup configuration you're working with, so I may be completely
> > wrong. Please let me know whether or not it works.
> >
> I believe the individual bonded interfaces don't *need* to speak IP at all;
> only the 'main' bond itself does.
> 
> -- 
> Mantas Mikulėnas