Yes i've read your patch, but i don't understand what you are
meaning...
and yes, changing the definition of rt_Update is not my first
intention,
but it is the way i've found to fix this.
Backing to the patch... The rt_Update need the ifp and ifa information
to correctly update the route, an
Qing,
Sorry, but your patch doesn't fix the issue, everytime the
route_UpdateMTU* is called the route is set to the ethernet
interface using the gateway address instead of the correct tun interface.
The patch in PR works exactly in that situation as confirmed by Brett.
Thanks,
Luiz
* This
>
> Yes i've read your patch, but i don't understand what you are
meaning...
> and yes, changing the definition of rt_Update is not my first
intention,
> but it is the way i've found to fix this.
>
> Backing to the patch... The rt_Update need the ifp and ifa information
> to correctly update the
At 05:31 AM 3/24/2009, Luiz Otavio O Souza wrote:
Hi,
I read over your patch and I don't think you need to
change the definition of rt_Update() to fix this bug.
Have you read my patch committed to head/user.sbin/ppp/route.c
on 12/18/2008? svn r186308, cvs r1.96.
Please take a look.
Thanks,
Hi,
I read over your patch and I don't think you need to
change the definition of rt_Update() to fix this bug.
Have you read my patch committed to head/user.sbin/ppp/route.c
on 12/18/2008? svn r186308, cvs r1.96.
Please take a look.
Thanks,
-- Qing
Hi Qing,
Yes i've read your patch, but i
-
> From: owner-freebsd-...@freebsd.org [mailto:owner-freebsd-
> n...@freebsd.org] On Behalf Of Luiz Otavio O Souza
> Sent: Monday, March 23, 2009 4:07 AM
> To: n...@freebsd.org; Brett Glass
> Subject: Re: Problems with inward PPTP tunnel
>
> > Just a quick followup: I've fin
P.S. -- Just tried the patches in bin/130159 and bin/131250 and
they do seem to function properly. Please commit.
--Brett Glass
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mai
Luis:
It looks as if bin/130159 ought to fix the problem I am having. I
see that it sets the "IFP" flag in the route update request and
specifies the interface, which ought to be what is needed. I am not
seeing problems with proxy ARP, but that may be because I am
running 7.1-RELEASE and not
Just a quick followup: I've finally figured out a workaround. A hack, to
be sure, but a workaround nonetheless.
I've created a shell script called /etc/ppp/pppfix, which looks like this:
#!/bin/sh
# Fix up PPP routes
sleep 1;
logger -i -t ppp Fixing route: route change -host $1 $2 -ifp $3
route
Just a quick followup: I've finally figured out a workaround. A
hack, to be sure, but a workaround nonetheless.
I've created a shell script called /etc/ppp/pppfix, which looks like this:
#!/bin/sh
# Fix up PPP routes
sleep 1;
logger -i -t ppp Fixing route: route change -host $1 $2 -ifp $3
route
Everyone:
I've routinely used FreeBSD to create firewall routers which
protect the machines inside the firewall from attempted connections
from the outside world, but allow an administrator to "tunnel into"
the LAN using PPTP to do maintenance. I've done this by making the
firewall into a PPT
11 matches
Mail list logo
