On Thu, Mar 11, 2010 at 09:20:00AM -0500, Michael Butler wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 03/11/10 05:52, Li, Qing wrote:
> >I spent some time looking into the issue and found the problem
> >is the if_tap interface turns out to be one of those interfaces
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/11/10 05:52, Li, Qing wrote:
>I spent some time looking into the issue and found the problem
>is the if_tap interface turns out to be one of those interfaces
>that claims to be of IFT_ETHER type, but does not touch the
>"if_lin
>
> Without the route.h patch, I can't ping 127.0.0.1 or the local or
> remote address of the OpenVPN tunnel (on tap0). In fact, you
> can't even build OpenVPN from ports as it'll fail its self-test.
>
Please see my previous clarification email on the what and the why
about the "route.h.d
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/10/10 12:18, Li, Qing wrote:
> Could you please provide me with more information, such as your
> ifconfig and netstat output? What's the error message?
With or without r204902, I do not see any difference in ifconfig or
netstat output. Addresses
gt; From: owner-freebsd-curr...@freebsd.org [mailto:owner-freebsd-
> > > curr...@freebsd.org] On Behalf Of Renato Botelho
> > > Sent: Tuesday, March 09, 2010 10:47 AM
> > > To: FreeBSD Current
> > > Subject: Error 127.0.0.1: no route to host
> > >
> > &
bsd-
> curr...@freebsd.org] On Behalf Of Michael Butler
> Sent: Wednesday, March 10, 2010 4:19 AM
> To: Doug Barton
> Cc: freebsd-current@freebsd.org
> Subject: Re: Error 127.0.0.1: no route to host
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 03/09/10 21:00,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/09/10 21:00, Doug Barton wrote:
> On 03/09/10 12:14, Li, Qing wrote:
>> This error was caused by my commit r204902 from yesterday.
>>
>> Please try patch at
>>
>> http://people.freebsd.org/~qingli/route.h.diff
>
> This doesn't appear to be
On 03/09/10 12:14, Li, Qing wrote:
> This error was caused by my commit r204902 from yesterday.
>
> Please try patch at
>
> http://people.freebsd.org/~qingli/route.h.diff
This doesn't appear to be committed yet, is it still the best fix?
Doug
--
... and that's just a little bi
Julian Elischer wrote:
Li, Qing wrote:
This error was caused by my commit r204902 from yesterday.
[...]
I remember saying "well the patch itself is basically ok but I don't
know about the side effects". (about the ARPv2 change in general)
I'm guessing you have had a rather interesting lea
Li, Qing wrote:
This error was caused by my commit r204902 from yesterday.
[...]
I remember saying "well the patch itself is basically ok but I don't
know about the side effects". (about the ARPv2 change in general)
I'm guessing you have had a rather interesting learning experience
about h
On Tue, Mar 9, 2010 at 5:14 PM, Li, Qing wrote:
> This error was caused by my commit r204902 from yesterday.
>
> Please try patch at
>
> http://people.freebsd.org/~qingli/route.h.diff
Patch fixed the problem, thanks for the quick reply and fix.
--
Renato Botelho
_
ng
> Sent: Tuesday, March 09, 2010 11:05 AM
> To: Renato Botelho; FreeBSD Current
> Subject: RE: Error 127.0.0.1: no route to host
>
> Thanks for the report, I am looking at it and will get back to you.
>
> -- Qing
>
>
> > -Original Message-
> > From:
rrent
> Subject: Error 127.0.0.1: no route to host
>
> I updated my 9.0-current amd64 today on rev. 204915 and start
> to get errors like this
>
> 127.0.0.1: no route to host
>
> I boot using kernel.old and everything back to normal. I don't know
> exactly revisi
I updated my 9.0-current amd64 today on rev. 204915 and start
to get errors like this
127.0.0.1: no route to host
I boot using kernel.old and everything back to normal. I don't know
exactly revision of my kernel.old because last change made on
sys/conf/newvers.sh simply removed this information f
14 matches
Mail list logo
