On Thu, Apr 22, 2004 at 03:17:31PM +0200, roberto.trovo@redix.it wrote:
> Johnnie Chen Wrote:
[...]
> The arp table is:
> bambolotto:/root> arp -a
> ? (xx.xx.xx.xx) at 00:06:1b:d9:83:3f on rtk0
> ? (192.168.0.1) at 00:a0:a2:00:25:69 on vr0
> ? (192.168.0.82) at (incomplete) on vr0
> ? (192.168.0.82) at 00:40:63:c9:cb:ec on vr0 permanent published (proxy only)

This is weird, having the two entries.

> bambolotto:/root>
> 
> My question are:
> 1) what are the meanings of the routing and its flags UHLc and UHLS2?:
> 192.168.0.82       link#1             UHLc        0        1      -  vr0
> 192.168.0.82       00:40:63:c9:cb:ec  UHLS2       0        0      -  vr0
> 
> 2) why your proxyarp option setup a route (different for mine)?:
> > 192.168.166.70     192.168.166.254    UH          0       25   1400  ppp0
> > 192.168.166.70     00:0d:88:17:0b:9a  UHLS2       0        0   1500  rtk1
> (look at interface ppp0 and not vr0!)
> 
> 1) why the pptp server do not tunnel the echo reply?

Because it's the system does not send it through ppp0.

FWIW, I have an ip-up script to add the correct route on my setup here.  I
admit I've never looked at this closely, and as long as my puny windows users
don't give me too much gas (which means that It Works), I'm happy.

It might be worth filling a PR.  Assign it to 'cube', so I can remember to
have a look at it when I have more time.  Meanwhile, the ip-up trick should
do.

Quentin Garnier.