Linux-Networking Digest #520, Volume #12          Wed, 8 Sep 99 21:13:40 EDT

Contents:
  Re: Have I been hacked? (Rod Smith)
  Re: Good Documnet for setting up ADSL (Paul Lew)
  SAMBA  (dkwok)
  HP Pavilion & Network Card problem ([EMAIL PROTECTED])
  PCMCIA or eth0 IRQ Problem. Not Sure? ([EMAIL PROTECTED])
  Re: Using DHCP (Scott Nolde)
  From woe to go... help ("Matt Anderson")
  Re: DSL Connection Using Linux (Rod Smith)
  Re: IP forwarding
  Re: Wireless: Aviator2.4 = Raytheon Raylink (Derrick J Brashear)
  connecting 2 lans  (Torsten Mueller)
  Re: Good Documnet for setting up ADSL (Rod Smith)
  Re: good 100Mb/s NIC for Linux? (Rod Smith)

----------------------------------------------------------------------------

Reply-To: [EMAIL PROTECTED]
From: [EMAIL PROTECTED] (Rod Smith)
Subject: Re: Have I been hacked?
Date: Wed, 08 Sep 1999 23:36:57 GMT

[Posted and mailed]

In article <7r6mp2$2dk$[EMAIL PROTECTED]>,
        "TURBO1010" <[EMAIL PROTECTED]> writes:
> Enlighten me, what are TCP/Wrappers?  I masquerade 2 machines behind my
> linux, I can't have anything blocking them from getting on the net.

TCP Wrappers is a daemon (tcpd) that sits between inetd and the daemon
that handles a specific service.  The TCP Wrappers package uses rules laid
out in /etc/hosts.allow and /etc/hosts.deny to allow or deny specific
computers or networks to connect to specific services.  TCP Wrappers
doesn't affect outgoing connections, just the connections coming in to any
servers you run, and then only servers run via TCP Wrappers are affected.

> A Guy Called Tyketto <[EMAIL PROTECTED]> wrote in message
> news:j_xB3.19470$[EMAIL PROTECTED]...
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> [EMAIL PROTECTED] wrote:
>> >
>> > I'm no guru, but may i suggest you look into using TCPwrappers? It helps
>> > prevent unwanted logins, from what i understand.
>> >
>> > -jeff
>>
>> Not only that, but IPChains as well, so you can set up minimal
>> firewalling rules, to block connections or attacks from a certain site,
>> to a certain port. But, DEFINITELY get TCPWrappers working. they will
>> help you a lot. You may want to check into the Linux Administrators
>> Security Guide, at https://www.seifried.org. Best piece of work I've
>> seen for security so far. Worked well in securing my network.
>>
>> BL.
>> - --
>> Brad Littlejohn                         | Email:
> [EMAIL PROTECTED]
>> Unix Systems Administrator,             |
> [EMAIL PROTECTED]
>> WebMaster, NewsMaster.. Smeghead! :)    |
> http://www.omnilinx.net/~tyketto
>>     PGP: 1024/E9DF4D85 67 6B 33 D0 B9 95 F4 37  4B D1 CE BD 48 B0 06 93
>>
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1.0.0 (GNU/Linux)
>> Comment: For info see http://www.gnupg.org
>>
>> iD8DBQE31m1SyBkZmuMZ8L8RAg5pAKDxmi0mSfb0tChTrQy7XEGZX+HH7wCfUJNZ
>> BelG+BYRa+slOS21Eq0/Nyg=
>> =LNC8
>> -----END PGP SIGNATURE-----
> 
> 
> 

-- 
Rod Smith
[EMAIL PROTECTED]
http://members.bellatlantic.net/~smithrod
Author of _Special Edition Using Corel WordPerfect 8 for Linux_, from Que

------------------------------

From: [EMAIL PROTECTED] (Paul Lew)
Subject: Re: Good Documnet for setting up ADSL
Reply-To: [EMAIL PROTECTED]
Date: Wed, 08 Sep 1999 23:19:08 GMT

Setting up ADSL on Linux is the same as setting Linux for
a lan ethernet connection as there is no difference.  One
thing you may need from the ISP is whether they use DHCP
for providing you an ipaddr in which case you would need
to install the DHCP client.  You would also need the ipaddr
of their DNS servers for your resolv.conf

Also at www.linux.com, use their search for ADSL and some
docs will show up most of it is the phone wiring for ADSL
and data/voice splitter.


<[EMAIL PROTECTED]> wrote:
>Greetings,
>
>My ISP started ADSL service, but they said Linux won't be supported
>because they haven't tested on it.  ISP said Linux will be supported by
>the end of October(hopefully), and I could try to install it myself if I
>really wanted to.
>
>If I want to do this by myself I'll have to spend $40 whether I succeed
>or not since  there is no trial period. I was wondering if there is any
>good document that I could look at; so that I could install it on my
>Linux Box by myself.
>
>From Winnipeg,
>Ben

------------------------------

From: dkwok <[EMAIL PROTECTED]>
Subject: SAMBA 
Date: Thu, 09 Sep 1999 10:07:32 +1000

I have set up samba to connect my win98 running VMware on top of Linux
box. The network only works when PPP is up and connect to the internet.
When the ppp is disconnected, win98 cannot establish network with the
linux box and the rest of the lan.

Any suggestion??
David


------------------------------

From: [EMAIL PROTECTED]
Subject: HP Pavilion & Network Card problem
Date: Wed, 08 Sep 1999 23:24:16 GMT

Hello,
        I'm trying to get my network card to function under RH6.0.  I have an
HP 4550z, and have tried the rtl driver for the card that came with it.
As that didn't work, I swapped NICs for a Linksys 10/100 LAN PCI card
(tulip).  ifconfig -a shows that it exists, and I can ping the
interface.  When I try to set up a route to the local net or a local
host, it gives me the error:  SIODD??:  Network is unavailable.  On the
card, the lights LINK and 100 are on, but the ACT light is off.  It
works fine under windoze (dual boot).  I'm pretty sure it isn't an IRQ
problem (IRQ is 3, and /proc/interrupts? doesn't have that listed).
There is a funky modem/sound card plugged in that isn't linux compatible
(yet), but the IRQs are different.
        Any ideas?
        Thanks,
        Jon French
        [EMAIL PROTECTED]


Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.

------------------------------

From: [EMAIL PROTECTED]
Crossposted-To: comp.os.linux.setup,linux.redhat.install
Subject: PCMCIA or eth0 IRQ Problem. Not Sure?
Date: Wed, 08 Sep 1999 20:06:18 GMT

 I have a tecra 780 with a RealPort Combo Lan/Modem card. I have not
been able to get it working in RedHat Linux 6. I was hoping somepne
could help me out as I am very new to Linux and this seems to be the
last setup hurdle (besides the sound not working).
   I bought the card because it is compatable with Linux and uses the
existing  xirc2ps_cs driver. I believe I might have an IRQ conflict but
I am not sure if it is with the Lan adapater or PCMCIA services itself.
I have included a portion of the boot log below:

Sep  8 15:24:56 localhost pcmcia: Starting PCMCIA services:
Sep  8 15:24:56 localhost pcmcia:  modules
Sep  8 15:24:56 localhost kernel: Linux PCMCIA Card Services 3.0.9
Sep  8 15:24:56 localhost kernel:   kernel build: 2.2.5-15 #1 Mon Apr
19 23:00:46 EDT 1999
Sep  8 15:24:56 localhost kernel:   options:  [pci] [cardbus] [apm]
Sep  8 15:24:56 localhost kernel: Intel PCIC probe:
Sep  8 15:24:56 localhost kernel:   Intel i82365sl B step ISA-to-PCMCIA
at port 0x3e0 ofs 0x00, 2 sockets
Sep  8 15:24:56 localhost kernel:     host opts [0]: none
Sep  8 15:24:56 localhost kernel:     host opts [1]: none
Sep  8 15:24:56 localhost kernel:     ISA irqs (scanned) = 4,7,10
status change on irq 10
Sep  8 15:24:56 localhost pcmcia:  cardmgr.
Sep  8 15:24:56 localhost cardmgr[314]: starting, version is 3.0.9
Sep  8 15:24:56 localhost cardmgr[314]: watching 2 sockets
Sep  8 15:24:56 localhost kernel: cs: IO port probe 0x1000-0x17ff:
clean.
Sep  8 15:24:56 localhost kernel: cs: IO port probe 0x0100-0x04ff:
excluding 0x220-0x22f 0x330-0x337 0x378-0x37f 0x388-0x38f 0x4d0-0x4d7
Sep  8 15:24:56 localhost kernel: cs: IO port probe 0x0a00-0x0aff:
clean.
Sep  8 15:24:56 localhost cardmgr[314]: initializing socket 0
Sep  8 15:24:56 localhost kernel: cs: memory probe 0x0d0000-0x0dffff:
clean.
Sep  8 15:24:56 localhost cardmgr[314]: socket 0: Xircom CEM56
Ethernet/Modem
Sep  8 15:24:56 localhost rc: Starting pcmcia succeeded
Sep  8 15:24:57 localhost cardmgr[314]:
executing: 'insmod /lib/modules/2.2.5-15/pcmcia/xirc2ps_cs.o'
Sep  8 15:24:57 localhost kernel: xirc2ps_cs.c 1.31 1998/12/09 19:32:55
(dd9jn+kvh)
Sep  8 15:24:57 localhost kernel: xirc2ps_cs: RequestIRQ: Resource in
use
Sep  8 15:24:57 localhost cardmgr[314]:
executing: 'insmod /lib/modules/2.2.5-15/pcmcia/serial_cs.o'
Sep  8 15:24:57 localhost cardmgr[314]: get dev info on socket 0
failed: No such device
Sep  8 15:24:57 localhost inet: inetd startup succeeded


I have read in a news posting that Linux sometimes does not do a good
job at scanning IRQ values so I added the following line to
my /etc/sysconfig/pcmcia file. After I did that PCMCIA services seemed
to start up but when I tried to use eth0 nothing worked. I was able to
assign an IP address and other config information to eth0 by using
netconfig but I was unable to access the Internet or Ping any other
machine on my network. During the boot process it listed its
initialization as FAILED. This is the bootlog having added the above
line to /etc/sysconfig/pcmcia

Sep  8 10:13:02 localhost pcmcia: Starting PCMCIA services:
Sep  8 10:13:02 localhost pcmcia:  modules
Sep  8 10:13:02 localhost kernel: Linux PCMCIA Card Services 3.0.9
Sep  8 10:13:02 localhost kernel:   kernel build: 2.2.5-15 #1 Mon Apr
19 23:00:46 EDT 1999
Sep  8 10:13:02 localhost kernel:   options:  [pci] [cardbus] [apm]
Sep  8 10:13:02 localhost kernel: Intel PCIC probe:
Sep  8 10:13:02 localhost kernel:   Intel i82365sl B step ISA-to-PCMCIA
at port 0x3e0 ofs 0x00, 2 sockets
Sep  8 10:13:02 localhost kernel:     host opts [0]: none
Sep  8 10:13:02 localhost kernel:     host opts [1]: none
Sep  8 10:13:02 localhost kernel:     ISA irqs (default) =
3,4,5,7,9,10,12 polling interval = 1000 ms
Sep  8 10:13:02 localhost pcmcia:  cardmgr.
Sep  8 10:13:02 localhost cardmgr[314]: starting, version is 3.0.9
Sep  8 10:13:02 localhost cardmgr[314]: watching 2 sockets
Sep  8 10:13:02 localhost kernel: cs: IO port probe 0x1000-0x17ff:
clean.
Sep  8 10:13:02 localhost kernel: cs: IO port probe 0x0100-0x04ff:
excluding 0x220-0x22f 0x330-0x337 0x378-0x37f 0x388-0x38f 0x4d0-0x4d7
Sep  8 10:13:02 localhost kernel: cs: IO port probe 0x0a00-0x0aff:
clean.
Sep  8 10:13:02 localhost cardmgr[314]: initializing socket 0
Sep  8 10:13:02 localhost kernel: cs: memory probe 0x0d0000-0x0dffff:
clean.
Sep  8 10:13:02 localhost cardmgr[314]: socket 0: Xircom CEM56
Ethernet/Modem
Sep  8 10:13:02 localhost rc: Starting pcmcia succeeded
Sep  8 10:13:02 localhost cardmgr[314]:
executing: 'insmod /lib/modules/2.2.5-15/pcmcia/xirc2ps_cs.o'
Sep  8 10:13:02 localhost kernel: xirc2ps_cs.c 1.31 1998/12/09 19:32:55
(dd9jn+kvh)
Sep  8 10:13:05 localhost kernel: eth0: MII link partner: 00a1
Sep  8 10:13:05 localhost kernel: eth0: media 100BaseT, silicon
revision 5
Sep  8 10:13:05 localhost kernel: eth0: Xircom: port 0x300, irq 3,
hwaddr 00:10:A4:F5:91:2A
Sep  8 10:13:02 localhost cardmgr[314]:
executing: 'insmod /lib/modules/2.2.5-15/pcmcia/serial_cs.o'
Sep  8 10:13:05 localhost kernel: tty03 at 0x02e8 (irq = 3) is a 16550A
Sep  8 10:13:05 localhost cardmgr[314]: executing: './network start
eth0'
Sep  8 10:13:05 localhost inet: inetd startup succeeded
Sep  8 10:13:06 localhost kernel: eth0: media 100BaseT, silicon
revision 5
Sep  8 10:13:06 localhost lpd: lpd startup succeeded


I only included portions of these log files due to space limitations.

I would be really greatful if someone could help me out as I spend $300
on this card and have yet to get it working. Thank you very much.

-David
[EMAIL PROTECTED]



Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.

------------------------------

From: Scott Nolde <[EMAIL PROTECTED]>
Subject: Re: Using DHCP
Date: Wed, 08 Sep 1999 19:27:16 GMT

I'm in the region and I use Mediaone RR just fine.  I battled this for a
while soon after the cable modem was installed.  I've had to make no
special modifications to any files, so try checking the follwing files
(I may miss one, so really check):
/etc/hosts
/etc/hosts.allow
/etc/sysconfig/network
/etc/sysconfig/network-scripts/ifcg-eth0 or -ethx - see example
following....


## ifcfg-eth0 to the cablemodem
DEVICE="eth0"
ONBOOT="yes"
BOOTPROTO="dhcp"
GATEWAY=24.88.21.1
IPXNETNUM_802_2=""
IPXPRIMARY_802_2="no"
IPXACTIVE_802_2="no"
IPXNETNUM_802_3=""
IPXPRIMARY_802_3="no"
IPXACTIVE_802_3="no"
IPXNETNUM_ETHERII=""
IPXPRIMARY_ETHERII="no"
IPXACTIVE_ETHERII="no"
IPXNETNUM_SNAP=""
IPXPRIMARY_SNAP="no"
IPXACTIVE_SNAP="no"
USERCTL=yes


## ifcfg-eth1 to the local subnet
DEVICE="eth1"
IPADDR="192.168.10.1"
NETMASK="255.255.255.0"
ONBOOT="yes"
BOOTPROTO="no"
IPXNETNUM_802_2=""
IPXPRIMARY_802_2="no"
IPXACTIVE_802_2="no"
IPXNETNUM_802_3=""
IPXPRIMARY_802_3="no"
IPXACTIVE_802_3="no"
IPXNETNUM_ETHERII=""
IPXPRIMARY_ETHERII="no"
IPXACTIVE_ETHERII="no"
IPXNETNUM_SNAP=""
IPXPRIMARY_SNAP="no"
IPXACTIVE_SNAP="no"
USERCTL=yes

## /etc/sysconfig/network
NETWORKING=yes
FORWARD_IPV4="yes"
HOSTNAME="host"
DOMAINNAME=domain.com
GATEWAY="gateway.ip.address.here"
GATEWAYDEV="eth0"
NISDOMAIN="domain.com"

Add these lines to /etc/rc.d/rc.local:

ipchains -P forward DENY
ipchains -A forward -s 192.168.10.0/255.255.255.0 -j MASQ

** You may also wish to add lines to build your firewall on eth0! **

I use dhcpd to assign IP addresses in my subnet.  This should be the
basic gist of configuring your subnet to work over the cablemodem.  I
also make my linux box the DNS of the subnet routing to MediaoneRR.  No
special route commands to use, so all/most the above should work.

email if necessary.

Chuck Hancock wrote:
> 
> Has anyone had any experience using linux on Media One Road Runner - south
> east region?
> 
> I can not get linux to get an IP.  I know my NIC is fine, because if I put
> my windows machine and my linux machine on the same subnet I can ping back
> and forth and I can telnet into my linux.
> 
> Media One claims it should work, but I have found a couple How To's that
> claim Media One does not use a standard DHCP and has caused problems.
> 
> Any suggestions on where to go from here?  Anything else I shoud test?
> 
> -chuck

-- 
================================================
                 Scott Nolde
          [EMAIL PROTECTED]
================================================

------------------------------

From: "Matt Anderson" <fuckoff>
Subject: From woe to go... help
Date: Thu, 9 Sep 1999 10:06:24 +1000

Ok,  I'm not entirely new to Linux, but I would like someone who has done
this before to maybe just outline some steps for me.  I haven't had to
actually set up the config that is needed in this situation before and want
to make sure I don't overlook anything.

Don't really need specifics, just an outline on how to go from a clean Linux
install, including Apache, Bind and Ipchains.  I have an ISDN line going
into a Router going into a Linux PC with two NIC's.  What various daemons
and services do I need to configure so that a Win95/NT LAN can talk to the
Internet thru the Linux box, and so that we can host our own e-mail, FTP and
website.  Also want the box to act as a primary DNS and firewall.

Any and all help would be greatly appreciated.

Thanks in advance

Matt



------------------------------

Reply-To: [EMAIL PROTECTED]
From: [EMAIL PROTECTED] (Rod Smith)
Subject: Re: DSL Connection Using Linux
Date: Wed, 08 Sep 1999 23:58:37 GMT

[Posted and mailed]

In article <[EMAIL PROTECTED]>,
        In Yen Tjin <[EMAIL PROTECTED]> writes:
> Hi,
> 
> I have a small business operating in Los Angeles area and am thinking to
> expand my business into e-commerce.  One best piece of advice that I
> have been given is to use a DSL service.  For this, I would like to use
> a Linux machine as my firewall as well as my DNS, mail, and WEB
> servers.  I already have applied for a subdomain and have been granted
> with a C domain with 256 IP addresses.  In the following, I would like
> to ask several questions to get my company connected to the Internet:

This is all do-able with Linux.  An entire C-class domain space is
probably overkill, but that won't cause you any problems.  (Whether it's
reasonable to grab 256 addresses when you only need a handful is another
matter....)

> 1. What is the current DSL support on Linux?  Is it reliable?

Linux neither has nor needs explicit DSL support.  In most cases, you just
set it up like any other Ethernet connection.  It's as reliable as Linux's
Ethernet networking (very reliable, given the right hardware) in
conjunction with the reliability of the DSL (which ranges from quite poor
to very good, depending upon the provider and your luck).

This does assume, though, that you use a DSL "modem" that sits outside the
computer and connects via an Ethernet cable.  If your DSL provider offers
an internal DSL "modem," *DO NOT* accept it.  As of now, Linux has no
drivers for such devices, AFAIK, though I've heard rumors that some
development is going on to get some of these things working.

> 2. Since this is a small business, it will make more sense if I least a
> residential DSL service with the local phone company.

I disagree.  It'll cost you more, but you should probably go for a
business-class account, for several reasons:

1) The residential accounts typically limit upstream bandwidth to 90kbps,
   128kbps, or some other smallish number.  Since many of the services you
   mentioned involve upstream traffic, you DO NOT want to limit your
   upstream speed in this way.  Better to get a business-class SDSL line
   or a higher-end ADSL line that has better upstream speeds.
2) Residential accounts often (but not always) include language in their
   terms of service (TOS) documents limiting your ability to run servers.
   You don't want to hassle with your ISP about this.
3) Business accounts are more likely to include guaranteed uptime in their
   TOS documents.  Most residential accounts are basically "it'll probably
   be up most of the time, but if not, tough."  This is NOT something you
   want to risk with your business connectivity.
4) ISPs offering residential accounts often (but not always) don't support
   your maintaining your own domain name.  A few actively forbid it.
5) As you note, most residential accounts only provide one IP address. 
   You can get around this in various ways with Linux, but you might want
   more flexibility in the future.
6) Your ISP might just get miffed if you run a business on a residential
   account.  The preceding are ways that ISPs encourage the split as
   labeled, but even if an ISP doesn't have those rules or if you adhere
   to them, the ISP might still unilaterally switch you or drop your
   service if you run a business on residential-class DSL.

> If I leased a
> residential DSL service, chances are that the leasing company will
> provide with one static IP.  Is it legal to have my domain connected to
> the Internet through a residential DSL service?

Legal?  Certainly.  Does it conform to the TOS with your ISP?  I don't
know.  You'll have to check the agreement with your ISP.

> If so, how can I have
> my domain setup so that any computer that has my domain IP address can
> go to Internet and surf, send/receive e-mail, and etc.?

IP masquerading.  This does have limits:

1) For the most part (but see #2), computers on your internal network will
   see the Internet in an unobstructed way.  This means you can Web surf,
   check for email on POP servers, send email, use FTP servers, etc. on
   any arbitrary internal computer.
2) A handful of services DO NOT work through IP masquerading.  I'm told
   this is true of some videoconferencing protocols, for instance.
3) To the Internet as a whole, it'll look like you've got one computer --
   the one with the direct connection to your ISP.  Therefore, for servers
   you want to be visible to the outside world, you'll either have to run
   them on that machine or provide some sort of port-forwarding mechanism.
   You might or might not want to do this.  For instance, you might want
   to run a high-visibility service like a web server on a machine that's
   not involved in the masquerading and that has no privileged access to
   the rest of the machines on your network.  This would require a
   separate IP address for that machine.

-- 
Rod Smith
[EMAIL PROTECTED]
http://members.bellatlantic.net/~smithrod
Author of _Special Edition Using Corel WordPerfect 8 for Linux_, from Que

------------------------------

From: <[EMAIL PROTECTED]>
Subject: Re: IP forwarding
Date: Wed, 08 Sep 1999 23:31:17 GMT


John Roberts wrote:

> I basically have 2 subnets: 192.168.0.0 and 192.168.1.0.  I can ping out
> from the gateway box to machines on either network.  I can ping the
gateway
> box (either address) from any machine on either network.  I cannot,
however,
> ping from a box on one subnet to a box on the other subnet.

192.168.0.0 isn't a subnet is it?  It's a whole class B.

192.168.0.0 is like 192.168.*.*.

--daemous/snowaep


==================  Posted via CNET Linux Help  ==================
                    http://www.searchlinux.com

------------------------------

From: Derrick J Brashear <[EMAIL PROTECTED]>
Subject: Re: Wireless: Aviator2.4 = Raytheon Raylink
Date: Wed, 8 Sep 1999 16:48:03 -0400

On Mon, 6 Sep 1999 [EMAIL PROTECTED] wrote:

In article <[EMAIL PROTECTED]>,
  George <[EMAIL PROTECTED]> wrote:
> Thanks Dick!
>
>  Can you supply any more information?
>    How stable is it?
>    throughput?
>    range?
>    opinions?
>
>  If this thing works OK Linux users can have a wireless network of 2
> machines
>  for under $200! I see that onsale.com is selling the Aviator2.4 network
> kit
>  for $150 but it has a different part number than the webgear site so
> I'm not
>  sure if it's the right stuff.

I got one of the Raytheon cards from onsale, I have it still sealed; our
local network is DSSS, not FHSS, so it's not useful to me; If anyone's
interested, make an offer.

-D



------------------------------

From: Torsten Mueller <[EMAIL PROTECTED]>
Subject: connecting 2 lans 
Date: Thu, 09 Sep 1999 01:45:31 +0200

Hello,

I have Problems with my network configuration.
I use Suse 6.0 . 
I want to use a Linux PC as a gateway between a 10 MB and 100 MB and the
Inter Net.
My network topolog is shown below. the 10 MB is the network
192.168.100.0 , the 100 MB network is the 192.168.0.0 both same subnet
255.255.255.0
my /etc/route.conf looks like this:
192.168.100.0           0.0.0.0                 255.255.255.0          
eth0
192.168.100.98          0.0.0.0                 255.255.255.255        
ippp0
192.168.0.0             0.0.0.0                 255.255.255.0          
eth1
default                 192.168.100.98
a part of my rc.config :
IFCONFIG_0="192.168.100.100 broadcast 192.168.100.255 netmask
255.255.255.0 up"
IFCONFIG_1="192.168.100.97 pointopoint 192.168.100.98 up"
IFCONFIG_2="192.168.0.50 broadcast 192.168.0.255 netmask 255.255.255.0
up"

What works: 
all pc can use the samba shares on the linux pc.
all pc can use the internet.

My Problems:
win 1 can ping linux on both 10 MB and 100 MB, but not (for example) win
4 or win 5
win 1 can not access resources on win 4 (windows networking)

I think i have to enable ip forwarding or to change the routing on my
linux box ??
How are the right steps to this? In the NET3 Howto i saw the point
bridging. is it that what i am looking for ? ( but if i enable bridging,
are the samba shares on my linux box accessable ?) 

Thank you for your help. 

Greetings Torsten

                     internet
                        :
                        :
                       isdn
                    linux-server
    ------------ 10mb nic   100mb nic ---------------
    :                                                :
    :                      ---------------------     :    
=======================
    :                      :                   :     :    
:                      :
win 1 10MB                 :                - 1 0 0  M B  H U B
-                 :
    :                      :               :                    
:                :
    :                      :               :                    
:                :
win 2 10MB           win 4 100MB      win 5 100MB         win 6
100MB        win 7 100MB
    :
    :
win 3 10MB

------------------------------

Reply-To: [EMAIL PROTECTED]
From: [EMAIL PROTECTED] (Rod Smith)
Subject: Re: Good Documnet for setting up ADSL
Date: Thu, 09 Sep 1999 00:10:06 GMT

[Posted and mailed]

In article <[EMAIL PROTECTED]>,
        =?EUC-KR?B?vNu787/4?= <[EMAIL PROTECTED]> writes:
> Greetings,
> 
> My ISP started ADSL service, but they said Linux won't be supported
> because they haven't tested on it.  ISP said Linux will be supported by
> the end of October(hopefully), and I could try to install it myself if I
> really wanted to.
> 
> If I want to do this by myself I'll have to spend $40 whether I succeed
> or not since  there is no trial period. I was wondering if there is any
> good document that I could look at; so that I could install it on my
> Linux Box by myself.

As one other person has already pointed out, setting up Linux for DSL is
essentially identical to setting Linux up for an Ethernet LAN.

One other point, though, is that DSL "modems" come in two varieties:
internal and external.  The external DSL "modems" are really more like
bridges or routers, and they connect to the computer via an Ethernet
cable.  You therefore need an Ethernet card on your Linux computer.  The
internal variety is really a network card in and of itself; it "talks" DSL
rather than Ethernet.  AFAIK, at present there are no Linux drivers for
any such boards, so unless you want to do some kernel hacking, don't get
an internal DSL "modem."  If necessary, buy your own external one (your
ISP should be able to privide you with recommendations).

-- 
Rod Smith
[EMAIL PROTECTED]
http://members.bellatlantic.net/~smithrod
Author of _Special Edition Using Corel WordPerfect 8 for Linux_, from Que

------------------------------

Reply-To: [EMAIL PROTECTED]
From: [EMAIL PROTECTED] (Rod Smith)
Subject: Re: good 100Mb/s NIC for Linux?
Date: Thu, 09 Sep 1999 00:04:03 GMT

[Posted and mailed]

In article <2gAB3.8827$[EMAIL PROTECTED]>,
        "Eugene" <[EMAIL PROTECTED]> writes:
> Hi everybody,
> 
> I'm planning to buy a 10/100Mb/s network card and I want it to work well
> with Linux. I have already 10 Mb/s network cards with Linux (NE2000 PCI) and
> they worked great. Is there some similar standard for 100Mb/s? I heard Intel
> Etherexpress works well. is that true?
> 
> anyhow, I'd greatly appreciate it if someone could post their success /
> horror stories with Linux + 10/100 Mb/s ethernet.

It's hard to go too far wrong, provided the card physically works, and
provided you're willing to compile in the latest driver.

The Intel boards certainly have good reputations, but they're pricey. 
Similar comments apply to most 3COM boards.  Most of the low-priced boards
you see in the stores have clones of the DEC Tulip chipset on them, and
these work quite well with recent drivers, but some may be unreliable with
older drivers, and sometimes even with certain specific recent ones. 
There are also a few boards using a variety of other chipsets and, hence,
drivers, like the D-Link DFE-530TX, which uses the VIA Rhine chipset and
driver.  For the most part, these work fine, too.  The most recommended
boards do seem to be the Intel, 3COM, and assorted Tulip "clone" boards. 
The closest thing to a non-manufacturer-specific standard is the Tulip
"clone" chipsets, and boards based on them.

-- 
Rod Smith
[EMAIL PROTECTED]
http://members.bellatlantic.net/~smithrod
Author of _Special Edition Using Corel WordPerfect 8 for Linux_, from Que

------------------------------


** 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
******************************

Reply via email to