[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: network card bridging failing on wheezy

On 10/11/14 12:50 AM, Christian Seiler wrote:

Am 10.11.2014 01:33, schrieb Gary Dale:

On 09/11/14 03:30 PM, Christian Seiler wrote:

Could you post the contents of your /etc/default/networking?
Specifically, it should have either no explicit settings (everything
commented out) or the following settings (which are default):

CONFIGURE_INTERFACES=yes
EXCLUDE_INTERFACES=          # (empty)

Just has comments. No active settings.


You're under Wheezy, so I'm assuming sysvinit + LSB, could you also
check whether the networking script is started at boot?

ls -l /etc/rc*.d/S??networking

(should turn up a single link in /etc/rcS.d)

Yes.


If both is the way it should be, could you perhaps set VERBOSE=yes in
/etc/default/networking and look for any relevant boot messages? Not
dmesg/syslog, but on the console.[1]

Also, might be relevant: did you install any software that might take
over network configuration? Such as NetworkManager or wicd or the such?

No.

When I look at the console messages, the networking doesn't show up even
with the zz-wait script inserted. Similarly, running
/etc/init.d/networking start doesn't work.

This is really strange... What does "doesn't work" mean in this context?
No output? A message that it's doing what it wants to do, but it doesn't
actually do it? Some error message?

I just looked at the /etc/init.d/networking source, and I don't see
anything in there that would make it not work other than
         if init_is_upstart; then
                 exit 1
         fi
Are you by chance using upstart as init? (Although, while I haven't
tried that with wheezy, ifupdown does install an alternative mechanism
with upstart, so that shouldn't matter...)

If not, what does the following command tell you?

   ifup -a -v
Aha! ifup didn't run, so I reinstalled ifupdown. This removed iproute2 and replaced it with iproute along with reinstalling ifupdown. Now my network is coming up properly. I suspect this is a problem caused by the wheezy-backports Samba package not getting along with the regular Wheezy packages. Fortunately it gets along well enough to give me a working Samba environment even with the older packages. 

Thanks Christian!
Reply to: