Linux-Networking Digest #616, Volume #12 Fri, 17 Sep 99 00:13:43 EDT
Contents:
Re: Serial to Networking (Raymonds Doetjes)
Re: File Table Overflow ... (Alejandro)
Re: IP Forwarding based on hostname ("Steve Cowles")
Re: linux networking (Yash Khemani)
Re: SOL_AX25 socket option (Clifford Kite)
Re: Test ether connection (Raymonds Doetjes)
Re: Newbie Looking for FF.exe Utility for Linux. (Clifford Kite)
Re: xdmcp on Red Hat 5.2 ("Steve Cowles")
RH6.0&NE2000 Compatible Card ([EMAIL PROTECTED])
Re: Am I using netmasks incorrectly? (Julien B Beasley)
Re: Recommendation for 100Mbps Switched Ethernet hardware (David C.)
Getting both my NICs working ("-=NFA=-")
Re: kernel 2.2.11 & 3c509 NIC ("Raterus")
Re: Getting both my NICs working ("Colvin")
Re: Linux to net through Win ("Colvin")
----------------------------------------------------------------------------
From: Raymonds Doetjes <[EMAIL PROTECTED]>
Subject: Re: Serial to Networking
Date: Thu, 16 Sep 1999 20:06:14 +0200
Kewl I know these problems pretty good I came out of a serial minded
company but now we switched to a combination of EThernet and Serial.
For your problem about steady ports is an very easy solution. It is a
device called IOLan+ portserver.
Actually it's a port and terminal server. You can connect terminals to it
and login and start a telnet session. Or you can run a respawn for a tty
for each port of this device. This device aslo supports Linux and
HP-UX flawlessly.
For terminals wich do not need steady ports you can use telnet sessions via
either a WOrkstation or the Old and steardy Terminals.
Using a combination of LAN techniques and Serial techniques makes it very
flexibel and pushes the code changes to a minimum. Thes IOLan+ PortServers
are very good and connect to any ethernet network. So what you do is, you
have a Ethernet backbone in every store connect a IOLan+ PortServer to the
lan and connect any serial equipment (even LCP printing is supported),
connect the ethrnet backbone to a router and connect the router to a
frame-relay, ISDN(dial on demand) or whatever and voila. You should have a
ethernet backbone and router setup on your central CPU side asswell ;)
Raymond
Ram0n wrote:
> I'm currently working for a company that uses serial communication with
> their applications (i.e a tty?? assign to an attached printer, another
> tty?? to a terminal, etc). They currently use HP-UX as their OS, but
> I'm trying to push Linux using networking in all their point of sale
> stations as an option. There are different complex issues I have
> encounter in analyzing this option like: Multi-stores setup (i.e.
> replacing serial with networking would mean something like frame relay
> to connect all the stores in a chain), and a lot of re-programming of
> the systems scripts that as I mention above that assign a specific tty##
> to certain devices (like attached printers). With networking this last
> one I founded kind of challenging since now the different devices are
> configured or respawn by inittab and in networking things would depend
> on initd (i.e. that it would assign a pseudo tty to every session and
> the same to the devices like printers) and would mean some
> reprogramming, which will not look good in my case of changing to LINUX
> and networking.
>
> If anyone have encounter something like this before or knows anything
> that can be of help, I would really appreciate.
>
> Sent via Deja.com http://www.deja.com/
> Share what you know. Learn what you don't.
------------------------------
From: Alejandro <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.misc
Subject: Re: File Table Overflow ...
Date: Fri, 17 Sep 1999 02:31:24 GMT
xfleblon wrote:
>
> Hi,
>
> I'm doing batch PPP connections to a Linux server in order to perform
> file transfers.
> Sometime, the upload fails returning the message "File Table Overflow
> ..." ! But the same upload (same file, same server, same location)
> performed few seconds after is successfull !
>
> Does anybody have an idea of the problem, and perhaps know a solution ?
> Please answer at [EMAIL PROTECTED]
>
> Thanks
echo 10000 > /proc/sys/kernel/file-max
This is what you increase the number of file open.
>
> FX
>
>
> Sent via Deja.com http://www.deja.com/
> Share what you know. Learn what you don't.
================== Posted via CNET Linux Help ==================
http://www.searchlinux.com
------------------------------
From: "Steve Cowles" <[EMAIL PROTECTED]>
Subject: Re: IP Forwarding based on hostname
Date: Fri, 17 Sep 1999 03:13:14 GMT
If I get some free time, I think I'm going to write an official How-To on this subject.
This question must be asked everyday in this newsgroup. Hmmm...
Anyway, to answer your question... Your on the right track using ipmasqadm, but I could
never get "ipmasqadm mfw" to work as specified. So I changed to using "ipmasqadm
portfw"
instead of "ipmasqadm mfw". If I understand your post correctly, you have two ip
addresses
bound to your external interface along with two internal web servers. Using the portfw
option of ipmasqadm you "should" be able to accomplish your goal. I use this to forward
all "external" port 80 and 110 requests to an internal exchange server. I have
included a
<cut/paste> of my rc.firewall that I use that should point you in the right direction.
The
only difference is I have one external ip address on my linux box and one exchange
server
begind the linux box, but you should be able to figure out the rest.
Hope this helps
Steve Cowles
<cut/paste from rc.firewall>
EXCH_IP=192.168.9.2 (Internal IP address of Exchange Server)
EXT_IP=1.1.1.1 (External IP address of Linux Server)
# Add additional support for autofw, mfw and portfw
# ${MODPROBE} ip_masq_autofw
# ${MODPROBE} ip_masq_mfw
${MODPROBE} ip_masq_portfw
# =========================================================
# Port Forwarding Settings (external to internal IP/ports)
# =========================================================
if [ -x ${IPMASQADM} ] ; then
${IPMASQADM} portfw -f
# ${IPMASQADM} autofw -f
# ${IPMASQADM} mfw -f
${IPMASQADM} portfw -a -P tcp -L ${EXT_IP} 80 -R ${EXCH_IP} 80
${IPMASQADM} portfw -a -P tcp -L ${EXT_IP} 110 -R ${EXCH_IP} 110
fi
eb <[EMAIL PROTECTED]> wrote in message
news:1zeE3.1115$[EMAIL PROTECTED]...
> I have a question regarding ipchains and ipmasqadm.
>
> Is it possible to forward requests based on hostname to an internal
> webserver?
>
> w1.domain.com 80 (ip is external interface of firewall) ----> w1.domain.com
> 80 (internal ip address)
> w2.domain.com 80 (ip is external interface of firewall) ----> w2.domain.com
> 80 (internal ip address)
>
> The only solution that I could find so far is to use ipmasqadm mfw, but this
> requires using different external ports. (Maybe I am missing something).
>
> Any help or advice appreciated.
>
> Thanks,
>
> Erik
>
>
>
>
>
>
>
>
>
------------------------------
From: Yash Khemani <[EMAIL PROTECTED]>
Subject: Re: linux networking
Date: Fri, 17 Sep 1999 02:18:59 GMT
Student wrote:
>
> i'm a university student and i live in a hostel...recently,
> i'm participating in a project that requires my group to make a network
> in the hostel. The hardware, including the network, is ready for
> use. but we are deciding whether using NT or linux is better...
> we have the following targets in our project..
> 1) each user has some space in the server HD
> 2)they can print by using the hostel's printer but with quota
> is NT or Linux is better? which one is easier to maintain?
> we have some ppl that knows NT and Linux, and we want to
> learn more in networking by reading books...can anyone give us some
> suggestion on that?
of course linux is better! but then what did you
expect to hear on this group :-). seriously, linux
is better for several reasons.
-> you can keep a linux box up for months, even
years. the longest i've had one up is 6 months.
but downtime has been either scheduled or at
discretion. show me an nt box that is being used
heavily where you can do that.
-> nt != true multi-user system. unless you want to
run terminal server (cough! choke! controlling
laughter!). i'm not sure what the limit is on the
number of users on a linux box. is there a limit?
-> with linux, there is printing and file sharing with
windows systems with samba (www.samba.org). there
is file sharing with other unix systems with nfs and
coda (well, coda with other linux at this time, i
believe). there is also printer sharing with other
unix systems.
-> there are filesystem quotas, but i'm not aware of
anything available that gives you printing quotas.
but it would be easy ehough to write a wrapper
around lpd.
-> which one is easier to maintain? i can maintain
linux boxes remotely by installing ssh. nt? you
must speak pcAnywhere or some other program that is
obscenely unusable over a slow link. and i can go
anywhere with a small linux distribution that i can
boot from a couple of floppies and connect securely
to my machine. how do you do this with nt? do you
install pcAnywhere on that machine? what if that
machine doesn't have a windows operating system?
Yash
------------------------------
From: kite@NoSpam.%inetport.com (Clifford Kite)
Subject: Re: SOL_AX25 socket option
Date: 16 Sep 1999 20:27:46 -0500
MICHAEL QUINLIVAN ([EMAIL PROTECTED]) wrote:
> When writing Ax.25 apps under Linux, the identifer SOL_AX25 is undefined
> when I run make. I have #include the linux/ax25.h and sys/socket.h files
> but it still cant find reference to it. The same problem also occurs when
Here it's
/usr/include/linux/socket.h:#define SOL_AX25 257
--
Clifford Kite <kite@inet%port.com> Not a guru. (tm)
/* Editing with vi is a lot better than using a huge swiss army knife.
Use =} to wrap paragraphs in vi. */
------------------------------
From: Raymonds Doetjes <[EMAIL PROTECTED]>
Subject: Re: Test ether connection
Date: Thu, 16 Sep 1999 20:06:07 +0200
==============5A96821EEB5596872A1A47E4
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
First try on a more elementry way. Try pinging the server from
workstations and vice versa if this works you can start troubleshooting
SMB.
My guess is, that the network card isn't the right one that the compiled
in the kernel and is'nt compiled as a module. I don't know what NIC's
are in these DELL machines.
My guess is probably onboard Intel Pro cards.
Raymond
Josh Flechtner wrote:
> Hello group.
>
> I am running a Linux RH6.0 server and am using Samba to (try) talk
> to the Win boxes here at the office. The Server came direct from Dell
> with the ethernet card preinstalled and on LILO boot it does not
> recognize it and subsequently fails. I must type ifconfig eth0
> 192.168.0.1 to activate the ether-connection. From this point how can
> I tell if the card is active and is capable of recieiving a signal
> from the hub and vice-versa?? I've tried everything in both smb.conf
> and the Windows machines to try and get the server to show in 'Network
> Neighboorhood' and no luck. Always met with an "Unable to browse
> network......." dialog box. Hence I suspect a hardware glitch.
>
> Thank you in advance!
>
> Josh Flechtner
> [EMAIL PROTECTED]
==============5A96821EEB5596872A1A47E4
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit
<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
First try on a more elementry way. Try pinging the server from workstations
and vice versa if this works you can start troubleshooting SMB.
<br>My guess is, that the network card isn't the right one that the compiled
in the kernel and is'nt compiled as a module. I don't know what NIC's are
in these DELL machines.
<br>My guess is probably onboard Intel Pro cards.
<p>Raymond
<p>Josh Flechtner wrote:
<blockquote TYPE=CITE>Hello group.
<p> I am running a Linux RH6.0 server and am using Samba
to (try) talk to the Win boxes here at the office. The Server came direct
from Dell with the ethernet card preinstalled and on LILO boot it does
not recognize it and subsequently fails. I must type <i>ifconfig eth0 192.168.0.1</i>
to activate the ether-connection. From this point how can I tell if the
card is active and is capable of recieiving a signal from the hub and vice-versa??
I've tried everything in both smb.conf and the Windows machines to try
and get the server to show in 'Network Neighboorhood' and no luck. Always
met with an "Unable to browse network......." dialog box. Hence I suspect
a hardware glitch.
<p>Thank you in advance!
<p>Josh Flechtner
<br><a href="mailto:[EMAIL PROTECTED]">[EMAIL PROTECTED]</a></blockquote>
</html>
==============5A96821EEB5596872A1A47E4==
------------------------------
From: kite@NoSpam.%inetport.com (Clifford Kite)
Subject: Re: Newbie Looking for FF.exe Utility for Linux.
Date: 16 Sep 1999 20:31:16 -0500
Clifford Kite (kite@NoSpam.%inetport.com) wrote:
> Here's a way that works well for me.
> find . -type f -name \*.txt -print | xargs grep foo 2> /dev/null
Another small point: If you want to include directory symbolic links in
the path then add the find option -follow .
--
Clifford Kite <kite@inet%port.com> Not a guru. (tm)
/* 97.3% of all statistics are made up. */
------------------------------
From: "Steve Cowles" <[EMAIL PROTECTED]>
Subject: Re: xdmcp on Red Hat 5.2
Date: Fri, 17 Sep 1999 02:35:34 GMT
After you regain control of your system... the command you are looking for is "xdm".
The
xdm command will answer direct XDMCP queries (even XDMCP broadcasts), if that's what
you
are referring to in your post. On redhat systems you can have xdm start automattically
at
boot up by changing the default run level from 3 to 5. To do this simply edit
/etc/inittab
and change the following line from:
id:3:initdefault:
to
id:5:initdefault:
also, at the bottom of the same file should be a line as follows: (if its not their,
put
it in)
# Run xdm in runlevel 5
x:5:respawn:/usr/bin/X11/xdm -nodaemon
Steve Cowles
SWCowles at gte dot net
Neil Zanella <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
>
> Hello,
>
> I have a PC on a LAN of preconfigured NCD X-Terminals. I would like to
>
> know exactly what services I need to run on my PC (eg. xdmcp deamon?) so that
>
> I can access my desktop from the X Terminals via xdmcp (without using the
>
> chooser).
>
> PS: I had to comment out everything in /etc/inetd.conf for security reasons
>
> and my PC stopped working as soon as I did this.
>
> Thanks,
>
> Neil
------------------------------
From: [EMAIL PROTECTED]
Subject: RH6.0&NE2000 Compatible Card
Date: Fri, 17 Sep 1999 02:30:45 GMT
Dear Sir:
I have installed RH6.0 on my machine.But it doesn't recognize one of my
Ethernet Card.During the installation,I have defined the type of
Ethernet Card as NE2000 Compatible.Otherwise,RH6.0 only configured the
Intel one on PCI bus and missed the NE2000 on ISA bus.
How can I make this one working?
Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.
------------------------------
From: Julien B Beasley <[EMAIL PROTECTED]>
Subject: Re: Am I using netmasks incorrectly?
Date: Fri, 17 Sep 1999 02:23:39 GMT
In article <[EMAIL PROTECTED]>,
"John Hardin" <[EMAIL PROTECTED]> wrote:
>
> Julien B Beasley wrote in message <7rppmj$is2$[EMAIL PROTECTED]>...
> >My /etc/sysconfig/static-routes file reads
> >
> >eth0 net 167.76.175.0 netmask 255.255.255.0 gw 167.76.232.1
> >eth0 net 167.76.196.0 netmask 255.255.255.0 gw 167.76.232.1
> >
> >Now if I traceroute to a computer on the 167.76.175.0 network, it
goes
> >through the gateway.
> >However, if I traceroute to the computer 167.76.196.24, it will not
go
> >through the gateway, and will not be able to connect!!
>
> Insufficient information to debug. Please post the output
of "ifconfig" and
> "route -n". Thanks.
Ok. I'm going nuts now :). Now I am able to ping any machine on the
167.76.196.0 network.
]$ /sbin/route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
167.76.196.0 167.76.232.1 255.255.255.0 UG 0 0 0
eth0
167.76.44.0 167.76.232.1 255.255.255.0 UG 0 0 0
eth0
167.76.175.0 167.76.232.1 255.255.255.0 UG 0 0 0
eth0
167.76.56.0 167.76.232.1 255.255.255.0 UG 0 0 0
eth0
167.76.0.0 0.0.0.0 255.255.0.0 U 0 0 0
eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0
lo
0.0.0.0 167.76.232.1 0.0.0.0 UG 0 0 0
eth0
Ok, I'm guessing that the reason why my 167.76.0.0 entry does not work
is that the gateway seems set to 0.0.0.0 above. I guess 0.0.0.0 is not
valid gateway :)
Furthermore, the 167.76.196.0 entry was also set to 0.0.0.0 when I
first ran route -n as you suggest! After re-edinting via linuxconf, it
changed back to the gateway 167.76.232.1.. I'm pretty confused :)
In linuxconf, the gateway for 167.76.0.0 is set to 167.76.232.1.. I
don't understand why in route -n, it shows up as 0.0.0.0. The
167.76.196.0 seems to have "fixed itself". How can I get the 167.76.0.0
entry to have a valid gateway?
running ifconfig gives
]$ /sbin/ifconfig
eth0 Link encap:Ethernet HWaddr 00:C0:4F:4A:A5:07
inet addr:167.76.232.183 Bcast:167.76.254.255
Mask:255.255.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1795650 errors:82 dropped:0 overruns:0 frame:128
TX packets:26337 errors:0 dropped:0 overruns:0 carrier:10
collisions:1645 txqueuelen:100
Interrupt:11 Base address:0xdc00
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:3924 Metric:1
RX packets:1255 errors:0 dropped:0 overruns:0 frame:0
TX packets:1255 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
Finally, /etc/sysconfig/static-routes is as follows:
eth0 net 167.76.175.0 netmask 255.255.255.0 gw 167.76.232.1
eth0 net 167.76.56.0 netmask 255.255.255.0 gw 167.76.232.1
eth0 net 167.76.44.0 netmask 255.255.255.0 gw 167.76.232.1
eth0 net 167.76.0.0 netmask 255.255.0.0 gw 167.76.232.1
eth0 net 167.76.196.24 netmask 255.255.255.255 gw 167.76.232.1
You can see that at least in the above file, the gateway for 167.76.0.0
seems to be set correctly. Why is it set to 0.0.0.0 in route -n, and
how can I change it?
Many thanks,
Julien Beasley
--
It may take a litte courage to ask your doctor about Erectile
Dysfunction.
But everything worthwhile usually does.
-Bob Dole
Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.
------------------------------
From: [EMAIL PROTECTED] (David C.)
Crossposted-To: comp.sys.ibm.pc.hardware.networking
Subject: Re: Recommendation for 100Mbps Switched Ethernet hardware
Date: 16 Sep 1999 15:09:59 -0400
Someone e-mailed me privately asking about what "layer-2", "layer-3",
"unmanaged" mean, and the difference between "switch" and "hub". He
says he asked publicly, but the message hasn't arrived in my news
spool. So, I'm just going to post the reply here.
For those of you who already know a lot about networking, this may seem
trivially simple. I'm trying to keep it that way. If I have anything
wrong, or if anything could be explained better, let me know. I plan on
making this answer a FAQ for a web page I'm in the process of setting
up.
-- David
=====================
- Hub - An incredibly generic term. Any device that connects multiple
network devices together. Usually, when people refer to "hubs" they
are referring to dumb repeaters.
A repeater takes every packet that comes in and transmits it out every
port. Repeaters have no intelligence. Repeaters can be used to
increase cable-lengths, or to connect extra workstations to a network
segment. There are limits to what you can do with repeaters, however.
For instance, Ethernet doesn't allow more than three repeaters between
any two nodes on the network.
If you use nothing but repeaters to make a large LAN, you won't get
good performance, because every packet will be transmitted to every
port on the network. This is where switches become useful.
- Switch. A very generic term for any device that moves packets from
one place to another without broadcasting it to everybody. A switch
will examine the content of packets to determine which port the
destination is connected to, and then send the packet only to that
port. There are layer-2 switches, layer-3 switches, and other
switches that aren't as easily classified.
Some kinds of networks (like ATM and frame-relay) only work when
network devices are directly connected to switches. Other kinds (like
Ethernet) will allow devices other than switches to be attached to
network devices.
The various layers refer to the layers of the OSI (Open Standards for
Interconnection) protocol stack:
layer 1 is the physical layer. The raw analog/optical signals that
make up a physical network link are defined by layer 1
standards. The layer 1 specification defines how bits are
encoded on the wire and how packets are delimited from one
another. SONET (a common fiber-optic standard), CSMA/CD
(the layer-1 signalling used by 10M Ethernet), and V.90
(used by 56K modems) are examples of layer-1 protocols.
layer 2 is the data-link layer. It defines useful packets that are
made of the bits that layer 1 defines. It defines
information necessary for getting a packet from one node to
another on the same network segment. (All devices that are
connected by the same physical wire or by only repeaters
are said to be in the same segment.) Ethernet, Token-Ring,
and PPP are some examples of layer-2 protocols.
layer 3 is the network layer. It defines additional information
for getting packets to nodes on other network segments.
IP, NetBEUI, and IPX are some examples of layer 3
protocols.
layer 4 is the transport layer. It provides flow-control and error
control for layer-3 protocols. It also defines ways to
identify separate flows of traffic between two hosts (for
example, port numbers) TCP and UDP are examples of layer 4
protocols.
layer 5 is the session layer. It adds more features to layer 4,
providing things like virtual full-duplex connectivity, and
prioritized flow control. This kind of functionality is
usually provided by internal operating system features.
Many layer-4 protocols (like TCP) include some layer-5
features as well.
layer 6 is the presentation layer. It formats all the data in ways
that make sense to the local operating system and its
applcations. The Berkeley sockets package and Microsoft's
WinSock libraries are presentation-layer protocols.
layer 7 is the application layer. SMTP (the e-mail protocol), NNTP
(the net-news protocol), and HTTP (the WWW protocol) are
examples of layer-7 protocols.
A layer-2 switch is one that uses layer-2 information to figure out what
to do with a packet. A layer-3 switch is one that uses layer-3
information to figure out what to do with it.
Layer-2 switches are often referred to as "bridges". They forward
packets between two network segments based on layer-2 information, which
is the 6-byte source and destination MAC addresses on Ethernet networks.
They are called bridges because the "bridge" between two layer-2
segments, combining them into a single layer-3 network.
Layer-2 switches can only work with the layer-2 protocols they're
designed for. Since the layer-2 protocol is usually tied closely to the
physical layer, this isn't usually a concern. (For instance, you're
never going to see Token Ring packets on an Ethernet network.)
layer-3 switches are often referred to as "routers". They forward
packets between two layer-2 network segments based on information in
each packet's layer-3 header. They will rewrite a packet's layer-2
information in doing so, because layer-2 information from one segment is
usually uselsss on another segment.
Layer-3 switches can only work with the layer-3 protocols they're
designed for. This is usually IP, but many networks will use other
protocols as well (like NetBEUI, IPX and AppleTalk). If the router
doesn't have software to deal with those (and other) protocols, it not
be able to forward those kinds of packets to other networks.
Layer-2 switches are relatively simple devices. They can learn the MAC
addresses of all attached nodes by snooping on every packet that they
receive. They, therefore, can operate without any configuration. Just
plug them in and go.
Sometimes, however, you may not want to use them in this way. You may
want the switch to give priority to packets coming from certain MAC
addreses, or to packets coming from or going to specific ports. Or
maybe you don't want to allow forwarding between certain groups of port.
A managed switch will give you the ability to configure stuff like this.
An unmanaged switch will have no such ability.
There are also managed repeaters (aka hubs), but they (obviously) are
incable of using the contents of any packets in deciding what to forward
where.
Layer-3 switches are almost always managed. In order to operate, a
layer-3 switch must know what networks are reachable through each port.
If a network is reachable through more than one port, it has to have
some idea of which ports are "better". (Maybe one port is less
congested, or maybe the packet will have to go through fewer routers to
get to the destination network.) This "routing table" information can
be manually provided by the switch's operator, but for large and
complicated networks, it is usually learned dynamically using a routing
protocol.
A routing protocol is a program running on a layer-3 switch. It keeps
the switch in communication with other switches on nearby networks.
Using routing protocols, the switch can be kept informed about the state
of distant networks and adjust its routing table appropriately. RIP,
OSPF, and BGP are examples of routing protocols.
------------------------------
From: "-=NFA=-" <[EMAIL PROTECTED]>
Subject: Getting both my NICs working
Date: Thu, 16 Sep 1999 22:36:11 GMT
I'm trying to get 2 NICs working in Redhat 6.0 (kernel 2.2.5-15)
Here some info on the cards:
1) D-Link DE220 ISA (PnP turn off) IO=0x300 IRQ=12
2) NetGear EA201c ISA (PnP turn off) IO=0x280 IRQ=9
On boot up it recognizes on of the cards but not the other. In 'linuxconf'
under basic host information when I set the 2 adapter's info and apply the
settings then go back in and look at it for some reason (i have no clue)
both adapters have the same IO and IRQ but the rest of the info is OK.
Any help would be appreciated because its driving me crazy ....
Thanks.
------------------------------
From: "Raterus" <[EMAIL PROTECTED]>
Subject: Re: kernel 2.2.11 & 3c509 NIC
Date: Thu, 16 Sep 1999 17:52:00 -0400
i'm not sure but you might have the same problem I did,
I had a 3c509b card which basically did what you said, didn't get the DHCP
ip. goto www.3com.com, and download the latest drivers for the card, then
run the dos program 3c5x9cfg or something and force the card out of PnP
mode.
hope this helps
Rat
Jon Michael Brown wrote in message <7ro9r0$p6d$[EMAIL PROTECTED]>...
>I recently tried to upgrade my kernel to 2.2.11 from 2.2.5 (Redhat 6.0).
On
>boot up, the computer no longer can detect the DHCP from my cablemodem, it
>justs hangs when initializing eth0 (a 3c509 NIC). Everything worked fine
>before I upgraded to 2.2.11. Does anyone know why this is happening?
>
>Thanks in advance.
>
>Jon
>
>
------------------------------
From: "Colvin" <[EMAIL PROTECTED]>
Subject: Re: Getting both my NICs working
Date: Thu, 16 Sep 1999 22:36:10 -0400
This is a quirk with linuxconf when outputing the options line in
/etc/conf.modules. To get around the quirk, set the io address to
0x300,0x280 and the irq to 12,9 for both adapters. This will get around the
quirk in linuxconf.
Regards
Bill Colvin
-=NFA=- wrote in message ...
>I'm trying to get 2 NICs working in Redhat 6.0 (kernel 2.2.5-15)
>
>Here some info on the cards:
>1) D-Link DE220 ISA (PnP turn off) IO=0x300 IRQ=12
>2) NetGear EA201c ISA (PnP turn off) IO=0x280 IRQ=9
>
>On boot up it recognizes on of the cards but not the other. In 'linuxconf'
>under basic host information when I set the 2 adapter's info and apply the
>settings then go back in and look at it for some reason (i have no clue)
>both adapters have the same IO and IRQ but the rest of the info is OK.
>
>Any help would be appreciated because its driving me crazy ....
>
>Thanks.
>
>
------------------------------
From: "Colvin" <[EMAIL PROTECTED]>
Subject: Re: Linux to net through Win
Date: Thu, 16 Sep 1999 22:44:31 -0400
You could try wingate ( http://wingate.net ). It will allow ip traffic to
pass through a win machine (Win 95/98/nt) and autodial your isp on demand.
I have used it with no problems (once you figure out how to configure the
services).
Or you could switch your configuration around and have the win machine go
through your linux box. For this you need ipchains and a few rules.
Regards
Bill Colvin
Chris wrote in message
<[EMAIL PROTECTED]>...
>Hi all
>
>I got 2 pcs one linux, one win. I use the win pc to connect to ISP, and
>would like the linux to pass through win onto the net.
>
>Do I need DNS services for Win? or win NT?
>
>At the moment, the linux pc can see the win, I can telnet on loopback on
>linux, and telnet from win to linux. I can ping etc... Cant ping outside
>address from linux though.
>
>I would appreciate some help on this.
>
>Thanks
>Christos
>
>
>
------------------------------
** 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
******************************
