Matthew Saltzman wrote: >> I sort of realized that this is the intention of the networking >> directories. Unfortunately it does not seem to work in my case, >> assuming one is meant to use system-config-network to choose the profile. > > One is, or one can select it on the kernel boot line in grub (but I > don't recall the parameter format). > > Use system-config-network to make copies of the base interfaces, then > edit them. Create a new profile and check your copies as being > activated in that profile. In theory, when you select a profile, the > ifcfg file for the edited copy is linked in. I did try this (with system-config-network) but it didn't seem to work. Doesn't really matter in my case, as I don't need profiles - I was just experimenting. But I certainly don't find the system-config-network interface very intuitive. > > I haven't seriously tried to make it work in quite a while, though. > >> >> > NetworkManager is a better tool for most wireless connections (modulo >> > issues with some older cards and some drivers). It works fine for >> > wired connections too, as long as they DHCP. >> >> Sadly, NM does not work with my WiFi device (Orinoco Classic Gold). >> In any case, I doubt if it is appropriate in this case, >> where I have a desktop server with fixed Access Point. > > If you only have one AP then you shouldn't need NM or profiles. If it's > WEP, then simple configuration with system-config-network should work. > If WPA, you'll need to work with wpa_supplicant. NM works with that, > but I don't know much about making it work on its own. > >> >> >> >> >> -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
