Mike,
This seems like a DSL router's problem. Because PPTP encapsulates PPP
using GRE, which is neither TCP nor UDP, routers sometimes can not NAT
PPTP traffic. Some router conqurs this problem by simply "passing
through" GRE packets (and hence this feature is sometimes called "VPN
Pass Through")
Mike,
From: "Mike Jakubik" <[EMAIL PROTECTED]>
Subject: Re: PPTP VPN using MPD behind NAT help needed
Date: Wed, 14 Jul 2004 22:15:49 -0400 (EDT)
> > This seems like a DSL router's problem. Because PPTP encapsulates PPP
> > using GRE, which is neither TCP nor UDP, routers sometimes can not NAT
>
akubik" <[EMAIL PROTECTED]>
Subject: Re: PPTP VPN using MPD behind NAT help needed
Date: Wed, 14 Jul 2004 23:36:57 -0400 (EDT)
> Motonori Shindo said:
>
> >> > This seems like a DSL router's problem. Because PPTP encapsulates PPP
> >> > using GRE, which is n
Alexander,
Most implementations fill target hardware address (which I will refer
to as 'THA' hereafter) with zero in ARP Request, so tcpdump omits to
print it out in that case. If THA is not filled with zero, tcpdump
prints it out with braces as you just saw.
I don't know what OS of what version
pd.links]
AC0:
set link type pppoe
set pppoe iface bge0
set pppoe service "*"
set pppoe enable incoming
set pppoe disable originate
AC1:
set link type pppoe
set pppoe iface bge0
set pppoe service "*"
set ppp
Gleb,
From: Gleb Smirnoff <[EMAIL PROTECTED]>
Subject: Re: Netgraph mpd as a PPPoE access concentrator
Date: Mon, 18 Jul 2005 15:06:36 +0400
> On Sun, Jul 10, 2005 at 04:51:28PM +0900, Motonori Shindo wrote:
> M> I'm trying to use Netgraph (mpd) as a PPPoE access concentra
.
Regards,
Motonori Shindo
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
; >> This sounds like "proxy ARPing" is enabled by default on your
> >> particular flavor of Linux. I don't think they all do that,
> >> hopefully, any more than ipforwarding should be enabled by default
> >> just because a machine has two NICs.
>
out this is [EMAIL PROTECTED]
> Good Luck!
>
> --
> Justin
>
>
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-net" in the body of the message
=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=
+++
|.. .|| Motonori Shindo
|_~__||
| .. |~~_~| S
MU Monarch Project has a Mobile-IPv4 support for FreeBSD, but it only
supports FreeBSD 2.2.2. For more detail, pls refer to:
http://www.monarch.cs.cmu.edu/
=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=
+++
|.. .|| Motonori Shindo
|_~__||
| .. |~~_~| Sr. Syste
) that SA (destination address, Security Protocol(AH/ESP), and SPI)
is properly established. I don't see anything that can prevent it from
working if the policy is specified as 'require'.
Will anybody here help me understand this?
Regards,
=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--
Gary,
From: Gary Corcoran <[EMAIL PROTECTED]>
Subject: Re: WEP problems with ndis and ath drivers
Date: Tue, 23 Mar 2004 23:05:11 -0500
> Sam Leffler wrote:
>
> > It appears your AP requires shared-key authentication to associate when
> > WEP is enabled. The current code in the tree does not
Kenneth,
Well, this is a bit off topic of this mailing list but let me
continue:-)
From: "Kenneth D. Merry" <[EMAIL PROTECTED]>
Subject: Re: WEP problems with ndis and ath drivers
Date: Tue, 23 Mar 2004 22:52:04 -0700
> > Shared-key authentication is in fact a worse option than open
> > authenti
13 matches
Mail list logo