Weird network problem

[Phil Dobbin]

On 05/27/2013 04:51 PM, Tim wrote:

> Allegedly, on or about 27 May 2013, Timothy Murphy sent:
>> As a matter of interest, how do you configure DHCP
>> to work with a dynamic IP? 
> 
> Um, generally you don't...  It does that by default.  Your DHCP client
> (your usual personal computer) asks a DHCP server for an address, and
> the DHCP server tells it what to do.  It's only people trying to bypass
> that automatic remote control, partially or totally, that go about
> trying to change the DHCP client configuration.
> 
> But are you talking about configuring a DHCP client or server?

Right. Computer asks server for address & it's done by automatic lease.

The state of the play at the moment is the network problem still occurs.
I restored (via Clonezilla) from a known good backup that was taken
before all this nonsense started & the box is still doing it.

So, to make sure it wasn't a hardware problem, I spun up a VM &
installed Ubuntu 13.04. It has no such problems & apt-get functions
normally.

When using yum update, curl is the culprit, throwing error after error:

'Could not get metalink
https://mirrors.fedoraproject.org/metalink?repo=updates-released-f17&arch=x86_64
error was
14: curl#6 - "Could not resolve host: mirrors.fedoraproject.org; Name or
service not known"'

Anybody know anything about curl under these circumstances? Is it a
certificate problem? Curl is installed via the repos so it's nothing out
of the ordinary.

Any help appreciated,

Cheers,

  Phil...

-- 
currently (ab)using
CentOS 5.9 & 6.4, Debian Squeeze & Wheezy, Fedora Beefy, Spherical &
That Damn Cat, Lubuntu 12.10, OS X Snow Leopard & Ubuntu Precise,
Quantal & Raring
GnuPG Key : http://www.horse-latitudes.co.uk/publickey.asc