Red Hat Bugzilla – Bug 197721
VNC install displaying incorrect IP address for viewer connection
Last modified: 2007-11-30 17:11:36 EST
Description of problem:
During VNC installation, the IP address being displayed (51:51:51:51) for
vncviewer connection is incorrect.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Assuming VNC kickstart file is ks.cfg with the following content:
vnc --password install
url -- ftp://192.168.3.107/mysrc/fed/x86_64/os
# has multiple NIC devices, so using eth0
network --device eth0 --bootproto dhcp --hostname mazatlan2
2. Invoke the following during initial installation prompt:
linux vnc ksdevice=eth0 ks=ftp://192.168.3.107/mysrc/ks/ks.cfg
3. The program installation will proceed, then install the VNC server and
display the its incorrect IP address (184.108.40.206)
The VNC server is now running.
Please connect to 220.127.116.11:1 to begin the install...
Starting graphical instalation...
Instead of 18.104.22.168:1 it should be displaying the actual IP address given by
DHCP server. example: 192.168.3.29:1
This could be hardware specific because the problem doesn't show up on other PCs
(tried on 5 PCs with different configuration). The following PC system is affected:
ECS (Elitegroup) K8M800-M2(v1.0) Semptron 2800+ socket 755 1GB RAM 300GB HDD
NOTE: Learning the true IP address (192.168.3.29 in my case) through probing
(ping), I was able to proceed with the installation using that IP address
(192.168.3.29) instead of the erroneous IP address (22.214.171.124). So I suspect
the program's module that obtain the IP address from DHCP is somewhat being
corrupted in the process.
Chris, FYI before you dig into this too much this looks like a dup of one I
filed a while back: 195218
Please run your installation again up to this point, then attach
/tmp/anaconda.log to this bug report.
I can't get into the shell terminal even though it prompt "Press <enter> for a
shell". I tried rsh, ssh, rlogin, telnet into the host machine but I get
refusal. It only allow vncviewer to go through. Any other suggestion how to
remote copy /tmp/anaconda.log file? I will try different hardware config. (use
another video instead of the on-board one, and remove the extra LAN card) and
see if I get the same error.
OK, I did more tests and came up with the following:
1. When there is only ONE LAN device attached, IP address is being displayed
2. When there are 2 LAN devices attached, the install program (anaconda?) is
querying the IP address on the wrong device (eth1) instead of the desired one
3. For some reason, the on-board LAN device is being defined first (eth0) on
some PCs, while the other PCs defined it last (eth1). I am guessing that the
order probably confused the install progam.
Maybe the install program should re-query the IP address just before displaying
it or just before running the VNC server?
NOTE: The latest build broke the ability to bring up a shell prompt during
installation on x86_64 and i386 platform. For this reason I can't access and
copy the /tmp/anaconda.log file.
Okay, committed a patch to use the interface configured for installation instead
of looping through all available devices and using whichever one gives back an
IP address first. I think this should take care of your problem.
*** Bug 195218 has been marked as a duplicate of this bug. ***