Bug 105873
Summary: | Can't 'ifup' alias to wireless-tools-controlled interface using dhcp | ||||||
---|---|---|---|---|---|---|---|
Product: | [Retired] Red Hat Linux Beta | Reporter: | George Karabin <gkarabin> | ||||
Component: | redhat-config-network | Assignee: | Harald Hoyer <harald> | ||||
Status: | CLOSED NOTABUG | QA Contact: | David Lawrence <dkl> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | beta1 | CC: | notting | ||||
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: | 2003-10-01 20:33:20 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: | |||||||
Attachments: |
|
Description
George Karabin
2003-09-28 20:25:52 UTC
Created attachment 94803 [details]
fixes ifup, but ifdown would need work, probably the wrong approach
This patch seems to work, but it worries me - I'm hacking out the alias in a
place where maybe it should carry through for other cases (I don't know,
haven't tried to identify all of the cases).
Oddities (at least from my point of view) are that 'ifconfig' shows a
configuration for "eth1", rather than "eth1:1", since I had to use what amounts
to "dhclient eth1" instead of using the alias.
ifdown eth1:1 doesn't bring the interface down, thought ifdown 'eth1' does. I
imagine something in 'ifdown' needs to swap DEVICE and REALDEVICE, assuming
that the ifup patch isn't inherently wrong.
Aliases do not work if the main interface isn't up. I don't think what you're trying to do fits into the alias framework... if it's just a different configuration, use a different device name. The difficulty (as near as I can see) is that iwconfig thinks the device is eth1, and I don't know that there's a way to change it, at least, not in a "just works" way for users of redhat-config-network. Any ideas? Have a /etc/sysconfig/network-scripts/ifcfg-somethingelse, that has DEVICE=eth1 in it.. that should work. Thanks. If that's the preferred solution, then I'll move the bug to redhat-config-network - it ought to be able to generate the file appropriately. It can, I'm pretty sure. I might be misunderstanding what you're trying to do, but it looks like you're setting up the wrong thing. Basically, if you want another configuration for an already existing device, you set up another configuration, you don't set up an alias. Aliases are for adding new IPs to already existing devices, not for different exclusive configurations. I'm not sure that redhat-config-network exposes a way to do this, though. From the "Devices" tab, pressing "New" generates the following set of menu transitions: New->Select Device Type->Select Wireless Device->airo_cs (eth1)->Configure Wireless Connection->Configure Network Settings->Create Wireless Device There's no option to assign the "eth" interface presented in the menu. You can pick "other" at the "Select Wireless Device" menu, but it doesn't give you the ability to pick the airo_cs driver - instead it shows a list of ethernet drivers and some wireless drivers, where airo_cs doesn't appear to be a choice. The only path that I can see (that seems obvious) ends up assigning the alias automatically - the user doesn't have a "create alias" option, just a "new device" option that uses aliases if the same interface is already in use. Unfortunately, comments were lost in the db crash, but this was resolved as not a bug; you do need to configure it differently than as an alias. |