Ethernet bridging weirdness

[Douglas Stanley]

Another thing I noticed that's different between the two machines as
well. On the machine with the working bridge, rpc.statd gets started
automatically (as I configured it in /etc/default/nfs-common),
however, on the machine that fails to bring up the bridge, that
machine also fails to start rpc.statd automatically (even though it's
configured exactly the same way).

Not sure if they're related or not.

Doug

On Wed, Sep 15, 2010 at 11:19 AM, Serge E. Hallyn
<serge.hallyn at canonical.com> wrote:
> Quoting Douglas Stanley (douglas.m.stanley at gmail.com):
>> On Tue, Sep 14, 2010 at 10:30 PM, Serge E. Hallyn
>> <serge.hallyn at canonical.com> wrote:
>> > Quoting Douglas Stanley (douglas.m.stanley at gmail.com):
>> >> True, it is manual, but it's a bridge. I can't seem to find it now,
>> >> but that's precisely how it was supposed to be configured, according
>> >> to the documentation I was going by (I think it was one of the KVM
>> >> oriented guides). And, no, it's not showing up when I do a brctl show
>> >> on this one server (it shows up fine on the other *identical* server).
>> >
>> > How does it show up?  'ifconfig -a', 'ifconfig', and 'brctl show' output?
>> >
>> The bridge device doesn't show up using any of those commands (not
>
> On the machine where it does
>
>
>



-- 
Please avoid sending me Word or PowerPoint attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html