Fred,
>>>Oh, you mean MPD. :-)
MPD, DMP, all these TLA's.... (thanks:-)
Based on what you mentioned, I looked again at
the windows "netstat" report....and I obtained a
netstat from m0n0 with the tunnel up.
It seems that indeed, it is a windows issue.
The question is, can anyone suggest a simple way
to get windows to route over the tunnel,
which is implemented as a SLIP interface?
In other words, when the tunnel comes up,
the WLAN (10.248.127.0) should only be accessible
to the PPTPD client driver on the PC.
Maybe just deleting the route
0.0.0.0 0.0.0.0 10.248.127.1 10.248.127.40 31
since the only route needed by the pptp client is the 10.248.127.0?
More current stats below.
I'm going to go try this, but I'll send this out, since
trying it will probably knock me off the network for a while.
Thanks
Seth
Netstats
$ netstat -nr (m0n0wall, with PPTP up)
Destination Gateway Flags Refs Use Netif Expire
default 216.220.103.177 UGSc 2 56157 sis1
10.248.126/24 link#1 UC 1 0 sis0
10.248.126.80 10.248.127.1 UH 1 789 ng1
10.248.126.80 00:00:24:c0:77:f4 UHLS2 0 0 sis0
10.248.126.199 00:20:ed:45:17:4f UHLW 1 18370 sis0 1151
10.248.127/24 link#7 UC 1 0 wi0
10.248.127.1 lo0 UHS 0 0 lo0
10.248.127.40 00:02:6f:07:56:a8 UHLW 7 600356 wi0 958
127.0.0.1 127.0.0.1 UH 1 0 lo0
216.220.103.176/29 link#2 UC 2 0 sis1
216.220.103.177 00:00:c5:97:30:20 UHLW 4 289 sis1 1171
216.220.103.178 00:00:24:c1:81:e0 UHLW 0 1097 sis1 919
216.220.103.181 127.0.0.1 UGHS 0 0 lo0
==================================================
PC, while connected::::
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...00 d0 59 4c 0b 9e ...... Intel(R) PRO/100+ MiniPCI - Packet
Scheduler Miniport
0xc0004 ...00 02 6f 07 56 a8 ...... 802.11b Wireless LAN PC Card - Packet
Scheduler
Miniport
0x110005 ...00 53 45 00 00 00 ...... WAN (PPP/SLIP) Interface
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 10.248.126.80 10.248.126.80 1
0.0.0.0 0.0.0.0 10.248.127.1 10.248.127.40 31
10.248.126.80 255.255.255.255 127.0.0.1 127.0.0.1 50
10.248.127.0 255.255.255.0 10.248.127.40 10.248.127.40 30
10.248.127.1 255.255.255.255 10.248.127.40 10.248.127.40 30
10.248.127.40 255.255.255.255 127.0.0.1 127.0.0.1 30
10.255.255.255 255.255.255.255 10.248.126.80 10.248.126.80 50
10.255.255.255 255.255.255.255 10.248.127.40 10.248.127.40 30
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
224.0.0.0 240.0.0.0 10.248.127.40 10.248.127.40 30
224.0.0.0 240.0.0.0 10.248.126.80 10.248.126.80 1
255.255.255.255 255.255.255.255 10.248.126.80 2 1
255.255.255.255 255.255.255.255 10.248.127.40 10.248.127.40 1
Default Gateway: 10.248.126.80
==========================================================================
PC, not connected:::
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...00 d0 59 4c 0b 9e ...... Intel(R) PRO/100+ MiniPCI - Packet
Scheduler Miniport
0xc0004 ...00 02 6f 07 56 a8 ...... 802.11b Wireless LAN PC Card - Packet
Scheduler
Miniport
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 10.248.127.1 10.248.127.40 30
10.248.127.0 255.255.255.0 10.248.127.40 10.248.127.40 30
10.248.127.40 255.255.255.255 127.0.0.1 127.0.0.1 30
10.255.255.255 255.255.255.255 10.248.127.40 10.248.127.40 30
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
224.0.0.0 240.0.0.0 10.248.127.40 10.248.127.40 30
255.255.255.255 255.255.255.255 10.248.127.40 2 1
255.255.255.255 255.255.255.255 10.248.127.40 10.248.127.40 1
Default Gateway: 10.248.127.1
========================================================================== | 