12.04.2 LTS, new install, network broken

[Tom H]

On Mon, Jul 8, 2013 at 11:22 PM, Ric Moore <wayward4now at gmail.com> wrote:
> On 07/07/2013 07:21 PM, Tom H wrote:


>> Do you have a blog where you could let off steam?
>>
>> If your experience with installing 12.04 is typical, don't you think
>> that this list, the Ubuntu forums, and Launchpad would be buzzing
>> about this?
>
> Venting on Bikeshed is probably more productive. One can cuss, but we can
> cuss back AS WELL AS remark on your parentage, or lack thereof. The more the
> merrier. I can feel for Gene though. There was a time when you could drive a
> nail into a config file and have it stay that way. Alas, and alack. Those
> sweet gentle days are history now.

I don't care where anyone vents as long as it's not while he/she's
asking for help because it just drowns out the technical request -
especially if the pseudo-technical report is "my networking's broken."

It's far better to say "my networking's broken and these are the
troubleshooting steps that I've taken, what next?" or "my networking's
broken and I don't know what to do; what steps should I take to
troubleshot and fix it?". All the other hot air is just that.

You can control resolv.conf via the configs of dhclient, ifupdown, and
NM and "nail" it to be exactly what you want it to be. You have to use
the tools with which you're provided rather than ignore them and try
to get around them.


> I think many will agree, Network Mangler needs a wake and a funeral for
> itself, after someone develops a suitable replacement. If I had the chops, I
> would surely do it.

NM's been improving with every release but it's been plagued with a
bad rep because it behaved badly when it was first released.

You can best configure it to do what you want by dropping config files
into "/etc/NetworkManager/system-connections/". The syntax is
convoluted but it works. NM can also read "/etc/network/interfaces" in
the same way that ifupdown does...