Adding IPv6 works but needs /48 in stead of /64

L

lightningbit

Verified User
Joined
Nov 7, 2008
Messages
35
Hi,

adding IPv6 to DA works fine,
assigning it to reseller, user, etc.. all fine
appearing in the DNS settings ... all fine

BUT it seems to add the IP by default with a /64 in stead of a /48 (which I need)

when I do an ipconfig,

Code: 
bash-3.2# /sbin/ifconfig
eth0      Link encap:Ethernet  HWaddr xxx

          inet6 addr: 2xx2:xxx:yy:zzzz::21:21/64 Scope:Global
          inet6 addr: 2xx2:xxx:yy:zzzz::22/64 Scope:Global
          inet6 addr: 2xx2:xxx:yy:zzzz::11/64 Scope:Global
          inet6 addr: 2xx2:xxx:yy:zzzz::23/64 Scope:Global
          inet6 addr: 2xx2:xxx:yy:zzzz::10/64 Scope:Global
          inet6 addr: 2xx2:xxx:yy:zzzz::1/64 Scope:Global
          inet6 addr: 2xx2:xxx:yy:zzzz::1/48 Scope:Global
          inet6 addr: 2xx2:xxx:yy:zzzz::2/64 Scope:Global
          inet6 addr: 2xx2:xxx:yy:zzzz::21/64 Scope:Global
          inet6 addr: 2xx2:xxx:yy:zzzz::3/64 Scope:Global

          inet6 addr: 2xx2:xxx:yy:zzzz::4/64 Scope:Global
          inet6 addr: 2xx2:xxx:yy:zzzz::5/64 Scope:Global
          inet6 addr: 2xx2:xxx:yy:zzzz::24/64 Scope:Global
          inet6 addr: 2xx2:xxx:yy:zzzz::6/64 Scope:Global
          inet6 addr: 2xx2:xxx:yy:zzzz::25/64 Scope:Global
          inet6 addr: 2xx2:xxx:yy:zzzz::7/64 Scope:Global
          inet6 addr: 2xx2:xxx:yy:zzzz::8/64 Scope:Global
          inet6 addr: 2xx2:xxx:yy:zzzz::9/64 Scope:Global
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

so, how can I tell DA to use /48 in stead of /64?

thanks

L.
 
When adding an IP in Directadmin use correct netmask. Or do you want to say, even with correct netmask, IP is added like that?
 
You can't add a proper netmask for IPv6 IPs in DA, but if DA is not adding the IPs to the server, then it shouldn't be a problem.
 
I'm not using Ipv6. Will you please say, why that's impossible? Directadmin doesn't support adding IPv6 via its interface?
 
To my knowledge (just confirmed by doing a test), DA doesn't add IPv6s to the server, it just uses whatever IPs you feed it and it will work as long as you add IPs to the server yourself.
That means that the ipconfig problem above has nothing to do with DA.

Also, the current implementation doesn't let you define a mask. You have to leave the IPv4 mask as is and the IP will be added.
 
Hello,

The IPv6 IPs should be loaded into the device when you add them in through Admin Level -> IP Manager.

If they're not getting loaded, something's wrong.
Try:
Code: 
cd /usr/local/directadmin/scripts
./addip 1:2:3:4:6:7:8 255.255.255.0 eth0
The netmask part of the interface may be throwing it off, but I've only ever added IPv6 to the device through DA.. I've never done it through ssh. Let us know what errors you get.

The proper /mask option is on the todo list, but they usually inherit the netmask of the main IP anyway, regardless of what we specify (may vary per OS)

John
 
The IPv6 IPs should be loaded into the device when you add them in through Admin Level -> IP Manager.
Click to expand...
Nothing gets added to /etc/rc.conf


./addip 1:2:3:4:6:7:8 255.255.255.0 re0
Click to expand...
./addip: arith: syntax error: "(1:2:3:4:6:7:8 & 255) | (255 & ~255)"
 
interfasys said:
To my knowledge (just confirmed by doing a test), DA doesn't add IPv6s to the server, it just uses whatever IPs you feed it and it will work as long as you add IPs to the server yourself.
That means that the ipconfig problem above has nothing to do with DA.

Also, the current implementation doesn't let you define a mask. You have to leave the IPv4 mask as is and the IP will be added.
Click to expand...

Actually, the way it works:

- you indeed need to add the IPv6 base address or subnet in my case a /48) to the interface config.
- then you can add individual IPv6 addresses through the DA GUI (but indeed, just the plain address, without mask
- there is a service which seems to be called by DA, and for sure upon reboot, named "startips" which goes through the list of addresses added to DA by yourself, and for each address calls the script usr/local/directadmin/scripts/addip
and it is this script which adds the individual IP's to the server
(it does that with a /64, as yuo can see in the addip script, but it works now)

P.S. actually, my primary issue was related to a typo error in the address between my network config and my upstream provider.

Now it works great:
- add an IPv6 as admin in DA
- assign it to a reseller
- assign it to a user
- add it to a domain config
- and "ding" ... it nicely adds to the DNS config, and a few seconds later, my domain is reachable on IPv6
- no need to touch the server config under the hood for each address.


I hope this was of some use for people reading this

L.
 
I'll definitely be taking a look before 1.38.0 is released. I just needed to get the current DA code out and tested, so it can be released sooner than later.

John
 
DirectAdmin Support said:
Hello,

The IPv6 IPs should be loaded into the device when you add them in through Admin Level -> IP Manager.
Click to expand...
This is still not working.

DirectAdmin Support said:
If they're not getting loaded, something's wrong.
Try:
Code: 
cd /usr/local/directadmin/scripts
./addip 1:2:3:4:6:7:8 255.255.255.0 eth0
Click to expand...
This works well.

Is there a reason why DA will not load it in the device?
(CentOS 5.6 i686 // 2.6.18-238.19.1.el5xen)
 
You must log in or register to reply here.
Back
Top