5:03 p.m.
Setting up the team driver on Debian Sid seems straight forward, and
the links seem to go up without error, but I cannot ping my router IP
address or otherwise connect outside the box. I am no expert in
networking, and am guessing the error may be obvious to someone on the
list, or someone might be able to point me in the right direction to
search for a solution.
To me, it seems this may be a gateway issue as, after setting up the
team driver, route -n gives:
Destination Gateway Genmask Flags Metric Ref
Use Iface
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0
0 myteam0
If I set the ip address of the router connected to the nic on eth0 as
the gateway, route -n gives:
Destination Gateway Genmask Flags Metric Ref
Use Iface
0.0.0.0 192.168.0.1 0.0.0.0 UG 0 0
0 myteam0
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0
0 myteam0
But pinging 192.168.0.1 results in "Destination Host Unreachable". If
I try setting a default gateway using myteam0 or eth0, the route
command returns "Unknown host".
After my initial day of failures, I commented out the eth0 and eth1
stanzas in the /etc/network/interfaces file and purged network-manager
to avoid potential problems. The original configuration has the router
connected to eth0 set the ip address of eth0 as 192.168.0.101 through
DHCP.
I tested initially with the Debian Sid libteam packages (v.12) and
then built v.15 from libteam-master.zip source. I have done most of my
testing with the basic commands:
teamd -g -t myteam0 -d
teamdctl myteam0 port add eth0
teamdctl myteam0 port add eth1
ip addr add 192.168.0.101/24 dev myteam0
ip link set myteam0 up
Before running the above commands to start teaming, ip link shows:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
mode DEFAULT group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode
DEFAULT group default qlen 1000
link/ether 50:e5:49:ec:d6:3f brd ff:ff:ff:ff:ff:ff
3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode
DEFAULT group default qlen 1000
link/ether e8:de:27:06:85:d5 brd ff:ff:ff:ff:ff:ff
After running the teaming commands, ip link shows:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
mode DEFAULT group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
master myteam0 state UP mode DEFAULT group default qlen 1000
link/ether 9e:a4:72:48:1d:f7 brd ff:ff:ff:ff:ff:ff
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
master myteam0 state UP mode DEFAULT group default qlen 1000
link/ether 50:e5:49:ec:d6:3f brd ff:ff:ff:ff:ff:ff
4: myteam0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue
state UP mode DEFAULT group default
link/ether 50:e5:49:ec:d6:3f brd ff:ff:ff:ff:ff:ff
and ip addr shows:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
master myteam0 state UP group default qlen 1000
link/ether 9e:a4:72:48:1d:f7 brd ff:ff:ff:ff:ff:ff
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
master myteam0 state UP group default qlen 1000
link/ether 50:e5:49:ec:d6:3f brd ff:ff:ff:ff:ff:ff
4: myteam0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue
state UP group default
link/ether 50:e5:49:ec:d6:3f brd ff:ff:ff:ff:ff:ff
inet 192.168.0.101/24 scope global myteam0
valid_lft forever preferred_lft forever
I have looked at syslog and see no errors or warnings. It seems
everything is fine as syslog shows:
Jan 4 17:09:56 thor avahi-daemon[3647]: Joining mDNS multicast
group on interface myteam0.IPv4 with address 192.168.0.101.
Jan 4 17:09:56 thor avahi-daemon[3647]: New relevant interface
myteam0.IPv4 for mDNS.
Jan 4 17:09:56 thor avahi-daemon[3647]: Registering new address
record for 192.168.0.101 on myteam0.IPv4.
Jan 4 17:09:57 thor ntpd[3708]: Listen normally on 2 myteam0
192.168.0.101 UDP 123
teamdctl myteam0 config dump
{
"device": "myteam0",
"ports": {
"eth0": {
"link_watch": {
"name": "ethtool"
}
},
"eth1": {
"link_watch": {
"name": "ethtool"
}
}
},
"runner": {
"name": "roundrobin"
}
}
teamdctl myteam0 state view
setup:
runner: roundrobin
ports:
eth1
link watches:
link summary: up
instance[link_watch_0]:
name: ethtool
link: up
eth0
link watches:
link summary: up
instance[link_watch_0]:
name: ethtool
link: up
I am running kernel 3.18.1 x86_64 with the .config:
CONFIG_NET_TEAM=y
CONFIG_NET_TEAM_MODE_BROADCAST=m
CONFIG_NET_TEAM_MODE_ROUNDROBIN=m
CONFIG_NET_TEAM_MODE_RANDOM=m
CONFIG_NET_TEAM_MODE_ACTIVEBACKUP=m
CONFIG_NET_TEAM_MODE_LOADBALANCE=m
Any suggestions appreciated,
J.L. Hill
6:50 a.m.
On Sunday, January 04, 2015 06:03:26 PM PanaColina wrote:
Setting up the team driver on Debian Sid seems straight forward, and
the links seem to go up without error, but I cannot ping my router IP
address or otherwise connect outside the box. I am no expert in
networking, and am guessing the error may be obvious to someone on the
list, or someone might be able to point me in the right direction to
search for a solution.
To me, it seems this may be a gateway issue as, after setting up the
team driver, route -n gives:
Destination Gateway Genmask Flags Metric Ref
Use Iface
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0
0 myteam0
If I set the ip address of the router connected to the nic on eth0 as
the gateway, route -n gives:
Destination Gateway Genmask Flags Metric Ref
Use Iface
0.0.0.0 192.168.0.1 0.0.0.0 UG 0 0
0 myteam0
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0
0 myteam0
But pinging 192.168.0.1 results in "Destination Host Unreachable". If
I try setting a default gateway using myteam0 or eth0, the route
command returns "Unknown host".
After my initial day of failures, I commented out the eth0 and eth1
stanzas in the /etc/network/interfaces file and purged network-manager
to avoid potential problems. The original configuration has the router
connected to eth0 set the ip address of eth0 as 192.168.0.101 through
DHCP.
I tested initially with the Debian Sid libteam packages (v.12) and
then built v.15 from libteam-master.zip source. I have done most of my
testing with the basic commands:
teamd -g -t myteam0 -d
teamdctl myteam0 port add eth0
teamdctl myteam0 port add eth1
ip addr add 192.168.0.101/24 dev myteam0
ip link set myteam0 up
Before running the above commands to start teaming, ip link shows:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
mode DEFAULT group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode
DEFAULT group default qlen 1000
link/ether 50:e5:49:ec:d6:3f brd ff:ff:ff:ff:ff:ff
3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode
DEFAULT group default qlen 1000
link/ether e8:de:27:06:85:d5 brd ff:ff:ff:ff:ff:ff
After running the teaming commands, ip link shows:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
mode DEFAULT group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
master myteam0 state UP mode DEFAULT group default qlen 1000
link/ether 9e:a4:72:48:1d:f7 brd ff:ff:ff:ff:ff:ff
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
master myteam0 state UP mode DEFAULT group default qlen 1000
link/ether 50:e5:49:ec:d6:3f brd ff:ff:ff:ff:ff:ff
4: myteam0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue
state UP mode DEFAULT group default
link/ether 50:e5:49:ec:d6:3f brd ff:ff:ff:ff:ff:ff
and ip addr shows:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
master myteam0 state UP group default qlen 1000
link/ether 9e:a4:72:48:1d:f7 brd ff:ff:ff:ff:ff:ff
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
master myteam0 state UP group default qlen 1000
link/ether 50:e5:49:ec:d6:3f brd ff:ff:ff:ff:ff:ff
4: myteam0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue
state UP group default
link/ether 50:e5:49:ec:d6:3f brd ff:ff:ff:ff:ff:ff
inet 192.168.0.101/24 scope global myteam0
valid_lft forever preferred_lft forever
I have looked at syslog and see no errors or warnings. It seems
everything is fine as syslog shows:
Jan 4 17:09:56 thor avahi-daemon[3647]: Joining mDNS multicast
group on interface myteam0.IPv4 with address 192.168.0.101.
Jan 4 17:09:56 thor avahi-daemon[3647]: New relevant interface
myteam0.IPv4 for mDNS.
Jan 4 17:09:56 thor avahi-daemon[3647]: Registering new address
record for 192.168.0.101 on myteam0.IPv4.
Jan 4 17:09:57 thor ntpd[3708]: Listen normally on 2 myteam0
192.168.0.101 UDP 123
teamdctl myteam0 config dump
{
"device": "myteam0",
"ports": {
"eth0": {
"link_watch": {
"name": "ethtool"
}
},
"eth1": {
"link_watch": {
"name": "ethtool"
}
}
},
"runner": {
"name": "roundrobin"
}
}
Could you try 'activebackup' instead of 'roundrobin'? Active-Backup is
more simple
and more likely to work. If that works out, we know there is something related to
roundrobin.
Thanks
fbl
teamdctl myteam0 state view
setup:
runner: roundrobin
ports:
eth1
link watches:
link summary: up
instance[link_watch_0]:
name: ethtool
link: up
eth0
link watches:
link summary: up
instance[link_watch_0]:
name: ethtool
link: up
I am running kernel 3.18.1 x86_64 with the .config:
CONFIG_NET_TEAM=y
CONFIG_NET_TEAM_MODE_BROADCAST=m
CONFIG_NET_TEAM_MODE_ROUNDROBIN=m
CONFIG_NET_TEAM_MODE_RANDOM=m
CONFIG_NET_TEAM_MODE_ACTIVEBACKUP=m
CONFIG_NET_TEAM_MODE_LOADBALANCE=m
Any suggestions appreciated,
J.L. Hill
_______________________________________________
libteam mailing list
libteam(a)lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/libteam
9:24 a.m.
Thank you for your response -- testing with activebackup pointed
towards one problem:
Jan 5 08:42:04 thor teamd_myteam0[5549]: eth0: Got link watch from port config.
Jan 5 08:42:04 thor teamd_myteam0[5549]: eth0: Using sticky "0".
Jan 5 08:42:04 thor teamd_myteam0[5549]: eth0: Failed to set port
hardware address.
Jan 5 08:42:04 thor teamd_myteam0[5549]: Failed to init port priv.
Jan 5 08:42:04 thor teamd_myteam0[5549]: Callback named
"lw_ethtool_delay" not found.
Jan 5 08:42:04 thor teamd_myteam0[5549]: Loop callback failed with:
Device or resource busy
Jan 5 08:42:04 thor teamd_myteam0[5549]: Failed loop callback:
libteam_events, 0x22073c0
I am booting the computer with the eth stanzas of the interfaces file
commented out, and before starting teamd, ip link shows eth0 down.
eth0 does work in a standard network config. If it helps, eth0 uses
the atl1c driver (Atheros AR8151 nic); eth1 uses r8169. Although eth1
comes up, no gateway is in the route and I cannot ping out from the
box.
I don't know what else to look for or test. I've pasted below
everything from this test that seems potentially relevant.
Thank you again for any suggestions,
J.L. Hill
----------------
dmesg:
[ 0.231304] atl1c 0000:03:00.0: version 1.0.1.1-NAPI
[ 0.231955] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
[ 0.232582] r8169 0000:04:00.0: can't disable ASPM; OS doesn't have
ASPM control
[ 0.233219] r8169 0000:04:00.0: enabling device (0000 -> 0003)
[ 0.234036] r8169 0000:04:00.0: irq 25 for MSI/MSI-X
[ 0.234140] r8169 0000:04:00.0 eth1: RTL8168e/8111e at
0xffffc90004098000, e8:de:27:06:85:d5, XID 0c200000 IRQ 25
[ 0.235420] r8169 0000:04:00.0 eth1: jumbo features [frames: 9200
bytes, tx checksumming: ko]
--------------
syslog after running "teamd -g -f teamd-activebackup.conf -d"
Jan 5 08:42:04 thor teamd_myteam0[5549]: Added loop callback: daemon, 0x22073c0
Jan 5 08:42:04 thor teamd_myteam0[5549]: Added loop callback:
libteam_events, 0x22073c0
Jan 5 08:42:04 thor teamd_myteam0[5549]: Added loop callback: workq, 0x22073c0
Jan 5 08:42:04 thor teamd_myteam0[5549]: Using team runner "activebackup".
Jan 5 08:42:04 thor kernel: [ 195.203271] myteam0: Mode changed to
"activebackup"
Jan 5 08:42:04 thor kernel: [ 195.204048] atl1c 0000:03:00.0: irq 29
for MSI/MSI-X
Jan 5 08:42:04 thor kernel: [ 195.204607] atl1c 0000:03:00.0: atl1c:
eth0 NIC Link is Up<100 Mbps Full Duplex>
Jan 5 08:42:04 thor teamd_myteam0[5549]: Using hwaddr_policy "same_all".
Jan 5 08:42:04 thor teamd_myteam0[5549]: usock: Using sockpath
"/var/run/teamd/myteam0.sock"
Jan 5 08:42:04 thor teamd_myteam0[5549]: Added loop callback: usock, 0x22073c0
Jan 5 08:42:04 thor teamd_myteam0[5549]: <ifinfo_list>
Jan 5 08:42:04 thor teamd_myteam0[5549]: 4: myteam0: ae:e7:26:5e:8c:99: 0
Jan 5 08:42:04 thor teamd_myteam0[5549]: </ifinfo_list>
Jan 5 08:42:04 thor teamd_myteam0[5549]: <port_list>
Jan 5 08:42:04 thor teamd_myteam0[5549]: </port_list>
Jan 5 08:42:04 thor teamd_myteam0[5549]: eth0: Adding port (found ifindex
"2").
Jan 5 08:42:04 thor teamd_myteam0[5549]: eth1: Adding port (found ifindex
"3").
Jan 5 08:42:04 thor kernel: [ 195.205436] myteam0: Port device eth0 added
Jan 5 08:42:04 thor kernel: [ 195.371968] r8169 0000:04:00.0 eth1: link down
Jan 5 08:42:04 thor kernel: [ 195.371981] r8169 0000:04:00.0 eth1: link down
Jan 5 08:42:04 thor kernel: [ 195.372057] myteam0: Port device eth1 added
Jan 5 08:42:04 thor teamd_myteam0[5549]: 1.15 successfully started.
Jan 5 08:42:04 thor teamd_myteam0[5549]: <ifinfo_list>
Jan 5 08:42:04 thor teamd_myteam0[5549]: 4: myteam0: ae:e7:26:5e:8c:99: 0
Jan 5 08:42:04 thor teamd_myteam0[5549]: </ifinfo_list>
Jan 5 08:42:04 thor teamd_myteam0[5549]: <port_list>
Jan 5 08:42:04 thor teamd_myteam0[5549]: *2: eth0: up 100Mbit FD
Jan 5 08:42:04 thor teamd_myteam0[5549]: </port_list>
Jan 5 08:42:04 thor teamd_myteam0[5549]: eth0: Got link watch from port config.
Jan 5 08:42:04 thor teamd_myteam0[5549]: eth0: Using sticky "0".
Jan 5 08:42:04 thor teamd_myteam0[5549]: eth0: Failed to set port
hardware address.
Jan 5 08:42:04 thor teamd_myteam0[5549]: Failed to init port priv.
Jan 5 08:42:04 thor teamd_myteam0[5549]: Callback named
"lw_ethtool_delay" not found.
Jan 5 08:42:04 thor teamd_myteam0[5549]: Loop callback failed with:
Device or resource busy
Jan 5 08:42:04 thor teamd_myteam0[5549]: Failed loop callback:
libteam_events, 0x22073c0
Jan 5 08:42:04 thor teamd_myteam0[5549]: <ifinfo_list>
Jan 5 08:42:04 thor teamd_myteam0[5549]: 4: myteam0: ae:e7:26:5e:8c:99: 0
Jan 5 08:42:04 thor teamd_myteam0[5549]: 2: eth0: 50:e5:49:ec:d6:3f: 4
Jan 5 08:42:04 thor teamd_myteam0[5549]: </ifinfo_list>
Jan 5 08:42:04 thor teamd_myteam0[5549]: <port_list>
Jan 5 08:42:04 thor teamd_myteam0[5549]: *3: eth1: down 0Mbit HD
Jan 5 08:42:04 thor teamd_myteam0[5549]: 2: eth0: up 100Mbit FD
Jan 5 08:42:04 thor teamd_myteam0[5549]: </port_list>
Jan 5 08:42:04 thor teamd_myteam0[5549]: eth1: Got link watch from port config.
Jan 5 08:42:04 thor teamd_myteam0[5549]: eth1: Using sticky "0".
Jan 5 08:42:04 thor teamd_myteam0[5549]: Added loop callback:
lw_ethtool_delay, 0x220cfc0
Jan 5 08:42:04 thor teamd_myteam0[5549]: eth0: Got link watch from port config.
Jan 5 08:42:04 thor teamd_myteam0[5549]: eth0: Current user link
state is "down".
Jan 5 08:42:04 thor teamd_myteam0[5549]: eth0: Using sticky "0".
Jan 5 08:42:04 thor teamd_myteam0[5549]: eth0: Failed to set port
hardware address.
Jan 5 08:42:04 thor teamd_myteam0[5549]: Failed to init port priv.
Jan 5 08:42:04 thor teamd_myteam0[5549]: Callback named
"lw_ethtool_delay" not found.
Jan 5 08:42:04 thor teamd_myteam0[5549]: Loop callback failed with:
Device or resource busy
Jan 5 08:42:04 thor teamd_myteam0[5549]: Failed loop callback:
libteam_events, 0x22073c0
Jan 5 08:42:04 thor teamd_myteam0[5549]: <ifinfo_list>
Jan 5 08:42:04 thor teamd_myteam0[5549]: *4: myteam0: *e8:de:27:06:85:d5: 0
Jan 5 08:42:04 thor teamd_myteam0[5549]: 3: eth1: e8:de:27:06:85:d5: 4
Jan 5 08:42:04 thor teamd_myteam0[5549]: 2: eth0: 50:e5:49:ec:d6:3f: 4
Jan 5 08:42:04 thor teamd_myteam0[5549]: </ifinfo_list>
Jan 5 08:42:06 thor kernel: [ 197.136967] r8169 0000:04:00.0 eth1: link up
Jan 5 08:42:06 thor teamd_myteam0[5549]: <port_list>
Jan 5 08:42:06 thor teamd_myteam0[5549]: *3: eth1: up 100Mbit FD
Jan 5 08:42:06 thor teamd_myteam0[5549]: 2: eth0: up 100Mbit FD
Jan 5 08:42:06 thor teamd_myteam0[5549]: </port_list>
Jan 5 08:42:06 thor teamd_myteam0[5549]: eth1: ethtool-link went up.
Jan 5 08:42:06 thor teamd_myteam0[5549]: Found best port: "eth1"
(ifindex "3", prio "0").
Jan 5 08:42:06 thor teamd_myteam0[5549]: Changed active port to "eth1".
Jan 5 08:42:06 thor teamd_myteam0[5549]: eth0: Got link watch from port config.
Jan 5 08:42:06 thor teamd_myteam0[5549]: eth0: Current user link
state is "down".
Jan 5 08:42:06 thor teamd_myteam0[5549]: eth0: Using sticky "0".
Jan 5 08:42:06 thor teamd_myteam0[5549]: eth0: Failed to set port
hardware address.
Jan 5 08:42:06 thor teamd_myteam0[5549]: Failed to init port priv.
Jan 5 08:42:06 thor teamd_myteam0[5549]: Current active port: "eth1"
(ifindex "3", prio "0").
Jan 5 08:42:06 thor teamd_myteam0[5549]: Callback named
"lw_ethtool_delay" not found.
Jan 5 08:42:06 thor teamd_myteam0[5549]: Loop callback failed with:
Device or resource busy
Jan 5 08:42:06 thor teamd_myteam0[5549]: Failed loop callback:
libteam_events, 0x22073c0
Jan 5 08:42:06 thor teamd_myteam0[5549]: Current active port: "eth1"
(ifindex "3", prio "0").
-----------------------------------
syslog after running "ip addr add 192.168.0.101/24 dev myteam0 \n ip
link set myteam0 up"
Jan 5 08:45:47 thor avahi-daemon[3691]: Joining mDNS multicast group
on interface myteam0.IPv4 with address 192.168.0.101.
Jan 5 08:45:47 thor avahi-daemon[3691]: New relevant interface
myteam0.IPv4 for mDNS.
Jan 5 08:45:47 thor avahi-daemon[3691]: Registering new address
record for 192.168.0.101 on myteam0.IPv4.
Jan 5 08:45:49 thor ntpd[3890]: Listen normally on 2 myteam0
192.168.0.101 UDP 123
Jan 5 08:45:49 thor ntpd[3890]: peers refreshed
-----------------------------------
# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 myteam0
-----------------------------------
# ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
mode DEFAULT group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
master myteam0 state UP mode DEFAULT group default qlen 1000
link/ether 50:e5:49:ec:d6:3f brd ff:ff:ff:ff:ff:ff
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
master myteam0 state UP mode DEFAULT group default qlen 1000
link/ether e8:de:27:06:85:d5 brd ff:ff:ff:ff:ff:ff
4: myteam0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue
state UP mode DEFAULT group default
link/ether e8:de:27:06:85:d5 brd ff:ff:ff:ff:ff:ff
-----------------------------------
# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
master myteam0 state UP group default qlen 1000
link/ether 50:e5:49:ec:d6:3f brd ff:ff:ff:ff:ff:ff
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
master myteam0 state UP group default qlen 1000
link/ether e8:de:27:06:85:d5 brd ff:ff:ff:ff:ff:ff
4: myteam0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue
state UP group default
link/ether e8:de:27:06:85:d5 brd ff:ff:ff:ff:ff:ff
inet 192.168.0.101/24 scope global myteam0
valid_lft forever preferred_lft forever
-----------------------------------
# teamdctl myteam0 config dump
{
"device": "myteam0",
"mcast_rejoin": {
"count": 1
},
"notify_peers": {
"count": 1
},
"ports": {
"eth0": {
"link_watch": {
"name": "ethtool"
}
},
"eth1": {
"link_watch": {
"name": "ethtool"
}
}
},
"runner": {
"name": "activebackup"
}
}
-----------------------------------
# teamdctl myteam0 state view
setup:
runner: activebackup
ports:
eth1
link watches:
link summary: up
instance[link_watch_0]:
name: ethtool
link: up
runner:
active port: eth1
On Mon, Jan 5, 2015 at 7:50 AM, Flavio Leitner <fbl(a)sysclose.org> wrote:
On Sunday, January 04, 2015 06:03:26 PM PanaColina wrote:
> Setting up the team driver on Debian Sid seems straight forward, and
> the links seem to go up without error, but I cannot ping my router IP
> address or otherwise connect outside the box. I am no expert in
> networking, and am guessing the error may be obvious to someone on the
> list, or someone might be able to point me in the right direction to
> search for a solution.
>
> To me, it seems this may be a gateway issue as, after setting up the
> team driver, route -n gives:
>
> Destination Gateway Genmask Flags Metric Ref
> Use Iface
> 192.168.0.0 0.0.0.0 255.255.255.0 U 0 0
> 0 myteam0
>
> If I set the ip address of the router connected to the nic on eth0 as
> the gateway, route -n gives:
>
> Destination Gateway Genmask Flags Metric Ref
> Use Iface
> 0.0.0.0 192.168.0.1 0.0.0.0 UG 0 0
> 0 myteam0
> 192.168.0.0 0.0.0.0 255.255.255.0 U 0 0
> 0 myteam0
>
> But pinging 192.168.0.1 results in "Destination Host Unreachable". If
> I try setting a default gateway using myteam0 or eth0, the route
> command returns "Unknown host".
>
> After my initial day of failures, I commented out the eth0 and eth1
> stanzas in the /etc/network/interfaces file and purged network-manager
> to avoid potential problems. The original configuration has the router
> connected to eth0 set the ip address of eth0 as 192.168.0.101 through
> DHCP.
>
> I tested initially with the Debian Sid libteam packages (v.12) and
> then built v.15 from libteam-master.zip source. I have done most of my
> testing with the basic commands:
>
> teamd -g -t myteam0 -d
> teamdctl myteam0 port add eth0
> teamdctl myteam0 port add eth1
> ip addr add 192.168.0.101/24 dev myteam0
> ip link set myteam0 up
>
> Before running the above commands to start teaming, ip link shows:
>
> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
> mode DEFAULT group default
> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> 2: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode
> DEFAULT group default qlen 1000
> link/ether 50:e5:49:ec:d6:3f brd ff:ff:ff:ff:ff:ff
> 3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode
> DEFAULT group default qlen 1000
> link/ether e8:de:27:06:85:d5 brd ff:ff:ff:ff:ff:ff
>
> After running the teaming commands, ip link shows:
>
> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
> mode DEFAULT group default
> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
> master myteam0 state UP mode DEFAULT group default qlen 1000
> link/ether 9e:a4:72:48:1d:f7 brd ff:ff:ff:ff:ff:ff
> 3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
> master myteam0 state UP mode DEFAULT group default qlen 1000
> link/ether 50:e5:49:ec:d6:3f brd ff:ff:ff:ff:ff:ff
> 4: myteam0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue
> state UP mode DEFAULT group default
> link/ether 50:e5:49:ec:d6:3f brd ff:ff:ff:ff:ff:ff
>
> and ip addr shows:
> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
> group default
> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> inet 127.0.0.1/8 scope host lo
> valid_lft forever preferred_lft forever
> 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
> master myteam0 state UP group default qlen 1000
> link/ether 9e:a4:72:48:1d:f7 brd ff:ff:ff:ff:ff:ff
> 3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
> master myteam0 state UP group default qlen 1000
> link/ether 50:e5:49:ec:d6:3f brd ff:ff:ff:ff:ff:ff
> 4: myteam0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue
> state UP group default
> link/ether 50:e5:49:ec:d6:3f brd ff:ff:ff:ff:ff:ff
> inet 192.168.0.101/24 scope global myteam0
> valid_lft forever preferred_lft forever
>
> I have looked at syslog and see no errors or warnings. It seems
> everything is fine as syslog shows:
> Jan 4 17:09:56 thor avahi-daemon[3647]: Joining mDNS multicast
> group on interface myteam0.IPv4 with address 192.168.0.101.
> Jan 4 17:09:56 thor avahi-daemon[3647]: New relevant interface
> myteam0.IPv4 for mDNS.
> Jan 4 17:09:56 thor avahi-daemon[3647]: Registering new address
> record for 192.168.0.101 on myteam0.IPv4.
> Jan 4 17:09:57 thor ntpd[3708]: Listen normally on 2 myteam0
> 192.168.0.101 UDP 123
>
>
> teamdctl myteam0 config dump
> {
> "device": "myteam0",
> "ports": {
> "eth0": {
> "link_watch": {
> "name": "ethtool"
> }
> },
> "eth1": {
> "link_watch": {
> "name": "ethtool"
> }
> }
> },
> "runner": {
> "name": "roundrobin"
> }
> }
Could you try 'activebackup' instead of 'roundrobin'? Active-Backup is
more simple
and more likely to work. If that works out, we know there is something related to
roundrobin.
Thanks
fbl
>
> teamdctl myteam0 state view
> setup:
> runner: roundrobin
> ports:
> eth1
> link watches:
> link summary: up
> instance[link_watch_0]:
> name: ethtool
> link: up
> eth0
> link watches:
> link summary: up
> instance[link_watch_0]:
> name: ethtool
> link: up
>
>
> I am running kernel 3.18.1 x86_64 with the .config:
> CONFIG_NET_TEAM=y
> CONFIG_NET_TEAM_MODE_BROADCAST=m
> CONFIG_NET_TEAM_MODE_ROUNDROBIN=m
> CONFIG_NET_TEAM_MODE_RANDOM=m
> CONFIG_NET_TEAM_MODE_ACTIVEBACKUP=m
> CONFIG_NET_TEAM_MODE_LOADBALANCE=m
>
> Any suggestions appreciated,
>
> J.L. Hill
> _______________________________________________
> libteam mailing list
> libteam(a)lists.fedorahosted.org
> https://lists.fedorahosted.org/mailman/listinfo/libteam
>
11:14 a.m.
On Monday, January 05, 2015 10:24:13 AM PanaColina wrote:
Thank you for your response -- testing with activebackup pointed
towards one problem:
Jan 5 08:42:04 thor teamd_myteam0[5549]: eth0: Got link watch from port config.
Jan 5 08:42:04 thor teamd_myteam0[5549]: eth0: Using sticky "0".
Jan 5 08:42:04 thor teamd_myteam0[5549]: eth0: Failed to set port
hardware address.
Either roundrobin or activebackup modes requires changing the HW
address for all ports. If that fails, the mode doesn't work.
It seems both your ports don't support that, unfortunately.
fbl
12:15 p.m.
Thank you again. Unfortunately, it seems I am misunderstanding.
When you say that both of my ports do not support changing the HW
address, I assume that means my NICs do not allow their MAC addresses
to be changed. However, it seems I can change their addresses via the
ip command with no problem (see below).
I guess I need details on what NIC card requirements teamd has. I can
buy new cards, if I know what I'm looking for.
Thank you for your patience,
J.L. Hill
---------------------
# ip add ls eth0
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
state UP group default qlen 1000
link/ether 50:e5:49:ec:d6:3f brd ff:ff:ff:ff:ff:ff
inet 192.168.0.101/24 brd 192.168.0.255 scope global eth0
valid_lft forever preferred_lft forever
# ifdown eth0
Killed old client process
...
Listening on LPF/eth0/50:e5:49:ec:d6:3f
Sending on LPF/eth0/50:e5:49:ec:d6:3f
Sending on Socket/fallback
DHCPRELEASE on eth0 to 192.168.0.1 port 67
# ip link set eth0 address 02:01:02:03:04:08
# ip link ls eth0
2: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast state DOWN
mode DEFAULT group default qlen 1000
link/ether 02:01:02:03:04:08 brd ff:ff:ff:ff:ff:ff
root@thor:/home/jh# ip addr ls eth0
2: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast state DOWN
group default qlen 1000
link/ether 02:01:02:03:04:08 brd ff:ff:ff:ff:ff:ff
On Mon, Jan 5, 2015 at 12:14 PM, Flavio Leitner <fbl(a)sysclose.org> wrote:
On Monday, January 05, 2015 10:24:13 AM PanaColina wrote:
> Thank you for your response -- testing with activebackup pointed
> towards one problem:
>
> Jan 5 08:42:04 thor teamd_myteam0[5549]: eth0: Got link watch from port config.
> Jan 5 08:42:04 thor teamd_myteam0[5549]: eth0: Using sticky "0".
> Jan 5 08:42:04 thor teamd_myteam0[5549]: eth0: Failed to set port
> hardware address.
Either roundrobin or activebackup modes requires changing the HW
address for all ports. If that fails, the mode doesn't work.
It seems both your ports don't support that, unfortunately.
fbl
12:44 p.m.
On Monday, January 05, 2015 01:15:06 PM PanaColina wrote:
Thank you again. Unfortunately, it seems I am misunderstanding.
When you say that both of my ports do not support changing the HW
address, I assume that means my NICs do not allow their MAC addresses
to be changed. However, it seems I can change their addresses via the
ip command with no problem (see below).
I guess I need details on what NIC card requirements teamd has. I can
buy new cards, if I know what I'm looking for.
teamd should be able to change HW too.
Could you put somewhere the output of strace command?
# strace -f -s 1024 -o /tmp/teamd.log -p <pid of teamd>
Run that command and then:
# teamdctl myteam0 port add eth0
after that stop the strace with ctrl+c and you should have
the /tmp/teamd.log with traces inside.
That could give us a clue.
fbl
Thank you for your patience,
J.L. Hill
---------------------
# ip add ls eth0
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
state UP group default qlen 1000
link/ether 50:e5:49:ec:d6:3f brd ff:ff:ff:ff:ff:ff
inet 192.168.0.101/24 brd 192.168.0.255 scope global eth0
valid_lft forever preferred_lft forever
# ifdown eth0
Killed old client process
...
Listening on LPF/eth0/50:e5:49:ec:d6:3f
Sending on LPF/eth0/50:e5:49:ec:d6:3f
Sending on Socket/fallback
DHCPRELEASE on eth0 to 192.168.0.1 port 67
# ip link set eth0 address 02:01:02:03:04:08
# ip link ls eth0
2: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast state DOWN
mode DEFAULT group default qlen 1000
link/ether 02:01:02:03:04:08 brd ff:ff:ff:ff:ff:ff
root@thor:/home/jh# ip addr ls eth0
2: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast state DOWN
group default qlen 1000
link/ether 02:01:02:03:04:08 brd ff:ff:ff:ff:ff:ff
On Mon, Jan 5, 2015 at 12:14 PM, Flavio Leitner <fbl(a)sysclose.org> wrote:
> On Monday, January 05, 2015 10:24:13 AM PanaColina wrote:
>> Thank you for your response -- testing with activebackup pointed
>> towards one problem:
>>
>> Jan 5 08:42:04 thor teamd_myteam0[5549]: eth0: Got link watch from port
config.
>> Jan 5 08:42:04 thor teamd_myteam0[5549]: eth0: Using sticky "0".
>> Jan 5 08:42:04 thor teamd_myteam0[5549]: eth0: Failed to set port
>> hardware address.
>
> Either roundrobin or activebackup modes requires changing the HW
> address for all ports. If that fails, the mode doesn't work.
>
> It seems both your ports don't support that, unfortunately.
>
> fbl
1:52 p.m.
Okay, I believe I did the strace correctly. Log file attached.
Again, I very much appreciate the assistance,
J.L. Hill
On Mon, Jan 5, 2015 at 1:44 PM, Flavio Leitner <fbl(a)sysclose.org> wrote:
On Monday, January 05, 2015 01:15:06 PM PanaColina wrote:
> Thank you again. Unfortunately, it seems I am misunderstanding.
>
> When you say that both of my ports do not support changing the HW
> address, I assume that means my NICs do not allow their MAC addresses
> to be changed. However, it seems I can change their addresses via the
> ip command with no problem (see below).
>
> I guess I need details on what NIC card requirements teamd has. I can
> buy new cards, if I know what I'm looking for.
teamd should be able to change HW too.
Could you put somewhere the output of strace command?
# strace -f -s 1024 -o /tmp/teamd.log -p <pid of teamd>
Run that command and then:
# teamdctl myteam0 port add eth0
after that stop the strace with ctrl+c and you should have
the /tmp/teamd.log with traces inside.
That could give us a clue.
fbl
> Thank you for your patience,
>
> J.L. Hill
> ---------------------
>
> # ip add ls eth0
> 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
> state UP group default qlen 1000
> link/ether 50:e5:49:ec:d6:3f brd ff:ff:ff:ff:ff:ff
> inet 192.168.0.101/24 brd 192.168.0.255 scope global eth0
> valid_lft forever preferred_lft forever
>
> # ifdown eth0
> Killed old client process
> ...
> Listening on LPF/eth0/50:e5:49:ec:d6:3f
> Sending on LPF/eth0/50:e5:49:ec:d6:3f
> Sending on Socket/fallback
> DHCPRELEASE on eth0 to 192.168.0.1 port 67
>
> # ip link set eth0 address 02:01:02:03:04:08
> # ip link ls eth0
> 2: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast state DOWN
> mode DEFAULT group default qlen 1000
> link/ether 02:01:02:03:04:08 brd ff:ff:ff:ff:ff:ff
> root@thor:/home/jh# ip addr ls eth0
> 2: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast state DOWN
> group default qlen 1000
> link/ether 02:01:02:03:04:08 brd ff:ff:ff:ff:ff:ff
>
> On Mon, Jan 5, 2015 at 12:14 PM, Flavio Leitner <fbl(a)sysclose.org> wrote:
> > On Monday, January 05, 2015 10:24:13 AM PanaColina wrote:
> >> Thank you for your response -- testing with activebackup pointed
> >> towards one problem:
> >>
> >> Jan 5 08:42:04 thor teamd_myteam0[5549]: eth0: Got link watch from port
config.
> >> Jan 5 08:42:04 thor teamd_myteam0[5549]: eth0: Using sticky "0".
> >> Jan 5 08:42:04 thor teamd_myteam0[5549]: eth0: Failed to set port
> >> hardware address.
> >
> > Either roundrobin or activebackup modes requires changing the HW
> > address for all ports. If that fails, the mode doesn't work.
> >
> > It seems both your ports don't support that, unfortunately.
> >
> > fbl
3398
days inactive
3399
days old
libteam@lists.fedorahosted.org
6 comments
2 participants
participants (2)
-
Flavio Leitner -
PanaColina