Bug 881
Summary: | Why the plip interface does not work & a simple laplink script | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | ppe |
Component: | netcfg | Assignee: | Michael K. Johnson <johnsonm> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 5.2 | ||
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: | 1999-03-23 02:22:05 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: |
Description
ppe
1999-01-19 19:42:40 UTC
I have verified this to be true with 5.2. When creating a plip device using netcfg, it does not properly put the DEVICE= line in the /etc/sysconfig/network-scipts/ifcfg-plip<0-2> file. Also you have to hit enter after entering the netmask before the network number is created. This should be either documented in the dialog or the app should be coded to check after hitting save to see if anything was entered into the netmask box instead if just putting a blank NETWORK= into the ifcfg file. Also something different needs to be done in regards to setting up of plip devices because you really do not know whether to use plip0, plip1, or plip2 until the module has been properly inserted and the kernel reports which device it has created. Linuxconf is supposed to address alot of these problems which will make netcfg obsolete. Michael, have you taken any action on this? fixed in netcfg-2.20 Will be available in RawHide and 6.0, but not as an erratum for 5.2 |