Bug 28036
| Summary: | Unable to edit IP aliases for virtual hosts | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | Devon Jones <hcomp> |
| Component: | linuxconf | Assignee: | Nalin Dahyabhai <nalin> |
| Status: | CLOSED WONTFIX | QA Contact: | David Lawrence <dkl> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 7.0 | ||
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2006-02-21 18:47:54 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Closing because we don't ship linuxconf anymore Changed to 'CLOSED' state since 'RESOLVED' has been deprecated. |
From Bugzilla Helper: User-Agent: Mozilla/4.0 (compatible; MSIE 5.0; Windows NT; DigExt) The Network device shows: eth0 lo lo If I telnet from hcomp5 to hcomp8, I appear to have a loopback problem, and get:- Trying 192.0.0.8 Connected to hcomp8 Escape character is '^]' Redhat Linux release 7.0(Guinness) Kernal 2.2.16-22smp on an i686 Login:dwj Last login: Fri 16 16:31:49 from hcomp8 [dwj@hcomp5 dwj] $ I have very little network experience, but assume that 'lo' should not be an alias for eth0, but of course it cannot be edited. If I select eth0, from the aliases for virtual hosts screen, then the next screen shows every field blank. netstat -rn shows: 192.0.0.0 0.0.0.0 255.255.255.0 U 00 0 lo 192.0.0.0 0.0.0.0 255.255.255.0 U 00 0 eth0 I assume that the 'lo' line should show 127.0.0.0 Also netstat -rn shows:- Reproducible: Didn't try Steps to Reproduce: 1.I believe that all setups for networking were made using linuxconf. Presumably there is a file which could be edited in order to clear the eth0 and lo entries, and then attempt to reproduce the problem by by repeating a setup using Linuxconf. 2. 3.