From owner-freebsd-questions Fri Nov 6 00:10:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA01858 for freebsd-questions-outgoing; Fri, 6 Nov 1998 00:10:30 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from smtp.tninet.se (mail.tninet.se [195.100.94.10]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id AAA01850 for ; Fri, 6 Nov 1998 00:10:26 -0800 (PST) (envelope-from dow489o@tninet.se) Received: (qmail 12244 invoked by uid 65537); 6 Nov 1998 09:10:13 +0100 Received: from sdu107-73.ppp.algonet.se (HELO jonaseri) (195.163.73.107) by mail.tninet.se with SMTP; 6 Nov 1998 09:10:13 +0100 From: "Jonas Ericson" To: Subject: PPP Date: Fri, 6 Nov 1998 09:11:30 +0100 Message-ID: <01be095d$0f3395c0$6b49a3c3@jonaseri> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_000B_01BE0965.70F7FDC0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.71.1712.3 X-MimeOLE: Produced By Microsoft MimeOLE V4.71.1712.3 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Det här är ett multipart-meddelande i MIME-format. ------=_NextPart_000_000B_01BE0965.70F7FDC0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi! A second try! Please! I have already asked this question before and got a few answers that i = am very thankful for, they got me in the right direction but i don=B4t get = it to work. It=B4s a pain. Here is my problem: I have a small LAN with a couple of = Win95 machines and a FreeBSD box running the 2.2.7 realese wich i use as a Samba server aswell as a Gateway to the internet via user ppp(dynamic = IP) with the -auto -alias switches. The problem is that when i want to = conect to a samba share it triggers the modem to dial and as far as i can see = it=B4s DNS -lookups that causes it? Is this a paradox? If i use packet filtering to = prevent the dns lookup packages that triggers the dialup, i can=B4t rech the = internet from the win95 boxes!? Here is an example of logging tun0 with bpf (the win95 box IP addres 192.168.1.6): 09:19:39.409585 192.168.1.6.netbios-ns > my ISP=B4s nameserver.domain: = 19+ A?MYDOMAIN.mydomain. (41) 09:19:40.080166 10.0.0.1.domain > 202.12.27.33.domain: 64940 (43) 09:19:40.916258 192.168.1.6.netbios-ns > ......... I have tried to install a caching name server (on the FreeBSD box) but = i=B4m not to sure that it is configuerd the right way. What am i doing wrong? Many thanks! Jonas ------=_NextPart_000_000B_01BE0965.70F7FDC0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
 
Hi!

A second try! Please!
I have already asked this = question=20 before and got a few answers that i am
very thankful for, they got me = in the=20 right direction but i don´t get it to work.
It´s a pain. Here is my problem: I have = a small=20 LAN with a couple of Win95
machines and a FreeBSD box running the = 2.2.7=20 realese wich i use as a
Samba server aswell as a Gateway to the = internet via=20 user ppp(dynamic IP)
with the -auto -alias switches. The problem is = that when=20 i want to conect to
a samba share it triggers the modem to dial and = as far as=20 i can see it´s DNS
-lookups that causes it? Is this a paradox? = If i use=20 packet filtering to = prevent
the=20 dns lookup packages that triggers the dialup, i can´t rech the=20 internet
from the = win95=20 boxes!?
Here is an example of logging tun0 with bpf (the win95 box IP = addres
192.168.1.6):

09:19:39.409585 192.168.1.6.netbios-ns = > my=20 ISP´s nameserver.domain: 19+=20 A?MYDOMAIN.mydomain. (41)
09:19:40.080166 10.0.0.1.domain > = 202.12.27.33.domain: 64940 (43)
09:19:40.916258 = 192.168.1.6.netbios-ns >=20 .........
I have tried to install a caching name server (on the = FreeBSD box)=20 but i´m
not to sure that it is configuerd the right way. What = am i=20 doing wrong?
 
 

Many thanks!

Jonas

 
------=_NextPart_000_000B_01BE0965.70F7FDC0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message