# RancherOS ISO - no external network **URL:** \ **Category:** RancherOS\ **Created:** [June 12, 2016, 12:33pm UTC](https://forums.suse.com/t/rancheros-iso-no-external-network/3097 "2016-06-12T12:33:26Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![PaulCharlton](https://avatars.discourse-cdn.com/v4/letter/p/ee59a6/32.png) [@PaulCharlton](https://forums.suse.com/u/PaulCharlton)\ **Post date:** [June 12, 2016, 12:33pm UTC](https://forums.suse.com/t/rancheros-iso-no-external-network/3097/1 "2016-06-12T12:33:26Z")
I have a n00b question for rancherOS — in particular uname -a “Linux rancher 4.2.8-ckt-rancher #1 SMP …” – when booting from ISO image on a VPS, it is not binding to any IPV4 address on eth0. the IPV6 address is assigned on eth0. As a consequence, the default install to hard disk “ros install” does not work because there is no network available on ipv4 one clue is that the logs are showing a duplicate ipv6 address with dhcpcd … after which the log shows a disabling the IF without showing that it is trying to obtain an ipv4 address. The VPS is running on QEMU. ---
**Author:** ![PaulCharlton](https://avatars.discourse-cdn.com/v4/letter/p/ee59a6/32.png) [@PaulCharlton](https://forums.suse.com/u/PaulCharlton)\ **Post date:** [June 12, 2016, 1:01pm UTC](https://forums.suse.com/t/rancheros-iso-no-external-network/3097/2 "2016-06-12T13:01:08Z")
after asking my hosting provider for the fixed IP for the VPS, the following incantation works: sudo ros config set rancher.network.interfaces.eth1.address "[93.xxx.xxx.xxx/24”](http://93.xxx.xxx.xxx/24%E2%80%9D) sudo ros config set rancher.network.interfaces.eth1.gateway "93.xxx.xxx.1" sudo system-docker restart network ================================== this points at a solution to the problem, but is not a solution in and of itself since it does not scale for vagrant or other automated deployment. I am imagining that the issue is that the rancherOS DHCPCD is giving up when it notices the duplicate ipv6, and as a consequence is not trying to locate the ipv4 DHCP information. 1. yes, I can ask my hosting provider to investigate the duplicate IPv6 2. rancherOS DHCPCD should be changed to continue looking for the ipv4 binding ---
**Author:** ![PaulCharlton](https://avatars.discourse-cdn.com/v4/letter/p/ee59a6/32.png) [@PaulCharlton](https://forums.suse.com/u/PaulCharlton)\ **Post date:** [June 12, 2016, 1:42pm UTC](https://forums.suse.com/t/rancheros-iso-no-external-network/3097/3 "2016-06-12T13:42:47Z")
logs: Jun 12 03:05:12 rancher kernel: [13.841919] device vethcfd4865 entered promiscuous mode Jun 12 03:05:12 rancher kernel: [13.842080] IPv6: ADDRCONF(NETDEV\_UP): vethcfd4865: link is not ready Jun 12 03:05:12 rancher kernel: [13.842083] docker-sys: port 1(vethcfd4865) entered forwarding state Jun 12 03:05:12 rancher kernel: [13.842088] docker-sys: port 1(vethcfd4865) entered forwarding state Jun 12 03:05:12 rancher kernel: [13.861409] eth0: renamed from veth5e922b9 Jun 12 03:05:12 rancher kernel: [13.868240] IPv6: ADDRCONF(NETDEV\_CHANGE): vethcfd4865: link becomes ready Jun 12 03:05:12 rancher dhcpcd[656]: eth0: waiting for carrier Jun 12 03:05:12 rancher dhcpcd[656]: eth0: carrier acquired Jun 12 03:05:12 rancher dhcpcd[656]: DUID 00:01:00:01:1e:ef:8d:e8:52:54:5d:5f:e3:9b Jun 12 03:05:12 rancher dhcpcd[656]: eth0: IAID 5d:5f:e3:9b Jun 12 03:05:13 rancher dhcpcd[656]: eth0: soliciting a DHCP lease Jun 12 03:05:13 rancher kernel: [14.497270] IPv6: eth0: IPv6 duplicate address fe80::42:acff:fe12:1 detected! Jun 12 03:05:27 rancher kernel: [28.896229] docker-sys: port 1(vethcfd4865) entered forwarding state Jun 12 03:05:42 rancher dhcpcd[656]: timed out Jun 12 03:05:42 rancher dhcpcd[656]: forked to background, child pid 694 Jun 12 03:05:42 rancher kernel: [43.975234] veth5e922b9: renamed from eth0 Jun 12 03:05:42 rancher kernel: [43.987534] docker-sys: port 1(vethcfd4865) entered disabled state Jun 12 03:05:42 rancher kernel: [43.988538] docker-sys: port 1(vethcfd4865) entered disabled state Jun 12 03:05:42 rancher kernel: [43.989156] device vethcfd4865 left promiscuous mode Jun 12 03:05:42 rancher kernel: [43.989161] docker-sys: port 1(vethcfd4865) entered disabled state Jun 12 03:05:43 rancher kernel: [44.608626] 9pnet\_virtio: no channels available Jun 12 03:05:43 rancher kernel: [45.011088] device veth640bc57 entered promiscuous mode Jun 12 03:05:43 rancher kernel: [45.011511] IPv6: ADDRCONF(NETDEV\_UP): veth640bc57: link is not ready Jun 12 03:05:43 rancher kernel: [45.011521] docker-sys: port 1(veth640bc57) entered forwarding state Jun 12 03:05:43 rancher kernel: [45.011557] docker-sys: port 1(veth640bc57) entered forwarding state Jun 12 03:05:43 rancher kernel: [45.011695] docker-sys: port 1(veth640bc57) entered disabled state Jun 12 03:05:43 rancher kernel: [45.040925] eth0: renamed from vethd61b1ba Jun 12 03:05:43 rancher kernel: [45.047296] IPv6: ADDRCONF(NETDEV\_CHANGE): veth640bc57: link becomes ready Jun 12 03:05:43 rancher kernel: [45.047331] docker-sys: port 1(veth640bc57) entered forwarding state Jun 12 03:05:43 rancher kernel: [45.047340] docker-sys: port 1(veth640bc57) entered forwarding state Jun 12 03:05:44 rancher dhcpcd[762]: control\_open: Connection refused Jun 12 03:05:44 rancher dhcpcd[762]: DUID 00:01:00:01:1e:ef:8e:08:52:54:5d:5f:e3:9b Jun 12 03:05:44 rancher dhcpcd[762]: eth0: IAID 5d:5f:e3:9b Jun 12 03:05:44 rancher dhcpcd[762]: eth0: soliciting a DHCP lease Jun 12 03:05:44 rancher kernel: [45.612200] IPv6: eth0: IPv6 duplicate address fe80::42:acff:fe12:1 detected! Jun 12 03:05:58 rancher kernel: [60.064082] docker-sys: port 1(veth640bc57) entered forwarding state Jun 12 03:06:14 rancher dhcpcd[762]: timed out Jun 12 03:06:14 rancher dhcpcd[762]: forked to background, child pid 786 Jun 12 03:06:14 rancher kernel: [75.192228] vethd61b1ba: renamed from eth0 Jun 12 03:06:14 rancher kernel: [75.197182] docker-sys: port 1(veth640bc57) entered disabled state Jun 12 03:06:14 rancher kernel: [75.207940] docker-sys: port 1(veth640bc57) entered disabled state Jun 12 03:06:14 rancher kernel: [75.208937] device veth640bc57 left promiscuous mode Jun 12 03:06:14 rancher kernel: [75.208942] docker-sys: port 1(veth640bc57) entered disabled state Jun 12 03:06:14 rancher chpasswd: Password for ‘rancher’ changed Jun 12 03:06:14 rancher kernel: [75.529733] device veth0c8435a entered promiscuous mode Jun 12 03:06:14 rancher kernel: [75.529879] IPv6: ADDRCONF(NETDEV\_UP): veth0c8435a: link is not ready Jun 12 03:06:14 rancher kernel: [75.529883] docker-sys: port 1(veth0c8435a) entered forwarding state Jun 12 03:06:14 rancher kernel: [75.529890] docker-sys: port 1(veth0c8435a) entered forwarding state Jun 12 03:06:14 rancher kernel: [75.565508] eth0: renamed from veth8eb6b9b Jun 12 03:06:14 rancher kernel: [75.573287] IPv6: ADDRCONF(NETDEV\_CHANGE): veth0c8435a: link becomes ready Jun 12 03:06:14 rancher kernel: [75.678097] veth8eb6b9b: renamed from eth0 Jun 12 03:06:14 rancher kernel: [75.695261] docker-sys: port 1(veth0c8435a) entered disabled state Jun 12 03:06:14 rancher kernel: [75.695732] device veth0c8435a left promiscuous mode Jun 12 03:06:14 rancher kernel: [75.695745] docker-sys: port 1(veth0c8435a) entered disabled state Jun 12 03:06:16 rancher sshd[1026]: Server listening on 0.0.0.0 port 22. Jun 12 03:06:16 rancher sshd[1026]: Server listening on :: port 22. Jun 12 03:06:18 rancher dhcpcd[786]: docker0: new hardware address: 02:42:29:3a:fa:93 Jun 12 03:06:18 rancher kernel: [79.152764] IPv6: ADDRCONF(NETDEV\_UP): docker0: link is not ready