All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
SyS - IPv6 - Setup Help
Running Centos7... Seems IPv6 is not configured by default on SoYouStart - ISO install.
I tried following instructions at https://docs.ovh.com/gb/en/dedicated/network-ipv6/
But, I am getting errors while restarting network service. Please help.
[root@server network-scripts]# ifconfig | cut -c1-7| sort -u| awk -F : '{print $1}'
eth0
eth1
eth2
eth3
lo
[root@server network-scripts]# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
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
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
link/ether 0c:c4:7a:c4:19:a6 brd ff:ff:ff:ff:ff:ff
3: eth1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
link/ether 0c:c4:7a:c4:19:a7 brd ff:ff:ff:ff:ff:ff
4: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 0c:c4:7a:c4:1e:ce brd ff:ff:ff:ff:ff:ff
inet 51.38.XX.YY/24 brd 51.38.XX.255 scope global noprefixroute dynamic eth2
valid_lft 69616sec preferred_lft 69616sec
inet6 fe80::ec4:7aff:fec4:1ece/64 scope link
valid_lft forever preferred_lft forever
5: eth3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 0c:c4:7a:c4:1e:cf brd ff:ff:ff:ff:ff:ff
/etc/sysconfig/network-scripts contains:
ifcfg-eth0 ifdown ifdown-ippp ifdown-post ifdown-sit ifdown-tunnel ifup-bnep ifup-ipv6 ifup-plusb ifup-routes ifup-TeamPort init.ipv6-global
ifcfg-eth2 ifdown-bnep ifdown-ipv6 ifdown-ppp ifdown-Team ifup ifup-eth ifup-isdn ifup-post ifup-sit ifup-tunnel network-functions
ifcfg-lo ifdown-eth ifdown-isdn ifdown-routes ifdown-TeamPort ifup-aliases ifup-ippp ifup-plip ifup-ppp ifup-Team ifup-wireless network-functions-ipv6
**Beats me - If eth2 and eth3 are valid interfaces, why is the file not created correctly?
**
I added IPV6 config data manually at:
[root@server network-scripts]# cat ifcfg-eth2
# Created by cloud-init on instance boot automatically, do not edit.
#
BOOTPROTO=dhcp
DEVICE=eth2
HWADDR=0c:c4:7a:c4:1e:ce
ONBOOT=yes
STARTMODE=auto
TYPE=Ethernet
USERCTL=no
IPV6INIT=yes
IPV6_AUTOCONF=no
IPV6_DEFROUTE=yes
IPV6_FAILURE_FATAL=no
IPV6ADDR=2001:41d0:JJJ:QQQQ::/64
IPV6_DEFAULTGW=2001:41d0:JJJ:6FF:FF:FF:FF:FF
[root@server network-scripts]# systemctl restart network.service
Job for network.service failed because the control process exited with error code. See "systemctl status network.service" and "journalctl -xe" for details.
systemctl status network.service gives:
● network.service - LSB: Bring up/down networking
Loaded: loaded (/etc/rc.d/init.d/network; bad; vendor preset: disabled)
Active: failed (Result: exit-code) since Thu 2021-12-23 19:43:49 UTC; 4min 18s ago
Docs: man:systemd-sysv-generator(8)
Process: 5341 ExecStart=/etc/rc.d/init.d/network start (code=exited, status=1/FAILURE)
Dec 23 19:43:49 server network[5341]: RTNETLINK answers: File exists
Dec 23 19:43:49 server network[5341]: RTNETLINK answers: File exists
Dec 23 19:43:49 server network[5341]: RTNETLINK answers: File exists
Dec 23 19:43:49 server network[5341]: RTNETLINK answers: File exists
Dec 23 19:43:49 server network[5341]: RTNETLINK answers: File exists
Dec 23 19:43:49 server network[5341]: RTNETLINK answers: File exists
Dec 23 19:43:49 server systemd[1]: network.service: control process exited, code=exited status=1
Dec 23 19:43:49 server systemd[1]: Failed to start LSB: Bring up/down networking.
Dec 23 19:43:49 server systemd[1]: Unit network.service entered failed state.
Dec 23 19:43:49 server systemd[1]: network.service failed.
Comments
Delete ifcfg-eth0 and reboot. Eth2 appears to be your plugged in nic.
server is rebooting now - q
How come eth3 is UP/ active?
5: eth3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000deleted - still no luck. Any other things I can check?
Beats me - why eth2 has the fe80 address along with the assigned IPv6
and can I use eth3? It seems to be up/ running...
In OVH the ipv6 gateway is outside of your /64 so you either need to declare your ipv6 with a /56 or create a static route to the gateway, like this: https://serverfault.com/a/912353
Dunno how that works as the official guide from OVH says /64 is all good. Plus, the example you shared - I feel is for guest OK.. Here, this is my only OS
That will work for the main OS as well, it's the same thing. Try the /56 if you don't want to create a route.
I don't know,what did you buy?
its Sys-2-sata... not sure how to utilize both... or can I even use both if it shows UP?
I don't know what that is, what does your order say?
SYS-2-SAT-32
There's a second adapter detected on all the SYS-xxx I've tested. I don't know why. Only the first adapter works, so just use eth2. I wonder if the second one is shared with IPMI or something.
Back to ipv6, below is how my SYS-1-SAT-32 is setup with the official Ubuntu image from OVH (not installed via IPMI). As you can see, OVH sets it up with a /56 on their own image, and the second adapter does nothing.
I still think seting it up with a /64 and creating a default route to the gateway is a cleaner solution.