You are not logged in.
I have spent the day trying to get IPv6 internet connectivity working in Arch and Im failing. No matter what I do my Arch install just isnt receiving and ipv6 temp address. If I use the exact same system but boot into another OS i automatically get an IPv6 temp address and can ping 1pv6.google.com .
If there is anything that might prevent this networking function from working Id appreciate to know what it could be. Thanks a lot.
Registered: 2007-05-05
Keep coming back to Arch because its hands down the most amazing distro God has given us.
Offline
Are you using WICD or Network Manager or ifup?
Offline
I use net profiles and have a profile for my bridge.
INTERFACE="br0"
CONNECTION="bridge"
DESCRIPTION="Gigabit Bridge"
PRE_UP="ip link set dev eth0 promisc on"
BRIDGE_INTERFACES="eth0"
IP="static"
IP6="stateless"
ADDR='192.168.11.66'
GATEWAY='192.168.11.1'
DNS=('8.8.8.8')
Registered: 2007-05-05
Keep coming back to Arch because its hands down the most amazing distro God has given us.
Offline
Just to give it a shot I reconfigured my networking to go via network-manager and that didnt help. So i went back to netcfg
Registered: 2007-05-05
Keep coming back to Arch because its hands down the most amazing distro God has given us.
Offline
I just cleared my iptables, that didnt seem to help either
Registered: 2007-05-05
Keep coming back to Arch because its hands down the most amazing distro God has given us.
Offline
I wont consider this solved until auto config works but in the mean time I have an ugly work around. I created a profile for eth0 to come up at 0.0.0.0 and I got static ipv6 working in my bridge like this
INTERFACE="br0"
CONNECTION="bridge"
DESCRIPTION="Gigabit Bridge"
POST_UP="ip -6 route add default via fe80::c851:85ff:fed0:e71f dev br0"
BRIDGE_INTERFACES="eth0"
IP="dhcp"
IP6="static"
ADDR6=(2001:470:1f07:be8:bd9a:b66d:248a:b866/64)
Gateway6=fe80::c851:85ff:fed0:e71f
ADDR='192.168.11.66'
#ROUTES=('192.168.0.0/24 via 192.168.1.2')
#GATEWAY='192.168.11.1'
#DNS=('8.8.8.8')
Registered: 2007-05-05
Keep coming back to Arch because its hands down the most amazing distro God has given us.
Offline
What's the reason for using a bridge?, never seen ipv6 autoconf play well with bridges in the past.
Hurricane Electric Certified IPv6 Sage
CPU: Core i7-2600 @ 4.0Ghz | RAM: 16GB (4x4GB) | GFX: AMD Radeon R9 290 4096MB VRAM | HDD: 1x 120GB SATA3 Corsair SSD (~500MB/s RW), 1x SATA2 250GB, 1x SATA2 320GB, 1x 180GB SATA3 Intel SSD
*EDIT* Replaced Nvidia GTX 570 for a AMD Radeon R9 290, and added an extra SSD 180GB
Offline
What's the reason for using a bridge?, never seen ipv6 autoconf play well with bridges in the past.
I use a bridge to allow my KVM virtual servers to connect to the network. I know the bridge isn't the issue, its got to be arch. I have tried it directly with eth0 and have the same problem, also all of my VMs that run off that bridge receive ipv6 autoconf.
Registered: 2007-05-05
Keep coming back to Arch because its hands down the most amazing distro God has given us.
Offline
no an easy one to solve is it? I bet its some kind of kernel setting but i feel like ive looked at them all, can t hey be set to defaults?
Registered: 2007-05-05
Keep coming back to Arch because its hands down the most amazing distro God has given us.
Offline
I had the same problem and was also stumped until I remembered that activating forwarding (e.g. net/ipv6/conf/all/forwarding) disables the stateless attribution of IPv6, as well as the temporary addresses. Since this forwarding mode is (only?) used by routers, bridged interface should not need it.
Offline
Are you sure the other OS you're testing is not getting assigned a tunneled (Windows does this) or stateless address?
Offline