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.
I find that with F10 then KVM networking almost but not quite works as expected.
It seems that regardless of the command line kvm options, I get the internal
network, 10.x.x.x, and the associated DNS. Since I have given the correct MAC
address to use, I have not found a reasonable way to get kvm to pass the MAC
address up directly and get an IP from my internal dhcp server. Since this works
on my two existing FC6 kvm servers, something has changed over time, and I can't
find a doc for it.
This results in packets using the kvm host MAC address, not at all what I want,
since I would like to move some of my virtual servers to a newer release and
hardware. I can probably hack things to get it working, but I assume there's a
more correct way than building and configuring all my own bridge stuff, etc.
Any pointer to doc on this? I need to start servers on demand and without a
human in the loop, so cute GUI managers aren't the solution.
--
Bill Davidsen <davidsen@xxxxxxx>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
