Arch Linux

gregghz

Member

Registered: 2013-09-07

Posts: 3

[SOLVED] Trouble Connecting to a DD-WRT Client Bridge

I've followed the instructions here: http://www.dd-wrt.com/wiki/index.php/Client_Bridged to set up a client bridge. I've verified that this works. I can connect to it (and use the internet) from one Arch desktop and a Windows laptop.

My problem is that my Arch laptop will not connect to the slave router in the client bridge setup. I'm using NetworkManager on both the Arch desktop and the Arch laptop. When I attempt to connect to the bridge on my laptop I get this output in journalctl:

Sep 07 10:07:33 mbp kernel: tg3 0000:02:00.0 enp2s0f0: Link is up at 1000 Mbps, full duplex
Sep 07 10:07:33 mbp kernel: tg3 0000:02:00.0 enp2s0f0: Flow control is on for TX and on for RX
Sep 07 10:07:33 mbp NetworkManager[4117]: <info> (enp2s0f0): carrier now ON (device state 20)
Sep 07 10:07:33 mbp NetworkManager[4117]: <info> (enp2s0f0): device state change: unavailable -> disconnected (reason 'carrier-changed') [20 30 40]
Sep 07 10:07:33 mbp kernel: tg3 0000:02:00.0 enp2s0f0: EEE is disabled
Sep 07 10:07:33 mbp NetworkManager[4117]: <info> Auto-activating connection 'Wired connection 1'.
Sep 07 10:07:33 mbp NetworkManager[4117]: <info> Activation (enp2s0f0) starting connection 'Wired connection 1'
Sep 07 10:07:33 mbp NetworkManager[4117]: <info> (enp2s0f0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Sep 07 10:07:33 mbp NetworkManager[4117]: <info> Activation (enp2s0f0) Stage 1 of 5 (Device Prepare) scheduled...
Sep 07 10:07:33 mbp NetworkManager[4117]: <info> Activation (enp2s0f0) Stage 1 of 5 (Device Prepare) started...
Sep 07 10:07:33 mbp NetworkManager[4117]: <info> Activation (enp2s0f0) Stage 2 of 5 (Device Configure) scheduled...
Sep 07 10:07:33 mbp NetworkManager[4117]: <info> Activation (enp2s0f0) Stage 1 of 5 (Device Prepare) complete.
Sep 07 10:07:33 mbp NetworkManager[4117]: <info> Activation (enp2s0f0) Stage 2 of 5 (Device Configure) starting...
Sep 07 10:07:33 mbp NetworkManager[4117]: <info> (enp2s0f0): device state change: prepare -> config (reason 'none') [40 50 0]
Sep 07 10:07:33 mbp NetworkManager[4117]: <info> Activation (enp2s0f0) Stage 2 of 5 (Device Configure) successful.
Sep 07 10:07:33 mbp NetworkManager[4117]: <info> Activation (enp2s0f0) Stage 3 of 5 (IP Configure Start) scheduled.
Sep 07 10:07:33 mbp NetworkManager[4117]: <info> Activation (enp2s0f0) Stage 2 of 5 (Device Configure) complete.
Sep 07 10:07:33 mbp NetworkManager[4117]: <info> Activation (enp2s0f0) Stage 3 of 5 (IP Configure Start) started...
Sep 07 10:07:33 mbp NetworkManager[4117]: <info> (enp2s0f0): device state change: config -> ip-config (reason 'none') [50 70 0]
Sep 07 10:07:33 mbp NetworkManager[4117]: <info> Activation (enp2s0f0) Beginning DHCPv4 transaction (timeout in 45 seconds)
Sep 07 10:07:33 mbp NetworkManager[4117]: <info> dhcpcd started with pid 29670
Sep 07 10:07:33 mbp NetworkManager[4117]: <info> Activation (enp2s0f0) Beginning IP6 addrconf.
Sep 07 10:07:33 mbp NetworkManager[4117]: <info> Activation (enp2s0f0) Stage 3 of 5 (IP Configure Start) complete.
Sep 07 10:07:33 mbp dhcpcd[29670]: dhcpcd already running on pid 998 (/run/dhcpcd-enp2s0f0.pid)
Sep 07 10:07:33 mbp NetworkManager[4117]: <info> (enp2s0f0): DHCPv4 client pid 29670 exited with status 1
Sep 07 10:07:33 mbp NetworkManager[4117]: <info> Activation (enp2s0f0) Stage 4 of 5 (IPv4 Configure Timeout) scheduled...
Sep 07 10:07:33 mbp NetworkManager[4117]: <info> Activation (enp2s0f0) Stage 4 of 5 (IPv4 Configure Timeout) started...
Sep 07 10:07:33 mbp NetworkManager[4117]: <info> Activation (enp2s0f0) Stage 4 of 5 (IPv4 Configure Timeout) complete.
Sep 07 10:07:53 mbp NetworkManager[4117]: <info> (enp2s0f0): IP6 addrconf timed out or failed.
Sep 07 10:07:53 mbp NetworkManager[4117]: <info> Activation (enp2s0f0) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
Sep 07 10:07:53 mbp NetworkManager[4117]: <info> Activation (enp2s0f0) Stage 4 of 5 (IPv6 Configure Timeout) started...
Sep 07 10:07:53 mbp NetworkManager[4117]: <info> (enp2s0f0): device state change: ip-config -> failed (reason 'ip-config-unavailable') [70 120 5]
Sep 07 10:07:53 mbp NetworkManager[4117]: <warn> Activation (enp2s0f0) failed for connection 'Wired connection 1'
Sep 07 10:07:53 mbp NetworkManager[4117]: <info> Activation (enp2s0f0) Stage 4 of 5 (IPv6 Configure Timeout) complete.
Sep 07 10:07:53 mbp NetworkManager[4117]: <info> (enp2s0f0): device state change: failed -> disconnected (reason 'none') [120 30 0]
Sep 07 10:07:53 mbp NetworkManager[4117]: <info> (enp2s0f0): deactivating device (reason 'none') [0]

As far as I know the only software difference between the desktop and the laptop is that the laptop is running wmii while the desktop is running the full gnome desktop. I've also tried this with two different routers with the same results.

lspci shows this ehternet adapter on the laptop:

02:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM57765 Gigabit Ethernet PCIe (rev 10)

What other information might be needed?

Last edited by gregghz (2013-09-11 14:26:37)

rufus

Banned

From: san francisco

Registered: 2013-04-20

Posts: 153

Re: [SOLVED] Trouble Connecting to a DD-WRT Client Bridge

I always had better luck with tomato you might wanna give that a go.

---

end ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     'the machine is not the end to the means., we are. In history, in board rooms and politic the greatest  decision and effort
        evolves from passion, lust for life, and a common sense of humanity. Never forget what you are and why'.         -me

WonderWoofy

Member

From: Los Gatos, CA

Registered: 2012-05-19

Posts: 8,414

Re: [SOLVED] Trouble Connecting to a DD-WRT Client Bridge

I always had better luck with tomato you might wanna give that a go.

@rufus, you should be aware that tomato is a fork of OpenWRT that is meant for broadcom based routers specifically.  So this recommendation is likely going to be an impossible feat quite often.

rufus

Banned

From: san francisco

Registered: 2013-04-20

Posts: 153

Re: [SOLVED] Trouble Connecting to a DD-WRT Client Bridge

well thanx for the headsup but lets face it G is out and going... and N is in

---

end ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     'the machine is not the end to the means., we are. In history, in board rooms and politic the greatest  decision and effort
        evolves from passion, lust for life, and a common sense of humanity. Never forget what you are and why'.         -me

WonderWoofy

Member

From: Los Gatos, CA

Registered: 2012-05-19

Posts: 8,414

Re: [SOLVED] Trouble Connecting to a DD-WRT Client Bridge

well thanx for the headsup but lets face it G is out and going... and N is in

I have no idea what you are talking about here…

rufus

Banned

From: san francisco

Registered: 2013-04-20

Posts: 153

Re: [SOLVED] Trouble Connecting to a DD-WRT Client Bridge

Either do I ....I havnt dealt with firmwares and wifi for a couple of years...and at last gasp N based routers werent supported
by tomato, or the likes, to my recollection. After a short check that doesnt appear to be the case today. As far as my internet
usage is based today its all ethernet and I kinda doubt there could be any appreciable advantage to messing with firmwares
.....I could be wrong....but Id be interested in knowing if there was....

---

end ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     'the machine is not the end to the means., we are. In history, in board rooms and politic the greatest  decision and effort
        evolves from passion, lust for life, and a common sense of humanity. Never forget what you are and why'.         -me

gregghz

Member

Registered: 2013-09-07

Posts: 3

Re: [SOLVED] Trouble Connecting to a DD-WRT Client Bridge

Thanks, but Tomato is not compatible with my router.

ewaller

Administrator

From: Pasadena, CA

Registered: 2009-07-13

Posts: 20,354

Re: [SOLVED] Trouble Connecting to a DD-WRT Client Bridge

System
Router Name DD-WRT
Router Model Netgear WNDR3400
Firmware Version DD-WRT v24-sp2 (04/07/12) big - build 18946M NEWD-2 K2.6 Eko

My dual band Netgear router hardware works just dandy in both G and N modes with DD-WRT

---

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

Lama reborn

Member

Registered: 2007-12-09

Posts: 3

Re: [SOLVED] Trouble Connecting to a DD-WRT Client Bridge

From the pasted log it seems that dhcp configuration fails - dhcpd is already running and so the interface does not get IP address. Also try turning off ipv6 if you don't need it.

WonderWoofy

Member

From: Los Gatos, CA

Registered: 2012-05-19

Posts: 8,414

Re: [SOLVED] Trouble Connecting to a DD-WRT Client Bridge

Look in the wiki for "disable ipv6"

gregghz

Member

Registered: 2013-09-07

Posts: 3

Re: [SOLVED] Trouble Connecting to a DD-WRT Client Bridge

From the pasted log it seems that dhcp configuration fails - dhcpd is already running and so the interface does not get IP address. Also try turning off ipv6 if you don't need it.

Look in the wiki for "disable ipv6"

As both of you suggested, I disabled ipv6 (using kernel parameters as suggested in the wiki) and the connection now works and the log no longer complains of dhcpcd already being running.

Thanks for this, I really appreciate it.

WonderWoofy

Member

From: Los Gatos, CA

Registered: 2012-05-19

Posts: 8,414

Re: [SOLVED] Trouble Connecting to a DD-WRT Client Bridge

The timeout looking of an IPv6 connection is not uncommon.  So if you don't want to fully disable it from your system, you can simply increase the timeout of dhcpcd.  Otherwise, dhcpcd can also be told to specifically use IPv4 explicitly with the '-4' switch.