Hello,
On 10 July 2014 15:27, Harald Dunkel wrote:
>>> Come on, does this really matter?
>> It does indeed.
> Sorry to say, but it doesn't. The current configuration of
> other hosts or services in a network is sometimes unpredictable.
> Esp. for IPv6 in a foreign LAN there is a high probability
On 07/10/14 13:35, Andrew Shadura wrote:
> Hello,
>
> On 10 July 2014 13:27, Harald Dunkel wrote:
>>> Maybe I'm misunderstanding something, but why do you add this line to
>>> your interfaces file if you don't have a DHCPv6 server?
>
>> Come on, does this really matter?
>
> It does indeed.
>
Andrew Shadura wrote:
>
> Maybe I'm misunderstanding something, but why do you add this line to
> your interfaces file if you don't have a DHCPv6 server?
Come on, does this really matter?
Point is that the Debian host got stuck at boot time
without any way out. This is fatal.
Regards
Harri
--
Hello,
On 10 July 2014 13:27, Harald Dunkel wrote:
>> Maybe I'm misunderstanding something, but why do you add this line to
>> your interfaces file if you don't have a DHCPv6 server?
> Come on, does this really matter?
It does indeed.
> Point is that the Debian host got stuck at boot time
> wi
Andrew Shadura wrote:
> Harald Dunkel wrote:
> > auto eth0
> > iface eth0 inet6 dhcp
>
> Maybe I'm misunderstanding something, but why do you add this line to
> your interfaces file if you don't have a DHCPv6 server?
Perhaps it is a mobile (or semi-mobile) device? That has always
Hi,
On 25 June 2014 16:07, Harald Dunkel wrote:
> If I set /etc/network/interfaces to
> ## The primary network interface (eth0)
> auto eth0
> iface eth0 inet6 dhcp
> without having a DHCP6 server in my LAN, then the next boot
> gets stuck (even for single user mode). I wa
Package: ifupdown
Version: 0.7.48.1
If I set /etc/network/interfaces to
## The loopback network interface
auto lo
iface lo inet loopback
## The primary network interface (eth0)
auto eth0
iface eth0 inet6 dhcp
without having a DHCP6 server in my LA
7 matches
Mail list logo