Linux-Networking Digest #392, Volume #12 Sat, 28 Aug 99 03:13:52 EDT
Contents:
Re: Being an ISP ("Odysseus")
Re: /net mounted as NFS (David Crooke)
WINS not working ("Daniel J. Peng")
Re: WINS not working ("Daniel J. Peng")
try replacing inetd(8), Re: telnet connects, but 'closed by foreign host' b4 prompt
(Cameron L. Spitzer)
Re: linux-based telnetrc tricks of the trade (Christopher Allen)
Re: Is this possible? HELP! SMB+Masq ('N)
Re: Being an ISP ("Scott Simpson")
Re: Cybercafe Linux (Scott Martin)
Re: VMware - wow! (Rod Roark)
Re: dual ethernet, no joy (Chris)
----------------------------------------------------------------------------
From: "Odysseus" <[EMAIL PROTECTED]>
Subject: Re: Being an ISP
Date: Sat, 28 Aug 1999 16:45:44 +1200
Reply-To: "Odysseus" <NOSPAM@NOSPAM>COM>
All your questions can be answered if you read the HOWTOs.
Assad Khan <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> Ok, I want to know how people can dial up to my machine. Also, I want to
> know how to IP Masq my home network (running 2 WinNT Workstations, 1
> Win98, and 1 Win95) with a T1 and 100mbit LAN.
> Specs:
>
> Pentium III 500mhz
> 128mb RAM
> 2 10/100mbit ethernet cards
> 1 internal modem (used for when I need to dialup to my machine)
> Running Slackware 4.0 with kernel 2.2.12 (compiled with everything I
> need).
>
> Assad
>
------------------------------
From: David Crooke <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Subject: Re: /net mounted as NFS
Date: Fri, 27 Aug 1999 13:53:32 GMT
It's the "hosts map" automounter - if you do "ls /net/host.name/" it
will show available filesystem which can be mounted from that host, and
mount them automatically when you access them.
It's the Unix equivalent of Windows "Network Neighbourhood" browser.
Dave
--
David Crooke, Austin TX, USA. +1 (512) 656 6102
"Open source software - with no walls and fences, who needs Windows
and Gates?"
------------------------------
From: "Daniel J. Peng" <[EMAIL PROTECTED]>
Subject: WINS not working
Date: Sat, 28 Aug 1999 01:12:15 -0400
Would one of you know how to fix this? I can't seem to get my linux WINS
server
(192.168.0.23) to work. Every time another (linux) Samba server
(192.168.0.42)
tries to register its name with WINS, it gives these error messages and
similar
ones when it tries to release its name: (No error messages show up in
the WINS
server's logs)
[1999/08/27 16:22:25, 1] nmbd/nmbd.c:main(672)
Netbios nameserver version 2.0.3 started.
Copyright Andrew Tridgell 1994-1998
doing parameter security = share
doing parameter socket options = TCP_NODELAY
doing parameter interfaces = 192.168.0.42/255.255.255.0
127.0.0.1/255.0.0.0
doing parameter local master = no
doing parameter os level = 33
doing parameter domain master = no
doing parameter preferred master = no
doing parameter wins support = no
doing parameter wins server = 192.168.0.23
doing parameter dns proxy = no
doing parameter comment = Linux File and Print Server
doing parameter encrypt passwords = no
doing parameter password level = 0
doing parameter preferred master = no
doing parameter os level = 0
doing parameter null passwords = yes
doing parameter dead time = 0
doing parameter debug level = 0
[1999/08/27 16:22:25, 0] libsmb/nmblib.c:send_udp(725)
Packet send failed to 192.168.0.23(137) ERRNO=Invalid argument
[1999/08/27 16:22:25, 0] nmbd/nmbd_packets.c:send_netbios_packet(170)
send_netbios_packet: send_packet() to IP 192.168.0.23 port 137 failed
[1999/08/27 16:22:25, 0]
nmbd/nmbd_nameregister.c:multihomed_register_name(305)
multihomed_register_name: Failed to send packet trying to register
name I686-3
00-LINUX<20> IP 127.0.0.1
[1999/08/27 16:22:25, 0] libsmb/nmblib.c:send_udp(725)
Packet send failed to 192.168.0.23(137) ERRNO=Invalid argument
[1999/08/27 16:22:25, 0] nmbd/nmbd_packets.c:send_netbios_packet(170)
send_netbios_packet: send_packet() to IP 192.168.0.23 port 137 failed
[1999/08/27 16:22:25, 0]
nmbd/nmbd_nameregister.c:multihomed_register_name(305)
multihomed_register_name: Failed to send packet trying to register
name I686-3
00-LINUX<03> IP 127.0.0.1
[1999/08/27 16:22:25, 0] libsmb/nmblib.c:send_udp(725)
Packet send failed to 192.168.0.23(137) ERRNO=Invalid argument
[1999/08/27 16:22:25, 0] nmbd/nmbd_packets.c:send_netbios_packet(170)
send_netbios_packet: send_packet() to IP 192.168.0.23 port 137 failed
[1999/08/27 16:22:25, 0]
nmbd/nmbd_nameregister.c:multihomed_register_name(305)
multihomed_register_name: Failed to send packet trying to register
name I686-3
00-LINUX<00> IP 127.0.0.1
[1999/08/27 16:22:25, 0] libsmb/nmblib.c:send_udp(725)
Packet send failed to 192.168.0.23(137) ERRNO=Invalid argument
[1999/08/27 16:22:25, 0] nmbd/nmbd_packets.c:send_netbios_packet(170)
send_netbios_packet: send_packet() to IP 192.168.0.23 port 137 failed
[1999/08/27 16:22:25, 0]
nmbd/nmbd_nameregister.c:multihomed_register_name(305)
multihomed_register_name: Failed to send packet trying to register
name I686-3
00-LINUX<00> IP 127.0.0.1
[1999/08/27 16:22:25, 0] libsmb/nmblib.c:send_udp(725)
Packet send failed to 192.168.0.23(137) ERRNO=Invalid argument
[1999/08/27 16:22:25, 0] nmbd/nmbd_packets.c:send_netbios_packet(170)
send_netbios_packet: send_packet() to IP 192.168.0.23 port 137 failed
[1999/08/27 16:22:25, 0]
nmbd/nmbd_nameregister.c:multihomed_register_name(305)
multihomed_register_name: Failed to send packet trying to register
name I686-3
00-W32<20> IP 127.0.0.1
[1999/08/27 16:22:25, 0] libsmb/nmblib.c:send_udp(725)
Packet send failed to 192.168.0.23(137) ERRNO=Invalid argument
[1999/08/27 16:22:25, 0] nmbd/nmbd_packets.c:send_netbios_packet(170)
send_netbios_packet: send_packet() to IP 192.168.0.23 port 137 failed
[1999/08/27 16:22:25, 0]
nmbd/nmbd_nameregister.c:multihomed_register_name(305)
multihomed_register_name: Failed to send packet trying to register
name I686-3
00-W32<03> IP 127.0.0.1
[1999/08/27 16:22:25, 0] libsmb/nmblib.c:send_udp(725)
Packet send failed to 192.168.0.23(137) ERRNO=Invalid argument
[1999/08/27 16:22:25, 0] nmbd/nmbd_packets.c:send_netbios_packet(170)
send_netbios_packet: send_packet() to IP 192.168.0.23 port 137 failed
[1999/08/27 16:22:25, 0]
nmbd/nmbd_nameregister.c:multihomed_register_name(305)
multihomed_register_name: Failed to send packet trying to register
name I686-3
00-W32<00> IP 127.0.0.1
[1999/08/27 16:22:25, 0] libsmb/nmblib.c:send_udp(725)
Packet send failed to 192.168.0.23(137) ERRNO=Invalid argument
[1999/08/27 16:22:25, 0] nmbd/nmbd_packets.c:send_netbios_packet(170)
send_netbios_packet: send_packet() to IP 192.168.0.23 port 137 failed
[1999/08/27 16:22:25, 0]
nmbd/nmbd_nameregister.c:multihomed_register_name(305)
multihomed_register_name: Failed to send packet trying to register
name WORKGR
OUP<00> IP 127.0.0.1
[1999/08/27 16:22:25, 0] libsmb/nmblib.c:send_udp(725)
Packet send failed to 192.168.0.23(137) ERRNO=Invalid argument
[1999/08/27 16:22:25, 0] nmbd/nmbd_packets.c:send_netbios_packet(170)
send_netbios_packet: send_packet() to IP 192.168.0.23 port 137 failed
[1999/08/27 16:22:25, 0]
nmbd/nmbd_nameregister.c:multihomed_register_name(305)
multihomed_register_name: Failed to send packet trying to register
name WORKGR
OUP<1e> IP 127.0.0.1
-- smb.conf for WINS server --
[global]
netbios name = I486
bind interfaces only = true
workgroup = WORKGROUP
server string = Samba Server
hosts allow = 192.168.0. 127.
printcap name = /etc/printcap
load printers = yes
log file = /var/log/samba/log.%m
max log size = 50
security = share
socket options = TCP_NODELAY
interfaces = 192.168.0.23/255.255.255.0 127.0.0.1/255.0.0.0
local master = yes
os level = 255
preferred master = yes
wins support = yes
dns proxy = no
comment = Linux File and Print Server
encrypt passwords = no
password level = 0
preferred master = no
os level = 0
null passwords = yes
dead time = 0
debug level = 0
domain master = no
[homes]
comment = Home Directories
browseable = no
writable = yes
available = no
public = no
only user = no
[root-ro]
comment = Root-readonly
browseable = yes
writeable = no
only user = no
[root-ro]
comment = Root-readonly
browseable = yes
writeable = no
available = yes
public = yes
guest ok = yes
path = /
[root-rw]
comment = Root-readwrite
browseable = yes
writable = yes
available = yes
public = no
path = /
[printers]
-- start smb.conf for WINS "client" --
[global]
netbios name = I686-300-LINUX
netbios aliases = I686-300-W32
workgroup = WORKGROUP
server string = Samba Server
hosts allow = 192.168.0. 127.
printcap name = /etc/printcap
load printers = yes
log file = /var/log/samba/log.%m
max log size = 50
log level = 3
security = share
socket options = TCP_NODELAY
interfaces = 192.168.0.42/255.255.255.0 127.0.0.1/255.0.0.0
local master = no
os level = 33
domain master = no
preferred master = no
wins support = no
wins server = 192.168.0.23
dns proxy = no
comment = Linux File and Print Server
encrypt passwords = no
password level = 0
preferred master = no
os level = 0
null passwords = yes
dead time = 0
debug level = 0
domain master = no
[homes]
comment = Home Directories
browseable = no
writable = yes
available = no
public = no
only user = no
[root-ro]
comment = Root-readonly
browseable = yes
writeable = no
available = yes
public = yes
guest ok = yes
path = /
[root-rw]
comment = Root-readwrite
browseable = yes
writable = yes
available = yes
public = no
path = /
[printers]
comment = All Printers
path = /var/spool/samba
browseable = yes
guest ok = yes
writable = no
printable = yes
=========
Could somebody help me get WINS working? I have no idea what could
possibly be
wrong. TCP/IP & all other services (ping, ftp, http, telnet, rlogin) all
seem to
be working fine, but Samba just keeps throwing this error at me. Please
e-mail
me if it would be helpful to have more information.
Thanks,
Daniel J. Peng
[EMAIL PROTECTED]
------------------------------
From: "Daniel J. Peng" <[EMAIL PROTECTED]>
Subject: Re: WINS not working
Date: Sat, 28 Aug 1999 01:13:31 -0400
Sorry about the ugly wrapping... here's a correctly wrapped version.
====================================
Would one of you know how to fix this? I can't seem to get my linux WINS server
(192.168.0.23) to work. Every time another (linux) Samba server (192.168.0.42)
tries to register its name with WINS, it gives these error messages and similar
ones when it tries to release its name: (No error messages show up in the WINS
server's logs)
[1999/08/27 16:22:25, 1] nmbd/nmbd.c:main(672)
Netbios nameserver version 2.0.3 started.
Copyright Andrew Tridgell 1994-1998
doing parameter security = share
doing parameter socket options = TCP_NODELAY
doing parameter interfaces = 192.168.0.42/255.255.255.0 127.0.0.1/255.0.0.0
doing parameter local master = no
doing parameter os level = 33
doing parameter domain master = no
doing parameter preferred master = no
doing parameter wins support = no
doing parameter wins server = 192.168.0.23
doing parameter dns proxy = no
doing parameter comment = Linux File and Print Server
doing parameter encrypt passwords = no
doing parameter password level = 0
doing parameter preferred master = no
doing parameter os level = 0
doing parameter null passwords = yes
doing parameter dead time = 0
doing parameter debug level = 0
[1999/08/27 16:22:25, 0] libsmb/nmblib.c:send_udp(725)
Packet send failed to 192.168.0.23(137) ERRNO=Invalid argument
[1999/08/27 16:22:25, 0] nmbd/nmbd_packets.c:send_netbios_packet(170)
send_netbios_packet: send_packet() to IP 192.168.0.23 port 137 failed
[1999/08/27 16:22:25, 0] nmbd/nmbd_nameregister.c:multihomed_register_name(305)
multihomed_register_name: Failed to send packet trying to register name I686-3
00-LINUX<20> IP 127.0.0.1
[1999/08/27 16:22:25, 0] libsmb/nmblib.c:send_udp(725)
Packet send failed to 192.168.0.23(137) ERRNO=Invalid argument
[1999/08/27 16:22:25, 0] nmbd/nmbd_packets.c:send_netbios_packet(170)
send_netbios_packet: send_packet() to IP 192.168.0.23 port 137 failed
[1999/08/27 16:22:25, 0] nmbd/nmbd_nameregister.c:multihomed_register_name(305)
multihomed_register_name: Failed to send packet trying to register name I686-3
00-LINUX<03> IP 127.0.0.1
[1999/08/27 16:22:25, 0] libsmb/nmblib.c:send_udp(725)
Packet send failed to 192.168.0.23(137) ERRNO=Invalid argument
[1999/08/27 16:22:25, 0] nmbd/nmbd_packets.c:send_netbios_packet(170)
send_netbios_packet: send_packet() to IP 192.168.0.23 port 137 failed
[1999/08/27 16:22:25, 0] nmbd/nmbd_nameregister.c:multihomed_register_name(305)
multihomed_register_name: Failed to send packet trying to register name I686-3
00-LINUX<00> IP 127.0.0.1
[1999/08/27 16:22:25, 0] libsmb/nmblib.c:send_udp(725)
Packet send failed to 192.168.0.23(137) ERRNO=Invalid argument
[1999/08/27 16:22:25, 0] nmbd/nmbd_packets.c:send_netbios_packet(170)
send_netbios_packet: send_packet() to IP 192.168.0.23 port 137 failed
[1999/08/27 16:22:25, 0] nmbd/nmbd_nameregister.c:multihomed_register_name(305)
multihomed_register_name: Failed to send packet trying to register name I686-3
00-LINUX<00> IP 127.0.0.1
[1999/08/27 16:22:25, 0] libsmb/nmblib.c:send_udp(725)
Packet send failed to 192.168.0.23(137) ERRNO=Invalid argument
[1999/08/27 16:22:25, 0] nmbd/nmbd_packets.c:send_netbios_packet(170)
send_netbios_packet: send_packet() to IP 192.168.0.23 port 137 failed
[1999/08/27 16:22:25, 0] nmbd/nmbd_nameregister.c:multihomed_register_name(305)
multihomed_register_name: Failed to send packet trying to register name I686-3
00-W32<20> IP 127.0.0.1
[1999/08/27 16:22:25, 0] libsmb/nmblib.c:send_udp(725)
Packet send failed to 192.168.0.23(137) ERRNO=Invalid argument
[1999/08/27 16:22:25, 0] nmbd/nmbd_packets.c:send_netbios_packet(170)
send_netbios_packet: send_packet() to IP 192.168.0.23 port 137 failed
[1999/08/27 16:22:25, 0] nmbd/nmbd_nameregister.c:multihomed_register_name(305)
multihomed_register_name: Failed to send packet trying to register name I686-3
00-W32<03> IP 127.0.0.1
[1999/08/27 16:22:25, 0] libsmb/nmblib.c:send_udp(725)
Packet send failed to 192.168.0.23(137) ERRNO=Invalid argument
[1999/08/27 16:22:25, 0] nmbd/nmbd_packets.c:send_netbios_packet(170)
send_netbios_packet: send_packet() to IP 192.168.0.23 port 137 failed
[1999/08/27 16:22:25, 0] nmbd/nmbd_nameregister.c:multihomed_register_name(305)
multihomed_register_name: Failed to send packet trying to register name I686-3
00-W32<00> IP 127.0.0.1
[1999/08/27 16:22:25, 0] libsmb/nmblib.c:send_udp(725)
Packet send failed to 192.168.0.23(137) ERRNO=Invalid argument
[1999/08/27 16:22:25, 0] nmbd/nmbd_packets.c:send_netbios_packet(170)
send_netbios_packet: send_packet() to IP 192.168.0.23 port 137 failed
[1999/08/27 16:22:25, 0] nmbd/nmbd_nameregister.c:multihomed_register_name(305)
multihomed_register_name: Failed to send packet trying to register name WORKGR
OUP<00> IP 127.0.0.1
[1999/08/27 16:22:25, 0] libsmb/nmblib.c:send_udp(725)
Packet send failed to 192.168.0.23(137) ERRNO=Invalid argument
[1999/08/27 16:22:25, 0] nmbd/nmbd_packets.c:send_netbios_packet(170)
send_netbios_packet: send_packet() to IP 192.168.0.23 port 137 failed
[1999/08/27 16:22:25, 0] nmbd/nmbd_nameregister.c:multihomed_register_name(305)
multihomed_register_name: Failed to send packet trying to register name WORKGR
OUP<1e> IP 127.0.0.1
-- smb.conf for WINS server --
[global]
netbios name = I486
bind interfaces only = true
workgroup = WORKGROUP
server string = Samba Server
hosts allow = 192.168.0. 127.
printcap name = /etc/printcap
load printers = yes
log file = /var/log/samba/log.%m
max log size = 50
security = share
socket options = TCP_NODELAY
interfaces = 192.168.0.23/255.255.255.0 127.0.0.1/255.0.0.0
local master = yes
os level = 255
preferred master = yes
wins support = yes
dns proxy = no
comment = Linux File and Print Server
encrypt passwords = no
password level = 0
preferred master = no
os level = 0
null passwords = yes
dead time = 0
debug level = 0
domain master = no
[homes]
comment = Home Directories
browseable = no
writable = yes
available = no
public = no
only user = no
[root-ro]
comment = Root-readonly
browseable = yes
writeable = no
only user = no
[root-ro]
comment = Root-readonly
browseable = yes
writeable = no
available = yes
public = yes
guest ok = yes
path = /
[root-rw]
comment = Root-readwrite
browseable = yes
writable = yes
available = yes
public = no
path = /
[printers]
-- start smb.conf for WINS "client" --
[global]
netbios name = I686-300-LINUX
netbios aliases = I686-300-W32
workgroup = WORKGROUP
server string = Samba Server
hosts allow = 192.168.0. 127.
printcap name = /etc/printcap
load printers = yes
log file = /var/log/samba/log.%m
max log size = 50
log level = 3
security = share
socket options = TCP_NODELAY
interfaces = 192.168.0.42/255.255.255.0 127.0.0.1/255.0.0.0
local master = no
os level = 33
domain master = no
preferred master = no
wins support = no
wins server = 192.168.0.23
dns proxy = no
comment = Linux File and Print Server
encrypt passwords = no
password level = 0
preferred master = no
os level = 0
null passwords = yes
dead time = 0
debug level = 0
domain master = no
[homes]
comment = Home Directories
browseable = no
writable = yes
available = no
public = no
only user = no
[root-ro]
comment = Root-readonly
browseable = yes
writeable = no
available = yes
public = yes
guest ok = yes
path = /
[root-rw]
comment = Root-readwrite
browseable = yes
writable = yes
available = yes
public = no
path = /
[printers]
comment = All Printers
path = /var/spool/samba
browseable = yes
guest ok = yes
writable = no
printable = yes
=========
Could somebody help me get WINS working? I have no idea what could possibly be
wrong. TCP/IP & all other services (ping, ftp, http, telnet, rlogin) all seem to
be working fine, but Samba just keeps throwing this error at me. Please e-mail
me if it would be helpful to have more information.
Thanks,
Daniel J. Peng
[EMAIL PROTECTED]
------------------------------
From: [EMAIL PROTECTED] (Cameron L. Spitzer)
Crossposted-To: comp.os.linux.misc
Subject: try replacing inetd(8), Re: telnet connects, but 'closed by foreign host' b4
prompt
Date: 28 Aug 1999 05:39:37 GMT
In article <[EMAIL PROTECTED]>, Bob Martin wrote:
>Can you telnet to localhost (127.0.0.1) and is the ervice allowed in
>inetd.conf ?
>
>matt shobe wrote:
>>
>> Telnet from anywhere has suddenly gone pear-shaped for my new install
>> of Mandrake 6.0. (it used to work fine.) Whether I telnet to my local
>> IP while logged on at the console, or try from some other machine on
>> the net, the result is the same:
On my Debian 1.3 and 2.0 systems, every few months, inetd would
go into a mode where it would accept connections and then immediately
close them. All services were affected: in.telnetd, in.ftpd,
Exim's smtpd and qmail-smtpd (via tcp-environ...) chargen, you name it.
The daemon doesn't exit, just seems to forget how to invoke servers.
Both machines host political Web content and attract script kiddies,
Winnukers, etc, so the inetd failures may follow some kind of
denail of service attack.
I eventually decided the inetd(8) that comes with Debian is broken.
I replaced it with D J Bernstein's tcpserver from
ftp://koobera.math.uic.edu/www/ucspi-tcp.html
Haven't been running that long enough to see if it's a fix.
Cameron
------------------------------
From: Christopher Allen <[EMAIL PROTECTED]>
Subject: Re: linux-based telnetrc tricks of the trade
Date: 28 Aug 1999 05:29:54 GMT
John Gianni <[EMAIL PROTECTED]> spake:
> Why am I looking for UNIX telnetrc file examples?
Check out a scripting language called expect. You will be surprised and content.
--man expect---
INTRODUCTION
Expect is a program that "talks" to other interactive pro-
grams according to a script. Following the script, Expect
knows what can be expected from a program and what the
correct response should be. An interpreted language pro-
vides branching and high-level control structures to
direct the dialogue. In addition, the user can take con-
trol and interact directly when desired, afterward return-
ing control to the script.
enjoy
-out
------------------------------
From: 'N <[EMAIL PROTECTED]>
Subject: Re: Is this possible? HELP! SMB+Masq
Date: Fri, 27 Aug 1999 15:14:40 +0100
I'm having major problems with this still.
'N wrote:
>
> Okay.. here's a brief ASCII art picture.
>
> [W98_NICK]
> 129.215.x.y backbone | 192.168.2.0 subnet
> |
> -----[NT_FRANK]----[W98_JOHN]----<LINUX_SV1>-----> To The Net ;)
> |
> | 192.168.3.0 subnet
> <LINUX_SV2>
> |
> | 192.168.1.0 subnet
> [w98_BILL]
>
> Okay, as you can see I have 4 PCs which need networking. Three Win 98
> machines and one NT machine. I have TCP/IP routing just fine. As
> you can tell, I had to use Masquerading on LINUX_SV1 to get the W98
> machines on the branches to see the net.
>
> Okay, what are my problems:-
>
> 1) The W98_JOHN sees NT_FRANK as the Domain Master, as do all the other
> machines on the 129.215.x.x network but all the machines on the
> subnets think that LINUX_SV1 is the Domain Master. How do I
> stop the NT machine from grabbing the domain?
>
> 2) Then I do SMBCLIENT -L W98_NICK from LINUX_SV1 I get:-
> Interface added 192.168.2.1 with netmase 255.255.255.0
> session request to W98_NICK failed
> session request to *SMBSERVER failed
>
> 3) How can I get all 4 computers in the Mygroup domain to all appear on
> ALL 4 computers browse lists? Each sees their own little segment of
> the network.. :-(((
>
> Can anyone point me in directions where I can fix these problems, or at
> least find out how to diagnose what's going wrong? I've been all over
> the net, and I've checked this newsgroup, and haven't seen anything
> similar.
>
> Many Thanks in advance
>
> Nick
>
>
> --
>
> Nick Walton 3rd year Postgraduate Mailto:[EMAIL PROTECTED]
> (work)
> http://www.tardis.ed.ac.uk/~aardvark
--
Nick Walton 3rd year Postgraduate Mailto:[EMAIL PROTECTED]
(work)
http://www.tardis.ed.ac.uk/~aardvark
------------------------------
From: "Scott Simpson" <[EMAIL PROTECTED]>
Subject: Re: Being an ISP
Date: Fri, 27 Aug 1999 22:11:58 -0700
Assad Khan <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> Ok, I want to know how people can dial up to my machine. Also, I want to
> know how to IP Masq my home network (running 2 WinNT Workstations, 1
I have an example at http://home.earthlink.net/~simpson3 but it uses
ipfwadm, not ipchains. You'll have to do the conversion.
------------------------------
From: Scott Martin <[EMAIL PROTECTED]>
Subject: Re: Cybercafe Linux
Date: Sat, 28 Aug 1999 01:41:59 -0400
"Just some guy..." wrote:
> I have been thinking about setting up a Cyber cafe type of business using
> Linux as the sole operating system. Is there any concern that I should have?
> Will it work with like 20 or 30 stations?
"Just some guy..." wrote:
> I have been thinking about setting up a Cyber cafe type of business using
> Linux as the sole operating system. Is there any concern that I should have?
> Will it work with like 20 or 30 stations?
No concerns specific to Linux, IMHO. The majority of the concern will be in how
to implement the 20-30 stations. What does a "station" consist of in hardware
and software? What programs do you have to run? How much space can it occupy?
How important is "total cost of ownership" vs. purchase price?
Personally, for someone with decent capitalization, I would start with a visit
to www.neoware.com followed by a phone call to get a quote. You'd be looking at
the NeoStation 2200 Basic with the "Internet It" software option. Then in the
back room, a "run of the mill" server running Linux would complete the picture
(along with all the network doodads like hubs, routers, etc.)
One "real" computer and 20 or 30 "toasters" and you're in business. BTW,
"toaster" is the nickname I apply to units like NeoStations since they have no
moving parts, have zero maintenance requirements (except for shaking out the
crumbs once in a while), occupy the same or less space, and are as simple as
....
Then, again, if you're interested in a "turn key" setup (probably not
Linux-based), check out http://www.cyberdiner.com/cyberdiner.html. They'll
"transform any establishment into an Internet Cafe." If nothing else, reviewing
their information will help you flesh out your plans.
Good luck!
Scott Martin
[EMAIL PROTECTED]
------------------------------
From: Rod Roark <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.misc,comp.os.linux.setup
Subject: Re: VMware - wow!
Date: 28 Aug 1999 06:04:10 GMT
steve mcadams <[EMAIL PROTECTED]> wrote:
>...From this I conclude that yes, it is in fact a crude hack....
You don't know what you are talking about.
As one who has written x86 emulators, I can tell you that VMware is a
truly remarkable piece of software. They have taken an instruction set
that won't virtualize itself, and virtualized it with only about a 1/3
performance penalty.
Furthermore the use of a host OS makes a great deal of sense for two
important reasons:
(1) The host OS doesn't have to run virtualized, and therefore does
not suffer the performance penalty; and
(2) They don't have to keep up with drivers for every device on the
planet; the nice Linux developers are doing that very well,
thank you.
Try VMware, you'll like it!
-- Rod
======================================================================
Sunset Systems Preconfigured Linux Computers
http://www.sunsetsystems.com/ and Custom Software
======================================================================
------------------------------
From: [EMAIL PROTECTED] (Chris)
Crossposted-To: athome.users-unix
Subject: Re: dual ethernet, no joy
Date: Sat, 28 Aug 1999 06:50:00 GMT
Which card is detected as eth0 or eth1 has to do with which one is
detected first on the system. You can try switching the slots around or
just do what I did after I gave up and just use ifconfig to setup
whichever card for whichever network and just ignore the eth* number
they wind up with. Iirc, eth0 will be whichever card winds up first in
scan priority so just setup ifconfig the way you want and move along.
from my lilo.conf
append = "ether=12,0x000,eth0 ether=9,0x400,eth1"
from my dmesg output
ne2k-pci.c:v0.99L 2/7/98 D. Becker/P. Gortmaker
http://cesdis.gsfc.nasa.gov/linu
x/drivers/ne2k-pci.html
ne2k-pci.c: PCI NE2000 clone 'RealTek RTL-8029' at I/O 0xd400, IRQ 9.
eth0: PCI NE2000 found at 0xd400, IRQ 9, 00:40:05:5A:F5:F2.
tulip.c:v0.89H 5/23/98 [EMAIL PROTECTED]
eth1: Lite-On 82c168 PNIC at 0xd000, 00 a0 cc 24 40 e9, IRQ 12.
eth1: MII transceiver found at MDIO address 1, config 3100 status 7829.
I don't use the ne2k right now and the tulip card is much faster so I
have the eth1 setup as the one I'm running now. My networking setup
only brings up eth1 so the ifconfig output is only loopback and eth1.
Incidentally I tried swapping things about to force eth0 and eth1 to the
'proper' cards and just gave up, I think it's a fixed situation
depending on the address range the card is config'ed for and I don't
have the DOS utils to reconfigure so I just went around the problem.
Worked for me.
On Sat, 28 Aug 1999 00:30:05 GMT,<[EMAIL PROTECTED]> wrote:
>I've got a linux box with the 2.0.34 kernel. Until recently I've had
>only one e-net card - a NE2000 clone. It's worked fine to connect
>to my wife's win95 box to do IP masquerading through my PPP
>connection.
>
>I just got cable modem service and installed a 3c900 in addition to
>the NE2000. The 3c900 is now recognized on boot, but
>not the NE2000.
>Both drivers are built into the kernel. I'd previously had the
>following line in lilo.conf:
>
>append="ether=5,0x240,eth0"
>
>and the card was recognized on boot. Since now the 3c900 is
>recognized first and assigned to eth0 I want the NE2000 to be picked
>up as eth1, so I put the following in lilo.conf and did 'lilo -C
>/etc/lilo.conf':
>
>append="ether=11,0xfc80,eth0 ether=5,0x240,eth1"
>
>I thought this is all it would take. What gives?
>
>Here's the result of 'cat /proc/ioports' for people who, unlike me,
>know how to interpret it:
>
>0000-001f : dma1
>0020-003f : pic1
>0040-005f : timer
>0060-006f : keyboard
>0070-007f : rtc
>0080-009f : dma page reg
>00a0-00bf : pic2
>00c0-00df : dma2
>00f0-00ff : npu
>0170-0177 : ide1
>01f0-01f7 : ide0
>02f8-02ff : serial(auto)
>0376-0376 : ide1
>0378-037f : lp
>03c0-03df : vga+
>03e8-03ef : serial(auto)
>03f0-03f5 : floppy
>03f6-03f6 : ide0
>03f7-03f7 : floppy DIR
>03f8-03ff : serial(auto)
>fc80-fc9f : 3c900
>
>--
>Scott Post [EMAIL PROTECTED]
------------------------------
** 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
******************************
