Good news, just tag the post [SOLVED]

1 members found this post helpful.

gmgf: Don't think I can, as I didn't originate the thread - I just hi-jacked it!

I think KJH originated it, so perhaps he could mark it solved?

Cheers,

--
Pete

Edit: Pete --

For future reference ... How did you add --without-gnome to the SlackBuild script ?

Thanks.

Woo Hoo !

You're welcome, Pete.

Now if only NetworkManager would behave with flakey Wireless Routers, I could replace wicd with NM.

That however, is something for the upstream team and I don't know where to begin ...

I would sure like to have the clicky-clicky NM VPN Management Tools though <G>

Marking this thread 'solved' as gmgf suggested.

-- kjh

Just as a matter of interest, what's the issue with wireless routers?

I'm using a TP-Link router here, but before that I was using the 'phone company supplied router and I've used a Belkin without any issues. I also use NM on my laptop when travelling, and never had any problems. Maybe I've just been lucky?

--
Pete

Pete --

Hoo boy ... where to begin <G>

I am not exactly sure what my issue here at home is but others have reported similar issues with NM on certain Wireless APs.

I also used to see it on CentOS Boxes running NetworkManager ( before we decided to disable NM on CentOS Servers )

The issue I have is that NM gets stuck in an infinite loop where it disables the Network Connection at the slightest hiccup, then it tries to reconnect but it never settles.

Hardware-wise, here at home, I've got a single AT&T DSL Internet Connection with a few Static IP Addrs.

I've got two networks, each with a Wireless AC Router ( Home and Work ) and both wireless APs broadcast on their 2 GHz and 5 GHz radios.

Then there is also a Wireless AC Extender so I can get at the Home Network from my 'lab' (<G> aka the garage <G>)...

So for all intents and purposes, counting the AT&T DSL Modem ( ARRIS NVG599 ), I've got 6 APs behind the Single AT&T DSL Wire !

I can't get at the 'juicy stuff' in the AT&T DSL Modem and I suspect it's subtly borked but it works for all Clients on either of my LANs except for the NetworkManager Client.

All Clients includes Slackware 13.37, 14.1, Current as well as Win7, Win10, Win2008, CentOS 5, CentOS 6 and various Android thingies.

I also run VMWare WorkStation on my New Work Laptop ( Slackware64 Current + Multilib ) and NM does not seem to like the VMWare vmnetX interfaces ... Network Connections on VMWare fail when I enable NM.

What I see in /var/log/syslog is that NM endlessly connects, then drops my wireless connection, never giving me a solid Network Connection.

I see the same issues in /var/log/messages on the CentOS Boxes with NM Activated -- not only in my Lab but in the field too so I am thinking there's a fundamental flaw in the NM design but I can't prove that.

Android, Windows, the wicd interface and 'hand-edited' configs on the other hand allow me to select any one of the Wireless AP's or my ethX -- they all 'just work'.

I have hand-configured VPN connections for now and NM just isn't worth the effort.

-- kjh

p.s. This is NM on CentOS 6.x which also misbehaves so the issue has been there for some time:

Interesting! I don't move around as much as I did before I retired 2 years ago, but I've never had an issue with NM anywhere here in the UK, or indeed in Europe. I'm pretty sure our regulatory environment is not that much different from the US. Maybe our telecoms companies use better routers? Er, no, I don't really believe that, either!

Here's how I configured the config to ignore gnome:
but beware - it borks building with 1.2.X !!!

--
Pete