On 26/05/13 02:00, Phil Dobbin wrote:
Hi, all.
I've got several machines on a LAN behind a NAT with DHCP assigning
always the same addresses from a dynamic IP.
A couple of days ago the IP changed & since then, one of the machines
running Fedora 17 always fails first time to connect to the netwo
Am 29.05.2013 22:14, schrieb Timothy Murphy:
> Patrick O'Callaghan wrote:
>
Timothy Murphy:
> Sorry, I mis-read the query.
> I was thinking of a DHCP server
The same basic answer still stands: A DHCP server, by default, doles
out dynamic IPs.
>>>
>>> I agree that dhc
Am 29.05.2013 19:34, schrieb Timothy Murphy:
> Tim wrote:
But are you talking about configuring a DHCP client or server?
>>
>> Timothy Murphy:
>>> Sorry, I mis-read the query.
>>> I was thinking of a DHCP server
>>
>> The same basic answer still stands: A DHCP server, by default, doles
>> o
On 30.05.2013 05:30, staticsafe wrote:
> Er, why are we disabling IPv6?
Er, for that very reason we are using 'dig'. ;)
…
> dig mirrors.fedoraproject.org
poma
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/m
On 30.05.2013 04:55, Patrick O'Callaghan wrote:
…
> I used to use ddclient but actually I've found that the least effort
> solution is just to let my router do it. Many home routers now support
> DynDNS (and similar services) directly, so I just configure it once and
> forget about it. Make sure to
On Thu, May 30, 2013 at 05:19:39AM +0200, poma wrote:
> On 26.05.2013 17:35, Phil Dobbin wrote:
> …
> > '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; Nam
On 26.05.2013 17:35, Phil Dobbin wrote:
…
> '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"'
curl -4
"https://mirrors.fedoraproject
On Thu, 2013-05-30 at 09:45 +0930, Tim wrote:
> If you felt like a lot of hard work, you could probably write
> something
> that was triggered by your DHCP client to talk to dyndns, if DHCP was
> responsible for your address changes. Less work would be to use
> NetworkManager's despatch scripts to
Allegedly, on or about 29 May 2013, Timothy Murphy sent:
> You all seem to be finding it difficult to follow my meaning.
> I'm saying that the term "dynamic IP" is normally used
> to refer to an ISP giving the same client different IP addresses
> at different times, in order to to limit the number
On Wed, 2013-05-29 at 21:14 +0100, Timothy Murphy wrote:
> Patrick O'Callaghan wrote:
>
> >> > Timothy Murphy:
> >> >> Sorry, I mis-read the query.
> >> >> I was thinking of a DHCP server
> >> >
> >> > The same basic answer still stands: A DHCP server, by default, doles
> >> > out dynamic IPs.
>
On 05/29/2013 01:14 PM, Timothy Murphy wrote:
You all seem to be finding it difficult to follow my meaning.
I'm saying that the term "dynamic IP" is normally used
to refer to an ISP giving the same client different IP addresses
at different times, in order to to limit the number of address requir
Patrick O'Callaghan wrote:
>> > Timothy Murphy:
>> >> Sorry, I mis-read the query.
>> >> I was thinking of a DHCP server
>> >
>> > The same basic answer still stands: A DHCP server, by default, doles
>> > out dynamic IPs.
>>
>> I agree that dhcp by default gives an IP address in a given range o
On Wed, 2013-05-29 at 18:34 +0100, Timothy Murphy wrote:
> Tim wrote:
>
> > Tim:
> >>> But are you talking about configuring a DHCP client or server?
> >
> > Timothy Murphy:
> >> Sorry, I mis-read the query.
> >> I was thinking of a DHCP server
> >
> > The same basic answer still stands: A DHCP
Tim wrote:
> Tim:
>>> But are you talking about configuring a DHCP client or server?
>
> Timothy Murphy:
>> Sorry, I mis-read the query.
>> I was thinking of a DHCP server
>
> The same basic answer still stands: A DHCP server, by default, doles
> out dynamic IPs.
I agree that dhcp by default g
Tim:
>> But are you talking about configuring a DHCP client or server?
Timothy Murphy:
> Sorry, I mis-read the query.
> I was thinking of a DHCP server
The same basic answer still stands: A DHCP server, by default, doles
out dynamic IPs.
In other words, until an administrator customises the
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?
> But are you talking about configuring a DHCP client or server?
Sorry, I mis-read the query.
I was thinking of a DHCP server
--
Timothy M
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 DHC
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 t
Phil Dobbin wrote:
> I've got several machines on a LAN behind a NAT with DHCP assigning
> always the same addresses from a dynamic IP.
As a matter of interest, how do you configure DHCP
to work with a dynamic IP?
I use ddclient with dyndns,
but are you saying one doesn't need to do something l
On 05/26/2013 05:11 AM, Phil Dobbin wrote:
The same address assigned is in the 192.168.1.xxx range & is, obviously,
internal. The dynamic IP is external & this is the one that changes & I
have no control over it (& I can't get a static IP unfortunately).
Sorry, I'd been under the impression tha
On Sun, 2013-05-26 at 02:00 +0100, Phil Dobbin wrote:
> I've got several machines on a LAN behind a NAT with DHCP assigning
> always the same addresses from a dynamic IP.
>
> A couple of days ago the IP changed & since then, one of the machines
> running Fedora 17 always fails first time to conne
On 05/26/2013 02:54 PM, Mikkel L. Ellertson wrote:
[...]
> Dumb question - have you checked the network connection? See if
> changing the cable or the port on the switch helps. It seams strange
> that the external IP address changing would cause this, but for some
> strange reason hardware probl
On 05/26/2013 02:54 PM, Mikkel L. Ellertson wrote:
> On 05/26/2013 07:18 AM, Phil Dobbin wrote:
>> On 05/26/2013 11:54 AM, Mikkel L. Ellertson wrote:
>>> On 05/25/2013 08:00 PM, Phil Dobbin wrote:
Hi, all.
I've got several machines on a LAN behind a NAT with DHCP assigning
alwa
On 05/26/2013 07:18 AM, Phil Dobbin wrote:
> On 05/26/2013 11:54 AM, Mikkel L. Ellertson wrote:
>> On 05/25/2013 08:00 PM, Phil Dobbin wrote:
>>> Hi, all.
>>>
>>> I've got several machines on a LAN behind a NAT with DHCP assigning
>>> always the same addresses from a dynamic IP.
>>>
>>> A couple of
On 05/26/2013 11:54 AM, Mikkel L. Ellertson wrote:
> On 05/25/2013 08:00 PM, Phil Dobbin wrote:
>> Hi, all.
>>
>> I've got several machines on a LAN behind a NAT with DHCP assigning
>> always the same addresses from a dynamic IP.
>>
>> A couple of days ago the IP changed & since then, one of the ma
On 05/26/2013 02:21 AM, Joe Zeff wrote:
> On 05/25/2013 06:00 PM, Phil Dobbin wrote:
>> I've got several machines on a LAN behind a NAT with DHCP assigning
>> always the same addresses from a dynamic IP.
>>
>> A couple of days ago the IP changed & since then, one of the machines
>> running Fedora
On 05/25/2013 08:00 PM, Phil Dobbin wrote:
> Hi, all.
>
> I've got several machines on a LAN behind a NAT with DHCP assigning
> always the same addresses from a dynamic IP.
>
> A couple of days ago the IP changed & since then, one of the machines
> running Fedora 17 always fails first time to conne
On 05/25/2013 06:00 PM, Phil Dobbin wrote:
I've got several machines on a LAN behind a NAT with DHCP assigning
always the same addresses from a dynamic IP.
A couple of days ago the IP changed & since then, one of the machines
running Fedora 17 always fails first time to connect to the network:
l
Hi, all.
I've got several machines on a LAN behind a NAT with DHCP assigning
always the same addresses from a dynamic IP.
A couple of days ago the IP changed & since then, one of the machines
running Fedora 17 always fails first time to connect to the network:
launch Thunderbird, no start screen,
29 matches
Mail list logo
