Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

IPv6 Problem, CentOS 6.8
New on LowEndTalk? Please Register and read our Community Rules.

IPv6 Problem, CentOS 6.8

cheridon561cheridon561 Member
edited June 2016 in Help

Hello, i have been trying to get my IPv6 working on my server but for some reason it's not working, I am not sure what the problem is, could someone maybe take a look at it & tell me what I am doing wrong or what could be the problem. I am running CentOS 6.8. It also seems that I can receice IPv6 pings but I can't ping anything that's IPv6, my server is hosted at OVH.

IPV6ADDR=1111:2222:33:444D::5/64
IPV6_DEFAULTGW=1111:2222:33:44FF:FF:FF:FF:FF

WARN : [ipv6_add_route] 'No route to host' adding route '::/0' via gateway '1234:1234:12:12FF:FF:FF:FF:FF' through device ''

^Every time i do "service network restart" it comes back with that error

Comments

  • rds100rds100 Member
    edited June 2016

    Your ipv6 gateway is not part of the ipv6 subnet on the interface.
    In your example the 4th number must be the same (123X vs 12FF)
    And your gateway is most probably 1234:1234:12:123X::1

    -

  • cheridon561cheridon561 Member
    edited June 2016

    @rds100 said:
    Your ipv6 gateway is not part of the ipv6 subnet on the interface.
    In your example the 4th number must be the same (123X vs 12FF)
    And your gateway is most probably 1234:1234:12:123X::1

    I followed OVH guide for setting the gateway.

  • cheridon561cheridon561 Member
    edited June 2016

    BUMP

  • cheridon561cheridon561 Member
    edited June 2016

    Bump

  • miTgiBmiTgiB Member

    Your gateway is on a different network than your interface.

    Based on the interface address, your gateway needs to be on 1111:2222:33:444D::x/64 While you are listing 1111:2222:33:44FF:FF:FF:FF:FF as you gateway, totally different subnet

    Hostigation High Resource Hosting - SolusVM KVM VPS / Proxmox OpenVZ VPS- Low Cost Comodo SSL Certificates
  • cheridon561cheridon561 Member
    edited June 2016

    @miTgiB said:
    Your gateway is on a different network than your interface.

    Based on the interface address, your gateway needs to be on 1111:2222:33:444D::x/64 While you are listing 1111:2222:33:44FF:FF:FF:FF:FF as you gateway, totally different subnet

    I'm not sure what I'm doing wrong here, I called OVH & four guys from there phone support could not figure out what the problem was, they said eth0 looks about right

  • cheridon561cheridon561 Member
    edited June 2016

    BUMP

  • jtkjtk Member

    @cheridon561 said:
    Well i followed the OVH guide & my gateway should be "2607:5300:61:09FF:FF:FF:FF:FF" but my block is "2607:5300:61:093a::/64"

    Based on that information, the gateway address is not in the same /64 network as your host address. According to that information, your 2607:5300:61:93a::/64 prefix will not contain the gateway's address. The first 64 bits of each are different, they must be the same.

    Often times providers make it easy and set it to the ::1 address of the network. Are you sure your gateway is not 2607:5300:61:93a::1?

    The f's gateway address seems an unlikely choice, especially since it would literally expand to: 2607:5300:0061:09FF:00FF:00FF:00FF:00FF. Most providers will just use ::1 for convenience. You may need to consult your provider to be sure. If you're masking your real addresses to hide them from being published publicly I understand. However, if you are it would help to know precisely what you're using. I'm happy to take a look if you want to PM them to me.

  • @jtk said:

    @cheridon561 said:
    Well i followed the OVH guide & my gateway should be "2607:5300:61:09FF:FF:FF:FF:FF" but my block is "2607:5300:61:093a::/64"

    Based on that information, the gateway address is not in the same /64 network as your host address. According to that information, your 2607:5300:61:93a::/64 prefix will not contain the gateway's address. The first 64 bits of each are different, they must be the same.

    Often times providers make it easy and set it to the ::1 address of the network. Are you sure your gateway is not 2607:5300:61:93a::1?

    The f's gateway address seems an unlikely choice, especially since it would literally expand to: 2607:5300:0061:09FF:00FF:00FF:00FF:00FF. Most providers will just use ::1 for convenience. You may need to consult your provider to be sure. If you're masking your real addresses to hide them from being published publicly I understand. However, if you are it would help to know precisely what you're using. I'm happy to take a look if you want to PM them to me.

    Would it be ok if i add you on Skype?

  • Yes, your gateway is outside your subnet, that's how OVH does it. You'll need to add a static route to the gateway ip. I don't know why the insist on doing it that way, but the do...

  • @joereid said:
    Yes, your gateway is outside your subnet, that's how OVH does it. You'll need to add a static route to the gateway ip. I don't know why the insist on doing it that way, but the do...

    How do i add a static route?

  • joereidjoereid Member
    edited June 2016

    @cheridon561 said:
    How do i add a static route?

    In /etc/sysconfig/network-scripts folder, create (or edit) the file "route6-eth0" and add this:

    2607:5300:0061:09ff:00ff:00ff:00ff:00ff dev eth0
    default via 2607:5300:0061:09ff:00ff:00ff:00ff:00ff
    

    Obviously change the gateway IP to the real one...then reboot

  • jtkjtk Member

    @joereid makes a good point. If the gateway is not within your locally configured prefix, you'd need something like this somewhere:


    ip -6 route add 2607:5300:61:09FF:FF:FF:FF:FF dev eth0
    ip -6 route add default via 2607:5300:61:09FF:FF:FF:FF:FF

    If that is the case, presumably the provider's local network has configured a larger prefix for the subnet than what they gave you. This is fine, but you will need to make sure you keep a record of that gateway address.

  • @jtk said:
    @joereid makes a good point. If the gateway is not within your locally configured prefix, you'd need something like this somewhere:


    ip -6 route add 2607:5300:61:09FF:FF:FF:FF:FF dev eth0
    ip -6 route add default via 2607:5300:61:09FF:FF:FF:FF:FF

    If that is the case, presumably the provider's local network has configured a larger prefix for the subnet than what they gave you. This is fine, but you will need to make sure you keep a record of that gateway address.

    [[email protected] network-scripts]# ip -6 route add 2607:5300:61:09FF:FF:FF:FF:FF dev eth0
    RTNETLINK answers: File exists
    [[email protected] network-scripts]# ip -6 route add default via 2607:5300:61:09FF:FF:FF:FF:FF
    RTNETLINK answers: File exists
    [[email protected] network-scripts]#

  • @jtk said:
    @joereid makes a good point. If the gateway is not within your locally configured prefix, you'd need something like this somewhere:


    ip -6 route add 2607:5300:61:09FF:FF:FF:FF:FF dev eth0
    ip -6 route add default via 2607:5300:61:09FF:FF:FF:FF:FF

    If that is the case, presumably the provider's local network has configured a larger prefix for the subnet than what they gave you. This is fine, but you will need to make sure you keep a record of that gateway address.
    @joereid said:

    @cheridon561 said:
    How do i add a static route?

    In /etc/sysconfig/network-scripts folder, create (or edit) the file "route6-eth0" and add this:

    2607:5300:0061:09ff:00ff:00ff:00ff:00ff dev eth0
    default via 2607:5300:0061:09ff:00ff:00ff:00ff:00ff
    

    Obviously change the gateway IP to the real one...then reboot

    [[email protected] network-scripts]# service network restart
    Shutting down interface eth0: [ OK ]
    Shutting down loopback interface: [ OK ]
    Bringing up loopback interface: [ OK ]
    Bringing up interface eth0: Determining if ip address 149.56.24.58 is already i n use for device eth0...
    WARN : [ipv6_add_route] 'No route to host' adding route '::/0' via gateway ' 2607:5300:61:09FF:FFFF:FFFF:FFFF:FFFF' through device ''
    [ OK ]
    [[email protected] network-scripts]#

  • cheridon561cheridon561 Member
    edited June 2016

    @joereid said:
    Yes, your gateway is outside your subnet, that's how OVH does it. You'll need to add a static route to the gateway ip. I don't know why the insist on doing it that way, but the do...

    Do you have skype?

  • I still need help with this

  • BUMP

  • @cheridon561 said:

    [[email protected] network-scripts]# service network restart
    Shutting down interface eth0: [ OK ]
    Shutting down loopback interface: [ OK ]
    Bringing up loopback interface: [ OK ]
    Bringing up interface eth0: Determining if ip address 149.56.24.58 is already in use for device eth0...
    WARN : [ipv6_add_route] 'No route to host' adding route '::/0' via gateway ' 2607:5300:61:09FF:FFFF:FFFF:FFFF:FFFF' through device ''

    [ OK ]

    [[email protected] network-scripts]#

    The gateway in your output is wrong. OVH gateways end with 4 sets of "00FF", not "FFFF"

  • @joereid said:

    @cheridon561 said:

    [[email protected] network-scripts]# service network restart
    Shutting down interface eth0: [ OK ]
    Shutting down loopback interface: [ OK ]
    Bringing up loopback interface: [ OK ]
    Bringing up interface eth0: Determining if ip address 149.56.24.58 is already in use for device eth0...
    WARN : [ipv6_add_route] 'No route to host' adding route '::/0' via gateway ' 2607:5300:61:09FF:FFFF:FFFF:FFFF:FFFF' through device ''

    [ OK ]

    [[email protected] network-scripts]#

    The gateway in your output is wrong. OVH gateways end with 4 sets of "00FF", not "FFFF"

    i have fixed that miss type & i could still not get it working

  • BUMP

  • rm_rm_ Member

    5 "Bumps" from you so far in this thread, you deserve to be shitcanned for life from this forum, not help.

Sign In or Register to comment.