Trying f15beta in a VM.
After install, I wanted to configure to start the wired ethernet at boot. Tried to use NM to do that, but didn't see any option for starting @boot.
Manually edited network-scripts file, setting ONBOOT=true. That did it. But isn't there a more newb-friendly way?
On 04/28/2011 08:42 AM, Neal Becker wrote:
Trying f15beta in a VM.
After install, I wanted to configure to start the wired ethernet at boot. Tried to use NM to do that, but didn't see any option for starting @boot.
Manually edited network-scripts file, setting ONBOOT=true. That did it. But isn't there a more newb-friendly way?
If you checked "Available to all users", then it's started when the NM daemon is started, before a user logs in.
Steven Stern wrote:
On 04/28/2011 08:42 AM, Neal Becker wrote:
Trying f15beta in a VM.
After install, I wanted to configure to start the wired ethernet at boot. Tried to use NM to do that, but didn't see any option for starting @boot.
Manually edited network-scripts file, setting ONBOOT=true. That did it. But isn't there a more newb-friendly way?
If you checked "Available to all users", then it's started when the NM daemon is started, before a user logs in.
No "Available to all users" here - this is kde, if that matters. There is a 'system connection', but that gave me a strange error message when I checked it and tried to apply.
On Thu, 2011-04-28 at 10:21 -0400, Neal Becker wrote:
No "Available to all users" here - this is kde, if that matters. There is a 'system connection', but that gave me a strange error message when I checked it and tried to apply.
It rather does matter, yeah, as it's a completely different NM configuration interface. You might want to ask in #fedora-kde on IRC...
On Thu, 2011-04-28 at 10:21 -0400, Neal Becker wrote:
Steven Stern wrote:
On 04/28/2011 08:42 AM, Neal Becker wrote:
Trying f15beta in a VM.
After install, I wanted to configure to start the wired ethernet at boot. Tried to use NM to do that, but didn't see any option for starting @boot.
Manually edited network-scripts file, setting ONBOOT=true. That did it. But isn't there a more newb-friendly way?
If you checked "Available to all users", then it's started when the NM daemon is started, before a user logs in.
No "Available to all users" here - this is kde, if that matters. There is a 'system connection', but that gave me a strange error message when I checked it and tried to apply.
When performing an installation, you are given the option to setup networking for the installer. Those same options also apply for the installed system. So if you use networking during the installation, it should also set it up for the installed system. If you perform a non-network install (DVD), and don't actively configure networking during installation, your installed system will not automatically enable networking. You can manually enable networking on the installed system using the preferred Network utility (nm-connection-editor in GNOME).
http://docs.fedoraproject.org/en-US/Fedora/14/html/Installation_Guide/sn-Net...
Thanks, James
On Thu, 2011-04-28 at 12:49 -0400, Tom Horsley wrote:
On Thu, 28 Apr 2011 12:39:39 -0400 James Laska wrote:
You can manually enable networking on the installed system using the preferred Network utility (nm-connection-editor in GNOME).
Unless you have a static IP, in which case you manually edit the ifcfg file.
nm-connection-editor has support for configuring static IP information. Is that not working for you?
Thanks, James
On Thu, 28 Apr 2011 12:55:50 -0400 James Laska wrote:
nm-connection-editor has support for configuring static IP information. Is that not working for you?
Certainly could not find anything on the network config dialog available on the live CD image. Maybe it is there now after updates, but I needed to config the static IP to get updates :-).
On Thu, 2011-04-28 at 13:06 -0400, Tom Horsley wrote:
On Thu, 28 Apr 2011 12:55:50 -0400 James Laska wrote:
nm-connection-editor has support for configuring static IP information. Is that not working for you?
Certainly could not find anything on the network config dialog available on the live CD image. Maybe it is there now after updates, but I needed to config the static IP to get updates :-).
Try again if you have a moment. nm-connection-editor (provided by NetworkManager-gnome) is available on the live image, and should allow you to configure a static IP connection. If that's failing, that would be good to know.
Thanks, James
nm-connection-editor has support for configuring static IP information. Is that not working for you?
Certainly could not find anything on the network config dialog available on the live CD image. Maybe it is there now after updates, but I needed to config the static IP to get updates :-).
Try again if you have a moment. nm-connection-editor (provided by NetworkManager-gnome) is available on the live image, and should allow you to configure a static IP connection. If that's failing, that would be good to know.
So here's what appears to be happening:
Using the livecd on a usb stick, there was no ifcfg-em1 file created.
The only app that appears in the control panel is not nm-connection-editor but something that calls itself "Network Settings" (or something like that anyway).
That app has an Options... button which is, apparently, always disabled if there is no matching ifcfg-whatever file.
If I make an ifcfg-em1 file, the Options... button becomes enabled, and when I press it, it does appear to bring up an app that looks a great deal like nm-connection-editor, but there is no GUI way to get there given the default configuration you get with the live CD.
If I manually run nm-connection-editor from a terminal, I can create the ifcfg file, so there doesn't appear to be any reason to have the Options... button disabled.
A separate issue is that nm-connection-editor has one of the most screwy interfaces I've ever tried to use to fill out fields in a form. If I type the IP in the first field then hit TAB (the most natural button in the world to hit to get to the next field), it erases the IP address I just typed while moving to the next field. Apparently I have to hit return rather than tab (but I'd expect hitting return to be like hitting OK or Apply).
All in all, just editing the ifcfg file is simpler :-).
On Thu, 2011-04-28 at 18:41 -0400, Tom Horsley wrote:
The only app that appears in the control panel is not nm-connection-editor but something that calls itself "Network Settings" (or something like that anyway).
That app has an Options... button which is, apparently, always disabled if there is no matching ifcfg-whatever file.
If I make an ifcfg-em1 file, the Options... button becomes enabled, and when I press it, it does appear to bring up an app that looks a great deal like nm-connection-editor, but there is no GUI way to get there given the default configuration you get with the live CD.
It's called 'Network Connections'. If you go to overview and type that, or 'nm-conn', you'll find it. Yeah, not super easy to find.
On Thursday 28 of April 2011 15:45:20 Steven Stern wrote:
On 04/28/2011 08:42 AM, Neal Becker wrote:
Trying f15beta in a VM.
After install, I wanted to configure to start the wired ethernet at boot. Tried to use NM to do that, but didn't see any option for starting @boot.
Manually edited network-scripts file, setting ONBOOT=true. That did it. But isn't there a more newb-friendly way?
If you checked "Available to all users", then it's started when the NM daemon is started, before a user logs in.
while at it ... pls, how to achieve that in KDE?
there's "System connection" checkbox which I'd expect to do the job, but it cannot be checked, it is grayed out ...
K.
-
Adam Williamson -
James Laska -
Karel Volný -
Neal Becker -
SternData -
Tom Horsley