Linux-Networking Digest #351, Volume #11         Mon, 31 May 99 16:13:44 EDT

Contents:
  IPCHAINS ("Ken")
  Great trouble with recent PCMCIA kit, how to fix it ? (Eric LEMAITRE)
  Need help with IP Masquerading and UDP packets (Luiz Otavio L. Zorzella)
  Re: What are drawbacks to using an ISA NIC? ("Steve Snyder")
  Simultaneous network/IDE traffic = reboot (Roland Olsson)
  Re: A question about collisions (Pat Crean)

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

From: "Ken" <[EMAIL PROTECTED]>
Subject: IPCHAINS
Date: Mon, 31 May 1999 07:10:14 -0800

I am running RedHat 6.0 and have ipchains working but I can not get ipchains
to allow NetMeeting inbound, outbound works fine.  Does anyone have a
successful set of rules for ipchains/NetMeeting?  I have been to several how
to's and have tried several configs but still no luck.
Please Help if you have the answer
Ken



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

From: Eric LEMAITRE <[EMAIL PROTECTED]>
Subject: Great trouble with recent PCMCIA kit, how to fix it ?
Date: Mon, 31 May 1999 20:31:04 +0200

Hi everybody !

I recently installed new Red-Hat 5.2 + 2.2.3 Kernel, and all worked perfectly,
untill I tried to install PCMCIA-3.0.9 or more package, which shows a nice
client (cardinfo) showing occupation of your PCMCIA ports : Either executables
only copy into /usr/bin PATH doesn't recognize a proper modules version, or the
whole package installation messes up the network scripts and all network is
fouled up.
So, is there a way to install this stuff safely (RPM or something) ?

Bye !


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

Subject: Need help with IP Masquerading and UDP packets
From: [EMAIL PROTECTED] (Luiz Otavio L. Zorzella)
Date: 31 May 1999 11:56:37 -0700


Hi,
                   
I have a Win 95 inside a private LAN (ppp) that I set up with ip
masquerading.
 
To start, I had only one very simple rule:
 
ipfwadm -F -a m -S 192.168.10.0/24 -D 0.0.0.0/0
 
Everything works fine: www, ftp, etc. Then I installed net2phone
(http://www.net2phone.com), and I'm trying to make it work.
 
While seting up, net2phone makes a "Test for firewall", and fails in
this test. I set up 2 specific rules for net2phone, then:
 
ipfwadm -F -a m -b -P udp -S 192.168.10.51 10000 -D 0.0.0.0/0 10000
ipfwadm -F -a m -b -P tcp -S 192.168.10.51 10000 -D 0.0.0.0/0 10000
ipfwadm -F -a m -b -P icmp -S 192.168.10.51 10000
 
and I configured net2phone to use the 10000 port number (it can be
configured to anything you want, according to their website). The
test still fails.
 
I tcpdumped both by eth0 (private LAN) and ppp0 (internet) while
doing the test, and I think the problem comes in this line from my
ppp0, though I don't know exactly what to do:
 
12:45:31.461066 169.132.184.211.46869 > w.x.y.z.6613: udp 55 (DF)
12:45:31.461066 w.x.y.z > 169.132.184.211: icmp: w.x.y.z udp port 6613 unreachable 
[tos 0xc0] 
 
Any help is appreciated. Please note that I made a "global replace"
of my firewall IP address by w.x.y.z in the dumps, and a replace of
my internal machine by internal.mydomain.com. Forgive my paranoia...
:^> 
 
Follows the traffic generated in the test, as seen by tcpdump in both
interfaces:
 
********
 
(eth0)
 
12:34:40.441066 0:0:86:16:ff:3 null > 0:20:18:38:18:54 sap 45 I (s=0,r=20,C) len=42 
8404 0000 1f11 100f ce84 d6d5 a984 b8d3 ef90 1a91 0014 1e01 5e68 656c 6c6f 5f71 2031 
200a 0000 0000 0000

12:34:40.441066 0:0:86:16:ff:3 null > 0:20:18:38:18:54 sap 45 I (s=0,r=20,C) len=42 
8504 0000 1f11 86dd ce84 d6d5 a984 4105 ef91 1a91 0014 95cd 5e68 656c 6c6f 5f71 2032 
200a 0000 0000 0000

12:34:40.751066 169.132.184.211.6801 > internal.mydomain.com.10000: udp 12 (DF)

12:34:40.751066 0:0:86:16:ff:3 null > 0:20:18:38:18:54 sap 45 I (s=0,r=91,P) len=178 
8604 0000 1f11 0d81 ce84 d6d5 a984 b8d3 ef90 1a91 00a2 861a 5e67 6574 6261 6c5f 6571 
2030 2030 2e30 2e30 2e30 2031 3030 3030

12:34:40.761066 ap2.labs.idt.net.6801 > internal.mydomain.com.10000: udp 12 (DF)

12:34:43.201066 0:0:86:16:5:6d > Broadcast sap e0 ui/C len=43 ffff 0022 0011 0000 0000 
ffff ffff ffff 0452 0000 0000 0000 8616 056d 4008 0001 0004 0000 0000 0000 0000 00
 
 
*********
 
(ppp0)
 
12:45:12.201066 w.x.y.z.61330 > 169.132.184.211.6801: udp 12

12:45:12.201066 w.x.y.z.61331 > ap2.labs.idt.net.6801: udp 12

12:45:12.571066 169.132.184.211.6801 > internal.mydomain.com.10000: udp 12 (DF)

12:45:12.571066 w.x.y.z.61330 > 169.132.184.211.6801: udp 154 12:45:12.581066 
ap2.labs.idt.net.6801 > internal.mydomain.com.10000: udp 12 (DF)

12:45:13.021066 169.132.184.211.62000 > w.x.y.z.10000: S 1448725872:1448725872(0) win 
8760 <mss 1460> (DF)

12:45:13.021066 w.x.y.z.10000 > 169.132.184.211.62000: R 0:0(0) ack 1448725873 win 0

12:45:13.341066 169.132.184.211.62003 > w.x.y.z.10000: S 1449001890:1449001890(0) win 
8760 <mss 1460> (DF)

12:45:13.341066 w.x.y.z.10000 > 169.132.184.211.62003: R 0:0(0) ack 1449001891 win 0

12:45:13.351066 169.132.184.211.62003 > w.x.y.z.10000: R 1449001891:1449001891(0) win 
8760 (DF)

12:45:16.391066 169.132.184.211.46869 > w.x.y.z.6613: udp 55 (DF)

12:45:16.391066 w.x.y.z > 169.132.184.211: icmp: w.x.y.z udp port 6613 unreachable 
[tos 0xc0]

12:45:21.371066 169.132.184.211.46869 > w.x.y.z.6613: udp 55 (DF)

12:45:21.371066 w.x.y.z > 169.132.184.211: icmp: w.x.y.z udp port 6613 unreachable 
[tos 0xc0]

12:45:26.351066 169.132.184.211.46869 > w.x.y.z.6613: udp 55 (DF)

12:45:26.351066 w.x.y.z > 169.132.184.211: icmp: w.x.y.z udp port 6613 unreachable 
[tos 0xc0]

12:45:31.461066 169.132.184.211.46869 > w.x.y.z.6613: udp 55 (DF)

12:45:31.461066 w.x.y.z > 169.132.184.211: icmp: w.x.y.z udp port 6613 unreachable 
[tos 0xc0] 

-- 
Luiz Otavio L. Zorzella                Computer Engineer
[EMAIL PROTECTED] 








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

Crossposted-To: comp.os.linux.hardware
From: "Steve Snyder" <[EMAIL PROTECTED]>
Reply-To: "Steve Snyder" <[EMAIL PROTECTED]>
Subject: Re: What are drawbacks to using an ISA NIC?
Date: Mon, 31 May 1999 15:40:46 GMT

1. I mis-wrote the expected top speed.  The cable modem moves a maximum of
3 megabits, not 3 megabytes, per second.  That should be well within the
capabilities of the ISA bus.  Sorry for the confusion.

2. That PCI slot is definitely defective.  Using a PCI NIC in that slot,
packets can be sent but not received.  I tried 2 different NICs in that
slot and examined all the IRQs in the system before deciding the slot was
bad.

Thanks for the response.


On Sun, 30 May 1999 21:47:58 -0700, Tim Moore wrote:

>ISA is clocked at 8.3MHz, PCI at 33MHz.  ISA has more CPU overhead too.
>
>This card is 10bT if I recall correctly, so it won't move more than
>about 850KB/s.  If you want 3MB/s you'll have to go 100bT which means
>PCI.
>
>Are you sure the slot is defective?  My PCI slots 4&5 share an IRQ which
>could cause weird behavior under some circumstances.  Other boards that
>have built-in SCSI, sound, etc are known to share IRQ's with particular
>PCI slots.
>
>Steve Snyder wrote:
>> 
>> I discovered (by trying to use it) that the last unused PCI slot in my
>> system is defective.  This forced me to add an ISA NIC (a 3Com 3C509B)
>> instead of the PCI device I had planned on.
>> 
>> The ISA NIC is working well.  I wonder, though, what the drawbacks are
>> compared to a PCI NIC.  This device is just attached to a cable modem,
>> which suggests that it will never be called upon to move more than
>> 3MB/second anyway.
>> 
>> Is interrupt latency higher with an ISA NIC?  Increased CPU use?  The
>> initial install involves more work because you have to specify the IRQ and
>> I/O port address range.  Now that the installation is done, though, I'm
>> interested in runtime gotchas.
>> 
>> Thank you.
>> 
>> ***** Steve Snyder *****
>
>-- 
>direct replies substitute timothymoore for user name
>
>"Everything is permitted.  Nothing is forbidden."
>                                   WS Burroughs.


***** Steve Snyder *****




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

Date: Mon, 31 May 1999 21:12:25 +0200
From: Roland Olsson <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.hardware
Subject: Simultaneous network/IDE traffic = reboot

This is a multi-part message in MIME format.
==============0B567FA2BC1A6CBE88523E35
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi,

I have stumbled upon a _big_ problem with my machine. It makes a silent
and instantaneous soft reboot when performing (pretty tough) disk and
network access at the same time. I noticed this when trying to transfer
some 10+ Mb files from this machine as the screen just turned black and
the BIOS "welcome" screen appeared. No kernel oops or other message,
just a plain reboot. I can't find anything in the logs either. *sigh*

If I am using the machine "normally" everything works just fine. That is
no fiddling with large files or performing any extreme network activity.

I have found a very simple way of reproducing the crash. Just do a 'ping
-f' to the machine for a second or so and run 'hdparm -t /dev/hda' at
the same time. It reboots almost immediately. One more thing, if I do
'ping -f' locally no matter to what address/if, I can't make it crash.
But from another machine - reboot.

I have checked everything I can think of, i.e. conflicting IRQ:s, DMA
etc. I have tried to reassign almost everything in the BIOS but to no
avail. Also tested the 2.2.9 kernel but same thing there. I do not know
what to do next, does anyone of you have an idea?

Some facts about the machine:
  Intel Celeron 333
  128Mb DIMM
  Motherboard Abit BH6 (Award BIOS rev 4.51PG)
  2pcs NIC 3Com 3C905B-TX
  Seagate Medalist ST38420A IDE 8,6Gb
  Redhat 6.0 (kernel build 2.2.5-15)

Attached are some files from /proc that may or may not help you to help
me.

Regards,
/Roland
==============0B567FA2BC1A6CBE88523E35
Content-Type: text/plain; charset=us-ascii;
 name="boot-allinfo"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename="boot-allinfo"

::::::::::::::
cpuinfo
::::::::::::::
processor       : 0
vendor_id       : GenuineIntel
cpu family      : 6
model           : 6
model name      : Celeron (Mendocino)
stepping        : 0
cpu MHz         : 334.098612
cache size      : 128 KB
fdiv_bug        : no
hlt_bug         : no
sep_bug         : no
f00f_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 2
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca cmov pat pse36 
mmx osfxsr
bogomips        : 333.41

::::::::::::::
devices
::::::::::::::
Character devices:
  1 mem
  2 pty
  3 ttyp
  4 ttyS
  5 cua
  7 vcs
 10 misc
 29 fb
 36 netlink
128 ptm
136 pts

Block devices:
  1 ramdisk
  3 ide0
  9 md
::::::::::::::
dma
::::::::::::::
 4: cascade
::::::::::::::
dmesg
::::::::::::::
Linux version 2.2.5-15 ([EMAIL PROTECTED]) (gcc version egcs-2.91.66 
19990314/Linux (egcs-1.1.2 release)) #1 Mon Apr 19 23:00:46 EDT 1999
Detected 334098612 Hz processor.
Console: colour dummy device 80x25
Calibrating delay loop... 333.41 BogoMIPS
Memory: 63140k/65536k available (996k kernel code, 412k reserved, 928k data, 60k init)
VFS: Diskquotas version dquot_6.4.0 initialized
CPU: Intel Celeron (Mendocino) stepping 00
Checking 386/387 coupling... OK, FPU using exception 16 error reporting.
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
mtrr: v1.26 (19981001) Richard Gooch ([EMAIL PROTECTED])
PCI: PCI BIOS revision 2.10 entry at 0xfb460
PCI: Using configuration type 1
PCI: Probing PCI hardware
Linux NET4.0 for Linux 2.2
Based upon Swansea University Computer Society NET3.039
NET4: Unix domain sockets 1.0 for Linux NET4.0.
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
Initializing RT netlink socket
Starting kswapd v 1.5 
vesafb: framebuffer at 0xe6000000, mapped to 0xc4800000, size 4096k
vesafb: mode is 1024x768x32, linelength=4096, pages=0
vesafb: protected mode interface info at c000:7ee0
vesafb: scrolling: redraw
vesafb: directcolor: size=8:8:8:8, shift=24:16:8:0
Console: switching to colour frame buffer device 128x48
fb0: VESA VGA frame buffer device
Detected PS/2 Mouse Port.
Serial driver version 4.27 with MANY_PORTS MULTIPORT SHARE_IRQ enabled
ttyS00 at 0x03f8 (irq = 4) is a 16550A
pty: 256 Unix98 ptys configured
apm: BIOS version 1.2 Flags 0x07 (Driver version 1.9)
Real Time Clock Driver v1.09
RAM disk driver initialized:  16 RAM disks of 4096K size
PIIX4: IDE controller on PCI bus 00 dev 39
PIIX4: not 100% native mode: will probe irqs later
    ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:DMA, hdb:DMA
    ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:DMA, hdd:DMA
hda: ST38420A, ATA DISK drive
hdb: Pioneer CD-ROM ATAPI Model DR-A12X 0100, ATAPI CDROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hda: ST38420A, 8223MB w/512kB Cache, CHS=1048/255/63
hdb: ATAPI 12X CD-ROM drive, 128kB Cache
Uniform CDROM driver Revision: 2.54
floppy0: no floppy controllers found
md driver 0.90.0 MAX_MD_DEVS=256, MAX_REAL=12
raid5: measuring checksumming speed
raid5: using high-speed MMX checksum routine
   pII_mmx   :   813.054 MB/sec
   p5_mmx    :   787.908 MB/sec
   8regs     :   576.072 MB/sec
   32regs    :   413.766 MB/sec
using fastest function: pII_mmx (813.054 MB/sec)
scsi : 0 hosts.
scsi : detected total.
md.c: sizeof(mdp_super_t) = 4096
Partition check:
 hda: hda1 hda2 < hda5 hda6 hda7 hda8 hda9 >
autodetecting RAID arrays
autorun ...
... autorun DONE.
VFS: Mounted root (ext2 filesystem) readonly.
Freeing unused kernel memory: 60k freed
Adding Swap: 72256k swap-space (priority -1)
3c59x.c:v0.99H 11/17/98 Donald Becker 
http://cesdis.gsfc.nasa.gov/linux/drivers/vortex.html
eth0: 3Com 3c905B Cyclone 100baseTx at 0xe400,  00:50:04:35:47:48, IRQ 10
  Internal config register is 1800000, transceivers 0xa.
  8K byte-wide RAM 5:3 Rx:Tx split, autoselect/Autonegotiate interface.
  MII transceiver found at address 24, status 786d.
  MII transceiver found at address 0, status 786d.
  Enabling bus-master transmits and whole-frame receives.
eth1: 3Com 3c905B Cyclone 100baseTx at 0xe800,  00:50:04:35:44:e8, IRQ 11
  Internal config register is 1800000, transceivers 0xa.
  8K byte-wide RAM 5:3 Rx:Tx split, autoselect/Autonegotiate interface.
  MII transceiver found at address 24, status 786d.
  MII transceiver found at address 0, status 786d.
  Enabling bus-master transmits and whole-frame receives.
eth0: Initial media type Autonegotiate.
eth0: MII #24 status 786d, link partner capability 0020, setting half-duplex.
eth0: vortex_open() InternalConfig 01800000.
eth0: vortex_open() irq 10 media status 8080.
eth1: Initial media type Autonegotiate.
eth1: MII #24 status 786d, link partner capability 41e1, setting full-duplex.
eth1: vortex_open() InternalConfig 01800000.
eth1: vortex_open() irq 11 media status 8080.
eth0: Media selection timer tick happened, Autonegotiate.
eth0: MII transceiver has status 7869.
eth1: Media selection timer tick happened, Autonegotiate.
eth1: MII transceiver has status 7869.
Installing knfsd (copyright (C) 1996 [EMAIL PROTECTED]).
nfsd_init: initialized fhcache, entries=256
CSLIP: code copyright 1989 Regents of the University of California
SLIP: version 0.8.4-NET3.019-NEWTTY-MODULAR (dynamic channels, max=256) (6 bit 
encapsulation enabled).
SLIP linefill/keepalive option.
cat uses obsolete /proc/pci interface
::::::::::::::
interrupts
::::::::::::::
           CPU0       
  0:      87868          XT-PIC  timer
  1:        933          XT-PIC  keyboard
  2:          0          XT-PIC  cascade
  8:          2          XT-PIC  rtc
 10:       1598          XT-PIC  eth0
 11:        441          XT-PIC  eth1
 13:          1          XT-PIC  fpu
 14:     654584          XT-PIC  ide0
NMI:          0
::::::::::::::
ioports
::::::::::::::
0000-001f : dma1
0020-003f : pic1
0040-005f : timer
0060-006f : keyboard
0070-007f : rtc
0080-008f : dma page reg
00a0-00bf : pic2
00c0-00df : dma2
00f0-00ff : fpu
01f0-01f7 : ide0
03c0-03df : vga+
03f6-03f6 : ide0
03f8-03ff : serial(auto)
e400-e47f : eth0
e800-e87f : eth1
f000-f007 : ide0
f008-f00f : ide1
::::::::::::::
modules
::::::::::::::
slip                    7636   2 (autoclean)
slhc                    4392   1 (autoclean) [slip]
nfsd                  151576   8 (autoclean)
lockd                  31208   1 (autoclean) [nfsd]
sunrpc                 52420   1 (autoclean) [nfsd lockd]
3c59x                  18472   2 (autoclean)
::::::::::::::
pci
::::::::::::::
PCI devices found:
  Bus  0, device   0, function  0:
    Host bridge: Intel 440BX - 82443BX Host (rev 2).
      Medium devsel.  Master Capable.  Latency=64.  
      Prefetchable 32 bit memory at 0xe0000000 [0xe0000008].
  Bus  0, device   1, function  0:
    PCI bridge: Intel 440BX - 82443BX AGP (rev 2).
      Medium devsel.  Master Capable.  Latency=64.  Min Gnt=128.
  Bus  0, device   7, function  0:
    ISA bridge: Intel 82371AB PIIX4 ISA (rev 2).
      Medium devsel.  Fast back-to-back capable.  Master Capable.  No bursts.  
  Bus  0, device   7, function  1:
    IDE interface: Intel 82371AB PIIX4 IDE (rev 1).
      Medium devsel.  Fast back-to-back capable.  Master Capable.  Latency=64.  
      I/O at 0xf000 [0xf001].
  Bus  0, device   7, function  2:
    USB Controller: Intel 82371AB PIIX4 USB (rev 1).
      Medium devsel.  Fast back-to-back capable.  Master Capable.  Latency=64.  
      I/O at 0xe000 [0xe001].
  Bus  0, device   7, function  3:
    Bridge: Intel 82371AB PIIX4 ACPI (rev 2).
      Medium devsel.  Fast back-to-back capable.  
  Bus  0, device  13, function  0:
    Ethernet controller: 3Com 3C905B 100bTX (rev 48).
      Medium devsel.  IRQ 10.  Master Capable.  Latency=64.  Min Gnt=10.Max Lat=10.
      I/O at 0xe400 [0xe401].
      Non-prefetchable 32 bit memory at 0xea001000 [0xea001000].
  Bus  0, device  15, function  0:
    Ethernet controller: 3Com 3C905B 100bTX (rev 48).
      Medium devsel.  IRQ 11.  Master Capable.  Latency=64.  Min Gnt=10.Max Lat=10.
      I/O at 0xe800 [0xe801].
      Non-prefetchable 32 bit memory at 0xea000000 [0xea000000].
  Bus  0, device  17, function  0:
    VGA compatible controller: Matrox Mystique (rev 3).
      Medium devsel.  Fast back-to-back capable.  Master Capable.  Latency=64.  
      Prefetchable 32 bit memory at 0xe6000000 [0xe6000008].
      Non-prefetchable 32 bit memory at 0xe7000000 [0xe7000000].
      Non-prefetchable 32 bit memory at 0xe8000000 [0xe8000000].


==============0B567FA2BC1A6CBE88523E35==


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

From: Pat Crean <[EMAIL PROTECTED]>
Subject: Re: A question about collisions
Date: Mon, 31 May 1999 15:07:58 -0400

Don't worry about it --- collisions are a part of the design of ethernet ---
there was an interesting analysis a year of so ago in Sys Admin magazine that
showed that there would be almost no effect on throughput of the network, even
with over 100% collisions.  You're only seeing about 1%.

Pat

On Mon, 31 May 1999, Chris Jackson wrote:
>ok, I have been living with this problem up till now thinking there
>was something wrong with my setup or maybe my connection to the
>internet wasn't so hot, but this is the problem I have....
>
>eth0      Link encap:Ethernet  HWaddr 00:10:5A:15:35:C8  
>          inet addr:24.3.254.64  Bcast:24.3.254.255      
>          Mask:255.255.255.0
>          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>          RX packets:1174178 errors:0 dropped:0 overruns:0 frame:0
>          TX packets:625644 errors:0 dropped:0 overruns:0 carrier:0
>          collisions:6823 txqueuelen:100 
>          Interrupt:11 Base address:0x6100 
>
>eth1      Link encap:Ethernet  HWaddr 00:20:78:15:67:20  
>          inet addr:192.168.1.1  Bcast:192.168.1.255  
>          Mask:255.255.255.0
>          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>          RX packets:629369 errors:0 dropped:0 overruns:0 frame:0
>          TX packets:1063614 errors:0 dropped:0 overruns:0 carrier:0
>          collisions:3232 txqueuelen:100 
>          Interrupt:9 Base address:0x6200 
>
>my eth0 has an extremely large amount of collisions on it, or is this
>normal?
>I am running RedHat 6.0 and this is the network cards lines from dmesg
>
>3c59x.c:v0.99Kb 5/7/99 Donald Becker
>http://cesdis.gsfc.nasa.gov/linux/drivers/vortex.html
>eth0: 3Com 3c905B Cyclone 100baseTx at 0x6100,  00:10:5a:15:35:c8,
> IRQ 11 8K byte-wide RAM 5:3 Rx:Tx split, autoselect/Autonegotiate
>interface.
>  MII transceiver found at address 24, status 786d.
>  MII transceiver found at address 0, status 786d.
>  Enabling bus-master transmits and whole-frame receives.
>ne2k-pci.c:v0.99L 2/7/98 D. Becker/P. Gortmaker
>http://cesdis.gsfc.nasa.gov/linux/drivers/ne2k-pci.html
>ne2k-pci.c: PCI NE2000 clone 'Winbond 89C940' at I/O 0x6200, IRQ 9.
>eth1: PCI NE2000 found at 0x6200, IRQ 9, 00:20:78:15:67:20.
>
>any help with this would be greatly appreciated thanks

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


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