On Fri, Jun 17, 2011 at 12:40:29PM +0900, Hiroki Sato wrote:
> jhell wrote
> in <20110617022950.ga58...@dataix.net>:
>
> jh> Gosh, Wouldnt it be something if we could store our dynamic resolver
> jh> information with the interface in the same sort of fashion that we store
> jh> our routing ta
jhell wrote
in <20110617022950.ga58...@dataix.net>:
jh> Gosh, Wouldnt it be something if we could store our dynamic resolver
jh> information with the interface in the same sort of fashion that we store
jh> our routing tables ? and then modify our routines in the library to look
jh> them up via
On Thu, Jun 16, 2011 at 10:29:50PM -0400, jhell wrote:
>
>
> On Thu, Jun 16, 2011 at 01:53:17AM +0900, Hiroki Sato wrote:
> > Hi,
> >
> > I would like your comments about the following issue and proposal.
> >
> > The background is as follows. The resolvconf(8) utility has been
> > importe
On Thu, Jun 16, 2011 at 1:01 PM, Rick Macklem wrote:
>> * We try to reconnect again, and again, and again
>> * the process in this state is unkillable
>>
> If you use the "intr" mount option, then an nfs reconnect
> should be killable. I know diddly about amd, so I can't
> help beyond that.
I
> * We try to reconnect again, and again, and again
> * the process in this state is unkillable
>
If you use the "intr" mount option, then an nfs reconnect
should be killable. I know diddly about amd, so I can't
help beyond that.
rick
___
freebsd-ne
Hi,
> On Thu, 16 Jun 2011 13:00:32 +
> "Bjoern A. Zeeb" said:
bzeeb> I can imaging ports like mpd, ... to join this scheme and by then
bzeeb> there might be different "ppp" or "dhcpv4", "dhcpv6" or even different
bzeeb> "slaac". The advantage of this one is that if I prefer dhcpv6 o
The following reply was made to PR kern/157802; it has been noted by GNATS.
From: "Andrey V. Elsukov"
To: bug-follo...@freebsd.org, alexey_kovale...@inbox.ru
Cc:
Subject: Re: kern/157802: [dummynet] [panic] kernel panic in dummynet
Date: Thu, 16 Jun 2011 15:05:59 +0400
Hi, Alexey
can you p
On Jun 16, 2011, at 5:28 AM, Hiroki Sato wrote:
Hi Umemoto-san, Sato-san,
> Our openresolv currently supports $interface_order with shell pattern
> matching only. What I thought was
>
> interface_order="lo lo[0-9]* *:ppp *:slaac *:dhcpv4 [a-z]*[0-9]*:*"
Hmm, indeed we do and I hadn't actually
On Jun 15, 2011, at 10:19 PM, Aleksandr Rybalko wrote:
> Maybe better to add default but changeable preference for each iface,
> like STP do:
> 1000Base - 20
> 100Base - 200
> PPP - 2000
>
> sources able to give IPv6 info for as we can give more preference
> (1000Base w/ IPv6 info - 19, 100 w/ v6
> > I do not recommend to use the rc.d/network_ipv6 script for manual
> > configuration because it often ends up an incomplete configuration as
> > you experienced. Rebooting the system would be better. The
> > rc.d/netif script on 9.X works well for that purpose without a
> > reboot, though
Charles Sprickman wrote
in <4df9accc.5070...@bway.net>:
sp> > LLA is a MUST for every IPv6-speaking interface, not for automatic
sp> > router discovery only. This is because ICMPv6 heavily depends on it.
sp> > Without LLA some unexpected and/or inconsistent behaviors can happen,
sp> > espe
Hiroki Sato wrote:
> Charles Sprickman wrote
> in <4df9970d.5000...@bway.net>:
>
> sp> -Edit rc.conf to include your IPv6 IP(s) and default route, specify
> sp> which interfaces will run IPv6, and enable IPv6:
> sp>
> sp> ipv6_enable="YES"
> sp> ipv6_network_interfaces="lo0 bce1"
> sp> ipv6_def
12 matches
Mail list logo
