From owner-freebsd-net@FreeBSD.ORG Thu Apr 17 14:48:05 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 844EC37B401 for ; Thu, 17 Apr 2003 14:48:05 -0700 (PDT) Received: from exchange.wan.no (exchange.wan.no [80.86.128.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4CFB643FBD for ; Thu, 17 Apr 2003 14:48:04 -0700 (PDT) (envelope-from sten.daniel.sorsdal@wan.no) X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Thu, 17 Apr 2003 23:47:53 +0200 Message-ID: <0AF1BBDF1218F14E9B4CCE414744E70F07DE93@exchange.wanglobal.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Userland PPP/PPTP tunneling problem Thread-Index: AcMFIR0z9CXmdR4lR6CCPsFHqmmdwAACGVgQ From: =?iso-8859-1?Q?Sten_Daniel_S=F8rsdal?= To: "Brett Glass" , Subject: RE: Userland PPP/PPTP tunneling problem X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Apr 2003 21:48:05 -0000 > >Say if client gets 192.168.1.2 when client connects, you=20 > need to manually > >Enter: route -p add 192.168.0.0 mask 255.255.0.0 192.168.1.2 > >On the windows client before connecting. >=20 > But won't the Windows machine still get the broadcast address=20 > wrong? Seems > to me that it'd send to 192.168.1.255 instead of 192.168.255.255. >=20 > --Brett It would send to 192.168.1.255 Broadcast and tunneling isnt a good combination, for NetBIOS use WINS. For broadcast to even have the remote chance of working you have to use proxy arp. To proxy arp you have to give the clients a range from the=20 LANs range and add 'enable proxy'. - Sten