Linux-Networking Digest #537, Volume #12 Fri, 10 Sep 99 06:13:41 EDT
Contents:
3com card/DSL problem? (Bobby Hayes)
Re: port forwarding woes ("Terra")
Linux as router (Andrejs Shtrumfs)
Re: DSL User: Problem with the configuration of the NIC (Peter Buelow)
Re: DNS nightmare Help... (Peter Buelow)
Re: Glibc Help?!? (Peter Buelow)
Re: IP packet generator for Linux? (Peter Buelow)
Masquerading for a Server (Sascha Pollok)
configuring nt users and groups in samba for pdc (Rage-DCA)
wu-ftpd - How to deny domains ("Gonzo")
Remote bridge (Sasa S Baksa)
Re: Crossover RJ45 ethernet cables - Re: Cable problem? (James Knott)
----------------------------------------------------------------------------
From: [EMAIL PROTECTED] (Bobby Hayes)
Subject: 3com card/DSL problem?
Date: Fri, 10 Sep 1999 00:51:15 -0700 (MST)
Need some help. Have redhat 5.1 installed
(Not completely configured) on a 233mhx, 64mb blah blah blah using 512kb
DSL Card is a 3com 3c905B Cyclone 100baseTX
at 0x6800, IRQ 10 <-from dmesg. Ifconfig reveals that eth0 is up and
configured correctly. resolv.conf is setup to the correct nameservers.
linuxconf shows that my default route is correct,however, netstat -rn
does not reveal my default route. The default route is not pingable. Ip
of eth0 is pingable. The .0 of my ip is not
pingable either.
Had solaris x86 2.7 running fine yesterday with the same network
confguation. 1.) Is my card not compatable with 5.1? (Cant seem to
acess the hardware compat list via my webtv browser) 2.) I have a static
route to my subnet but cant reach it, route configuration problem? or
hardware? operator? 3.)Can someone post a working networked
netstaat -rn output so's I may compare?
Been over a year since I last played with Linux,
be gentle.
Remind me, why not /etc/defaultrouter?
Shouldnt
route add default gw 'gateway-ip' set my default gateway and shoudnt
that be displyed with netstat?
Preciate the help.... really
Regards,
red eyed lack of sleep linux binge hack the planet need jolt help me
------------------------------
From: "Terra" <[EMAIL PROTECTED]>
Subject: Re: port forwarding woes
Date: Fri, 10 Sep 1999 07:12:17 GMT
I dont think it does! I have the same problem, read endless newsgroups,
tried different configs ..... I am ready to chuck Linux for NT. AT least it
doesn't take me a week to download a program and figure out how to make it
work with NT!
Cort Schaefer <[EMAIL PROTECTED]> wrote in message
news:7qvug3$t5g$[EMAIL PROTECTED]...
> I am having a simular problem (that is going to drive me nuts). I am
> somewhat new to Linux, so please bear with me.
>
> I have a network at home with multiple machines. I have a Linux RedHat
6.0
> machine that dials my ISP for me and does IP masquerading just fine. I am
> using IPCHAINS for the masquerading. I have Apache running on the Linux
> box, but would really like to redirect port 80 to another internal machine
> on the same port. I have read many HOWTOs and lots of newsgroup messages
> and they all say use IPMASQADM. I have tried this with no luck. Before
> running the portfw command (ipmasqadm portfw -a -P tcp -L <dialup addr>
> 80 -R <internal addr> 80), I can see the Apache page. After, I get an
error
> message saying that a connection with the server could not be establised
> (after what seems like a long timeout period).
>
> I have read that IPMASQADM is "experimental", but what else is avaliable
if
> you are using IPCHAINS? I have read about rinetd, and that might work for
> just www, but I would also like to forward ftp later on (assuming I can
> forward www!) and that is not supported in 0.52.
>
> I would appreciate any comments.
>
> Cort
>
> James Offutt <[EMAIL PROTECTED]> wrote in message
> news:7ph875$[EMAIL PROTECTED]...
> > Ok. I've read the FAQs, scoured the Linux newsgroups and even contacted
> the
> > author of ipmasqadm (who verified my configuration) and I still can't
get
> > simple port forwarding to work. This is driving me nuts. Any
suggestions
> > are greatly appreciated.
> >
> > The scenario:
> >
> > Standard Redhat 6.0
> > Kernel 2.2.5-15
> > ipchains-1.3.8-3
> > ipmasqadm-0.4.2
> > Two ethernet interfaces
> > External is ip_aliased with three legal addresses (DNS registered)
> > Internal is a single reserved address and network
> >
> > IP masquerading is configured and working for intenal -> external
> > connections. I use the following:
> >
> > /sbin/ipchains -P forward DENY
> > /sbin/ipchains -A forward -s 192.168.32.0/24 -d 0.0.0.0/0 -j MASQ
> >
> > IP forwarding is enabled in /proc/sys/net/ipv4/ip_forward
> >
> > The kernel and modules have been rebuilt with all the relevant options
> set.
> >
> >
> > The requirement:
> >
> > I want to forward several ports from each external ip address to
different
> > internal IP addresses. This seems like it should be simple. To forward
a
> > simple telnet I use:
> >
> > /sbin/modprobe ip_masq_portfw
> > /usr/sbin/ipmasqadm portfw -a -P tcp -L x.x.x.x 23 -R 192.168.32.20 23
> >
> > The result:
> >
> > A telnet sessions to x.x.x.x (from a completely outside source) just
> > hangs. Closer investigation shows that port forward is working -- sort
> of.
> > The netstat output of 192.168.32.20 shows a SYN_RECV connection from the
> > remote address. Also, netstat -M on masquerading Linux box shows a
> correct
> > entry for the translation. Nevertheless, the conversation is never
> > completed and the session just hangs.
> >
> > I've also tried adding several ipchains, in particular:
> >
> > ipchains -I forward -p tcp -s 192.168.32.20/32 23 -j MASQ
> >
> > -- with no luck. Unless I misunderstand the ipchains syntax this
seemed
> > redundant anyway...
> >
> >
> > Am I missing something obvious?
> >
> > TIA.
> >
> > --
> > James Offutt
> >
>
>
------------------------------
From: Andrejs Shtrumfs <[EMAIL PROTECTED]>
Subject: Linux as router
Date: Fri, 10 Sep 1999 11:36:01 +0300
Hello!
I have a linux box with two network interfaces and a win95 box. Eth0 on
linux is connected to RadioLink going to ISP. Eth1 - to win95. Linux
have to act as router. But i cannot ping the linux box from win95 and
vice versa. Ifconfig shows that both interface are up. What can be the
problem?
Andrejs
------------------------------
From: Peter Buelow <[EMAIL PROTECTED]>
Subject: Re: DSL User: Problem with the configuration of the NIC
Date: Thu, 09 Sep 1999 10:42:44 -0500
Herve Dubreuil wrote:
>
> I'm a DSL user and have 2 Network Card.
> The first is a EtheRx VP 10/100: KNE110 TX from Kingston
> It's the one I use under Windows to access internet.
>
> The second on is a 3Com 905B and is used on the Local Area Network
>
> I configured both of them in the kernel (I put them in, no as module).
> I configured the card:
> The kingston:
> Eth0 using the tulip driver and the corect DNS IP IRQ
> The 3com
> Eth1 using the 3c509 driver and the correct DNS IP IRQ
>
> And linux doesn't even detect the cards.
>
> Can anyone help. I've tried Red Hat and Mandrake and both don't go with it.
> I've reinstall several time and still nothing.
>
> Ireally need help !!
>
> Thanks
I don't think you are using the right driver(s). Use the 3Com
Vortex/Boomerang driver for the 905 card. I have the same chipset and
this is the only drive that I could use. Also, I don't know if the tulip
driver is right for the first one. I am not sure here, but you might try
the de4x5 driver instead.However, in my opinion, tulip probably should
work!? Anyway, try those.
Also, if you are compiling both cards into the kernel then you need to
add this line to your lilo.conf file prior to installing the kernel, or
run lilo after.
image = /boot/vmlinuz <-- probably already there
append = "ether=0,0,eth1" <-- you are going to need this!
This tells the kernel that there are two cards to find and not just one.
This isn't specific to NIC's, but also for any other controller card
(SCSI etc...). These should take care of the problem. Good Luck.
--
Peter Buelow - Software Engineer
--
"Finger to spiritual emptiness underlying everything." -- How a C manual
referred to a "pointer to void."
------------------------------
From: Peter Buelow <[EMAIL PROTECTED]>
Subject: Re: DNS nightmare Help...
Date: Thu, 09 Sep 1999 10:49:11 -0500
Philippe Wetterwald wrote:
>
> I spent already hours trying to figure out why my system does not work the
> way it should and, I know that out there someone knows the answer... would
> you help?
>
> Goal: a linux box that act as a file (Samba) and Internet server for PC
> (win95, win98 and Dos 3.11. The Linux box is connected via a modem to an ISP
> and is configured as a Firewall (or I think I configure it as a firewall..).
> Linux box has an ethernet card as 198.162.0.1, Suse 2.0 is the Linux
> currently installed.
> PC's are 198.162.0.X with X different from 0 and 1 (Samba works thus...)
> Samba works OK
>
> Netscape from the linux box works OK
>
> If from a remote PC (Win98) I use the explorer (network is configure using
> TCP/IP address as 198.162.0.1 and DNS is set ON with IP addresses as my
> Linux box and two IP addresses provided by my ISP):
> The Linux box Diald call the ISP provider,
> While the modem is connected I can ping from the remote PC a valid Internet
> address
> and get response,
> I can FTP and download files (Yes it works)
> I can browse throught Newsgroup and read news BUT,
> I CANNOT display any Web page (I get DNS error)
> I cannot send or receive any mail.
>
> I lost already a bunch of my hairs...
>
> What's wrong? My PC setups? My linux box setup?
> I really do not know where to look and Help would be very appreciated!!
>
> Thanks, Philippe.
Actually, this may be a Netscape problem, especially if it is older!
If everything else works from the inside network (192.168.0.*), then
look to OS and program issues. You don't say here which mail client you
use, but I would suspect it is Netscape. Try browsing from IE. Also,
have you got a proxy? You would probably know if you did, but it doesn't
hurt to ask. :-)
Do you read news through Netscape? And what do you use to FTP? Post
some of these and let us know. More info makes this easier. Also, what
kernel version are you running and how do you setup MASQ? You may have
inadvertently blocked ports 80, 25, and whatever POP is, I can't
remember. Post this stuff as I don't see what the problem could be just
from what you posted. Sorry.
--
Peter Buelow - Software Engineer
--
"Finger to spiritual emptiness underlying everything." -- How a C manual
referred to a "pointer to void."
------------------------------
From: Peter Buelow <[EMAIL PROTECTED]>
Subject: Re: Glibc Help?!?
Date: Thu, 09 Sep 1999 11:52:31 -0500
Poohba wrote:
>
> When I try to 'make' glibc-2.0.7pre6 i get this error:
>
>usr/src/linux/lib/nis:/usr/src/linux/lib/db:/usr/src/linux/lib/resolv/usr/src/linux/lib/libc.so.6
> /usr/src/linux/lib/libc_nonshared.a -lgcc`gcc -B/usr/src/linux/lib/
> --print-file-name=crtend.o`/usr/src/linux/lib/csu/crtn.o/usr/src/linux/lib/libc.so.6:
> undefined reference to `__libc_cleanup_end'make[2]: ***
> [/usr/src/linux/lib/db/makedb] Error 1make[2]: Leaving directory
> `/usr/src/linux/lib/glibc-2.0.7pre6/db'make[1]: *** [db/others] Error
> 2make[1]: Leaving directory `/usr/src/linux/lib/glibc-2.0.7pre6'make: ***
> [all] Error 2
>
> Y???
>
> * Web Page Designs *
> / [EMAIL PROTECTED] | www.io.com/~poohba\
> ---------------------------------------
> \ For info about me send message with /
> * subject "send file help" *
>
Post to comp.os.linux.setup! Just because this has nis in it doesn't
make it a network question. Good luck.
--
Peter Buelow - Software Engineer
--
"Finger to spiritual emptiness underlying everything." -- How a C manual
referred to a "pointer to void."
------------------------------
From: Peter Buelow <[EMAIL PROTECTED]>
Subject: Re: IP packet generator for Linux?
Date: Thu, 09 Sep 1999 11:55:59 -0500
Sylvain GIL wrote:
>
> Chap Harrison wrote:
> >
> > Hi folks,
> Hi
>
> > First time post from a Linux newbie - the usual caveats apply :)
> >
> > I'm testing an ethernet-based IP router, and I would very much like to
> > find a Linux tool that would allow me to create IP packets for
> > transmission over the ethernet NIC. In particular, I want to manipulate
> > the IP header, including being able to insert bogus values therein.
> >
> > Anyone heard of such tool? Anyone know a good reason it's not possible?
> > Such as, "there's no published interface"?
>
> If you know perl, you can use the Net-RawIP module to forge your own
> packets
>
Yep, or spend some time writing a C language Packet
generator/receiver. Wouldn't take all that long I suppose if you knew
what you were doing. The closest tool I can think of is TTCP which is
floating around the web. This is a network test tool, but is very
configurable and is distributed with source so you can modify and change
to your hearts desire. Good luck.
> --
> G (�- -[ Sylvain GIL <[EMAIL PROTECTED]> || http://www.tootella.com
> ]-
> N //\ -[ Tootella : L'information Linux au quotidien
> ]-
> U v_/_
> -[----------------------------------------------------------------]-
> LINUX -[ Tout le monde me d�teste parce que je suis parano�aque
> ]-
--
Peter Buelow - Software Engineer
--
"Finger to spiritual emptiness underlying everything." -- How a C manual
referred to a "pointer to void."
------------------------------
From: Sascha Pollok <[EMAIL PROTECTED]>
Subject: Masquerading for a Server
Date: Fri, 10 Sep 1999 10:47:52 +0200
Dear folks,
here is some fine networking problem. Let's say I have
a subnet full of servers. Webservers/Mailservers/Nameservers running
WinNT and some Linux Servers.
Infront of this subnet we have a Linux-Gateway running 2.2.12
that is the def. gateway for the Servers and vice versa.
All works fine. Now we need to change IP-Addresses of the Servers
in order to route the machines via another Backbone. To keep the Servers
reachable even when some Nameservers in the world still have the
old IP.
Let's do rewriting with die Linux Box. Incoming packets for the
Subnet should be rewritten in case they carry the Server's old address.
And then should be forwarded to the Server. But what about the
packets coming from the Servers? Uhmm... did anyone get the point?
Can anyone help me, please?
Regards,
Sascha
------------------------------
From: Rage-DCA <[EMAIL PROTECTED]>
Crossposted-To:
linux.dev.admin,linux.dev.config,comp.protocols.smb,news.groups.protocols.smb,epc.samba
Subject: configuring nt users and groups in samba for pdc
Date: Fri, 10 Sep 1999 07:49:53 GMT
This is a multi-part message in MIME format.
==============7D041C8159F11DDA3B2BE448
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
i have just installed samba-2.0.5a.tar.gz and set it up as a primary
domain controller. i was able to get samba to initialize a domain in
which nt 4 workstations log in to but am having a bit of trouble. i
visited the samba site and found a samba doc
(http://us1.samba.org/docs/ntdom_faq/samba_ntdom_faq.txt) entitled
"faq for samba nt domain pdc support" and had a few quick questions
about it.
smb.conf file attached below.
roaming profiles
============
how do you turn them off and is this a good/bad idea?
user and group accounts
==================
problem:
can't get samba to recognize groups and user manager can't admin them
details:
i added the following lines to smb.conf and configured them like so
# Domain Admins
domain group map = /usr/local/samba/lib/domaingroup.map
domaingroup.map:
admin="Domain Admins"
# Local Admins
local group map = /usr/local/samba/lib/localgroup.map
localgroup.map:
wheel = BUILTIN\Administrators
# Domain User
domain user map = /usr/local/samba/lib/domainuser.map
domainuser.map:
root=Administrator
however this seems to not work correctly. local admin rights are not
passed out across the domain and i get the following error while
trying to edit the domain rules with user manager: "a remote procedure
call (RPC) protocol error occured. would you like to select another
domain to administer?" this is on an nt 4 workstation with service
pack 3. usermanger was d/led off microsoft's site.
samba also gives me the following error while loading:
[1999/09/09 20:12:14, 1] smbd/server.c:main(628)
smbd version 2.0.5a started.
Copyright Andrew Tridgell 1992-1998
[1999/09/09 20:12:14, 0] param/loadparm.c:map_parameter(1624)
Unknown parameter encountered: "domain group map"
[1999/09/09 20:12:14, 0] param/loadparm.c:lp_do_parameter(1996)
Ignoring unknown parameter "domain group map"
[1999/09/09 20:12:14, 0] param/loadparm.c:map_parameter(1624)
Unknown parameter encountered: "local group map"
[1999/09/09 20:12:14, 0] param/loadparm.c:lp_do_parameter(1996)
Ignoring unknown parameter "local group map"
[1999/09/09 20:12:14, 0] param/loadparm.c:map_parameter(1624)
Unknown parameter encountered: "domain user map"
[1999/09/09 20:12:14, 0] param/loadparm.c:lp_do_parameter(1996)
Ignoring unknown parameter "domain user map"
any ideas? the smb.conf file is included in this email. if you could
help me, i would much appreciate it. thank you, jason.
--
Jason Osborne (Rage-DCA)
- [EMAIL PROTECTED]
- http://rage.dynip.com
- LinuxInside - I run it, do you?
==============7D041C8159F11DDA3B2BE448
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]
# workgroup = NT-Domain-Name or Workgroup-Name, eg: REDHAT4
workgroup = DCA
# server string is the equivalent of the NT Description field
server string = DCA Domain/File 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.0. 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 = pcguest
# this tells Samba to use a separate log file for each machine
# that connects
log file = /usr/local/samba/var/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 = <NT-Server-Name>
# 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.12.2/24 192.168.13.2/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 = yes
# 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 = <NT-Domain-Controller-SMBName>
# 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
# Domain Admins
domain group map = /usr/local/samba/lib/domaingroup.map
# Local Admins
local group map = /usr/local/samba/lib/localgroup.map
# Domain User
domain user map = /usr/local/samba/lib/domainuser.map
#============================ Share Definitions ==============================
[homes]
comment = Home Directories
browseable = no
writable = yes
# 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/lib/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 = /usr/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/pc/%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
==============7D041C8159F11DDA3B2BE448
Content-Type: text/plain; charset=us-ascii;
name="localgroup.map"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
filename="localgroup.map"
wheel = BUILTIN\Administrators
==============7D041C8159F11DDA3B2BE448
Content-Type: text/plain; charset=us-ascii;
name="domainuser.map"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
filename="domainuser.map"
root=Administrator
==============7D041C8159F11DDA3B2BE448
Content-Type: text/plain; charset=us-ascii;
name="domaingroup.map"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
filename="domaingroup.map"
admin="Domain Admins"
==============7D041C8159F11DDA3B2BE448==
------------------------------
From: "Gonzo" <[EMAIL PROTECTED]>
Subject: wu-ftpd - How to deny domains
Date: Fri, 10 Sep 1999 08:50:49 GMT
Sorry to bother with this problem again, but it seems to be impossible for
me to solve this problem.
I'm running BeroFTPD (a wu-ftpd-based daemon) and want to be able to ban
whole domains from this service. But how the hell, I should do this ???
I tried to add the file:
deny xxx.yyy.*.*
to my ftpaccess
also I tried
deny xxx.yyy.
but this unholy deny-command only seems to work with a specified IP-adress.
if I enter
deny xxx.yyy.zzz.aaa
it works great and the host is denied !
Thanx for any kind of help !
gonZo
------------------------------
From: [EMAIL PROTECTED] (Sasa S Baksa)
Subject: Remote bridge
Date: Thu, 09 Sep 1999 08:37:39 GMT
Is there a way to setup a remote bridge (two of them) using linux box?
I have done bridging with one linux box + 2 ether cards and it works
nice, but this should be 1 ether + ppp on both sides ( ppp link
betwen).
Sasa Baksa
------------------------------
From: [EMAIL PROTECTED] (James Knott)
Subject: Re: Crossover RJ45 ethernet cables - Re: Cable problem?
Date: Thu, 09 Sep 1999 12:39:26 -0400
Reply-To: James Knott <[EMAIL PROTECTED]>
In article <[EMAIL PROTECTED]>, [EMAIL PROTECTED] (David C.) wrote:
>>> How can a cable crossing pairs 2 and 3 work for a network where
>>> signals are sent on pairs 1 and 2 (or pairs 1 and 3, depending on
>>> your patch-panel configuration)?
>>>
>>> Either way, it's a moot point for token ring. AFAIK, token ring can
>>> not work without it's MAU (TR functional equivalent of an ethernet
>>> hub). I've never heard of anybody using crossover cable to directly
>>> connect TR hosts to each other.
>>
>> I was referring to straight through cables. A 4 pair cable wired
>> according to the specs given also supports token ring. Take a look at
>> modern TR cards and media filters. You'll find an RJ45 connector, the
>> same as on ethernet systems.
>
>Ah. Yes. All Cat5-compatible devices should work with straight cables
>if all four pairs are wired. That's a no-brainer - every pin is wired
>directly to its matching pin.
>
>The same straight cables can also be used with ATM, T1, GigE (there's a
>new spec for relibaly running GigE over Cat5, in case you didn't know),
>phone systems, and many other kinds of networks.
>
>I am aware of TR running over Cat5. I saw it almost 10 years ago - back
>when IBM only supported it over the large STP cables. But doesn't it
>still require an MAU (albeit, one with RJ45 connectors) to operate? I
>don't think any kind of cabling will allow two TR hosts to be directly
>connected to each other.
Some people have claimed to have done it, but I've never seen it done.
A while ago, someone posted a circuit that emulates a MAU, using just
capacitors and resistors. I haven't tried that, but I may some day.
--
E-mail [EMAIL PROTECTED]
_________________________________________________________________________
The above opinions are my own and not those of ISM Corp., a subsidiary of
IBM Canada Ltd.
------------------------------
** FOR YOUR REFERENCE **
The service address, to which questions about the list itself and requests
to be added to or deleted from it should be directed, is:
Internet: [EMAIL PROTECTED]
You can send mail to the entire list (and comp.os.linux.networking) via:
Internet: [EMAIL PROTECTED]
Linux may be obtained via one of these FTP sites:
ftp.funet.fi pub/Linux
tsx-11.mit.edu pub/linux
sunsite.unc.edu pub/Linux
End of Linux-Networking Digest
******************************
