top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

How to determine DUID for DHCPv6 on F19?

0 votes
440 views

I'm investigating IPv6, and wondering how, on Fedora 19, the best way to determine the appropriate DUID (DHCP unique identifier) to be used in the host sections, along with fixed-address statements.
If this is documented, please mention.

posted Jun 30, 2013 by anonymous

Share this question
Facebook Share Button Twitter Share Button LinkedIn Share Button

1 Answer

+1 vote
 
Best answer

Unfortunately there is more than one method that a client may choose to make up their DUID, making it difficult if not impossible to predict what DUID a client will use. However once the client does use a DUID, it should not change.

There is

DUIDLL Based on Link Layer Address
DUIDLLT Based on Link Layer Address plus Time
DUIDEN Based on Enterprise Number

ISC DHCPv6 barfs on PPP links which have no LL address. see https://bugzilla.redhat.com/show_bug.cgi?id=626514#c83
see http://www.ietf.org/rfc/rfc3315.txt Section 9 for documentation.

answer Jun 30, 2013 by anonymous
Similar Questions
0 votes
Enabling new UI of LibreOffice on F19

I'm having a problem trying to enable the new UI of LibreOffice 4.1, all this in F19+KDE; but for some reason I can't see it in any menu item or any other menu or option; is this because of KDE or is there a dependency I haven't resolve?

0 votes
retrofitting LUKS encryption on installed F19 system

I've got a F19 installation that I'd like to turn into a fully encrypted system with LUKS.

There are many howtos on the web for encrypting a partition, but they all show doing it to /home.

the implication is that you need to be logged in as root on the actual system you're modifying, though I don't think that is explicitly stated. That would mean you can't encrypt the root partition itself, since you've got to have an empty partition to work on, then restore its contents from backup.

So, my question(s):
-can you do it while being booted into a recovery environment?
-if not, is there any way to convert the whole thing that I'm not able to figure out on my own (perhaps I'm having a whole series of senior moments) ???
-Or would it simply be best to do a fresh installation?

+5 votes
After upgrade from Windows 8 to Windows 8.1, F19 grub menu does not appear

I installed Fedora 19 on my laptop, and it worked beautifully with the already installed Windows 8. When I upgraded the Windows 8 to Windows 8.1. Now it boots straight to Windows 8.1 and grub does not appear.

I disabled secure boot in the firmware.

I do not even know which version of grub was booting the UEFI system before; it just worked.

Can anyone suggest:

  1. What grub would the Fedora 19 installer have provided to boot it and Windows 8? (grub2, grub-efi,...)
  2. Can anyone point to any documentation on how to fix this?
0 votes
How to start a vncserver on reboot on fedora19

I cannot manage to get fedora 19 to start a vnc server on reboot. I have tried various approaches:

a) edit /etc/systemd/system/vncserver@:1.service It does not work. It kills any vncserver I am running at :1, but *never* starts a new one.
systemctrl status vncserver@:1.service reports the service as dead, but without any error message.

b) I wrote a small bash script that starts vncserver at :1, and set a cronjob on the user. The server runs ok when I run the script from the terminal (I can see gnome desktop in it), but gnome does not start from the cronjob. (I have even set a sleep of 30 seconds to delay the start of the vncserver). The vncserver starts, but it is empty.

Method b worked in fedora 18, but not anymore in fedora 19. What is the way to start a tiger vnc server at reboot for a user?

+1 vote
Can not start VirtualBox on Fedora19

I am getting the error message below on a Fredora 19 system when attempt to start VirualBox Any help will be greatly appreciated :

Kernel driver not installed (rc=-1908) The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv. Please reinstall the kernel module by executing '/etc/init.d/vboxdrv setup' as root.

...