On Wed, Dec 03, 2008 at 04:51:28PM -0500, Paul W. Frields wrote:
> On Wed, Dec 03, 2008 at 04:39:54PM -0500, fred smith wrote:
> > On Wed, Dec 03, 2008 at 01:33:32PM -0500, Paul W. Frields wrote:
> > > On Wed, Dec 03, 2008 at 12:58:15PM -0500, fred smith wrote:
> > > > OK, next dumb question: Now the NM applet says the wired network is "unmanaged".
> > > > It WAS, a couple days ago, working via NM, as I could plug in the cable and
> > > > the little icon in the top panel went round and round then it connected.
> > > > Today it's not doing anything even if I forcefully disconnect wireless first.
> > > > I suppose I must have changed something, but again I can't see what that
> > > > would have been.
> > > >
> > > > once again, advice will be appreciated, thanks!
> > >
> > > In System > Administration > Network, if your adapter is listed, edit
> > > its settings and make sure "Controlled by NetworkManager" is
> > > selected. If you don't see the adapter that's not ipso facto a
> > > problem, but my bet is you will.
> >
> > Paul, you hit the nail on the head. Thanks for the tip!
> >
> > Perhaps I can throw out ONE MORE networking question...
> >
> > I keep seeing this in the output of /sbin/ifconfig:
> >
> > virbr0 link encap:Ethernet HWaddr 5A:4C:8D:5F:54:EA
> > inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0
> > inet6 addr: fe80::584c:8dff:fe5f:54ea/64 Scope:Link
> > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> > RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:28 errors:0 dropped:0 overruns:0 carrier:0
> > collisions:0 txqueuelen:0
> > RX bytes:0 (0.0 b) TX bytes:4977 (4.8 KiB)
> >
> > but I have never configured anything named "virbr0" or even close to it.
> > My LAN is not 192.168.122. I don't know where this comes from. Or what
> > is the proper way to get rid of it.
> >
> > I've never encountered anything like it on any other Linux box (of which
> > there have been many under my care) so I'm a little nervous about just
> > whacking it.
> >
> > Thanks, once again!
>
> That's a virtual bridge adapater provided for the benefit of any
> virtual guests you might later use. It's normal and safe to ignore,
> or IIRC you can simply turn the libvirtd service off to make it
> disappear.
Once again, Paul, thanks!
I assume that's for XEN or KVM guests? Since this is an eeepc I don't
think I'll be running any such things on it! :) In fact I'm looking around
for services I don't want/need, as I want to keep it fairly tightly closed.
--
---- Fred Smith -- fredex@xxxxxxxxxxxxxxxxxxxxxx -----------------------------
But God demonstrates his own love for us in this:
While we were still sinners,
Christ died for us.
------------------------------- Romans 5:8 (niv) ------------------------------
Attachment:
pgpxtAbiq2Vjv.pgp
Description: PGP signature
-- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
