From owner-freebsd-net Sun Nov 22 12:51:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA11269 for freebsd-net-outgoing; Sun, 22 Nov 1998 12:51:08 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from mhs.mhs.rosmail.com (mhs.rosmail.com [195.90.130.88]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA11263 for ; Sun, 22 Nov 1998 12:51:05 -0800 (PST) (envelope-from 0824@08700000.mhs.rosmail.com) Received: from NetWare MHS (SMF70) by mhs.mhs.rosmail.com via Connect2-SMTP 4.32.03; Sun, 22 Nov 1998 23:49:52 +0300 Message-ID: <151BD2D781F0D57E%151BD2D781F0D57E@mhs.mhs.rosmail.com> Date: Sun, 22 Nov 1998 23:37:07 +0300 From: Vladislav SAFRONOV <0824@08700000.mhs.rosmail.com> Organization: Rosnet To: freebsd-net@FreeBSD.ORG Subject: Help! Modifying Linux sources to compile under 2.2.7R. X-SMF-Hop-Count: 3 MIME-Version: 1.0 Content-type: text/plain; charset="KOI8-R" Content-transfer-encoding: 7bit X-Mailer: Connect2-SMTP 4.32.03 MHS/SMF to SMTP Gateway Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I want to compile a little c program under Freebsd, but the source warns: "Linux 2.0.33 source, will compile on BSD if you modify the ip header etc." I thought small tcp/ip applications could be copmiled under any Unix :(, Well what should I modify? What's the difference between BSD ip header and Linux ip header? ... struct iphdr *iph=(struct iphdr *)buf; struct udphdr *udp=(struct udphdr *)(buf + 20); ... iph->version=4; iph->ihl=5; iph->tos=0; iph->tot_len=htons(sizeof(buf)); iph->id=htons(1234); iph->frag_off=0; iph->ttl=255; iph->protocol=17; iph->saddr=inet_addr(SIP); iph->daddr=resolve_address(argv[1]); Should I modify udp header as well? Sincerely, Vlad Safronov To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Nov 23 00:32:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA14076 for freebsd-net-outgoing; Mon, 23 Nov 1998 00:32:00 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from obie.softweyr.com ([204.68.178.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA14071 for ; Mon, 23 Nov 1998 00:31:57 -0800 (PST) (envelope-from wes@softweyr.com) Received: from softweyr.com (zaphod.softweyr.com [204.68.178.35]) by obie.softweyr.com (8.8.8/8.8.8) with ESMTP id BAA04997; Mon, 23 Nov 1998 01:31:10 -0700 (MST) (envelope-from wes@softweyr.com) Message-ID: <36591D4D.F335DC8F@softweyr.com> Date: Mon, 23 Nov 1998 01:31:10 -0700 From: Wes Peters Organization: Softweyr llc X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.0-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Vladislav SAFRONOV <0824@08700000.mhs.rosmail.com> CC: freebsd-net@FreeBSD.ORG Subject: Re: Help! Modifying Linux sources to compile under 2.2.7R. References: <151BD2D781F0D57E%151BD2D781F0D57E@mhs.mhs.rosmail.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Vladislav SAFRONOV wrote: > > I want to compile a little c program under Freebsd, but the source > warns: > > "Linux 2.0.33 source, will compile on BSD if you modify the ip > header etc." > > I thought small tcp/ip applications could be copmiled under any Unix > :(, Hah! You don't understand UNIX portability that well. You always have to poke around the various header files a bit. > Well what should I modify? What's the difference between BSD ip > header and Linux ip header? Well, first of all, if you're dinking with the raw IP header, this isn't a "typical" tcp/ip program at all. A typical tcp/ip program just opens a socket connection and pumps data through it. > ... > struct iphdr *iph=(struct iphdr *)buf; > struct udphdr *udp=(struct udphdr *)(buf + 20); > ... > iph->version=4; > iph->ihl=5; > iph->tos=0; > iph->tot_len=htons(sizeof(buf)); > iph->id=htons(1234); > iph->frag_off=0; > iph->ttl=255; > iph->protocol=17; > > iph->saddr=inet_addr(SIP); > iph->daddr=resolve_address(argv[1]); See /usr/include/netinet/ip.h, /usr/include/netinet/tcp.h, and /usr/include/netinet/udp.h. Or, better yet, get yourself a copy of Unix Network Program vol 1 by W. Richard Stevens. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.softweyr.com/~softweyr wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Nov 23 05:44:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA15978 for freebsd-net-outgoing; Mon, 23 Nov 1998 05:44:45 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from databus.databus.com (databus.databus.com [198.186.154.34]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id FAA15971 for ; Mon, 23 Nov 1998 05:44:43 -0800 (PST) (envelope-from barney@databus.databus.com) From: Barney Wolff To: freebsd-net@FreeBSD.ORG Date: Mon, 23 Nov 1998 08:41 EST Subject: Re: Help! Modifying Linux sources to compile under 2.2.7R. Content-Type: text/plain Message-ID: <365966a20.59bc@databus.databus.com> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As I recall, some flavors of Unix have already converted the length field to host order before delivering the packet, on a raw socket. I seem to remember that FreeBSD is one of them, and Linux is not. The same probably applies to output. Barney Wolff To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Nov 23 06:55:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA22566 for freebsd-net-outgoing; Mon, 23 Nov 1998 06:55:36 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from foonly.scimitar.org (cr323989-a.yec1.on.wave.home.com [24.112.82.27]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA22561 for ; Mon, 23 Nov 1998 06:55:34 -0800 (PST) (envelope-from pnadeau@wave.home.com) Received: from localhost (pnadeau@localhost) by foonly.scimitar.org (8.8.5/8.8.5) with SMTP id JAA22227 for ; Mon, 23 Nov 1998 09:54:59 -0500 (EST) X-Authentication-Warning: foonly.scimitar.org: pnadeau owned process doing -bs Date: Mon, 23 Nov 1998 09:54:59 -0500 (EST) From: Patrick Nadeau X-Sender: pnadeau@foonly.scimitar.org To: net@FreeBSD.ORG Subject: arp problem Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I just had a wierd 'problem' with arp over the weekend. I noticed this line in /var/log/messages Nov 21 13:37:12 foonly /kernel: arp: 10.0.0.1 moved from 00:60:97:1f:18:ce to 00:20:35:e7:b5:bc I have not done anything that would make this change, i.e.: change the network card, add a new host to the network with ip 10.0.0.1 by mistake, issued any arp commands. This is a dual homed host with two 3com 3c509's in it. netstat -i still says: ep0 1500 00.60.97.3a.2f.80 9245953 10800 122177 1 0 ep1 1500 00.60.97.1f.18.ce 62020 0 73826 1 0 which makes sense to me since both's mac start with 00.60.97, i.e. they are from the same manufacturer. but now arp -a reports: foonly.scimitar.org (10.0.0.1) at 0:20:35:e7:b5:bc permanent cr323989-a.yec1.on.wave.home.com (24.112.82.27) at 0:60:97:3a:2f:80 permanent Is this a bug in arp. BTW I am using 2.2.1 with ipfw and natd with ep0 as the outside interface and ep1 as the inside interface. Everything seems to still work fine though. And I have since changed it back with arp -S, no problem. Any ideas? Please send any replies by email. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Nov 23 11:23:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA04560 for freebsd-net-outgoing; Mon, 23 Nov 1998 11:23:42 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from mathserv.mps.ohio-state.edu (mathserv.mps.ohio-state.edu [128.146.111.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA04552 for ; Mon, 23 Nov 1998 11:23:40 -0800 (PST) (envelope-from alden@math.ohio-state.edu) Received: from zaphod.mps.ohio-state.edu (zaphod.mps.ohio-state.edu [128.146.111.36]) by mathserv.mps.ohio-state.edu (8.9.1a/8.9.1) with ESMTP id NAA09090; Mon, 23 Nov 1998 13:38:26 -0500 (EST) Received: (from alden@localhost) by zaphod.mps.ohio-state.edu (8.9.1a/8.9.1) id NAA06828; Mon, 23 Nov 1998 13:38:25 -0500 (EST) Message-ID: <19981123133825.A5023@zaphod.mps.ohio-state.edu> Date: Mon, 23 Nov 1998 13:38:25 -0500 From: Dave Alden To: Luigi Rizzo Cc: freebsd-net@FreeBSD.ORG Subject: Re: bridging hints? References: <199811202109.QAA06927@math.mps.ohio-state.edu> <199811210400.FAA28620@labinfo.iet.unipi.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199811210400.FAA28620@labinfo.iet.unipi.it>; from Luigi Rizzo on Sat, Nov 21, 1998 at 05:00:58AM +0100 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, On Sat, Nov 21, 1998 at 05:00:58AM +0100, Luigi Rizzo wrote: > i am not sure what you mean by "client" firewall -- i suppose that you > are setting the firewall on the machine acting as a bridge. That's what I'm trying to do. :-) What I meant by "client" was that I set "firewall_type" to "client" in rc.conf. > i have never tried this... have you tried, by chance, to block > single ports as opposed to a range and see if it makes a difference ? > If it does it could be a bug in ipfw.c, otherwhise it is in the way the > bridge code uses ipfw It doesn't make a difference. I've gotten a little bit further. Here's my setup: Hub_1 | | A Hub_2 | | | B C D | E A is a an Ultra 10 (Solaris 2.6). B is a Dell Inspiron 3200 (RedHat 5.1). C is a Mac G3/266 (MacOS 8.1). D is the FreeBSD bridge box. E is an Ultra 60 (Solaris 2.6). They're all on the same class C subnet. Hub_1 is a 48 port HP hub, Hub_2 is a 12 port Asante hub. I've got the following rules on D: % ipfw l 00100 deny log tcp from any to E 23 00200 allow log tcp from any to any 65535 allow ip from any to any If I telnet from B to E, I get the following syslog'ed on D: Nov 23 13:04:54 D /kernel: ipfw: 100 Deny TCP B:1114 E:23 out via fxp1 Which is what I'd expect. If I telnet from C (or A) to E, I get the following syslog'ed on D: ipfw: 200 Accept TCP C E out via fxp1 Fragment = 64 ipfw: 200 Accept TCP C E out via fxp1 Fragment = 64 ipfw: 200 Accept TCP C E out via fxp1 Fragment = 64 ipfw: 200 Accept TCP C E out via fxp1 Fragment = 64 Nov 23 13:06:23 D /kernel: ipfw: 200 Accept TCP C E out via fxp1 Fragment = 64 I ran snoop (Solaris packet sniffer) and as far as I can tell, the packets coming from C (and A) are not fragmented. Have I misconfigured something? Any ideas? Help? :-) ...thnx, ...dave ps I'm running 2.2.7-stable -- should I be running 2.2-current? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Nov 23 11:32:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA06134 for freebsd-net-outgoing; Mon, 23 Nov 1998 11:32:20 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA06120 for ; Mon, 23 Nov 1998 11:32:18 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id UAA03233 for freebsd-net@FreeBSD.ORG; Mon, 23 Nov 1998 20:32:12 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id EED7E147E; Mon, 23 Nov 1998 20:25:51 +0100 (CET) Date: Mon, 23 Nov 1998 20:25:51 +0100 From: Ollivier Robert To: freebsd-net@FreeBSD.ORG Subject: Re: your mail Message-ID: <19981123202551.A11240@keltia.freenix.fr> Mail-Followup-To: freebsd-net@FreeBSD.ORG References: <19981117223745.AAA1211@mailmtx.acnet.net@denpmfe.acnet.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.16i In-Reply-To: <19981117223745.AAA1211@mailmtx.acnet.net@denpmfe.acnet.net>; from Ivan Villalobos on Tue, Nov 17, 1998 at 04:38:05PM -0600 X-Operating-System: FreeBSD 3.0-CURRENT/ELF ctm#4829 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org According to Ivan Villalobos: > 1.- Tweak the firewall's TCP timeout. > 2.- Tweak FreeBSD's tcp.keepalives. > 3.- Tweak telnetd's keepalives. Is this possible ? 4.- use SSH instead of Telnet. It has its own keepalive option. Of course that's not the only advantage... :-) -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #2: Sun Nov 8 01:22:20 CET 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Nov 24 06:22:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA27443 for freebsd-net-outgoing; Tue, 24 Nov 1998 06:22:20 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id GAA27438 for ; Tue, 24 Nov 1998 06:22:18 -0800 (PST) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id NAA05659; Tue, 24 Nov 1998 13:26:31 +0100 From: Luigi Rizzo Message-Id: <199811241226.NAA05659@labinfo.iet.unipi.it> Subject: Re: bridging hints? To: alden@math.ohio-state.edu (Dave Alden) Date: Tue, 24 Nov 1998 13:26:31 +0100 (MET) Cc: freebsd-net@FreeBSD.ORG In-Reply-To: <19981123133825.A5023@zaphod.mps.ohio-state.edu> from "Dave Alden" at Nov 23, 98 01:38:06 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > That's what I'm trying to do. :-) What I meant by "client" was that I > set "firewall_type" to "client" in rc.conf. > It doesn't make a difference. I've gotten a little bit further. Here's my > setup: > > Hub_1 > | | > A Hub_2 > | | | > B C D > | > E > ... > If I telnet from B to E, I get the following syslog'ed on D: > > Nov 23 13:04:54 D /kernel: ipfw: 100 Deny TCP B:1114 E:23 out via fxp1 > > Which is what I'd expect. If I telnet from C (or A) to E, I get the > following syslog'ed on D: > > ipfw: 200 Accept TCP C E out via fxp1 Fragment = 64 > ipfw: 200 Accept TCP C E out via fxp1 Fragment = 64 > ipfw: 200 Accept TCP C E out via fxp1 Fragment = 64 > ipfw: 200 Accept TCP C E out via fxp1 Fragment = 64 > Nov 23 13:06:23 D /kernel: ipfw: 200 Accept TCP C E out via fxp1 Fragment = 64 > > I ran snoop (Solaris packet sniffer) and as far as I can tell, the packets > coming from C (and A) are not fragmented. Have I misconfigured something? > Any ideas? Help? :-) it is really curious that B and C behave differently. Do you have a tcpdump/snoop output to see what options are carried by the packets ? luigi > ps I'm running 2.2.7-stable -- should I be running 2.2-current? there is no 2.2-current, -current is on the 3.0 branch and there is no bridging in that branch (yet) luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Nov 26 18:23:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA01542 for freebsd-net-outgoing; Thu, 26 Nov 1998 18:23:39 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from mars.mds.com.sg (mars.mds.com.sg [203.127.216.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA01528 for ; Thu, 26 Nov 1998 18:23:36 -0800 (PST) (envelope-from juriarte@asiansources.com) Received: from zeus.asiansources.com (root@zeusfr [203.172.0.46]) by mars.mds.com.sg (8.8.5/8.8.5) with ESMTP id KAA00364 for ; Fri, 27 Nov 1998 10:30:52 +0800 Received: from ph.asiansources.com (IDENT:mta@ph-2.asiansources.com [203.172.0.3]) by zeus.asiansources.com (8.9.1/8.9.1) with ESMTP id KAA21853 for ; Fri, 27 Nov 1998 10:47:32 +0800 Received: from asiansources.com ([192.168.8.201]) by ph.asiansources.com (post.office MTA v2.0 0906 ID# 50-42442U500) with ESMTP id AAA31602 for ; Fri, 27 Nov 1998 10:25:07 +0800 Message-ID: <365E0CC8.372D9F7A@asiansources.com> Date: Fri, 27 Nov 1998 10:22:00 +0800 From: Joubert Uriarte X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 2.2.6-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 Newsgroups: comp.unix.bsd.freebsd.misc To: freebsd-net@FreeBSD.ORG Subject: Help! Samba on FreeBSD Content-Type: multipart/mixed; boundary="------------F5D3D32A075C943A4BB09EC9" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is a multi-part message in MIME format. --------------F5D3D32A075C943A4BB09EC9 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Dear All, I need help on my samba server configuration on my FreeBSD v.2.2.6. I hope you don't mind a little history... I used the samba package with came with FreeBSD v.2.2.6 before. It installed fine... I was able to view the shared folders of other Windows machines and other Linux boxes with samba installed could also see my FreeBSD machine. I was even able to send and receive Winpop messages to and from a Windows 95 box. At first, the problem was my machine could not be seen in the Network Neighborhood of the Windows machines. I tried accessing my machine directly from the Windows box -- however to no avail. I found it quite wierd that my machine was not listed and could not be found by Windows machines, but those same machines can send Winpop messages to my Samba Server. Anyway, after playing around with the various settings in smb.conf, for some reason I am not aware of, my machine becomes listed in the Network Neighborhood. However, if you double-click on my machine, an error is displayed indicating that the computer cannot be accessed. I decided to download the source code from www.samba.org and recompile it for FreeBSD -- it still didn't work. I recompiled it again and added another option (the option for those having password problems), it worked! BUT! The Winpop didn't anymore... =8( I said to myself, 'okay... I can live with that..." BUT! Now for some reason... it doesn't want to work anymore! I remembered that I tried the NetCon package, after Samba was working, which was quite disappointing so I removed NetCon. I noticed afterwards that my Samba was not working anymore... Out of sheer desperation, I decided to backup all my data, reformat the hard disk, and re-install everything from scratch. I was hoping that this time it would work... BUT I GUESS NOT! =8( Can somebody tell my what I am doing wrong.... please!!!! I have attached a copy of my rc.local and smb.conf files.. Thank you so much in advance... Joubert Uriarte xichrome@pacific.net.ph juriarte@asiansources.com --------------F5D3D32A075C943A4BB09EC9 Content-Type: text/plain; charset=us-ascii; name="rc.local" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="rc.local" # # site-specific startup actions, daemons # # $Id: rc.local,v 1.21.2.2 1998/02/15 14:24:49 jkh Exp $ # # If there is a global system configuration file, suck it in. #if [ -f /etc/rc.conf ]; then # . /etc/rc.conf #fi T=/tmp/_motd rm -f $T uname -v | sed -e 's,^\([^#]*\) #\(.* [1-2][0-9][0-9][0-9]\).*/\([^\]*\) $,\1 (\3) #\2,' > $T awk '{if (NR == 1) {if ($1 == "FreeBSD") {next} else {print "\n"$0}} else {print}}' < /etc/motd >> $T cp $T /etc/motd chmod 644 /etc/motd rm -f $T echo -n 'starting local daemons:' # put your local stuff here echo '.' echo 'nmbd '; /usr/local/samba/bin/nmbd -s /usr/local/samba/lib/smb.conf echo 'smbd '; /usr/local/samba/bin/smbd -s /usr/local/samba/lib/smb.conf echo 'wdm '; /usr/X11R6/bin/wdm --------------F5D3D32A075C943A4BB09EC9 Content-Type: text/plain; charset=us-ascii; name="smb.conf" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="smb.conf" # This is the main Samba configuration file. You should read the # smb.conf(5) manual page in order to understand the options listed # here. Samba has a huge number of configurable options (perhaps too # many!) most of which are not shown in this example # # Any line which starts with a ; (semi-colon) or a # (hash) # is a comment and is ignored. In this example we will use a # # for commentry and a ; for parts of the config file that you # may wish to enable # # NOTE: Whenever you modify this file you should run the command "testparm" # to check that you have not many any basic syntactic errors. # #======================= Global Settings ===================================== [global] # message command = sh -c 'exec 2> /tmp/xmessage.err; /usr/X11R6/bin/xmessage -title %f -file %s; echo . > /dev/console; echo Message From: %f > /dev/console; cat %s > /dev/console' & # workgroup = NT-Domain-Name or Workgroup-Name, eg: REDHAT4 workgroup = ISD # server string is the equivalent of the NT Description field server string = Samba Server # This option is important for security. It allows you to restrict # connections to machines which are on your local network. The # following example restricts access to two C class networks and # the "loopback" interface. For more examples of the syntax see # the smb.conf man page ; hosts allow = 192.168.8. 192.168.28. 127. # If you want to automatically load your printer list rather # than setting them up individually then you'll need this load printers = yes # you may wish to override the location of the printcap file ; printcap name = /etc/printcap # on SystemV system setting printcap name to lpstat should allow # you to automatically obtain a printer list from the SystemV spool # system ; printcap name = lpstat # It should not be necessary to specify the print system type unless # it is non-standard. Currently supported print systems include: # bsd, sysv, plp, lprng, aix, hpux, qnx ; printing = bsd # Uncomment this if you want a guest account, you must add this to /etc/passwd # otherwise the user "nobody" is used ; guest account = guest # this tells Samba to use a separate log file for each machine # that connects log file = /var/log/log.%m # Put a capping on the size of the log files (in Kb). max log size = 50 # Security mode. Most people will want user level security. See # security_level.txt for details. security = user # Use password server option only with security = server ; password server = # You may wish to use password encryption. Please read # ENCRYPTION.txt, Win95.txt and WinNT.txt in the Samba documentation. # Do not enable this option unless you have read those documents ; encrypt passwords = yes # Using the following line enables you to customise your configuration # on a per machine basis. The %m gets replaced with the netbios name # of the machine that is connecting ; include = /usr/local/samba/lib/smb.conf.%m # Most people will find that this option gives better performance. # See speed.txt and the manual pages for details socket options = TCP_NODELAY # Configure Samba to use multiple interfaces # If you have multiple network interfaces then you must list them # here. See the man page for details. interfaces = 192.168.8.201/24 192.168.28.201/24 # Browser Control Options: # set local master to no if you don't want Samba to become a master # browser on your network. Otherwise the normal election rules apply ; local master = no # OS Level determines the precedence of this server in master browser # elections. The default value should be reasonable ; os level = 33 # Domain Master specifies Samba to be the Domain Master Browser. This # allows Samba to collate browse lists between subnets. Don't use this # if you already have a Windows NT domain controller doing this job ; domain master = yes # Preferred Master causes Samba to force a local browser election on startup # and gives it a slightly higher chance of winning the election ; preferred master = yes # Use only if you have an NT server on your network that has been # configured at install time to be a primary domain controller. ; domain controller = # Enable this if you want Samba to be a domain logon server for # Windows95 workstations. ; domain logons = yes # if you enable domain logons then you may want a per-machine or # per user logon script # run a specific logon batch file per workstation (machine) ; logon script = %m.bat # run a specific logon batch file per username ; logon script = %U.bat # Where to store roving profiles (only for Win95 and WinNT) # %L substitutes for this servers netbios name, %U is username # You must uncomment the [Profiles] share below ; logon path = \\%L\Profiles\%U # Windows Internet Name Serving Support Section: # WINS Support - Tells the NMBD component of Samba to enable it's WINS Server ; wins support = yes # WINS Server - Tells the NMBD components of Samba to be a WINS Client # Note: Samba can be either a WINS Server, or a WINS Client, but NOT both ; wins server = w.x.y.z # WINS Proxy - Tells Samba to answer name resolution queries on # behalf of a non WINS capable client, for this to work there must be # at least one WINS Server on the network. The default is NO. ; wins proxy = yes # DNS Proxy - tells Samba whether or not to try to resolve NetBIOS names # via DNS nslookups. The built-in default for versions 1.9.17 is yes, # this has been changed in version 1.9.18 to no. dns proxy = no # Client codepage setting # for Western European users ; client code page=850 # for Japanese Users ; client code page=932 ; coding system=cap # for Chinese Users ; client code page=950 ; coding system=cap #============================ Share Definitions ============================== [homes] comment = Home Directories browseable = no writable = yes [guest] comment = Guest Account browseable = no writable = yes path = /usr/home # Un-comment the following and create the netlogon directory for Domain Logons ; [netlogon] ; comment = Network Logon Service ; path = /usr/local/samba/lib/netlogon ; guest ok = yes ; writable = no ; share modes = no # Un-comment the following to provide a specific roving profile share # the default is to use the user's home directory ;[Profiles] ; path = /usr/local/samba/profiles ; browseable = no ; guest ok = yes # NOTE: If you have a BSD-style print system there is no need to # specifically define each individual printer [printers] comment = All Printers path = /var/spool/samba browseable = no # Set public = yes to allow user 'guest account' to print guest ok = no writable = no printable = yes # This one is useful for people to share files ;[tmp] ; comment = Temporary file space ; path = /tmp ; read only = no ; public = yes # A publicly accessible directory, but read only, except for people in # the "staff" group ;[public] ; comment = Public Stuff ; path = /home/samba ; public = yes ; writable = yes ; printable = no ; write list = @staff # Other examples. # # A private printer, usable only by fred. Spool data will be placed in fred's # home directory. Note that fred must have write access to the spool directory, # wherever it is. ;[fredsprn] ; comment = Fred's Printer ; valid users = fred ; path = /homes/fred ; printer = freds_printer ; public = no ; writable = no ; printable = yes # A private directory, usable only by fred. Note that fred requires write # access to the directory. ;[fredsdir] ; comment = Fred's Service ; path = /usr/somewhere/private ; valid users = fred ; public = no ; writable = yes ; printable = no # a service which has a different directory for each machine that connects # this allows you to tailor configurations to incoming machines. You could # also use the %U option to tailor it by user name. # The %m gets replaced with the machine name that is connecting. [pchome] comment = PC Directories path = /usr/home/%m public = no writable = yes # A publicly accessible directory, read/write to all users. Note that all files # created in the directory by users will be owned by the default user, so # any user with access can delete any other user's files. Obviously this # directory must be writable by the default user. Another user could of course # be specified, in which case all files would be owned by that user instead. ;[public] ; path = /usr/somewhere/else/public ; public = yes ; only guest = yes ; writable = yes ; printable = no # The following two entries demonstrate how to share a directory so that two # users can place files there that will be owned by the specific users. In this # setup, the directory should be writable by both users and should have the # sticky bit set on it to prevent abuse. Obviously this could be extended to # as many users as required. ;[myshare] ; comment = Mary's and Fred's stuff ; path = /usr/somewhere/shared ; valid users = mary fred ; public = no ; writable = yes ; printable = no ; create mask = 0765 --------------F5D3D32A075C943A4BB09EC9-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Nov 27 00:45:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA26327 for freebsd-net-outgoing; Fri, 27 Nov 1998 00:45:32 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from it.sivma.ru (sivmac.dialup.ru [194.87.17.172]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA26322; Fri, 27 Nov 1998 00:45:28 -0800 (PST) (envelope-from info@sivma.ru) Received: from valeric.sivma.ru (VALERY.SIVMA.RU [10.10.10.3]) by it.sivma.ru (8.8.8/8.8.8) with SMTP id LAA17883; Fri, 27 Nov 1998 11:48:26 +0300 (MSK) (envelope-from info@sivma.ru) Message-ID: <003a01be19e1$c9f0f3a0$030a0a0a@valeric.sivma.ru> From: "Sivma" To: , Subject: Deny for spec. MAC-address Date: Fri, 27 Nov 1998 11:41:42 +0300 MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I want to deny access for machine with specifed MAC-address. How can I do it? Thanks. Valery Lobachev To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message