Howdy, Stranger!

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

Sign In Register

Quick Links


Shells Virtual Desktop
BMail.ag - Secure Email Service
Server.net
CPLicense.net
VPS Server
Buy VPN
Vultr
VMs for AI
HostDare
ReliableSite White-Label Dedicated Hosting for Resellers
InterServer VPS
BMail.ag - Secure Email Service
Best VPN
High-Performance Bare Metal Server Solutions
Karvl.com
Server Mania Cloud Hosting
DataWagon Hosting
AlphaVPS Hosting
Evoxt.com
Clouvider
VPS Hosting with NVMe
Residential IPs in the US & 4G Mobile Proxies in EU & US with Unlimited Bandwidth
ReliableSite White-Label Dedicated Hosting for Resellers
Rabisu - Hosting Solutions
Shells Virtual Desktop

Categories

In this Discussion

Home › General
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

IPv6 on online.net?

linuxthefishlinuxthefish Member
in General

Does anyone know how to get ipv6 working at online.net? I've tried dibbler-client, and the logs say I'm assigned my /48 but it doesn't actually work. Sometimes it works when I add the address manually, however it always dies after a few hours. :(

2014.07.08 17:28:59 Client Debug     PD: Adding 2001:bc8:33c0:: prefix to PD (iaid=1) to addrDB.
2014.07.08 17:28:59 Client Notice    PD: Adding prefix 2001:bc8:33c0::/48 to all interfaces (prefix will be split to /56 prefixes if necessary).
«1

Comments

  • AmitzAmitz Member
    edited July 2014

    Does that help?
    http://forum.online.net/index.php?/topic/4546-ipv6/

    Seems dibbler is not the best choice for online.net.

  • rm_rm_ IPv6 Advocate, Veteran

    Do not use dibbler, try the WIDE client (wide-dhcpv6-client package).

    Thanked by 2linuxthefish marrco
  • linuxthefishlinuxthefish Member

    @rm_ said:
    Do not use dibbler, try the WIDE client (wide-dhcpv6-client package).

    Thanks, this works perfectly! Topic solved :)

  • SASPSASP Member
    edited July 2014

    Do you use debian?

    If so, I suggest you to to use dibbler to only broadcast the duid.

    Therefore, add your duid in /var/lib/dibbler/client-duid. Create the file if it does not exist.

    In /etc/dibbler/client.conf only add:

    log-level 8

duid-type duid-ll

iface "eth0" {
 pd
 }

    Restart dibbler. Check the logs to make sure everything is fine.

    Then add the prefix like this:

    ip -6 addr add 2001:bc8:33c0::cafe/48 dev eth0

    The default next-hop is automatically retrieved via RA packets sent by online's router so you don't have to worry about adding a default route.

    Please let me know if this helped.

    Thanked by 1linuxthefish
  • sz1hostingsz1hosting Member

    I would recommend contacting there support or checking the faqs.

  • linuxthefishlinuxthefish Member

    @SASP said:
    Do you use debian?

    If so, I suggest you to to use dibbler to only broadcast the duid.

    Therefore, add your duid in /var/lib/dibbler/client-duid. Create the file if it does not exist.

    In /etc/dibbler/client.conf only add:

    log-level 8

duid-type duid-ll

iface "eth0" {
 pd
 }

    Restart dibbler. Check the logs to make sure everything is fine.

    Then add the prefix like this:

    ip -6 addr add 2001:bc8:33c0::cafe/48 dev eth0

    The default next-hop is automatically retrieved via RA packets sent by online's router so you don't have to worry about adding a default route.

    Please let me know if this helped.

    2014.07.08 19:14:45 Client Notice    My pid (2771) is stored in /var/lib/dibbler/client.pid
2014.07.08 19:14:45 Client Notice    Detected iface eth1/3, MAC=0c:c4:7a:05:5c:d9.
2014.07.08 19:14:45 Client Notice    Detected iface eth0/2, MAC=0c:c4:7a:05:5c:d8.
2014.07.08 19:14:45 Client Notice    Detected iface lo/1, MAC=00:00:00:00:00:00.
2014.07.08 19:14:45 Client Notice    Parsing /etc/dibbler/client.conf config file...
2014.07.08 19:14:45 Client Debug     Prefix delegation option found.
2014.07.08 19:14:45 Client Debug     Parsing /etc/dibbler/client.conf done, result=0
2014.07.08 19:14:45 Client Debug     1 interface(s) specified in /etc/dibbler/client.conf
2014.07.08 19:14:45 Client Critical  Interface eth0/2 is down or doesn't have any link-local address.
2014.07.08 19:14:45 Client Critical  Fatal error during CfgMgr initialization.

    Thanks, but :(

  • SASPSASP Member
    edited July 2014

    @linuxthefish said:
    Thanks, but :(

    Well it says your interface is down. You should have this interface up first, do you get a link-local address when you up it?

    Oh, also you should remove autoconf, add this in /etc/sysctl.conf:

    net.ipv6.conf.all.autoconf = 0
net.ipv6.conf.default.autoconf = 0
net.ipv6.conf.eth0.autoconf = 0

    Then,

    sysctl -p /etc/sysctl.conf
    Thanked by 1linuxthefish
  • linuxthefishlinuxthefish Member

    @SASP I think I broke something big, I'll try reinstalling! Thanks.

    sysctl: cannot stat /proc/sys/net/ipv6/conf/all/autoconf: No such file or directory
sysctl: cannot stat /proc/sys/net/ipv6/conf/default/autoconf: No such file or directory
sysctl: cannot stat /proc/sys/net/ipv6/conf/eth0/autoconf: No such file or directory
    Thanked by 1masteri
  • linuxthefishlinuxthefish Member

    Works fully now with that solution, thanks for your help.

    Yey for IPv6! :D

  • ahmiqahmiq Member

    @linuxthefish said:
    Works fully now with that solution, thanks for your help.

    Yey for IPv6! :D

    i am also having debian. could you please share what you did without breaking stuff :(

  • KeithKeith Member

    I've 2 servers, ipv6 is ok with one using dhclient, waiting to see if it remains so. While configuring using ifdown and ifup didn't always work as expected, it worked as expected after a reboot.

    The other server worked ok initially with dhclient, then no ipv6. Now trying dibbler, although while I have a 2001:bc8:: subnet, the dibbler log shows
    PD: Adding prefix 2001:db8:3333::2164:0:0/96 to all interfaces (prefix will be split to /104 prefixes if necessary). with an 2001:db8:1111::/64 address also. Support ticket sent in for that one.

  • SpiritSpirit Barred

    @ahmiq step by step IPv6 setup for Debian with dibbler:
    http://www.lowendtalk.com/discussion/comment/706713/#Comment_706713

  • nullnullnullnull Member

    I compile and use odhcp6c in CentOS 7 to negotiate PD but configure interface manually.

    Wait to see if it remains working too.

  • KeithKeith Member

    ipv6 now working, with a blocked spoofer.

  • linuxthefishlinuxthefish Member

    @Keith, I just run dibbler only now - dhclient seemed unstable for me. Not dropped out on irc to ipv6 servers for a month now.

  • KeithKeith Member

    @linuxthefish dhclient had stopped running on the other server, changed to dibbler.

    Thanked by 1linuxthefish
  • KupolKupol Member

    @Keith

    How did you solve getting wrong prefix assigned?

  • KeithKeith Member

    @Kupol support ticket

  • rm_rm_ IPv6 Advocate, Veteran
    edited August 2014

    It turns out Dibbler is not reliable (fails to work after some time, while still technically running; also the shutdown script sometimes hangs), so I am trying out the WIDE DHCPv6 client now. Wrote a small script to quickly install and configure it on a server.

    Thanked by 3Spirit linuxthefish ahmiq
  • ahmiqahmiq Member

    @rm_ said:
    It turns out Dibbler is not reliable (fails to work after some time, while still technically running; also the shutdown script sometimes hangs), so I am trying out the WIDE DHCPv6 client now. Wrote a small script to quickly install and configure it on a server.

    Thank you for the script , the wide client is running but cannot seem to ping6 ipv6 addresses. it says:

    root@online:~# ping6 ipv6.google.com
connect: Network is unreachable

    no idea what i am doing wrong. would appreciate a little help if possible. Should i be adding gateway in my /etc/network/interfaces?

  • linuxthefishlinuxthefish Member
    edited August 2014

    @ahmiq said:
    no idea what i am doing wrong. would appreciate a little help if possible. Should i be adding gateway in my /etc/network/interfaces?

    Change nameservers in /etc/resolv.conf to the following:

    nameserver 8.8.8.8
    nameserver 8.8.4.4

  • ahmiqahmiq Member

    @linuxthefish said:
    nameserver 8.8.4.4

    looks the same. Network is unreachable. my ifconfig shows:

    eth0      Link encap:Ethernet  HWaddr xxxxxxxxxxxx
          inet addr:xxxxxxxx  Bcast:xxxxxxxxx  Mask:255.255.255.0
          inet6 addr: fe80::ca0a:a9ff:fec8:e61b/64 Scope:Link
          inet6 addr: 2001:bc8:3bea::1/48 Scope:Global
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:421021096 errors:1 dropped:0 overruns:0 frame:1
          TX packets:183047686 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:540622897208 (503.4 GiB)  TX bytes:150439786340 (140.1 GiB)
          Interrupt:28 Memory:feae0000-feb00000

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:63839393 errors:0 dropped:0 overruns:0 frame:0
          TX packets:63839393 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:498057777099 (463.8 GiB)  TX bytes:498057777099 (463.8 GiB)
  • MorningIrisMorningIris Member

    ipv6 sucks.

    Thanked by 2linuxthefish Upstage
  • linuxthefishlinuxthefish Member
    edited August 2014

    ahmiq said: looks the same. Network is unreachable. my ifconfig shows:

    Missed that bit, ignore what I said above!

    Looks like ipv6 is not being routed, check /var/lib/dhcpv6/dhcp6c_duid contains your duid and run "/etc/init.d/wide-dhcpv6-client restart".

    Also it can take up to 10 mins for DHCP to 'work', so try waiting a bit!

  • ahmiqahmiq Member

    @linuxthefish said:
    Also it can take up to 10 mins for DHCP to 'work', so try waiting a bit!

    there was some weired things in /var/lib/dhcpv6/dhcp6c_duid , i changed it to duid to my duid and when restart it didnt work. Ran @rm_ script with ./setup-dhcpv6.sh duid and it seems to restart fine.

    Is there any log or something for the wide to check what is going on.

  • rm_rm_ IPv6 Advocate, Veteran

    ahmiq said: some weired things in /var/lib/dhcpv6/dhcp6c_duid

    That's because the WIDE client stores this file in a binary format.

    Thanked by 1ahmiq
  • ahmiqahmiq Member
    edited August 2014

    my netstat -r:

    root@online:~# netstat -r
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
default         xxxxx 0.0.0.0         UG        0 0          0 eth0
xxxxxxx   *               255.255.255.0   U         0 0          0 eth0

    root@online:~# ip -6 route
    2001:myipv6::/48 dev eth0 proto kernel metric 256
    fe80::/64 dev eth0 proto kernel metric 256
    root@online:~# traceroute6 ipv6.google.com
    traceroute to ipv6.google.com (2a00:1450:4010:c03::71), 30 hops max, 80 byte packets
    connect: Network is unreachable

    looks like no route

  • ahmiqahmiq Member

    ahh looks like. it will never work.. Would put it down .. i think i have broken something

  • ahmiqahmiq Member

    Okay it works now. I just had to add gateway in my /etc/network/interfaces and boom:

    PING ipv6.google.com(la-in-x64.1e100.net) 56 data bytes
64 bytes from la-in-x64.1e100.net: icmp_seq=1 ttl=53 time=38.7 ms
64 bytes from la-in-x64.1e100.net: icmp_seq=2 ttl=53 time=38.7 ms
64 bytes from la-in-x64.1e100.net: icmp_seq=3 ttl=53 time=38.7 ms

    thanks everyone for help

  • ben78ben78 Member

    Thanks @rm_ for the script, though I can get it working with dibbler-client too.

    I'd like to know what do you guys add to your ip6tables to let the ra defines the route?
    Adding the gateway in the interfaces file like @ahmiq did works fine, but if they change it it won't work..

    Thx :)

This discussion has been closed.