From: Ruslan Ermilov <[EMAIL PROTECTED]>
> > If the reason is "Prevent icmp_reflect() from calling ip_output() with
> > a NULL route pointer which will then result in the allocated route's
> >~
> > reference count never being dec
From: Markus Stumpf <[EMAIL PROTECTED]>
> On Mon, Apr 15, 2002 at 11:07:53AM +0900, Keiichi SHIMA / ?$BEg7D0l?(B wrote:
> > Does anyone know where is the document for configuring IPv6 on
> > FreeBSD, if any? The NetBSD web page has a really cool manual
> > (http://w
Hi,
From: Ruslan Ermilov <[EMAIL PROTECTED]>
> I strongly object to this change. BSD historically didn't allow for
> ip_output() to be called with the NULL route pointer. I changed this
I don't know the history of BSD, but, if the reason is the history
(that BSD didn't allow NULL route), I ag
Hi,
Does anyone know where is the document for configuring IPv6 on
FreeBSD, if any? The NetBSD web page has a really cool manual
(http://www.netbsd.org/Documentation/network/ipv6/) for IPv6 people
using NetBSD. I'm looking for such a document for FreBSD.
---
Keiichi SHIMA
IIJ Research Laborato
From: "Merlin" <[EMAIL PROTECTED]>
> If I understand it correctly, all I need to do on a network host is set
> ipv6_enable="YES"
>
> and the rest is done automagically.
Correct.
> net.inet6.forwarding=0
> net.inet6.accept_rtadv=1
> rtsol
>
> are all set automatically from the rc.network6 sta
From: Markus Stumpf <[EMAIL PROTECTED]>
>
> Thanks a lot! I have applied the patches and it works only partially.
Sorry, it needs more work...
Please revert the previous patches, and try with these attached again.
---
Keiichi SHIMA
IIJ Research Laboratory <[EMAIL PROTECTED]>
KAME Project <[EM
Hi,
From: Markus Stumpf <[EMAIL PROTECTED]>
> I am trying to get dnscache running with IPv6 patches.
> dnscache binds to the IPv6 unqualified address "::". This works fine
> and I get (from netstat)
> udp46 0 0 *.53 *.*
> As the sending address the IPv6 unqualifi
Hi Luigi,
Luigi Rizzo wrote:
>
> so i have a question for you -- the next step on this kind of
> optimizations is to avoid that m_pullup() allocates an mbuf
> when data is already contiguous and in a writable (non-shared)
> cluster.
>
> Garret was suggesting a new interface for this, at the beg
Hi Bosko,
Bosko Milekic wrote:
>
> > M_LEADINGSPACE might be meant to return as you were saying. But
> > because of some reasons (maybe a lack of time to implement the
> > complete code), it behaves as we see now. For a long time, in many
> > systems, M_LEADINGSPACE had been returning writable
Hi, Bosko.
Bosko Milekic wrote:
>
> Just because M_LEADINGSPACE may be broken in the other systems does
> not mean that it should be broken in our system as well. I am against
> sacrificying good code in order to deal with the left-over stupidities
> (pardon the seemingly harsh vocabulary) in
Hi, I am one of the KAME members.
> The only problem I can see with this tack is that we might end up
> with M_LEADINGSPACE macro which does something different to the
> same macro in {Net,Open}BSD. I guess we should check what their
> macros do at the moment.
Right. And we will have a problem
Alex Feldman wrote:
>
> I update the driver to accept IPv6 address.
> When I configure interface for both IPv4 and IPv6, everything is good (I
> can
> ping), but when I'm using only IPv6, the remote machine not replying to my
> request.
>
> Is it some configuration problem? Or something els
Julian,
Julian Elischer wrote:
>
> > Please look into the attached patch for FreeBSD-current.
>
> I am looking now
>
> they seem fine..
> If you wish I could commit them..
Yes. As I am not a commiter, could you commit them?
> have you tested them?
Not all parts. I have checked 1) gif over
Hi all,
At first, I told a lie in one point,
> We had removed all the varargs input/output functions from the
> IPv4/IPv6 stacks of the KAME repositry. These modifications will
> make
We removed all the varargs functions from the IPv4 stack (#ifdef'ed
for FreeBSD), but preserved for the IPv6 s
14 matches
Mail list logo
