Linux-Networking Digest #423, Volume #11 Sat, 5 Jun 99 17:13:33 EDT
Contents:
Re: DFE-530TX won't be recognized ("Christopher A. Gaul")
got samba up and running.... ("Dave")
Re: Route (Frank Hahn)
ipautofw ("Gerald Ng")
Re: telnet as root (Green Screen)
Re: Viewing IpChains (Green Screen)
Re: Linu-NT newbie question (Green Screen)
Re: MARS_EMU for administrators ("Christopher A. Gaul")
smbclient works fine, but smbmount failes (Wilfried Huebner)
Re: Making an ICQ server (Douglas Bollinger)
Re: Linux - Windows emulators? ("Christopher A. Gaul")
----------------------------------------------------------------------------
From: "Christopher A. Gaul" <[EMAIL PROTECTED]>
Subject: Re: DFE-530TX won't be recognized
Date: Sat, 05 Jun 1999 15:41:45 -0400
==============3E07752DC8B366A9FD74D5DD
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
I checked D-Link's web-site and they have this file available for the 530TX:
ftp://ftp.dlinknet.com/PUB/Drivers/linux.zip
Not sure if it's what you need, but definitely worth checking out.
Christopher A. Gaul
CyberDyne Systems
------------------------------------------------------------------------
John Porsley wrote:
> I have tried just about everything I have read or guessed at to get this
> board up. I have tried via-rhine, ne, ne-pci, etc. Rearranging the
> cards/slots. Disabling Pnp.
>
> The machine works fine under w95 (internet and peer to peer). But Linux
> can't find the NIC at installation, and won't see it when I feed it the
> I/O that the DOS utility gives me (e480h) and the IRC (9). I have
> re-installed several times.
>
> I even tried putting an ISA Linksys in that I know works in w95, but
> Linux won't see that card either (NE2000 compatible).
>
> I called D-Link, and they say there is no way to disable PnP.
>
> I have tried:
>
> /etc/conf.modules
> alias eth0 via-rhine
>
> /etc/sysconfig/ifup-eth0
> insmod via-rhine
>
> /etc/sysconfig/ifdown-eth0
> rmmod via-rhine
>
> No joy.
>
> What gives? I have a Tyan mobo, if that matters.
>
> Any help from the experts?
>
> Thanks,
>
> John
==============3E07752DC8B366A9FD74D5DD
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit
<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
I checked D-Link's web-site and they have this file available for the 530TX:
<br> <a
href="ftp://ftp.dlinknet.com/PUB/Drivers/linux.zip">ftp://ftp.dlinknet.com/PUB/Drivers/linux.zip</a>
<p>Not sure if it's what you need, but definitely worth checking out.
<p>Christopher A. Gaul
<br>CyberDyne Systems
<p>
<hr WIDTH="100%">
<p>John Porsley wrote:
<blockquote TYPE=CITE>I have tried just about everything I have read or
guessed at to get this
<br>board up. I have tried via-rhine, ne, ne-pci, etc. Rearranging
the
<br>cards/slots. Disabling Pnp.
<p>The machine works fine under w95 (internet and peer to peer).
But Linux
<br>can't find the NIC at installation, and won't see it when I feed it
the
<br>I/O that the DOS utility gives me (e480h) and the IRC (9). I
have
<br>re-installed several times.
<p>I even tried putting an ISA Linksys in that I know works in w95, but
<br>Linux won't see that card either (NE2000 compatible).
<p>I called D-Link, and they say there is no way to disable PnP.
<p>I have tried:
<p>/etc/conf.modules
<br> alias eth0 via-rhine
<p>/etc/sysconfig/ifup-eth0
<br> insmod via-rhine
<p>/etc/sysconfig/ifdown-eth0
<br> rmmod via-rhine
<p>No joy.
<p>What gives? I have a Tyan mobo, if that matters.
<p>Any help from the experts?
<p>Thanks,
<p>John</blockquote>
</html>
==============3E07752DC8B366A9FD74D5DD==
------------------------------
From: "Dave" <[EMAIL PROTECTED]>
Subject: got samba up and running....
Date: Sat, 5 Jun 1999 15:38:17 -0400
okay i have it all working... however....i can't WRITE any files or
directories... on the linux box itself, only ROOT can write to "/dev/hda1
/mnt/store" ... i want another user to have write acess as well...any ideas
how to do this? this is a -vfat drive filesystem..and like i said, root CAN
write to it..but i don't care about that.....i want another user to be able
to as well.... thanks for any input..
-dave
------------------------------
From: [EMAIL PROTECTED] (Frank Hahn)
Subject: Re: Route
Date: Sat, 05 Jun 1999 19:39:52 GMT
Reply-To: [EMAIL PROTECTED]
On Fri, 04 Jun 1999 17:09:08 -0400, valner <[EMAIL PROTECTED]> wrote:
> but I found out that my ISP was waiting for the name of the machine I want
>login... .. then I add the line in my script and it seems work .. until ... I
>get another error:
>
> valner pppd[156]: Using interface ppp0
> valner pppd[156]: Connect: ppp0 <--> /dev/ttyS2
> valner pppd[156]: serial line is looped back
> valner pppd[156]: connection terminated
>valner pppd[156]: exit
>
This comes directly from the pppd FAQ included in the pppd source
file:
========================================================================
Q: When I try to establish a connection, I get an error message saying
"Serial line is looped back". Why?
A: Probably your connection script hasn't successfully dialled out to
the remote system and invoked ppp service there. Instead, pppd is
talking to something which is just echoing back the characters it
receives. The -v option to chat can help you find out what's going
on. It can be useful to include "~" as the last expect string to
chat, so chat won't return until it's seen the start of the first PPP
frame from the remote system.
Another possibility is that your phone connection has dropped for some
obscure reason and the modem is echoing the characters it receives
from your system.
========================================================================
The source file can be downloaded from here:
ftp://cs.anu.edu.au/pub/software/ppp/
Most likely, if you have a distribution on CD, these documents are
on it.
Good luck.
--
Frank Hahn
Your life would be very empty if you had nothing to regret.
------------------------------
From: "Gerald Ng" <[EMAIL PROTECTED]>
Subject: ipautofw
Date: Sat, 05 Jun 1999 19:40:22 GMT
Hi all,
I'm very new to Linux and would like to know how ipautofw works. Could I
use this to open a port (TCP, UDP) for one of my nodes on the linux server?
If so, how could I do that?? If anyone knows please shed some light to the
issue.
Thanx in advance
Gerald
------------------------------
From: Green Screen <[EMAIL PROTECTED]>
Subject: Re: telnet as root
Date: 5 Jun 1999 19:39:35 GMT
either login as normal user and use 'su' (good way)
or fix /etc/securetty (and possibly /etc/login.defs) so root logins are
allowed on ttyp0, ttyp1, ttyp2, etc
Lint^^
Marten Weber <[EMAIL PROTECTED]> wrote:
: Hi
: How can I make a telnet session to a linux computer in my little network
: as "root", so that I don't need a graphic card and a monitor in this
: computer ?
: Thanks for help
: Marten
------------------------------
From: Green Screen <[EMAIL PROTECTED]>
Subject: Re: Viewing IpChains
Date: 5 Jun 1999 19:32:47 GMT
ipchains -L
Dzerdecki <[EMAIL PROTECTED]> wrote:
: How do you view all your IpChains?
: Thanks.
: Drew
------------------------------
From: Green Screen <[EMAIL PROTECTED]>
Subject: Re: Linu-NT newbie question
Date: 5 Jun 1999 19:33:56 GMT
NET-3 HOWTO, ETHERNET HOWTO, etc... http://metalab.unc.edu/LDP/
El Squid <[EMAIL PROTECTED]> wrote:
: Hello - I am considering adding a Linux box to my soon to be NT
: network. Can someone point me to a FAQ or other reference for
: constructing this ?
: Thanks in advance,
: El-Squid
: --
:>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
:>>> Remember the future, Imagine the Past... >>>>
:>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
: Sent via Deja.com http://www.deja.com/
: Share what you know. Learn what you don't.
------------------------------
From: "Christopher A. Gaul" <[EMAIL PROTECTED]>
Subject: Re: MARS_EMU for administrators
Date: Sat, 05 Jun 1999 15:44:28 -0400
Alexei,
Thanks for the post and the info. Hopefully this will clear up my own MARS_NWE
problems.
Christopher A. Gaul
CyberDyne Systems
Alexei Kakhno wrote:
> I see many questions in the newsgroup about MarsNWE server
> and decide to help because my server works for a long time
> without any problems and never turned off as Unix server,
> IP router, PPP for remote Windows95 users to access to Internet,
> NFS AIX <--> Linux.
> Hardware: Motherboard HX chipset, CPU P166,
> Netcards: ISS 3c509, 3 of PCI 3c590. Linux 5.0 with kernel 2.0.36.
>
> First, IPX must be in your kernel for NCP package and
> MarsNWE Server,
>
> do:
>
> cd /usr/src/linux
> make config # assign Y for CONFIG_IPX
> # or check .config if CONFIG_IPX=Y all ok!!!
>
> re-compile kernel and install it.
>
> then unzip , untar... MarsNWE sources and edit config.h of the MarsNWE
>
> for your needs, read README, etc Be attention!!! read, read ...
>
> create novell group
> add users they must be belong to the novell group
> -----------------------------------------------------------
> each user has the same home directory i.e /home/novell
>
> .bash_profile:
>
> # add exit 1 --- user can't use telnet
> exit 1
>
> ----------------------------------------------------------
> add names of the novell users into /etc/ftpusers
> # user can't use ftp
> ----------------------------------------------------------
>
> chmod +t /usr1/SYS # each user can control own files, delete, etc
>
> ------------------------------------------------------------
> Here's my /etc/nwserv.conf :
>
> # This is the configuration-file for "mars_nwe", a free
> # netware-emulator
> # for Linux.
> #
> #
> # !! section 4 : automatic creation of ipx-interfaces changed in
> # 0.98.pl9 !!
> #
> # since version 0.98.pl11:
> # the most important options in config.h can now be altered in
> # this file begin at section 60.
> #
>
> # This file specifies which Linux-resources (printers, users,
> # directories)
> # should be accessible to the DOS-clients via "mars_nwe". Furthermore
> # some general parameters are configured here.
> # Some options of "mars_nwe" can only be altered by editing the the
> # file
> # `config.h' and re-compiling "mars_nwe", please see there for more
> # information.
>
> #
> =========================================================================
> # Section 1: volumes (required)
> #
>
> 1 SYS /usr1/SYS k
> 1 SYS1 /usr2/SYS k
>
> #
> =========================================================================
> # Section 2: servername (optional)
> #
> 2 ROF
>
> #
> =========================================================================
> # Section 3: Number of the internal network (required)
> #
>
> 3 auto
>
> #
> =========================================================================
> # Section 4: IPX-devices (strongly recommended)
>
> 4 0x1 eth2 802.2 1
> 4 0x3 eth3 802.2 1
> 4 0x4 eth1 802.2 1
>
> # Section 5: special device flags
> #
> =========================================================================
> # Flags
>
> 5 0x1
>
> #
> =========================================================================
> # Section 6: version-"spoofing"
>
> 6 1 0x0
>
> #
> =========================================================================
> # Section 7: password handling of DOS-clients (required)
>
> 7 0
>
> # Section 8: special login/logout/security and other flags.
>
> 8 0x0
>
> # Section 9: Standard creat mode for creating directories and files.
> #
> #=========================================================================
>
> 9 0770 0770
>
> #=========================================================================
> # Section 10: UID and GID with minimal rights
>
> 10 200
> 11 65534
>
> #
> =========================================================================
> # Section 12: supervisor-login (required)
>
> 12 SUPERVISOR root
>
> #
> =========================================================================
> # Section 13: user-logins (optional)
> #
>
> 13 ALEX alex baba 0x1
> 13 director director 0x1
>
> # Section 14: currently not used
>
> #
> =========================================================================
> # Section 15: automatic mapping of logins (decision required)
>
> 15 0 top-secret
>
> #
> =========================================================================
> # Section 16: Tests on startup
>
> 16 1
>
> # Section 17-20: currently not used
>
> #
> =========================================================================
> # Section 21: print queues (optional)
>
> #
> =========================================================================
> # Section 22: print server entries (optional)
>
> #
> =========================================================================
> # Section 30: Burst mode values (optional)
>
> #
> =========================================================================
> # Section 40ff: Some pathes (optional)
> #
> -------------------------------------------------------------------------
> # 40 = path for vol/dev/inode->path cache, needed for
> client-32,namespace
> 40 /var/spool/nwserv/.volcache
> # 41 = path for share/lock files
> 41 /var/spool/nwserv/.locks
> # 42 = path for spool dir
> 42 /var/spool/nwserv
> #
> #
> # 45 = path for bindery file's
>
> 45 /var/mars_nwe/bindery
>
> #
> =========================================================================
> # Section 50: Conversion tables by Victor Khimenko <[EMAIL PROTECTED]>
> # Tables for DOS->Unix names translation & upper/lowercase
> translations
> # For more information see doc/README.NLS
> # some examples files exist in the examples directory.
> # Conversation file must include 4 tables a 256 byte.
> # 0 = dos2unix
> # 1 = unix2dos
> # 2 = down2up 'dosname'
> # 3 = up2down 'dosname'
> #
> -------------------------------------------------------------------------
> # Syntax:
> # 50 Filename of conversation file.
> #
> # Examples:
> # 50 /etc/nwserv.cnv
>
> # Changing defaults from config.h
> # more information in config.h
> # 60 10 # MAX_CONNECTIONS
> # 61 10 # MAX_NW_VOLS
>
> # 68 1 # USE_MMAP (use mmap=1, no mmap=0)
> # 69 0 # HANDLE_ALL_SAP_TYPS (all sap typs=1, only typ 4=0)
>
> # 70 0x44444444 # NETWORK_SERIAL_NMBR (4 byte)
> # 71 0x2222 # NETWORK_APPL_NMBR (2 byte)
>
> # --------------------------------------------------------
> # You usally don't want to change anything below this line
> # --------------------------------------------------------
>
> # Sections 100-106: amount of debug-information
> #
> # FLAG:
> # 0 no debug messages
> # 1 errors and notes are reported
> # 99 maximum debug levels
>
> 100 0 # debug IPX KERNEL (0 | 1)
> 101 1 # debug NWSERV
> 102 0 # debug NCPSERV
> 103 0 # debug NWCONN
> 104 0 # debug (start) NWCLIENT, should *always* be
> '0' !
> 105 0 # debug NWBIND
> 106 1 # debug NWROUTED
>
> # Sections 200-202: logging of "nwserv"
> #
> 200 1 # 0 = no logfile and dont daemonize
> nwserv/nwrouted
> # 1 = daemonize nwserv/nwrouted and use
> logfile
> 201 /var/mars_nwe/nw.log # filename of logfile
> #201 syslog # if filename == syslog then syslogd will be
> used for
> # all messages
>
> 202 0x0 # flag in hex notation
> # 0x0=append all messages to logfile.
> # & 0x1=creat new logfile instead of
> appending.
> #202 0x3 # & 0x2=use syslogd for error messages instead
> of logfile.
>
> # Sections 210,211: timing
>
> 210 10 # 1 .. 600 (default 10) seconds after server
> # really goes down after a down command
> 211 60 # 10 .. 600 (default 60) broadcasts every x
> seconds
>
> # Sections 300-302: loging of routing-information
>
> 300 1 # > 0 print routing info to file every x
> broadcasts.
> # ( normally minutes )
> 301 /var/mars_nwe/nw.routes # filename of logfile
>
> 302 0x0 # flags will be interpreted as hex value.
> # 0 = append to this file
> # & 0x1 = creat new routing info file
> # & 0x2 = split info into several files
> # (extensions = .1, .2, .3 ... )
>
> # Section 310: watchdogs
>
> 310 7 # send wdog's only to device net < x ticks.
> # 0 = always send wdogs. < 0 = never send
> # wdogs
>
> # Section 400:
> # station file for special handling of stations.
>
> 400 /etc/nwserv.stations # for syntax see file in the examples
>
> # Section 401: nearest server
> #
> # for special handling of the 'get nearest server request'.
> 401 0 # 0 = ignore entry 400, get nearest response always
> # enabled.
>
> # Section 402: station connect restrictions
> #
> # for special handling of the 'creat connection' (attach) call.
> 402 0 # 0 = ignore entry 400, create connection always
> # enabled.
>
> # *************************************************************
>
> i'll be glad if this information usefull
>
> Best wishes, Alexei
> mailto: [EMAIL PROTECTED]
------------------------------
From: [EMAIL PROTECTED] (Wilfried Huebner)
Subject: smbclient works fine, but smbmount failes
Date: Sat, 05 Jun 1999 19:48:56 GMT
I have Suse 6.1, Kernel 2.2.5 and Samba 2.03. and W98 on a second
Machine. The Network runs in both directions. But on the Linux Machine
I get only the ftp like connection to the remote W98 Partitions by
smbclient //W98Name/W98Partition/
which is followed by the smb:\> Prompt.
Unfortunately I cannot mount any remote W98 Partition on the Linux
Machine. I have read lots of notes and manpages and tried out
everything which has been recommended in this newsgroup.
The only Instruction which did something was:
smbmount //W98Name/W98Partition -c "mount /mountpoint"
Afterwards the W98Partition was loaded bitwise into the mountpoint
directory.
I have loaded the smb filesystem module by modprobe smbfs and then
tried
mount -t smbfs //W98Name/W98Partition /mountpoint
No success. Does anyone know what I do wrong?
Wilfried
------------------------------
From: [EMAIL PROTECTED] (Douglas Bollinger)
Crossposted-To: comp.os.linux.misc
Subject: Re: Making an ICQ server
Date: Sat, 5 Jun 1999 16:33:38 -0400
[EMAIL PROTECTED] at [EMAIL PROTECTED] says...
> IRC and ICQ are TOTALLY differnt concepts. ICQ is for sending messages
> back and forth, and does NOT require you to sit and watch the chat go
> by. You can have messages sent to you, and you don't have to answer
> them right away, because they're not getting pushed out of the way by
> others. IRC is a CHAT program. Totally different.
Another great advantage to ICQ is that you can easily see if someone
on your buddy list is online and read to talk. It transparently
handles the fact the most internet users don't have a dedicated IP#.
It's great for sending someone a quick message, and in a pinch works
well as chat client and allows the users to exchange binaries.
It would be nice if some of the UN*X diehards around here would
crawl out from under their rocks and see what's going on in the rest
of the world. There are some good reasons why ICQ is one of the
most d/l programs on the internet.
--
Douglas Bollinger
Mt. Holly Springs, PA 17065
My other computer runs Linux.
------------------------------
From: "Christopher A. Gaul" <[EMAIL PROTECTED]>
Subject: Re: Linux - Windows emulators?
Date: Sat, 05 Jun 1999 16:00:02 -0400
==============56AF33FA20130D00320DE559
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Probably the ultimate solution exists at:
VM-Ware
Christopher A. Gaul
CyberDyne Systems
Jon Finanger wrote:
> Does such emulator exist?
> (to run windows programs in linux env.)
>
> -Jon
>
> --
> -- -- -- --
> [EMAIL PROTECTED]
==============56AF33FA20130D00320DE559
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit
<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
Probably the ultimate solution exists at:
<br> <a href="http://www.vmware.com/">VM-Ware</a>
<p>Christopher A. Gaul
<br>CyberDyne Systems
<p>Jon Finanger wrote:
<blockquote TYPE=CITE>Does such emulator exist?
<br>(to run windows programs in linux env.)
<p>-Jon
<p>--
<br>-- -- -- --
<br>[EMAIL PROTECTED]</blockquote>
</html>
==============56AF33FA20130D00320DE559==
------------------------------
** 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
******************************
