/etc/dhcp3/dhclient.conf should be honoured in packages uploaded
yesterday/today.
** Changed in: network-manager (Ubuntu)
Status: Confirmed = Fix Released
--
NM doesn't pass hostname to DHCP server
https://bugs.launchpad.net/bugs/210095
You received this bug notification because you are
I can confirm the behavior described above. Intrepid-5
ifup/ifdown uses the settings in /etc/dhcp3/dhclient.conf.
NetworkManager does not.
Workaround:
ln -s dhcp3/dhclient.conf /etc/dhclient-wlan0.conf
ln -s dhcp3/dhclient.conf /etc/dhclient-eth0.conf
Under edit connections, connection-name,
On Fri, Aug 29, 2008 at 02:07:36PM -, zedic wrote:
Okay I have finally figured out the workaround for NetworkManager 0.7.0
in Ubuntu/Debian.
NetworkManager should be looking at /etc/dhcp3/dhclient.conf, but
it's not. It seems to be looking for /etc/dhclient-eth0.conf or /etc
Okay I have finally figured out the workaround for NetworkManager 0.7.0
in Ubuntu/Debian.
NetworkManager should be looking at /etc/dhcp3/dhclient.conf, but
it's not. It seems to be looking for /etc/dhclient-eth0.conf or /etc
/dhclient-wlan0.conf.
For example if your interface is eth0 here is
Okay, I was switching back and forth between Fedora 10 Alpha and Ubuntu
Intrepid Ibex Alpha. I'm in Ubuntu now, and it's not working, so I
guess that was in Fedora. In Fedora I believe I ran system-config-
network and setup eth0. I believe in system-config-network there is an
Advanced button
Okay in Fedora it looks like this configuration was setup in a user
profile. I found an awesome article on Fedora Network Configuration
that tells where all the different networking scripts are kept.
http://openskill.info/infobox.php?ID=247 So the workaround for Fedora
is to use a network
On Sun, Aug 24, 2008 at 03:06:56AM -, zedic wrote:
I found one solution that worked for me in UBUNTU Intrepid Ibex Alpha 4.
Just setup a new profile for the interface in NetworkManager and tell it
what host name to use in the profile settings. It seems NetworkManager
is looking for the
I've been fighting with this bug for the last few days once I finally
realized that it was the cause of my system backups not happening. My
dhcp server is keyed based on hostname, and in Hardy it completely seems
to be ignoring the send host-name string in /etc/dhcp3/dhclient.conf.
This means it
I found one solution that worked for me in UBUNTU Intrepid Ibex Alpha 4.
Just setup a new profile for the interface in NetworkManager and tell it
what host name to use in the profile settings. It seems NetworkManager
is looking for the settings in the interface's profile, but it's
ignoring the
Upgraded to intrepid ibex Alpha 4 - Still Not Working...
I have confirmed the line send host-name hostname; in my
/etc/dhcp3/dhclient.conf file. NetworkManager still doesn't send the
hostname.
My company's DHCP sever won't give out a DHCP address unless the host
name starts with a specific
This seems to happen only on new Hardy installs; upgrades preserve the
required file. The missing piece is the line
send host-name hostname;
in /etc/dhcp3/dhclient.conf -- EXACTLY as typed (include , ).
--
NM doesn't pass hostname to DHCP server
https://bugs.launchpad.net/bugs/210095
You
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) = Alexander Sack (asac)
--
NM doesn't pass hostname to DHCP server
https://bugs.launchpad.net/bugs/210095
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Changed in: network-manager (Ubuntu)
Status: New = Confirmed
--
NM doesn't pass hostname to DHCP server
https://bugs.launchpad.net/bugs/210095
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Tried this on multiple computers with both LiveCD and installed systems.
The resulting comparison between Gutsy and Hardy is the same as I
indicated in the original report above. No hostname.
--
NM doesn't pass hostname to DHCP server
https://bugs.launchpad.net/bugs/210095
You received this bug
14 matches
Mail list logo
