Linux-Networking Digest #571, Volume #10 Sat, 20 Mar 99 18:13:49 EST
Contents:
Re: ISP<->Wingate(WIN NT)<->Linux ("Dr. Al Bento")
Re: RH5.0 won't get on the net ("MattW")
Re: SAMBA: Enrypted Passwords ("M. Brian Akins")
Re: Samba 2.0.2 problem : Couldn't set effective gid ...Can't become ("M. Brian
Akins")
blocking services on an interface ("M. Brian Akins")
Re: NFS Hack Attack ? CERT says many linux systems vunerable! (Holger Matthoefer)
Re: Win terminal for Linux? ("MattW")
winmodems ("batags")
Re: winmodems ("MattW")
Re: winmodems ("Jeff Shultz")
Q: Tool to check external IP address assigned by NAT? (Albert)
Transmit timeouts.. (Haavard Engum)
Simple Problem
Re: Simple Problem ("MattW")
Re: Tool to check external IP address assigned by NAT? ("MattW")
Re: Tool to check external IP address assigned by NAT? (Albert)
kernel is complaining (Rico Dreier)
_Networking Ques.: Is "Peer-to-Peer" Networking Possible Among Multiple Linux
Standalone Machines? ("LScott")
Advice on Linux Hardware and Networking Please ("Chris B")
----------------------------------------------------------------------------
From: "Dr. Al Bento" <[EMAIL PROTECTED]>
Subject: Re: ISP<->Wingate(WIN NT)<->Linux
Date: Fri, 19 Mar 1999 09:13:09 GMT
I have it working without any problems. I have Netscape, WXftp, Pine,
etc, running in the Linux machine. This is how I set it up:
/etc/HOSTNAME
LINUX-NAME ... name of your machine without domain
/etc/hosts
127.0.0.1 localhost
192.168.0.1 gateway ... the machine running Wingate
192.168.0.X LINUX-NAME ... the Linux machine: X is the number in LAN
.......... xxxxxxxxxx ... (all other machines in LAN)
/etc/resolv.conf
nameserver 192.168.0.1 ... the machine running Wingate
/etc/sysconfig/network-scripts/ifcfg-eth0
DEVICE=eth0
IPADDR=192.168.0.X .... X is the number of the Linux machine in LAN
NETMASK=255.255.255.0
NETWORK=192.168.0.0
BROADCAST=192.168.0.255
ONBOOT=yes
BOOTPROTO=none
USERCTL=no
/etc/sysconfig/network
NETWORKING=yes
FORWARD IPV4=yes
HOSTNAME=LINUX-NAME
DOMAINNAME=ISP-domain ... I believe that it can be blank.
GATEWAY=192.168.0.1
GATEWAYDEV=eth0
If you are using RedHat 5.2 you can setup the above in the networking
tool of the control-panel.
Sendmail will be slow to start (reverse lookup times out), but it will
work fine if you set forward to the gateway machine. I have an Apache
server running in the Linux machine using a TCP mapping in Wingate. I
also tested a FTP server and a RealServer in the Linux machine using
Wingate mappings and both worked.
Regards, Al
Jorge Nagasaki wrote:
>
> Anyone have successfully make wingate work with Linux?
> I m trying to access a internet ISP from LINUX machine connected
> to a Windows NT machine (with Wingate) and this windows NT
> connected to ISP via dial up , and it fails.
> from windows NT everything is fine. Looks like I could not
> get the wingate proxy server working.
> Also wingate support gives me configuration information for Windows NT
> in both machines, looks like they don't klnow about linux.
> I appreciate any suggestion.
------------------------------
Reply-To: "MattW" <[EMAIL PROTECTED]>
From: "MattW" <[EMAIL PROTECTED]>
Subject: Re: RH5.0 won't get on the net
Date: Sat, 20 Mar 1999 13:00:36 -0800
What ever 192.168.0.1 is... That's where your having problems.
If you can get out of your linux machine and ping your network locally
there is nothing different about going through your default gateway as long
as its set and working.
It sounds like your default gateway is not set in Linux or the 192.168.0.1
is not working.
Check it with the route command. 0.0.0.0 default gateway is 192.168.0.1.
and 192.168.0.1 had better be a router of some type doing NAT if you want to
talk to CNN.com
Matt W
mike dombrowski <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> I kinda have networking working but still have some problems. On my
> linux box I can ping the my network fine. But the problem arises when
> I want to get out onto the internet thru my gateway. The machine dual
> boots Win95 and Linux. In windows I can access the net fine so it is a
> problem with Linux config. In windows the settings are
>
> Ip: 192.168.0.5
> Mask: 255.255.255.0
> Gateway: 192.168.0.1
> Dns Server: 192.168.0.1
> Hostname: Linux
>
> I entered all these settings into netcfg and can ping the rest of my
> network fine. But the second I try to ping either cnn.com or
> 24.2.77.128 (the internet address of my gateway computer) it says
>
> [root@linux /root]# ping cnn.com
> ping: unknown host cnn.com
>
> and
>
> [root@linux /root]# ping 24.2.77.128
> PING 24.2.77.128 (24.2.77.128): 56 data bytes
> ping: sendto: Network is unreachable
> ping: wrote 24.2.77.128 64 chars, ret=-1
> ping: sendto: Network is unreachable
> ping: wrote 24.2.77.128 64 chars, ret=-1
> ping: sendto: Network is unreachable
> ping: wrote 24.2.77.128 64 chars, ret=-1
>
> --- 24.2.77.128 ping statistics ---
> 3 packets transmitted, 0 packets received, 100% packet loss
>
> What's up? Am I doing something wrong? Thanks in advance for your
> help.
>
> Mike Dombrowski
------------------------------
Date: Sat, 20 Mar 1999 10:54:48 -0500
From: "M. Brian Akins" <[EMAIL PROTECTED]>
Subject: Re: SAMBA: Enrypted Passwords
Jason McKnight wrote:
> Has anybody gotten this to work properly? I can access my linux box via
> NT and SAMBA if I turn off encrypted passwords in the registry and in
> smb.conf. But if they are both on, I can't log in.
>
> I did the cat /etc/passwd | mssmbpasswd.sh > /etc/smbpasswd and got a
> smbpasswd file, but it doesn't seem to work.
>
> I have my smb.conf pointed to /etc/smbpasswd but I can't seem to get it
> to work.
>
> Any ideas what I am doing wrong? I would like to get this to work so
> that I can give some people remote access, but I would rather have
> encrypted passwords.
>
what version of samba? With 2 and up try this.
after making the smb passwd file, chmod 600 /etc/passwd
then to set up a user:
smbpasswd -e user
it will then prompt you for password and confirm. the "-e" is very
important, it enables, the user
let me know what happens.
>
> tia,
>
> Jason McKnight
------------------------------
Date: Sat, 20 Mar 1999 11:44:17 -0500
From: "M. Brian Akins" <[EMAIL PROTECTED]>
Crossposted-To: linux.redhat.install,linux.samba
Subject: Re: Samba 2.0.2 problem : Couldn't set effective gid ...Can't become
Did you enable your users?? do this by --> smbpasswd -e user
I had a similar problem and that did it
You may also have to chmod 600 /etc/smbpasswd
"Beno�t Cousson" wrote:
> Hi,
>
> I've a problem using Samba 2.0.2 on a redhat 5.2. When I try to connect a
> NT, 95 or Linux PC to the Samba server, I've got a "Bad password" error
> although the user account is defined (in passwd and smbpasswd), encrypt
> passwords = yes, and smb passwd file = /etc/smbpasswd. With the log level
> sets to 3, I've got this messages:
>
> [1999/03/19 14:39:32, 3] smbd/reply.c:reply_sesssetup_and_X(679)
> sesssetupX:name=[bco]
> [1999/03/19 14:39:32, 3] param/loadparm.c:lp_add_home(1440)
> adding home directory bco at /home/bco
> [1999/03/19 14:39:32, 3] smbd/password.c:setup_groups(192)
> bco is in 1 groups: 500
> [1999/03/19 14:39:32, 3] smbd/password.c:register_vuid(270)
> uid 500 registered to name bco
> [1999/03/19 14:39:32, 3] smbd/password.c:register_vuid(272)
> Clearing default real name
> [1999/03/19 14:39:32, 3] smbd/process.c:chain_reply(715)
> Chained message
> [1999/03/19 14:39:32, 3] smbd/process.c:switch_message(402)
> switch message SMBtconX (pid 3634)
> [1999/03/19 14:39:32, 3] smbd/password.c:authorise_login(737)
> ACCEPTED: validated uid ok as non-guest
> [1999/03/19 14:39:32, 3] smbd/service.c:make_connection(386)
> Connect path is /tmp
> [1999/03/19 14:39:32, 0] smbd/uid.c:become_gid(105)
> Couldn't set effective gid to 500 currently set to (real=0,eff=0)
> [1999/03/19 14:39:32, 0] smbd/service.c:make_connection(425)
> Can't become connected user!
> [1999/03/19 14:39:32, 3] smbd/error.c:error_packet(138)
> error packet at line 162 cmd=117 (SMBtconX) eclass=2 ecode=2
> [1999/03/19 14:39:32, 3] smbd/error.c:error_packet(143)
> error string = Function not implemented
>
> The name/password seems to be OK (ACCEPTED: validated uid ok as non-guest).
> So what does the error "Couldn't set effective ..." mean???
>
> Thanks in advance.
>
> Benoit Cousson.
------------------------------
Date: Sat, 20 Mar 1999 10:50:35 -0500
From: "M. Brian Akins" <[EMAIL PROTECTED]>
Subject: blocking services on an interface
I have a lan set up with a linux box as a "firewall" What I would like
to be able to do is block all services on the external interface (eth1)
or selectively do it. I have ALL: ALL in my /etc/hosts.deny and ALL:
(internal network) in my hosts.allow and have banners set up when
soemone tries to telnet or whatever from outside (tcp-wrappers). But
what I would like for it to do is when someone tries to telnet in, that
it would just die like there wasn't even a system on the other end.
Alos how can I keep people from pinging me???
I am extremely paranoid now after someone cracked my box and screwed it
up, not to metion screwing with my ISP and getting me in a bad
situation.
Please e-mail me directly.
Thanks.
------------------------------
From: [EMAIL PROTECTED] (Holger Matthoefer)
Subject: Re: NFS Hack Attack ? CERT says many linux systems vunerable!
Date: Sat, 20 Mar 1999 13:31:51 +0100
Reply-To: [EMAIL PROTECTED]
In article <[EMAIL PROTECTED]>,
Bill Anderson <[EMAIL PROTECTED]> writes:
> "M. Buchenrieder" wrote:
>
>> BTW, please adjust your quoting style. It's pretty much annoying
>> having to scroll down first, just to find out what you're
>> commenting onto.
>
> Actually, many people (myself included) prefer to have the follow-up
> after the quote.
> For us, it is quite annoying to read the response, then scroll down to
> find out the question or quote.
> Different strokes, different folks.
Reread what Michael wrote and tell me where you and him differ. :)
Holger
------------------------------
Reply-To: "MattW" <[EMAIL PROTECTED]>
From: "MattW" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.x
Subject: Re: Win terminal for Linux?
Date: Sat, 20 Mar 1999 11:44:10 -0800
If all of the machines are connected and using TCP/IP then
on your Win machines do:
start menu: Run:
telnet <your linux machine>
Of course this assumes linux is running inetd and in.telenetd and that
networking is working.
Shareware program CRT is much better then the built in telent though. Or
you can use any other VT100 type emulators.
Matt W
Kevin White <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> Hi, I love using my linux box, but sometimes have to work on the other
> boxes (Win95 or WinNT). I would like to be able to do my linux "work"
> (emacs, compiling, working with files that are on my linux box, etc.)
> from the Win95 or NT box. Is this possible? Is this what a "terminal
> emulator" is for? (Sorry, I'm quite a newbie to this stuff). So, if a
> terminal emulator program is the right tool for the job, is there a free
> one available for nt/95? If there is a better way to do this, please
> offer whatever suggestions you can.
>
> Thanks,
>
> Kevin
> --
> Kevin White, Software Engineer
> Envision Telephony
> [EMAIL PROTECTED]
> [EMAIL PROTECTED]
------------------------------
From: "batags" <[EMAIL PROTECTED]>
Subject: winmodems
Date: Sat, 20 Mar 1999 16:37:26 -0500
I have installed RH 5.2 and have set up ppp0 through linuxconf, But I still
can't get connected to my isp. I have all the info from my isp <like
gateway-primary dns-sec dns> But I still can't hear the modem dialing up or
even get connected. I have a UsRobotics 56k Winmodem, Could that be my
problem? And if it is, is there a way to solve it without getting a new
modem? Any help will be appreciated
Thanks
Bu||
------------------------------
Reply-To: "MattW" <[EMAIL PROTECTED]>
From: "MattW" <[EMAIL PROTECTED]>
Subject: Re: winmodems
Date: Sat, 20 Mar 1999 13:46:27 -0800
WinModems and linux don't work to well.
It's a software compression thing. WinModems are not that smart. There are
even problems with them on NT.
I have a generic 56k V.90 $40.00 modem and it works just fine.
Matt W.
batags <[EMAIL PROTECTED]> wrote in message
news:rvUI2.2651$[EMAIL PROTECTED]...
> I have installed RH 5.2 and have set up ppp0 through linuxconf, But I
still
> can't get connected to my isp. I have all the info from my isp <like
> gateway-primary dns-sec dns> But I still can't hear the modem dialing up
or
> even get connected. I have a UsRobotics 56k Winmodem, Could that be my
> problem? And if it is, is there a way to solve it without getting a new
> modem? Any help will be appreciated
> Thanks
> Bu||
>
>
------------------------------
From: "Jeff Shultz" <[EMAIL PROTECTED]>
Subject: Re: winmodems
Date: Sat, 20 Mar 1999 13:37:15 -0800 (PST)
Reply-To: "Jeff Shultz" <[EMAIL PROTECTED]>
On Sat, 20 Mar 1999 16:37:26 -0500, batags wrote:
:>I have installed RH 5.2 and have set up ppp0 through linuxconf, But I still
:>can't get connected to my isp. I have all the info from my isp <like
:>gateway-primary dns-sec dns> But I still can't hear the modem dialing up or
:>even get connected. I have a UsRobotics 56k Winmodem, Could that be my
:>problem? And if it is, is there a way to solve it without getting a new
:>modem? Any help will be appreciated
:>Thanks
:>Bu||
That Winmodem is the problem, the whole problem, and nothing but the
problem (so swear at it).
Winmodems only function under Win9x or maybe Win3.x - the modem
offloads most of the processing onto the CPU, which means you are
taking a massiver performance hit with the thing.
Jeff Shultz
http://www.netcom.com/~jbshultz
Here an OS, there an OS... I need more computers.
------------------------------
From: Albert <[EMAIL PROTECTED]>
Subject: Q: Tool to check external IP address assigned by NAT?
Date: Sat, 20 Mar 1999 21:46:29 +0000
Hi all. I was wondering if there is a Linux tool to check the
external IP address (assigned by NAT)?
Yours,
--Albert
------------------------------
From: Haavard Engum <[EMAIL PROTECTED]>
Subject: Transmit timeouts..
Date: 20 Mar 1999 22:58:07 +0100
Hi!
I am having problems lately with a linux-box. I seem to get
a lot of these error messages in the log(also written to the console):
Mar 20 22:24:32 localhost kernel: eth0: Transmit timeout, status 0d 0000 media 08.
Mar 20 22:24:32 localhost kernel: eth0: Tx queue start entry 99 dirty entry 95.
Mar 20 22:24:36 localhost kernel: eth0: Transmit timeout, status 0d 0000 media 08.
Mar 20 22:24:36 localhost kernel: eth0: Tx queue start entry 115 dirty entry 111.
Mar 20 22:24:42 localhost kernel: eth0: Transmit timeout, status 0d 0000 media 08.
Mar 20 22:24:42 localhost kernel: eth0: Tx queue start entry 184 dirty entry 180.
And then the network is _very_ slow. It appears sometimes very often, and
sometimes very seldom. Earlier, when I used the 2.0.36 kernel version, after I
got some of these the network connection was down until I manually put it up
again (ifconfig eth0 down, ifconfig eth0 up, routes etc.) After I installed the
newest prepatch to kernel version 2.0.37 the network connection doesn't go down,
but I still have the problems with the error-messages, and the network-connection
to the box being extremely slow.
As I said, I am using linux kernel version 2.0.37pre8 on a Pentium MMX 200Mhz
computer with a brand new Realtek 8139 PCI card. I also got the same errors
when using a 3com 59x Boomerang PCI card. The linux-box do run quite a few
services, and there is at some times quite a bit of network-load, but not
that much. We are running it on a 10Mbit network.
--
Haavard Engum <[EMAIL PROTECTED]>
------------------------------
From: [EMAIL PROTECTED] ()
Subject: Simple Problem
Date: 20 Mar 1999 21:51:10 GMT
I can access (telnet/ftp/lynx...) machines on the local network
(*.oberlin.edu), with no problems. I can not access anything outside, with
Linux.
(I can with windows but I don't use that for anything and it's a drag to
boot it up just to run Netscape really slowly for 45 minutes 'til it dies.)
I am assuming that there's a simple solution, but I don't know what to ask
for.
I am running Redhat 5.1 (2.0.34). I have an ethernet connection. If you
need any more info just ask.
------------------------------
Reply-To: "MattW" <[EMAIL PROTECTED]>
From: "MattW" <[EMAIL PROTECTED]>
Subject: Re: Simple Problem
Date: Sat, 20 Mar 1999 14:13:22 -0800
Check your default gateway.
it's probably not set. You can check your /etc/sysconfig/network file.
You have no way set as your default route out of your local network.
That usually will do it.
Matt W.
<[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> I can access (telnet/ftp/lynx...) machines on the local network
> (*.oberlin.edu), with no problems. I can not access anything outside, with
> Linux.
>
> (I can with windows but I don't use that for anything and it's a drag to
> boot it up just to run Netscape really slowly for 45 minutes 'til it
dies.)
>
> I am assuming that there's a simple solution, but I don't know what to ask
> for.
>
> I am running Redhat 5.1 (2.0.34). I have an ethernet connection. If you
> need any more info just ask.
------------------------------
Reply-To: "MattW" <[EMAIL PROTECTED]>
From: "MattW" <[EMAIL PROTECTED]>
Subject: Re: Tool to check external IP address assigned by NAT?
Date: Sat, 20 Mar 1999 14:09:41 -0800
Yeah...
Traceroute... Your routers IP address on the second interface. The
one not connected to your internal network is the IP address usually
assigned if that is you NAT router.
It all works through the use of that single IP.
Matt W.
Albert <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> Hi all. I was wondering if there is a Linux tool to check the
> external IP address (assigned by NAT)?
>
> Yours,
> --Albert
------------------------------
From: Albert <[EMAIL PROTECTED]>
Subject: Re: Tool to check external IP address assigned by NAT?
Date: Sun, 21 Mar 1999 06:27:40 +0800
MattW wrote:
> Traceroute... Your routers IP address on the second interface. The
> one not connected to your internal network is the IP address usually
> assigned if that is you NAT router.
>
> It all works through the use of that single IP.
I think you misunderstood my situation a little bit. Mine is a many-to-
many setup here, that is, the NAT router assigns my internal host an
external IP address every time I initiate network. My internal host IP
address remains the same, and it is just that the external IP address
that keeps changing all the time (hence NAT)?
Yours,
--Albert
------------------------------
From: Rico Dreier <[EMAIL PROTECTED]>
Subject: kernel is complaining
Date: Sat, 20 Mar 1999 23:31:50 +0100
Hello,
I'm using redhat 5.2 (kernel 2.0.36) and a 3C905B-TX. The network driver is
3c59x.c:v0.99H 11/17/98 from D. Becker. It is compiled with debug level 6.
The problem is that as a matter of principle the network is functioning,
but is not reliable. Sometimes it is incredible slow. There are strange
entries in /var/log/messages...
> Mar 20 19:34:02 data kernel: In interrupt loop, status e401.
> Mar 20 19:34:48 data kernel: cket, Tx index 1072706.
> Mar 20 19:34:57 data kernel: iting interrupt, status e000.
> Mar 20 19:35:30 data kernel: 0.
> Mar 20 19:35:42 data kernel: ing interrupt, status e000.
> Mar 20 19:35:46 data kernel: cket, Tx index 1080365.
> Mar 20 19:36:45 data kernel: send a packet, Tx index 1088203.
> Mar 20 19:36:46 data kernel: 7>eth0: exiting interrupt, status e000.
> Mar 20 19:38:31 data kernel: nterrupt loop, status e201.
> Mar 20 19:38:32 data kernel: a packet, Tx index 1097582.
> Mar 20 19:44:22 data kernel: eth0: Trying to send a packet, Tx index 1129054.
> Mar 20 19:44:26 data kernel: _rx(), status e001, rx_status 0030.
Does anyone know what these entries could mean? Thx for every hint.
Rico
------------------------------
From: "LScott" <[EMAIL PROTECTED]>
Subject: _Networking Ques.: Is "Peer-to-Peer" Networking Possible Among Multiple
Linux Standalone Machines?
Date: 20 Mar 1999 22:05:28 GMT
Gentlemen and Ladies:
This message asks whether a "Peer-to-Peer" network, instead of a
client-server network, may be used between multiple, standalone, Linux
machines. Our "QUESTIONS" follow the preliminary "BACKGROUND" information
provided with respect to the current design of the existing network that we
want to convert entirely into a "peer-to-peer" Linux-only network (if
possible and reasonably practical to do so).
BACKGROUND: We would like to convert our computing entirely over to Linux
operating systems in all of our computers. That is, we would like to have
Linux be the sole and only operating system used in our organization.
Thus, we have no plans at all for integrating any other O/S, such as
Windows or Macintosh, with or into this Linux network that we hope we can
accomplish.
Historically, we have conducted our activities in our workgroup in a
so-called "peer-to-peer" network configuration that has the following
characteristics:
1. There are four machines in our immediate group:
a. Three (3) standalone workstations; and
b. One file server that contains only an O/S and
the data files with which the personnel at the
three standalone machines perform their work.
2. Each of the three standalone workstations contains
the various programs and applications employed by
the users at their respective standalone machines in
accomplishing their work.
Note: Only programs and applications are kept on
the hard drives of the three standalone machines; no
data files at all are kept on the hard drives of the three
standalone machines.
Further: Each of the respective users of the
standalone machines is entirely free to use
the applications and programs of his or her
own choice in performing his or her own work.
Thus, in varying degree, the three standalone
machines each contains differing programs and
applications fom the other standalone workstations.
3. The file server contains no programs or applications
whatsoever. In other words, no programs are run
from the file server by any of the standalone machines.
However, in addition to being only a "file server,"
the file server is the machine that
a. contains the printers for the entire network
and actually handles for the entire network
the print jobs that are sent to it from the
three standalone machines; and
b. contains the Post Office for the email system
used on the network. The Post Office is actually
remotely administered by one of the users on
one of the three standalone machines.
4. The following "resources" are shared around
the network by all four machines:
a. All drives and directories (Or "folders") and
files are read/write shared by all four
machines;
b. The printers (located on the file server) are
shared by all four machines;
c. One of the three standalone machines is a
dial-in network server for the entire network
and also acts as a faxmodem (fax) server for
all of the machines in the network.
5. No programs at all are shared as between any two or
more computers in the network.
5. The network uses thin ethernet coax cable that runs
from each machine to the next -- i.e., there is no
"star" or "hub" involved.
Although at first blush this network may seem "too open" or lacking in the
security features of a "client-server" network arrangement, you may assume
that, among the persons who work in this network, security is not an issue.
To the extent that security may be required from time to time, we simply
password the relevant directories or other resources so that they can be
used only by those who are working upon the particular project that needs
to be secured.
QUESTIONS: Based upon the foregoing background information provided with
respect to our currently existing network, and since, to a person, we are
the barest of novices at Linux, we would be most appreciative if the more
knowledgeable and experienced members of the newsgroup could enlighten us
with respect to the questions we need to consider in making our transition
of our existing network to a Linux-only network:
1. Can Linux be networked as a "Peer-to-Peer"
network as described above?
a. If so, do the distributions of Linux come
equipped to set up such a network or is
some additional network application or
program needed to effect the "Peer-to-Peer"
network configuration that we want to create?
b. If not, what kind of network would we have
to use? Client-Server? (client-server is simply
overkill for us)
2. Can Linux be used to accomplish the "sharing" of the
resources as we have outlined the degree of "resource
sharing" above?
If so, is this a complicated matter to accomplish or is
it a relatively simple matter such as is true in
peer-to-peer networking in Windows for Workgroups
and among Win95 machines that have been arranged
in workgroups?
3. Finally, in the event that we should find ourselves
at some point merging or combining with another
group that uses an O/S different from Linux (such
as NT, Win95/98, Macintosh, or OS2):
a. Is it a complicated matter to "plug in" a Linux
workgroup, such as ours would be, into a larger
network that uses neither Linux nor Unix as
the O/S for its network?
b. Is it a complicated matter to "plug in" a
computer -- that uses an O/S other than
Linux -- to a Linux workgroup such as the
one we hope we can create? (i.e., for
example, would it be particulary difficult
for an NT or for a Win95/98 machine to
join us and use our network?).
These two operations ("plug in" to someone else's
network and remain peer-to-peer among ourselves
or "plug in" someone else to our peer-to-peer
network and have them now also be a peer-to-peer
member of our workgroup) was, and has been,
rather simple and easy to accomplish both under
Windows for Workgroups and under Win95. Are
we in for some wrenching "shocks" and "surprises"
under Linux? Or, will life just go on -- albeit under
a different, and hopefully much more useful,
operating system?
4. Finally, given what we would like to accomplish
with our network configuration, is there a
particular distribution of Linux upon which we
should be focusing? SUSE? Caldera? RedHat?
Sorry to send up such a long message, but we thought it would probably be
best to "lay it all out at once" and first find out if we are even on the
right track or whether we need to learn a whole new mindset with respect to
how we are going to have to get our work done under Linux?
Any enlightenment, insights, suggestions, comments, or references to web
or hard copy resources with respect to our questions will be greatly
appreciated. Thus far, our search for the answers at the linux.org, et.
al. web sites has turned up no answers to our questions.
Thanks,
LScott
------------------------------
From: "Chris B" <[EMAIL PROTECTED]>
Subject: Advice on Linux Hardware and Networking Please
Date: Sat, 20 Mar 1999 17:34:59 -0500
Hey,
I am relatively new to Linux but not UNIX in general. This weekend I
finished installing an extremely small network (two machines) with a Linux
Redhat box (5.2) as the server and a dual boot Win98/NT Server as the
client. The machines communicate like a charm.
I would like to run the Linux machine as a gateway to the Internet, thereby
allowing the client PC access the Web and other resources. In this regard I
have two questions:
1. Can anyone recommend a good but preferably inexpensive modem? I have
checked the hardware comp. lists and it appears the one I was going to use
(an internal USR 56K Win modem with X2 tech.) won't work. Any
recommendations regarding a replacement or setup instructions for the one I
have? Which models have you had experience with?
2. In setting up the gateway, any recommendations regarding settings or
where to look for info? I haven't attempted to install PPP yet (no modem)
but I'm assuming the Win98/NT box will be using the Linux server's IP
address as the gateway.
Thanks for any suggestions.
Chris
------------------------------
** 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
******************************
