Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 10 Dec 2009 22:31:05 -0800
From:      "Li, Qing" <qing.li@bluecoat.com>
To:        "Li, Qing" <qing.li@bluecoat.com>, "Mario Pavlov" <freebsd@abv.bg>, <freebsd-stable@freebsd.org>, <freebsd-current@freebsd.org>
Subject:   RE: proxy arp and MPD in RELENG_8
Message-ID:  <B583FBF374231F4A89607B4D08578A430611E2C7@bcs-mail03.internal.cacheflow.com>
In-Reply-To: <B583FBF374231F4A89607B4D08578A4304673741@bcs-mail03.internal.cacheflow.com>
References:  <1005992950.59541.1260385306946.JavaMail.apache@mail53.abv.bg> <B583FBF374231F4A89607B4D08578A4304673741@bcs-mail03.internal.cacheflow.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Hi,

I think I managed to reproduce this issue. The root cause appears
to be the SIN_PROXY usage, which is no longer part of any routing
entry after the L2/L3 rewrite. As such, the RTM_GET command
should be issued once in the ARP utility, not twice.=20

In addition, since ARP does not apply to PPP link type, the=20
prefix route of the local end point needs to be returned
in order for the subsequent RTM_ADD command to succeed.
I need to update the routing code a bit more to properly
handle such proxy-arp scenario.

In the meantime, please try a hack at

	http://people.freebsd.org/~qingli/ppp-patch.diff

and let me know how it works out for you. The hack appears
to work in my test environment.

I need just a bit more time to work out the permanent
solution in the kernel routing code, as well as the
utilities in the userland.

-- Qing


> -----Original Message-----
> From: owner-freebsd-current@freebsd.org [mailto:owner-freebsd-
> current@freebsd.org] On Behalf Of Li, Qing
> Sent: Wednesday, December 09, 2009 12:04 PM
> To: Mario Pavlov; freebsd-stable@freebsd.org; freebsd-
> current@freebsd.org
> Subject: RE: proxy arp and MPD in RELENG_8
>=20
>=20
> Let me look into this issue and work with you offline.
>=20
> I have been quite busy with day job and just starting to slowly
> resume my FreeBSD work.
>=20
> -- Qing
>=20
>=20
> -----Original Message-----
> From: owner-freebsd-stable@freebsd.org on behalf of Mario Pavlov
> Sent: Wed 12/9/2009 11:01 AM
> To: freebsd-stable@freebsd.org; freebsd-current@freebsd.org
> Subject: proxy arp and MPD in RELENG_8
>=20
>=20
>  Hi,
> some time ago I noticed that there's a problem with the new arp
> implementation - proxy arp was somehow not working when mpd is
involved.
> I decided to try this out again assuming it was fixed for the
> release...unfortunately the problem is still there...
> Here are the last few lines of the mpd output:
>=20
>=20
> [B-1] IPCP: state change Ack-Rcvd --> Opened
> [B-1] IPCP: LayerUp
> [B-1]   192.168.10.1 -> 192.168.10.50
> [B-1] IFACE: Connecting tcpmssfix
> [B-1] IFACE: Add address 192.168.10.1/32->192.168.10.50 to ng0
> [B-1] exec: /usr/sbin/arp -S 192.168.10.50 0:e0:28:62:e:9 pub
> [B-1] system: command "/usr/sbin/arp" returned 256
> [B-1] IFACE: Up event
> [B-1] IFACE: idle-timeout: 1800 seconds
> [B-1] IFACE: Change interface flags: -0 +1
>=20
>=20
> there this is mpd.conf:
>=20
>=20
> startup:
>=20
> default:
>         load pptp_server
>=20
> pptp_server:
>=20
>         set ippool add pool1 192.168.10.50 192.168.10.99
>=20
>         create bundle template B
>         set iface enable proxy-arp
>         log +iface2
>         set iface idle 1800
>         set iface enable tcpmssfix
>         set ipcp yes vjcomp
>         set ipcp ranges 192.168.10.1/32 ippool pool1
>         set ipcp dns 192.168.10.1
>         set bundle enable compression
>         set ccp yes mppc
>         set mppc yes e40
>         set mppc yes e128
>         set mppc yes stateless
>=20
>         create link template L pptp
>         set link action bundle B
>         set link enable multilink
>         set link yes acfcomp protocomp
>         set link no pap chap
>         set link enable chap
>         set link keep-alive 10 60
>         set link mtu 1460
>         set pptp self pub.ip.add.res
>         set link enable incoming
>=20
>=20
> this is probably the most common VPN setup and it was working fine
with
> 7.2-STABLE but after I upgraded to 8-STABLE it broke up...
> Is there a workaround or a plan to fix this? Or should I just go back
> to RELENG_7?
>=20
> thank you.
>=20
> P.S. this is discussed in the forums as well:
> http://forums.freebsd.org/showthread.php?t=3D8427
>=20
> -----------------------------------------------------------------
> ???????? ? ?????? ???????? ?? iZone.bg ? ??????? ???? ?? 5?? ???????
> Acer!
> http://www.izone.bg/6/index.html
> _______________________________________________
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-
> unsubscribe@freebsd.org"
>=20
> _______________________________________________
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-
> unsubscribe@freebsd.org"



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?B583FBF374231F4A89607B4D08578A430611E2C7>