* lk maintainers
From: Denis Vlasenko @ 2003-01-09 8:54 UTC (permalink / raw)
To: linux-kernel
This document is mailed to lkml regularly and will be modified
whenever new victim wishes to be listed in it or someone can
no longer devote his time to maintainer work.
If you want your entry added/updated/removed, contact me.
BTW, requests to move your entry to the top of the list
without actually changing the text are fine too: that
will indicate that entry is not outdated, so don't be shy ;-)
--
vda
------- cut here ------ cut here ------ cut here ------ cut here ------
So, you are new to Linux kernel hacking and want to submit a kernel bug
report or a patch but don't know how to do it and _where_ to report it?
Preparing bug report:
=====================
*** Remember: bad/incomplete bug report ONLY wastes bandwidth! ***
How To Ask Questions The Smart Way:
http://www.tuxedo.org/~esr/faqs/smart-questions.html
Anybody who has written software for public use will
probably have received at least one bad bug report.
Reports that say nothing ("It doesn't work!");
reports that make no sense; reports that don't give
enough information; reports that give wrong information.
How to Report Bugs Effectively:
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html
Before asking a technical question by email, or in
a newsgroup, or on a website chat board, do the following:
* Try to find an answer by searching the Web.
* Try to find an answer by reading the manual.
* Try to find an answer by reading a FAQ.
* Try to find an answer by inspection or experimentation.
* Try to find an answer by reading the source code.
Compile problems: report GCC output and result of
"grep '^CONFIG_' .config"
Oops: decode it with ksymoops (or use 2.5 with kksymoops enabled ;).
Unkillable process: Alt-SysRq-T and ksymoops relevant part.
Yes it means you should have ksymoops installed and tested,
which is easy to get wrong. I've done that too often.
Sending bug report/patch:
=========================
* Some device drivers have active developers, try to contact them first.
* Otherwise find a subsystem maintainer to which your report pertains
and send report to his address.
* Small fixes and device driver updates are best directed to subsystem
maintainers and "small bits" integrators.
* It never hurts to CC: Linux kernel mailing list, but without specific
maintainer address in To: field there is high probability that your
patch won't be noticed. You have been warned.
* Do not send it to all addresses at once! This will annoy lots of
people
and isn't useful at all. It's a spam.
* Do NOT send small fixes to Linus, he just can't handle _everything_.
He will eventually receive it from maintainers/integrators, send it
their way.
* If your patch is something big and new, announce it on lkml and try
to attract testers. After it has been tested and discussed, you can
expect Linus to consider inclusion in mainline.
Current Linux kernel people
Note that this list is sorted in reversed date order, most recent
entries first. This means than entries at bottom can be outdated :-(
Linux kernel mailing list <linux-kernel@vger.kernel.org>
Post anything related to Linux kernel here, but nothing else :-)
John Bradford <john@grabjohn.com> [25 dec 2002]
I'm happy to help people who are trying to get run Linux usefully on
old and/or low spec machines, (4 MB 486s, etc).
Adam Belay <ambx1@neo.rr.com> [17 dec 2002]
I am Plug and Play maintainer.
Andrew Morton <akpm@digeo.com> [10 dec 2002]
- VM
- The "data" part of the VFS: pagecache, buffer layer, etc.
- memory management
- ext2 and ext3
- 3c59x.c
- direct-IO
James Simmons <jsimmons@infradead.org> [28 Nov 2002]
Console and framebuffer subsystems.
I also play around with the input layer.
Petko Manolov <petkan@users.sourceforge.net> [27 nov 2002]
pegasus and rtl8150 usb-ethernet drivers maintainer.
Interested in any bugs or new devices related to those drivers.
string-486.h code maintainer.
Greg Ungerer <gerg@snapgear.com> [14 nov 2002]
uClinux (MMU-less support) maintainer. I'll take antyhing
specifically related to MMU-less support or any of the
MMU-less architecture branches (m68knommu, v850, etc).
I would highly recommend sending to uclinux-dev@uclinux.org
mailing list as well.
Andre Hedrick <andre@linux-ide.org> [02 oct 2002]
ATA/ATAPI Storage Architect [2.0,2.2,2.4,2.5]
HBA interface developer
Serial ATA Architect [future release]
Voting NCITS member AT-Attachment Committee
Jeff Garzik <jgarzik@mandrakesoft.com> [24 sep 2002]
I am the network-card-drivers guy (8139 for instance).
CC me and Andrew Morton <akpm@digeo.com> on network driver patches.
Jan-Benedict Glaw <jbglaw@lug-owl.de> [18 sep 2002]
I'm responsible for Alpha's srm_env driver, providing access to
SRM's firmware variables.
Stuart MacDonald <stuartm@connecttech.com> [13 sep 2002]
Connect Tech's linux kernel guy. Currently includes hacking on
drivers/char/serial.c (Blue Heat, Xtreme, Dflex) and maintaining
drivers/usb/serial/whiteheat.c (WhiteHEAT)
Vojtech Pavlik <vojtech@ucw.cz> [13 sep 2002]
Feel free to send me bug reports and patches to input device drivers
(drivers/input/*, drivers/char/joystick/*)
I also want to receive bug reports and patches for following
USB drivers: printer, acm, catc, hid*, usbmouse, usbkbd, wacom.
All other (not in the list) USB driver changes should go to USB
maintainer (hopefully there is one listed here :-).
Also CC me if you are posting VIA IDE driver related message
(although I am not IDE subsystem maintainer).
Robert Love <rml@tech9.net> [12 sep 2002]
Preemptible kernel maintainer.
I am also interesting in anything related to scheduling or locking
primitives.
Jan Kara <jack@suse.cz> [22 aug 2002]
quota subsystem maintainer
Paul Larson <plars@linuxtestproject.org> [20 aug 2002]
I'm a maintainer for the Linux Test Project and it would be nice
if people knew to send their test programs, etc. to me. I see
a lot of them flying around on lkml and try to catch them when
I can, but it's a lot to keep up with. It would be even better
if people just knew to send them our way so we could clean
them up and put them in LTP for regression testing.
Dave Engebretsen <engebret@vnet.ibm.com> [15 aug 2002]
PPC64 architecture maintainer. Please send PPC64 patches to me
and our mailing list at <linuxppc64-dev@lists.linuxppc.org>
Ingo Molnar <mingo@elte.hu> [30 jul 2002]
Ingo wrote the new scheduler for 2.5.
Ralf Baechle <ralf@uni-koblenz.de> [30 jul 2002]
I am maintainer of the AX.25 code
Victor Yodaiken <yodaiken@fsmlabs.com> [30 jul 2002]
RTLinux patches, updates, contributions, drivers.
Please send first to the list: rtl@rtlinux.org
Pavel Machek <pavel@ucw.cz> [27 jul 2002]
I am network block device maintainer. Visit http://nbd.sf.net.
(see Steven Whitehouse <steve@gw.chygwyn.com> entry)
I am working on software suspend.
William Irwin <wli@holomorphy.com> [02 jul 2002]
Send bug reports and/or feature requests related to many tasks,
rmap, space consumption, or allocators to me. I'm involved in
* rmap
* memory allocators
* reducing space consumed by data structures (e.g. struct page)
* issues arising in workloads with many tasks
* kernel janitoring
See also:
Rik van Riel <riel@surriel.com>
Andrea Arcangeli <andrea@suse.de>
Martin Bligh <Martin.Bligh@us.ibm.com>
Andrew Morton <akpm@digeo.com>
Dave Jones <davej@suse.de> [23 apr 2002]
I collect various bits and pieces for inclusion in 2.5,
especially small and trivial ones and driver updates.
I'll feed them to Linus when (and if) they
are proved to be worthy.
Andrea Arcangeli <andrea@suse.de> [28 mar 2002]
Send VM related bug reports and patches to me.
I'm especially interested in VM issues with:
* lots of RAM and CPUs
* NUMA
* heavy swap scenarios
* performance of I/O intensive workloads (in particular
with lots of async buffer flushing involved)
See also Martin J. Bligh <Martin.Bligh@us.ibm.com> entry
Mail also:
Arjan van de Ven <arjanv@redhat.com>
Martin J. Bligh <Martin.Bligh@us.ibm.com> [28 mar 2002]
I'm interested in VM issues with lots (>4G for i386)
of RAM, lots of CPUs, NUMA
Steven Whitehouse <steve@chygwyn.com> [27 mar 2002]
I am the Linux DECnet network stack maintainer
Visit http://www.chygwyn.com/decnet/
Arnaldo Carvalho de Melo <acme@conectiva.com.br> [26 mar 2002]
IPX, 802.2 LLC, NetBEUI, http://kerneljanitors.org,
cyclom2x sync card driver
John Cagle <jcagle@kernel.org> [19 mar 2002]
The current maintainer of devices.txt, the list of
assigned device numbers for LANANA. Consult the web
site (www.lanana.org) for instructions on submitting
requests for new device numbers. Send all device
related email to <device@lanana.org>.
Tigran Aivazian <tigran@veritas.com>
I am author and maintainer of BFS filesystem and IA32
microcode update driver.
Rogier Wolff <R.E.Wolff@BitWizard.nl> [12 mar 2002]
I do "specialix serial ports":
drivers/char/specialix.c (IO8+)
drivers/char/sx.c (SX, SI, SIO)
drivers/char/rio/*.c (RIO)
Martin Dalecki <martin@dalecki.de> [11 mar 2002]
IDE subsystem maintainer for 2.5
(mail Vojtech Pavlik <vojtech@suse.cz> too)
Ed Vance <serial24@macrolink.com> [05 mar 2002]
Maintainer for the generic serial driver, serial.c,
for 2.2 and 2.4 kernels. Please post patches to
linux-serial@vger.kernel.org for tested bug
fixes or to add support for a new serial device.
Limited to time available. If I have not responded
in a week, yell at serial24@macrolink.com
netfilter/iptables <netfilter-devel@lists.samba.org> [23 feb 2002]
Please report all netfilter/iptables related problems
to this mailinglist, where all netfilter developers are present.
See also http://www.netfilter.org/contact.html
Hans Reiser <reiser@namesys.com> [16 feb 2002]
Send me all reiserfs related patches with a cc to
reiserfs-dev@namesys.com, send bug reports to
reiserfs-dev@namesys.com, send paid support requests to
support@namesys.com after going to www.namesys.com/support.html
to pay, send discussions (not bug reports unless they are
interesting to most persons) to reiserfs-list@namesys.com.
If we sit on your patch for a week without responding,
yell at us, we deserve it. Look at our web page
at www.namesys.com for more about sending us code,
working with us, and our patch submission and tracking system.
Paul Bristow <paul@paulbristow.net> [16 feb 2002]
I am an ide-floppy driver maintainer
(ATAPI ZIP, LS-120/240 Superdisk, Clik! drives).
Mike Phillips <phillim2@comcast.net> [15 feb 2002]
Token ring subsystem and drivers.
Anton Altaparmakov <aia21@cam.ac.uk> [15 feb 2002]
I am the NTFS guy.
https://bugzilla.redhat.com/bugzilla [14 feb 2002]
Reports of problems with the Red Hat shipped kernels.
Alan Cox <alan@lxorguk.ukuu.org.uk> [14 feb 2002]
Linux 2.2 maintainer (maintenance fixes only).
Collator of patches for unmaintained things in 2.2/2.4.
Maintainer of the 2.4-ac (2.4 plus stuff being tested) tree.
I2O, sound, 3c501 maintainer for 2.2/2.4.
ALSA development <alsa-devel@alsa-project.org> [12 feb 2002]
Jaroslav Kysela <perex@perex.cz> [12 feb 2002]
Advanced Linux Sound Architecture
ALSA patches are available at
ftp://ftp.alsa-project.org/pub/kernel-patches/*
Neil Brown <neilb@cse.unsw.edu.au> [08 feb 2002]
I am interested in any issues with the code in:
NFS server (fs/nfsd/*)
software RAID (drivers/md/{md,raid,linear}*)
or related include files.
Maksim Krasnyanskiy <maxk@qualcomm.com> [08 feb 2002]
I'm author and maintainer of the Bluetooth subsystem
and Universal TUN/TAP device driver.
These days mostly working on Bluetooth stuff.
Rik van Riel <riel@conectiva.com.br> [07 feb 2002]
Send me VM related stuff, please CC to linux-mm@kvack.org
Geert Uytterhoeven <geert@linux-m68k.org> [07 feb 2002]
I work on the frame buffer subsystem, the m68k port (Amiga part),
and the PPC port (CHRP LongTrail part).
Unfortunately I barely have spare time to really work on these
things. My job is not Linux-related (so far :-). I can not
promise anything about my maintainership performance.
H. Peter Anvin <hpa@zytor.com> [07 feb 2002]
i386 boot and feature code, i386 boot protocol, autofs3,
compressed iso9660 (but I'll accept all iso9660-related
changes). kernel.org site manager; please contact me
for sponsorship-related issues.
kernel.org admins <ftpadmin@kernel.org> [07 feb 2002]
Kernel.org sysadmins. Contact us if you notice something breaks,
or if you want a change make sure you give us at least 1-2 weeks.
Please note that we got a lot of feature requests, a lot of
which conflict or simply aren't practical; we don't have time to
respond to all requests.
Greg KH <greg@kroah.com> [07 feb 2002]
I am USB and PCI Hotplug maintainer.
Trond Myklebust <trond.myklebust@fys.uio.no> [07 feb 2002]
I am NFS client maintainer.
Richard Gooch <rgooch@atnf.csiro.au> [07 feb 2002]
I maintain devfs. I want people to Cc: me when reporting devfs
problems, since I don't read all messages on linux-kernel.
Send devfs related patches to me directly, rather than
bypassing me and sending to Linus/Marcelo/Alan/Dave etc.
Russell King <rmk@arm.linux.org.uk> [06 feb 2002]
ARM architecture maintainer. Please send all ARM patches through
the patch system at http://www.arm.linux.org.uk/developer/patches/
New serial drivers maintainer for 2.5. Submit patches to
rmk+serial@arm.linux.org.uk
Petr Vandrovec <vandrove@vc.cvut.cz> [05 feb 2002]
ncpfs filesystem, matrox framebuffer driver, problems related
to VMware - in all of 2.2.x, 2.4.x and 2.5.x.
Reiserfs developers list <reiserfs-dev@namesys.com> [05 feb 2002]
Send all reiserfs-related stuff here including but not limited to bug
reports, fixes, suggestions.
Oleg Drokin <green@linuxhacker.ru> [05 feb 2002]
SA11x0 USB-ethernet and SA11x0 watchdog are mine.
======= These entries are suggested by lkml folks ========
Ralf Baechle <ralf@gnu.org> [27 mar 2002]
I am mips/mips64 maintainer.
David S. Miller <davem@redhat.com> [07 feb 2002]
I am Sparc64 and networking core maintainer.
======= These ones I made myself ========
======= I am waiting confirmation/correction from these people ========
Urban Widmark <urban@teststation.com> [13 feb 2002]
smbfs
video4linux list <video4linux-list@redhat.com> [12 feb 2002]
Gerd Knorr <kraxel@bytesex.org> [12 feb 2002]
video4linux
Tim Waugh <twaugh@redhat.com> [08 feb 2002]
> Who is maintaining the linux iomega stuff?
For 2.4.x, me (in theory). I don't have time for 2.5.x at the moment.
Alexander Viro <viro@math.psu.edu> [5 feb 2002]
I am NOT a fs subsystem maintainer. But I won't kill
you if you send me some generic fs bug reports and (hopefully) patches.
Eric S. Raymond <esr@thyrsus.com> [5 feb 2002]
Send kernel configuration bug reports and suggestions to me.
Also I'll be more than happy to accept help enties for kernel config
options (Configure.help).
GИrard Roudier <groudier@free.fr> [5 feb 2002]
I am SCSI guy.
Jens Axboe <axboe@suse.de> [5 feb 2002]
I am block device subsystem maintainer.
Linus Torvalds <torvalds@transmeta.com> [5 feb 2002]
Do not send anything to me unless it is for 2.5, well tested,
discussed on lkml and is used by significant number of people.
In general it is a bad idea to send me small fixes and driver
updates, send them to subsystem maintainers and/or
"small stuff" integrator (currently Dave Jones <davej@suse.de>,
see his entry). Sorry, I can't do everything.
Marcelo Tosatti <marcelo@conectiva.com.br> [5 feb 2002]
Do not send anything to me unless it is for 2.4 and well tested.
If you are sending me small fixes and driver updates, send
a copy to subsystem maintainers and/or "small stuff" integrators:
- Alan Cox <alan@lxorguk.ukuu.org.uk>,
- Rusty Russell <trivial@rustcorp.com.au>.
Rusty Russell <rusty@rustcorp.com.au> [5 feb 2002]
> Here are some cleanups of whitespace in .....
Want me to add this to the trivial patch collection for tracking?
If so just send (or cc:) it to trivial@rustcorp.com.au.
^ permalink raw reply
* Re: How to route "spdif" to an FXBUS of emu10k1
From: Gerard Janssen @ 2003-01-09 8:24 UTC (permalink / raw)
To: Jaroslav Kysela; +Cc: alsa-devel@alsa-project.org
In-Reply-To: <Pine.LNX.4.33.0301081618500.2215-100000@pnote.perex-int.cz >
Hi Jaroslav,
Many thanks for your reply. This realy solved my problem.
I have been able to implement a new PCM-stream and send it to empty FXBUS
registers. However, I could not find .asoundcr (I am using SUSE 8.1 with
ALSA_rc6). Where is it? In stead, I adapted alsa.conf, emu10k1.conf and
added a pcm_new.conf in /usr/share/alsa/ and this worked.
After having done this, I am stuck with some questions. Why are there no
"Send Routing" lines in the "front" and "rear" config files, since they are
routed to FXBUS?
Why do the lines:
> /* 22: */ OP(icode, &ptr, iMACINT1, ETRAM_ADDR(ipcm->etram[0]),
GPR(gpr + 8), GPR_DBAC, C_ffffffff);
> /* 23: */ OP(icode, &ptr, iMACINT1, ETRAM_ADDR(ipcm->etram[1]),
GPR(gpr + 9), GPR_DBAC, C_ffffffff);
have to be removed?
With kind regards,
Gerard Janssen
At 04:30 PM 1/8/03 +0100, Jaroslav Kysela wrote:
>On Wed, 8 Jan 2003, Gerard Janssen wrote:
>
>> Hi,
>>
>> By making slight changes in emufx.c, I could use all four spdif stereo
>> channels of the sblive! that are present on the audio-ext connector. These
>> spdif0..3 outputs can be accessed via: EXTOUT_TOSLINK_L,R ;
>> EXTOUT_HEADPHONE_L,R ; EXTOUT_REAR_L,R and EXTOUT_CENTER,LFE. By re-routing
>> "spdif", "front", "rear" and "center_lfe" to the respective outputs, four
>> stereo signals (8 channels) can be simultaneously send to these outputs.
>>
>> The "front", "rear" and "center_lfe" signals are alsmost perfectly
>> synchronized (within a few samples) and the small delays are constant.
>> However, the signal via "spdif" is not: its delay w.r.t. the other signals
>> is about 60 samples and changes randomly every time the application is
>> started.
>> The "spdif" signal is taken from GPR(8) and GPR(9) in emufx.c. As far as I
>> could backtrace these signals come from etram, which probably is the cause
>> of the random delay.
>>
>> A solution might be to put the "spdif" also directly in two FXBUS registers
>> (there are still 6 free FXBUS registers), as is done with the other
>> signals. However, I don't know how to do this.
>>
>> I would appreciate any help or suggestions in routing "spdif" to an FXBUS.
>
>These steps are necessary:
>
>1) remove the emufx PCM code (or the last two lines):
>
> /* 22: */ OP(icode, &ptr, iMACINT1, ETRAM_ADDR(ipcm->etram[0]),
GPR(gpr + 8), GPR_DBAC, C_ffffffff);
> /* 23: */ OP(icode, &ptr, iMACINT1, ETRAM_ADDR(ipcm->etram[1]),
GPR(gpr + 9), GPR_DBAC, C_ffffffff);
>
> you can do it without modification of driver code itself (see
> SNDRV_EMU10K1_IOCTL_CODE_POKE and SNDRV_EMU10K1_IOCTL_CODE_PEEK ioctls)
>
>2) replace these two lines in emufx:
>
> OP(icode, &ptr, iMACINT0, GPR(6), C_00000000,
FXBUS(FXBUS_PCM_CENTER), C_00000004);
> OP(icode, &ptr, iMACINT0, GPR(7), C_00000000,
FXBUS(FXBUS_PCM_LFE), C_00000004);
>
>to
>
> OP(icode, &ptr, iMACINT0, GPR(6), C_00000000, FXBUS(8), C_00000004);
> OP(icode, &ptr, iMACINT0, GPR(7), C_00000000, FXBUS(9), C_00000004);
>
>3) create a new "chn67" pcm in your .asoundrc:
>
>pcm.chn67 {
> @args [ CARD ]
> @args.CARD {
> type string
> }
> type hooks
> slave.pcm {
> type hw
> card $CARD
> device 0
> }
> hooks.0 {
> type ctl_elems
> hook_args [
> {
> name "EMU10K1 PCM Send Volume"
> index { @func private_pcm_subdevice }
> lock true
> value [ 0 0 0 0 255 0 0 0 0 255 0 0 ]
> }
> {
> name "EMU10K1 PCM Send Routing"
> index { @func private_pcm_subdevice }
> lock true
> value [ 0 1 2 3 8 9 0 1 8 9 0 1 ]
> }
> }
>}
>
>Note: Send Routing is fxbus setup
>
> Jaroslav
>
>-----
>Jaroslav Kysela <perex@suse.cz>
>Linux Kernel Sound Maintainer
>ALSA Project, SuSE Labs
>
>
>
>-------------------------------------------------------
>This SF.NET email is sponsored by:
>SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
>http://www.vasoftware.com
>_______________________________________________
>Alsa-devel mailing list
>Alsa-devel@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/alsa-devel
>
**********************************************************************
Dr.ir. Gerard J.M. Janssen
Delft University of Technology
Faculty of Information Technology and Systems (ITS)
Wireless Mobile Communications Group
P.O. Box 5031, 2600 GA Delft, The Netherlands
Phone +31-15-2786736, Fax +31-15-2781774
E-mail G.Janssen@ITS.TUDelft.NL
**********************************************************************
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
^ permalink raw reply
* Re: 2.4.21-pre3 fails compile of ehci-hcd.c
From: Kristofer T. Karas @ 2003-01-09 8:29 UTC (permalink / raw)
To: Greg KH; +Cc: Linux Kernel
In-Reply-To: <20030109073849.GC8400@kroah.com>
On Thu, 2003-01-09 at 02:38, Greg KH wrote:
> On Thu, Jan 09, 2003 at 02:11:15AM -0500, Kristofer T. Karas wrote:
> > Noticed that I could not get patch-2.4.21-pre3 to compile:
>
> Does this patch solve it for you?
Hi Greg - Yes. The extra whitespace made gcc do the right thing.
Thanks.
<Bewilderment> Well I learn something new every day </Bewilderment>
I notice, however, that speed with this version of EHCI seems down.
hdparm -t /dev/discs/disc1/disc
2.4.21-pre2 2.4.21-pre3
----------- -----------
10.5 MB/s 8.3 MB/s
Either way, this is a great improvement over my previous attempts at
getting USB2.0 running with a Soltek SL75-DRV2 MoBo, which resulted in
instantaneous reboots.
Kris
^ permalink raw reply
* RE: opening a port..
From: Rob Sterenborg @ 2003-01-09 8:21 UTC (permalink / raw)
To: netfilter
In-Reply-To: <1042080082.606.21.camel@nirvana>
> > # netstat -an|grep 4662
> > should tell you if your box is listening at all on port 4662.
> >
> > If you run eDonkey server on the firewall box, open port in
> the INPUT
> > chain.
> > If your eDonkey server is *behind* the firewall, open the
> port in the
> > FORWARD chain, and add a DNAT rule in the nat table ->
> PREROUTING chain.
>
> the edonkey server is behind the firewall
>
> 210.54.175.12--->eth0 (Router) 10.0.0.6(eth1)--->10.0.0.x
>
> iptables -t nat -A PREROUTING -p tcp -i eth0 -d 210.54.175.12
> --dport 4662 -j DNAT --to 10.0.0.6:4662
> iptables -A FORWARD -p tcp -i eth0 -d 10.0.0.6 --dport 4662 -j ACCEPT
>
> like that?
If default policy for FORWARD is ACCEPT then it should work without the
FORWARD, else you need it.
For me such a setup works.
If you do a netstat -an on the eDonkey box (you don't need netcat to do
that) and it doesn't report 4662 then eDonkey is not running/listening
and you can never connect.
About opening ports for eDonkey, from the eDonkey website :
(http://www.edonkey2000.com/documentation/index.html)
====
2. Software Firewall
If you are running software like Norton Personal Firewall, Tiny
Firewall, Zone Alarm, BlackIce or <...snip...>
Alternatively, with some more advanced firewalls, or firewall settings
you will need to open ports 4661 and 4662 TCP for both incoming and out
going connections, as well as port 4665 UDP for both incoming and
outgoing connections.
3. Hardware firewall
Setting up your hardware firewall is a tad more difficult, but if you
have one chances are you know what your doing. You will need to set it
to allow both incoming and outgoing connections on 4661 & 4662 TCP and
port 4665 UDP.
====
So you need to open more ports than just 4662/tcp I think.
And IMHO you want a statefull packetfilter, if you haven't made it
already statefull.
(iptables -A FORWARD -m state --state RELATED,ESTABLISHED -j ACCEPT)
Rob
^ permalink raw reply
* Re: Some advice for QoS setup ...
From: Jörg Esser @ 2003-01-09 8:20 UTC (permalink / raw)
To: Netfilter Mailing List
In-Reply-To: <1042094506.26551.111.camel@rayw.knowledgefactory.co.za>
Raymond Leach wrote:
>Hi all
>
>Am I going about this in the right way?
>
>This is what I plan to do :
>
>1. Outgoing www traffic originating from our web servers has priority 1
>with min 30% bandwidth and max 60% bandwidth.
>2. Outgoing mail traffic (smtp and pop3) originating from our mail
>servers has priority 2 with min 5% bandwidth and max 20% bandwidth.
>3. Outgoing ftp traffic originating from our ftp servers has priority 3
>with min 5% bandwidth and max 10% bandwidth.
>4. All other traffic has priority 4 with min 0% bandwidth and max 10%
>bandwidth.
>
>I was thinking of using htb and sfq. What should my 'tree that is not a
>tree' look like?
>
>I was also planning to use netfilter iptables to mark the traffic and
>use tc to filter the packets based on the mark (let's say 1,2,3,4
>corresponding to the priorities above).
>
>Any suggestions?
>
>I thought my tree would look something like this:
>
> 10: (htb)
> |
> 10:1 (htb)
> (rate 512kbps, ceil 512kbps)
> |
> ________________________________________________________
> | | | |
>10:10 (htb) 10:20 (htb) 10:30 (htb) 10:40 (htb)
>(rate 153kbps, (rate 25kbps, (rate 25kbps, (rate 0kbps,
> ceil 306kbps) ceil 102kbps) ceil 50kbps) ceil 50kbps)
> | | | |
> SFQ SFQ SFQ SFQ
>
>Does my tree look correct? Will this tree honour the priorities I want
>to set? Is netfilter FWMARK the right way to go here?
>
>Regards
>
>Ray
>
Found this in german journal ct.
Maybe you can use it.
You need this:
http://luxik.cdi.cz/~devik/qos/htb/v3/htb3.6-020525.tgz
(The tc binary is needed without the right version it won´t work)
Insert all QOS stuff from kernel sources in your kernel.
put this as qos-on script.
-----------------------------------------
#!/bin/sh
#
# Shell-Skript fuer Quality of Service mit HTB
#
EXTIF=ppp0
INTIF=eth0
############
# Outgoing
############
## Root
tc qdisc add dev $EXTIF root handle 1:0 htb default 12
## Hauptklasse
tc class add dev $EXTIF parent 1:0 classid 1:1 htb rate 125kbit ceil 125kbit
## Klasse fuer ACK
tc class add dev $EXTIF parent 1:1 classid 1:10 htb rate 10kbit ceil
125kbit prio 0
## Klasse fuer VPN/SSH
tc class add dev $EXTIF parent 1:1 classid 1:11 htb rate 30kbit ceil
125kbit prio 1
## Klasse fuer normalen Traffic
tc class add dev $EXTIF parent 1:1 classid 1:12 htb rate 75kbit ceil
125kbit prio 2
## Klasse fuer Bulk
tc class add dev $EXTIF parent 1:1 classid 1:13 htb rate 10kbit ceil
100kbit prio 3
# ACKs
#iptables -A OUTPUT -t mangle -o $EXTIF -p tcp -m length --length :64 -j
MARK --set-mark 10
# VPN/IPsec
iptables -A POSTROUTING -t mangle -o $EXTIF -p 50 -j MARK --set-mark 11
# SSH
iptables -A POSTROUTING -t mangle -o $EXTIF -p tcp --dport 22 -j MARK
--set-mark 11
## lokaler SSH Server auf Port 4444
## iptables -A OUTPUT -t mangle -o $EXTIF -p tcp --sport 4444 -j MARK
--set-mark 11
## SMTP
iptables -A POSTROUTING -t mangle -o $EXTIF -p tcp --dport 25 -j MARK
--set-mark 13
# eDonkey
iptables -A POSTROUTING -t mangle -o $EXTIF -p tcp --dport 4662 -j MARK
--set-mark 13
iptables -A POSTROUTING -t mangle -o $EXTIF -p tcp --sport 4662 -j MARK
--set-mark 13
tc filter add dev $EXTIF parent 1:0 prio 0 protocol ip handle 10 fw
flowid 1:10
tc filter add dev $EXTIF parent 1:0 prio 0 protocol ip handle 11 fw
flowid 1:11
# default: 1:12
tc filter add dev $EXTIF parent 1:0 prio 0 protocol ip handle 13 fw
flowid 1:13
###########
# Incoming
###########
tc qdisc add dev $INTIF root handle 2:0 htb default 20
tc class add dev $INTIF parent 2:0 classid 2:2 htb rate 750kbit ceil 750kbit
tc class add dev $INTIF parent 2:2 classid 2:20 htb rate 500kbit ceil
700kbit prio 1
tc class add dev $INTIF parent 2:2 classid 2:21 htb rate 150kbit ceil
750kbit prio 0
tc class add dev $INTIF parent 2:2 classid 2:22 htb rate 100kbit ceil
500kbit prio 3
# ACKs
#iptables -A POSTROUTING -t mangle -o $INTIF -m length --length :200 -j
MARK --set-mark 21
# SSH
#iptables -A POSTROUTING -t mangle -o $INTIF -p tcp --sport 22 -j MARK
--set-mark 21
# eDonkey
iptables -A POSTROUTING -t mangle -o $INTIF -p tcp --dport 4662 -j MARK
--set-mark 22
iptables -A POSTROUTING -t mangle -o $INTIF -p tcp --sport 4662 -j MARK
--set-mark 22
# zu drosselnder Rechner
#iptables -A POSTROUTING -t mangle -o $INTIF -d 192.168.111.1 -j MARK
--set-mark 22
tc filter add dev $INTIF parent 2:0 prio 0 protocol ip handle 21 fw
flowid 2:21
tc filter add dev $INTIF parent 2:0 prio 0 protocol ip handle 22 fw
flowid 2:22
#########
# SFQ
#########
tc qdisc add dev $EXTIF parent 1:10 handle 10: sfq perturb 10
tc qdisc add dev $EXTIF parent 1:11 handle 11: sfq perturb 10
tc qdisc add dev $EXTIF parent 1:12 handle 12: sfq perturb 10
tc qdisc add dev $EXTIF parent 1:13 handle 13: sfq perturb 10
tc qdisc add dev $INTIF parent 2:20 handle 20: sfq perturb 10
tc qdisc add dev $INTIF parent 2:21 handle 21: sfq perturb 10
tc qdisc add dev $INTIF parent 2:22 handle 22: sfq perturb 10
-----------------------------------------------------------------------
and this as qos-off script.
-----------------------------------------------------------------
# /bin/sh
EXTIF=ppp0
INTIF=eth0
iptables -F -t mangle
tc qdisc del dev $EXTIF root 2> /dev/null > /dev/null
tc qdisc del dev $EXTIF ingress 2> /dev/null > /dev/null
tc qdisc del dev $INTIF root 2> /dev/null > /dev/null
tc qdisc del dev lo root 2> /dev/null > /dev/null
----------------------------------------------------------------
Have a nice day,
Joerg Esser
^ permalink raw reply
* Re: Undelete files on ext3 ??
From: Michael Knigge @ 2003-01-09 8:27 UTC (permalink / raw)
To: root; +Cc: Max Valdez, Jan Hudec, kernel
In-Reply-To: <Pine.LNX.3.95.1030107131613.3523A-100000@chaos.analogic.com>
Hi there,
> There is a project waiting for someone who wants
> to contribute. It only slightly involves the kernel,
> but is quite useful.
Libtrash?
http://freshmeat.net/projects/libtrash/?topic_id=137
http://www.m-arriaga.net/software/libtrash/
libtrash is a shared library which implements a trash can on
GNU/Linux. When preloaded, it intercepts calls to a series of GNU libc
functions and, instead of permanently destroying files, moves them to
a "trash can".
Bye
Michael
^ permalink raw reply
* 2.5.x inspiron touchpad breakage
From: Andres Salomon @ 2003-01-09 8:27 UTC (permalink / raw)
To: linux-kernel
2.5.54 and 2.5.55 do not appear to initialize the touchpad on my Dell
Inspiron 3800. No mouse device is detected until I plug a normal ps/2
mouse into the laptop. I assume this is some weird bios thing. 2.4.x
works fine with it. Does anyone have suggestions about where to look for
any changed in the 2.5 series that might've broken it, or any patches that
fix it?
^ permalink raw reply
* Re: [PATCH] kallsyms off-by-one and sorting
From: Hugh Dickins @ 2003-01-09 8:29 UTC (permalink / raw)
To: Andi Kleen; +Cc: torvalds, linux-kernel
In-Reply-To: <20030109064011.GA27152@wotan.suse.de>
On Thu, 9 Jan 2003, Andi Kleen wrote:
> On Thu, Jan 09, 2003 at 06:22:50AM +0000, Hugh Dickins wrote:
> > Beware of kksymoops reports on 2.5.55:
> > kallsyms was off-by-one, showing the preceding symbol name. For
> > example, if best index 0, no string was copied into the namebuf.
>
> Thanks. Wasn't it there before?
Not before 2.5.54: it was a consequence of the change from leaving
a pointer to the next name, to filling the buffer with the name -
it didn't fill with the next name, but left the previous name there.
Hugh
^ permalink raw reply
* Re: [PATCH] proc.txt document fix of error_burst and error_cost
From: David S. Miller @ 2003-01-09 8:14 UTC (permalink / raw)
To: blueflux; +Cc: kuznet, netdev
In-Reply-To: <Pine.LNX.4.44.0211071755470.5001-200000@laptop1.agatha>
From: Oskar Andreasson <blueflux@koffein.net>
Date: Thu, 7 Nov 2002 18:00:35 +0100 (CET)
The patch should apply against both 2.4.19 and 2.5.45 without problems.
Is there anything wrong with it, or may it be included? Suggestions?
Patch applied, thanks.
^ permalink raw reply
* Re: Status of linuxppc_2.5
From: Pantelis Antoniou @ 2003-01-09 8:13 UTC (permalink / raw)
To: Benjamin Herrenschmidt; +Cc: Boris Bezlaj, linuxppc-dev
In-Reply-To: <1042049915.787.9.camel@zion.wanadoo.fr>
Benjamin Herrenschmidt wrote:
>On Wed, 2003-01-08 at 18:32, Boris Bezlaj wrote:
>
>
>>On Wed, Jan 08, 2003 at 11:18:10AM +0200, Pantelis Antoniou wrote:
>>
>>
>>
>>>BTW, are there any gotchas, or anything
>>>I should pay attention moving
>>>from 2.4 -> 2.5?
>>>
>>>
>>AFAIK, you need the new module-init-tools for loading/unloading modules.
>>
>>I see there is a little patch for swim3 driver. Do you have any problems
>>with swim3 driver in 2.4 kernel when writing to floppy? What is the status
>>in v2.5?
>>
>
>What patch ? I'm interested ;)
>
>So far, swim3 in 2.5 is not up-to-date to new BIO semantics in 2.5. I've wanted
>to do that for some time now but didn't find time yet.
>
>Ben.
>
>
>
>
>
I'm sorry, the patch is just trivial stuff needed
to get it to compile. I don't even have hardware
that applies to swim3 driver. I just added the
include for the header and modified the call
to ide_unregister to use the new calling convention.
BTW ide_unregister was not exported in linux/ide.h
and so I added the prototype there. Maybe someone
should notify the maintainer of the IDE layer that
since this function is needed by the swim3 driver
it should be visible in the header?
Or we should use a new infrastructure?
As I mentioned since I don't have a power mac testing
system, I'm not willing to sacrifice my workstation
to the gods of 2.5 just yet.
What I want to do is to use 2.5 for my board which
uses a 8xx, and there I'm up against greater problems...
My major obstacle is the 8xx uart driver.
I'm not up to speed on 2.5 yet, but what
happened to DECLARE_TASK_QUEUE? Apparently alot of
things changed significantly.
Is there any document or whatever to help me
clean up the confusion?
Finally, if I am permitted to say, it appears that we are
a little behind in the 2.5 train. The release date
is getting closer, and I'm not sure that there
are any people using 2.5 in PPC systems.
IMHO we should pick up the pace a little bit.
Regards
Pantelis
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
^ permalink raw reply
* Re: [LARTC] Setup IMQ on kernel 2.4.20
From: Remus @ 2003-01-09 8:13 UTC (permalink / raw)
To: lartc
In-Reply-To: <marc-lartc-104209941917250@msgid-missing>
[-- Attachment #1: Type: text/plain, Size: 626 bytes --]
Yes, no problem.
Just take a look to the attached files.
Regards
Remus
----- Original Message -----
From: "Koot, M." <koot@ecn.nl>
To: "List LARTC" <lartc@mailman.ds9a.nl>
Sent: Thursday, January 09, 2003 8:02 AM
Subject: [LARTC] Setup IMQ on kernel 2.4.20
> Hi,
>
> does someone have setup IMQ succesfully on kernel 2.4.20?
> If so, how did you do that.
> I only see the diff for kernel 2.4.19. Can I use that?
>
>
> Thanks,
>
> Martijn
>
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
>
>
[-- Attachment #2: IMQ for iptables 1.2.7a and kernel 2.4.20.txt --]
[-- Type: text/plain, Size: 955 bytes --]
You can successfully run iptables 1.2.7a with patch from IMQ homepage.
The thing what you have to do is to replace strings contains:
NETFILTER_VERSION to "1.2.7a" in libipt_IMQ.c and libip6t_IMQ.c .
How to patch iptables and 2.4.xx kernel:
cd iptables-1.2.7a
patch -p1 < ./iptables-1.2.7a-imq.diff
chmod a+x extensions/.IMQ-test
chmod a+x extensions/.IMQ-test6
cd linux-2.4.20
patch -p1 < ./imq-2.4.19.diff
cd patch-o-matic-YYYYMMDD
patch -p1 < ./pom-imq.diff
KERNEL_DIR=/usr/src/linux-2.4.20 ./runme extra/IMQ.patch
You will have three new options:
Networking options ---> IP: Netfilter Configuration --->IMQ target support
Networking options ---> IPv6: Netfilter Configuration --->IMQ target support
Network device support --->IMQ (intermediate queueing device) support
Choose at least one of the targets and the device itself.
Netfilter debugging should be turned off, otherwise cou get lots of annoying messages.
[-- Attachment #3: imq-2.4.19.tar.bz2 --]
[-- Type: application/octet-stream, Size: 6681 bytes --]
^ permalink raw reply
* marking all h323 packets with some TOS
From: Upma Gandhi @ 2003-01-09 8:13 UTC (permalink / raw)
To: netfilter
[-- Attachment #1: Type: text/plain, Size: 540 bytes --]
Hello All,
I have a following setup
Internet <-> Router with netfilter configure <-> LAN(192.9.201.0/24)
lets supopose eth0 is LAN side Interface and
eth1 is WAN side interface.
what I want to do is "Mark all h323 packets with some tos value".
for which my iptables command seems to be like this-
iptables -t mangle -A FORWARD -o eth0 -d 192.9.201.0/24 -p tcp -m
rtp -j FTOS --set-ftos 0xb8.
but it's giving an error message -
iptable: No chain/target/match by tha rule.
Can anybody help me out.
Thanks & Regards
Upma
[-- Attachment #2: Type: text/html, Size: 759 bytes --]
^ permalink raw reply
* RE: opening a port..
From: Dharmendra.T @ 2003-01-09 8:11 UTC (permalink / raw)
To: mdew; +Cc: netfilter
In-Reply-To: <1042095879.433.17.camel@nirvana>
it was netcat
>
> apt-get install netcat
>
>
try with netcat and let us know.
--
Dharmendra.T
Linux Enthu
^ permalink raw reply
* [parisc-linux] Printing problem with HP9000 712/80 and two more questions
From: Vilmos Soti @ 2003-01-09 7:55 UTC (permalink / raw)
To: parisc-linux
Hello,
I have an old HP9000 712/80 box which I would like to use as an
internal file/print server. The printing doesn't work. I tried
the original kernel which came with Debian, I also tried to cross
compile (on a much faster P3 600MHz) numerous kernels, and I also
tried 2.4.20-pa18 from ftp://ftp.parisc-linux.org. I tried to
permute every option regarding the printer in the kernel config
file, and in all cases, including the default Debian kernel and
the 2.4.20-pa18, I consistently cannot get the printer work.
The printer is a HP LaserJet 1100 connected to the parallel port. The
printer works fine on an Intel box, so it is hopefully not a printer
problem. Whenever I try to print from the HPPA box (even something
like "cat /etc/passwd > /dev/lp0"), absolutely nothing happens.
Here are some relevant files:
cat /proc/iomem
00000000-03ffffff : System RAM
00000000-000009ff : PDC data (Page Zero)
00100000-002fbfff : Kernel code
002fc000-003fbcd3 : Kernel data
f0100000-f01fffff : Lasi
f0100000-f0100fff : Lasi
f0102000-f0102fff : Parallel
f0104000-f0104fff : Lasi Harmony
f0105000-f0105fff : Serial RS232
f0106000-f0106fff : Lasi SCSI
f0107000-f0107fff : Apricot
f0108000-f010800f : keyboard
f0108100-f01090ff : Lasi psaux
f0500000-f05fffff : Lasi
f0500000-f0500fff : Lasi
f0505000-f0505fff : Serial RS232
f8000000-f8000fff : sti (native)
f8100000-f84fffff : stifb mmio
f9000000-f9ffffff : stifb
fff80000-fffaffff : Central Bus
fffb0000-fffdffff : Local Broadcast
fffbe000-fffbefff : CPU
fffe0000-ffffffff : Global Broadcast
/proc/interrupts
CPU00
32: 37262217 PARISC-CPU timer
33: 176500 PARISC-CPU lasi
34: 0 PARISC-CPU lasi
69: 1022 Lasi keyboard
82: 9 Lasi harmony
86: 126441 Lasi lasi710
87: 49028 Lasi i82596
88: 0 Lasi parport0
Here is the dmesg of the box. I won't break the lines so it is
easier to read.
Linux version 2.4.20-pa18 (bame@dsl2) (gcc version 3.0.3) #1 Fri Dec 27 06:12:20 MST 2002
FP[0] enabled: Rev 1 Model 13
The 32-bit Kernel has started...
Determining PDC firmware type: Snake.
model 00006010 00000481 00000000 00000000 77da0338 00000000 00000004 00000072 00000072
vers 00000009
model 9000/712
Total Memory: 64 Mb
pagetable_init
On node 0 totalpages: 16384
zone(0): 16384 pages.
zone(1): 0 pages.
zone(2): 0 pages.
Kernel command line: root=/dev/sda2 HOME=/ console=tty0 sti=1 sti_font=VGA8x16 TERM=linux palo_kernel=2/boot/vmlinux
Console: colour dummy device 160x64
Calibrating delay loop... 79.66 BogoMIPS
Memory: 61624k available
Dentry cache hash table entries: 8192 (order: 4, 65536 bytes)
Inode cache hash table entries: 4096 (order: 3, 32768 bytes)
Mount-cache hash table entries: 1024 (order: 1, 8192 bytes)
Buffer-cache hash table entries: 1024 (order: 0, 4096 bytes)
Page-cache hash table entries: 16384 (order: 4, 65536 bytes)
Searching for devices...
Found devices:
1. Gecko 80 GSC Core Graphics (10) at 0xf8000000 [1], versions 0x1c, 0x0, 0x85
2. Gecko 80 Core BA (11) at 0xf0100000 [2], versions 0x1c, 0x0, 0x81
3. Gecko 80 Core SCSI (10) at 0xf0106000 [2/0/1], versions 0x1c, 0x0, 0x82
4. Gecko 80 Core LAN (802.3) (10) at 0xf0107000 [2/0/2], versions 0x1c, 0x0, 0x8a
5. Gecko 80 Core RS-232 (10) at 0xf0105000 [2/0/4], versions 0x1c, 0x0, 0x8c
6. Gecko 80 Core Centronics (10) at 0xf0102000 [2/0/6], versions 0x1c, 0x0, 0x74
7. Gecko 80 Audio (10) at 0xf0104000 [2/0/8], versions 0x1c, 0x0, 0x7b
8. Gecko 80 Core PC Floppy (10) at 0xf010a000 [2/0/10], versions 0x1c, 0x0, 0x83
9. Gecko 80 Core PS/2 Port (10) at 0xf0108000 [2/0/11], versions 0x1c, 0x0, 0x84
10. Gecko 80 Core PS/2 Port (10) at 0xf0108100 [2/0/12], versions 0x1c, 0x0, 0x84
11. Gecko 80 Core BA (11) at 0xf0500000 [6], versions 0x1c, 0x0, 0x81
12. Gecko Optional RS-232 (10) at 0xf0505000 [6/0/4], versions 0x18, 0x0, 0x8c
13. Gecko 80 (712/80) (0) at 0xfffbe000 [8], versions 0x601, 0x0, 0x4
14. Memory (1) at 0xfffbf000 [9], versions 0x38, 0x0, 0x9
CPU(s): 1 x PA7100LC (PCX-L) at 80.000000 MHz
Lasi version 0 at 0xf0100000 found.
Lasi version 0 at 0xf0500000 found.
POSIX conformance testing by UNIFIX
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
Gecko-style soft power switch enabled.
Starting kswapd
Journalled Block Device driver loaded
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
parport_init_chip: initialize bidirectional-mode.
parport0: PC-style at 0xf0102800, irq 88 [PCSPP,TRISTATE]
STI GSC/PCI graphics driver version 0.9
STI word mode ROM at f0080000, hpa at f8000000
STI id 2b4ded6d-40a00499, conforms to spec rev. 8.04
STI device: HPA208LC1280
Console: switching to colour frame buffer device 160x64
fb0: stifb 1280x1024-8 frame buffer device, id: 2b4ded6d, mmio: 0xf8100000
pty: 256 Unix98 ptys configured
Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ SERIAL_PCI enabled
ttyS00 at iomem 0xf0105800 (irq = 90) is a 16550A
ttyS01 at iomem 0xf0505800 (irq = 122) is a 16550A
PS/2 keyboard port at 0xf0108000 (irq 69) found, device attached.
PS/2 psaux port at 0xf0108100 (irq 69) found, no device attached.
lp0: using parport0 (interrupt-driven).
Generic RTC Driver v1.02 05/27/1999 Sam Creasey (sammy@oh.verio.com)
Uniform Multi-Platform E-IDE driver Revision: 6.31
ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
loop: loaded (max 8 devices)
Found i82596 at 0xf0107000, IRQ 87
eth0: 82596 at 0xf0107000, 08 00 09 83 F6 4A IRQ 87.
82596.c $Revision: 1.30 $
SCSI subsystem driver Revision: 1.00
53c700: Version 2.8 By James.Bottomley@HansenPartnership.com
scsi0: 53c710 rev 2
scsi0 : LASI SCSI 53c700
scsi0: (6:0) Synchronous at offset 8, period 100ns
Vendor: MICROP Model: 2112 Rev: 4024
Type: Direct-Access ANSI SCSI revision: 02
Attached scsi disk sda at scsi0, channel 0, id 6, lun 0
SCSI device sda: 2051460 512-byte hdwr sectors (1050 MB)
Partition check:
sda: sda1 sda2 sda3
Lasi Harmony Audio driver V0.9a, h/w id 20, rev. 18 at 0xf0104000, IRQ 82
mice: PS/2 mouse device common for all mice
HP SDC: No SDC found.
HP SDC MLC: Registering the System Domain Controller's HIL MLC.
HP SDC MLC: Request for raw HIL ISR hook denied
md: linear personality registered as nr 1
md: raid0 personality registered as nr 2
md: raid1 personality registered as nr 3
md: raid5 personality registered as nr 4
raid5: measuring checksumming speed
8regs : 60.800 MB/sec
8regs_prefetch: 60.800 MB/sec
32regs : 70.800 MB/sec
32regs_prefetch: 70.800 MB/sec
raid5: using function: 32regs_prefetch (70.800 MB/sec)
md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 4096 bind 8192)
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Freeing unused kernel memory: 266k freed
Adding Swap: 130836k swap-space (priority -1)
EXT3 FS 2.4-0.9.19, 19 August 2002 on sd(8,2), internal journal
eth0: link ok.
Now one thing I found is that the interrupt count for the
printer port doesn't increase even if I send a file to /dev/lp0
or print through the printer daemon. I tried to run
"tunelp /dev/lp0 -i 0", but it complained about invalied argument
to ioctl (maybe wasn't updated since 2.2?) and it says "using IRQ 88".
Anyone has any idea how to solve this problem?
And two more questions. Is the sound card full duplex? My standard
method of determinig, "cat /dev/audio > /dev/audio" told me that
"Device or resource busy" therefore it seems it is not. Is it true?
The other question. I am using emacs, and I regularly see these messages:
Jan 8 23:52:33 hp kernel: emacs(17795): unaligned access to 0x001cdaf2 at ip=0x0008937f
Jan 8 23:52:33 hp kernel: emacs(17795): unaligned access to 0x001cdaf2 at ip=0x0008930b
What are they?
TIA, Vilmos
^ permalink raw reply
* Re: opening a port..
From: Jörg Esser @ 2003-01-09 8:04 UTC (permalink / raw)
To: netfilter
In-Reply-To: <1042095879.433.17.camel@nirvana>
mdew wrote:
>On Thu, 2003-01-09 at 19:53, Dharmendra.T wrote:
>
>
>>>># nc -l -p 4662
>>>>
>>>>And then run nmap. You should get listed this port!
>>>>
>>>>--
>>>>Dharmendra.T
>>>>Linux Enthu
>>>>
>>>>
>>>mdew:~# nc -l -p 4662
>>>ãP<H¹ogÝT'b´\Y6▒http://emule-project.net<6Ñ~ÖEmdew:~#
>>>
>>>(some strange characters, then it quits)
>>>
>>>mdew:~# netstat -an|grep 4662
>>>mdew:~#
>>>
>>>nirvana:/home/mdew# nmap 10.0.0.6
>>>
>>>
nmap -p4662 10.0.0.6
Should work better.
and a new version of nmap should work better, too.
I heard that when you use nmap as your way it picks just well known
ports (/etc/service file ?) and then you won´t get this special port if
its not in there.(Maybe I´m wrong)
>>>Starting nmap V. 3.10ALPHA4 ( www.insecure.org/nmap/ )
>>>Interesting ports on debian (10.0.0.6):
>>>(The 1591 ports scanned but not shown below are in state: closed)
>>>Port State Service
>>>22/tcp open ssh
>>>25/tcp open smtp
>>>110/tcp open pop-3
>>>111/tcp filtered sunrpc
>>>113/tcp open auth
>>>135/tcp filtered loc-srv
>>>136/tcp filtered profile
>>>137/tcp filtered netbios-ns
>>>138/tcp filtered netbios-dgm
>>>139/tcp filtered netbios-ssn
>>>199/tcp filtered smux
>>>826/tcp filtered unknown
>>>953/tcp filtered rndc
>>>8080/tcp open http-proxy
>>>
>>>
>>>
>>>
>>>
>>>
>>nc, I mean to say netcat.?
>>
>>
>
>it was netcat
>
>apt-get install netcat
>
>
>
>
>
>
^ permalink raw reply
* dns doctoring
From: Micah Abrams @ 2003-01-09 8:03 UTC (permalink / raw)
To: netfilter
List --
I'm building an iptables firewall to replace my pix 506. The firewall will
only have two interfaces for now. My dns server sits outside my firewall on
the internet and answers queries for both my internal network and the world.
Of course it only contains real world ips. The pix has an option (called
alias) that doctors dns request from my internal lan so that the reply
packet contains the internal ip address instead of the public address given
out by my dns server. This lets the internal machines access internal hosts
via dns without having to run two dns servers. For example with following
command:
alias (inside) 192.168.0.5 245.243.3.5 255.255.255.255
all dns queries passing through the pix containing the address 245.243.3.5
are re-written to contain 192.168.0.5. My question is, is there any way to
do this with iptables? How is everyone handling this? I would really like
to avoid having two dns servers. I am very new to iptables so any and all
help is much appreciated.
Thanks
~Micah
^ permalink raw reply
* [LARTC] Setup IMQ on kernel 2.4.20
From: Koot, M. @ 2003-01-09 8:02 UTC (permalink / raw)
To: lartc
Hi,
does someone have setup IMQ succesfully on kernel 2.4.20?
If so, how did you do that.
I only see the diff for kernel 2.4.19. Can I use that?
Thanks,
Martijn
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
^ permalink raw reply
* Re: Maybe OT: Unregistering a USB device
From: Greg KH @ 2003-01-09 8:10 UTC (permalink / raw)
To: Rus Foster; +Cc: Dmitri, linux-kernel
In-Reply-To: <20030106072607.L27804-100000@freebsd.rf0.com>
On Mon, Jan 06, 2003 at 07:27:12AM +0000, Rus Foster wrote:
> On 5 Jan 2003, Dmitri wrote:
>
> > On Sun, 2003-01-05 at 15:09, Rus Foster wrote:
> >
> > Someone else asked this question earlier:
> >
> > http://marc.theaimsgroup.com/?l=linux-usb-users&m=104127472526623&w=2
> >
> > Dmitri
>
> Ah right the problem is that
> a) I still want one of the usb-mass storage devices to still be accessible
> at the same time.
> b) My kernel is monolithic
You can use the USBDEVFS_DISCONNECT ioctl on the usb device node in
usbfs to disconnect the driver from the device.
Hope this helps,
greg k-h
^ permalink raw reply
* Re: Gauntlet Set NOW!
From: Andrew Morton @ 2003-01-09 8:08 UTC (permalink / raw)
To: rms; +Cc: andre, linux-kernel
In-Reply-To: <E18WX7P-0001cV-00@fencepost.gnu.org>
Richard Stallman wrote:
>
> ...
> That's not the FSF's view. Our view is that just using structure
> definitions, typedefs, enumeration constants, macros with simple
> bodies, etc., is NOT enough to make a derivative work. It would take
> a substantial amount of code (coming from inline functions or macros
> with substantial bodies) to do that.
The last part doesn't make a lot of sense.
Use of an inline function is just that: usage. It matters not at
all whether that function is invoked via inline integration or via
subroutine call. This is merely an implementation detail within
the code which provides that function.
Such functions are part of the offered API which have global scope,
that's all.
^ permalink raw reply
* Re: DMZ trouble!
From: Joel Newkirk @ 2003-01-09 7:58 UTC (permalink / raw)
To: David Collodel, netfilter
In-Reply-To: <1042090495.2320.216.camel@jimmy>
On Thursday 09 January 2003 12:34 am, David Collodel wrote:
{Very heavily snipped}
> Perhaps it would help if I included my entire script? Or at least the
> relevant parts of it.
It seems you included it entire. :^)
> Thanks for any help you can offer.
[snipped lengthy but self-explanatory IP & interface aliases]
> $IPTABLES -P INPUT DROP
> $IPTABLES -P OUTPUT DROP
> $IPTABLES -P FORWARD DROP
>
> $IPTABLES -F
>
> $IPTABLES -F INPUT
> $IPTABLES -F OUTPUT
> $IPTABLES -F FORWARD
>
> $IPTABLES -F -t mangle
> $IPTABLES -t mangle -X
Why are you not flushing nat table as well? BTW, the "$IPTABLES -F"
encompasses all the filter table chains, so the following three flushes
are redundant.
Why do you have so many (snipped) rules for INPUT to the firewall box
itself? Do you really need to allow all ports and all protocols from
the DMZ and the LAN?? Unless you are running some services on the box
(which should probably be run on a server on the LAN or in the DMZ) you
really shouldn't allow ANY access, except SSH if you must. Other than
SSH I can't conceive of why you need ANY access to this box from the
Internet. Even the EST/REL shouldn't be necessary.
> $IPTABLES -A FORWARD -i $DMZ_IFACE -o $EXT_IFACE -j ACCEPT
This should probably be dropped in favor of individual rules to allow
each (if any other than DNS) connection that the DMZ machines would need
to initiate.
> $IPTABLES -A FORWARD -i $LAN_IFACE -j ACCEPT
Do you trust the LAN machines and users this much? You'd probably be
much better off if you just have a handful of rules to ACCEPT the
services they really require. If someone needs something that doesn't
get through the firewall, you'll certainly get a call. :^) You can then
decide if you want to allow it, and if so then add an appropriate rule.
On my home network, where I control all machines, I STILL only allow
four ports through FORWARD, and log everything else. And my INPUT rules
are tighter than this, and my firewall IS my desktop machine, web
server, and an Unreal Tournament server, and runs P2P sometimes. (Both
those are toggled through a script, so I open the ports manually with
"fw ut" for example then close with "fw utx")
> $IPTABLES -A FORWARD -m state --state ESTABLISHED,RELATED -j ACCEPT
This one makes all your other FORWARD state rules rather unnecessary,
since they are all tighter than this, and this accepts any interface.
> $IPTABLES -A OUTPUT -p ALL -s $EXT_IP -j ACCEPT
Again, what need do you have for this box to communicate directly with
anything on the internet? I would lock this sucker down TIGHT. Set up
a script owned by root that you can execute to temporarily open INPUT
and OUTPUT only as far as absolutely necessary if there's anything you
need to do from the box. Other than that leave OUTPUT and INPUT at just
DROP, with SSH allowed in and responded only if you have to. If
somebody gets this box, they own your network. Don't invite trouble.
(especially now that your complete firewall is part of a publicly
accessibly archive...)
I'm not sure why you bothered with a DROP policy on OUTPUT with the four
OUTPUT rules you use. The ONLY thing you prevent from going out is an
incorrect IP.
> $IPTABLES -F -t nat
Ah, here's the nat table flush, 2/3 of the way through the script... :^)
Not a big deal, just that everything else is organized fairly clearly.
> # 3.2 PREROUTING chain
> # 3.2.3 DMZ DNAT
> #
>
> $IPTABLES -t nat -A PREROUTING -p TCP -i $EXT_IFACE -d $HTTP_IP
> --dport 80 -j DNAT --to-destination $DMZ_HTTP_IP
> $IPTABLES -t nat -A PREROUTING -p TCP -i $EXT_IFACE -d $HTTP_IP
> --dport 22 -j DNAT --to-destination $DMZ_HTTP_IP
> $IPTABLES -t nat -A PREROUTING -p TCP -i $EXT_IFACE -d $HTTP_IP
> --dport 443 -j DNAT --to-destination $DMZ_HTTP_IP
> $IPTABLES -t nat -A PREROUTING -p TCP -i $EXT_IFACE -d $HTTP_IP
> --dport 8000 -j DNAT --to-destination $DMZ_HTTP_IP
> $IPTABLES -t nat -A PREROUTING -p TCP -i $EXT_IFACE -d $HTTP_IP
> --dport 8001 -j DNAT --to-destination $DMZ_HTTP_IP
>
> $IPTABLES -t nat -A PREROUTING -p TCP -i $EXT_IFACE -d $DNS_IP --dport
> 53 -j DNAT --to-destination $DMZ_DNS_IP
> $IPTABLES -t nat -A PREROUTING -p UDP -i $EXT_IFACE -d $DNS_IP --dport
> 53 -j DNAT --to-destination $DMZ_DNS_IP
> $IPTABLES -t nat -A PREROUTING -p TCP -i $EXT_IFACE -d $DNS_IP --dport
> 443 -j DNAT --to-destination $DMZ_DNS_IP
> $IPTABLES -t nat -A PREROUTING -p TCP -i $EXT_IFACE -d $DNS_IP --dport
> 22 -j DNAT --to-destination $DMZ_DNS_IP
> $IPTABLES -t nat -A PREROUTING -p TCP -i $EXT_IFACE -d $DNS_IP --dport
> 25 -j DNAT --to-destination $DMZ_DNS_IP
> $IPTABLES -t nat -A PREROUTING -p TCP -i $EXT_IFACE -d $DNS_IP --dport
> 995 -j DNAT --to-destination $DMZ_DNS_IP
Hmmm. Well, this is the answer to your 'real' question. I don't see ANY
rules in PREROUTING to DNAT connections from the LAN. Those would be
addressed -d $DNS_IP, but would be -i $LAN_IFACE.
You should seriously reconsider what communications the firewall box
itself requires, and what traffic the LAN is allowed to conduct.
j
^ permalink raw reply
* Re: "Mother" == "computer-illiterate"
From: J Sloan @ 2003-01-09 8:05 UTC (permalink / raw)
To: Val Henson; +Cc: Miles Bader, dpaun, rms, lm, acahalan, linux-kernel
In-Reply-To: <20030109072043.GE26010@boardwalk>
Val Henson wrote:
>
>
>Can we quit with the "clueless mother" examples already? My own
>mother has installed more distributions of Linux than I've even logged
>into. I know quite a few mothers who have PhDs in CS, own several
>CS-related patents, and/or made important fundamental discoveries in
>CS. Hint: Find out who invented the spanning tree algorithm for
>ethernet bridges, $10 ThinkGeek gift certificate to the first person
>who emails me the correct answer.
>
Radia Perlman
Joe
^ permalink raw reply
* Re: Nvidia and its choice to read the GPL "differently"
From: Dimitrie O. Paun @ 2003-01-09 6:44 UTC (permalink / raw)
To: rms; +Cc: lm, acahalan, linux-kernel
In-Reply-To: <E18WX6e-0001Xj-00@fencepost.gnu.org>
On January 9, 2003 02:28 am, Richard Stallman wrote:
> These discussions will never convince those people, but they do win
> support from others who read both sides and find that we have right on
> our side. So we have something to gain.
I have not touched upon the principle side of things on purpose:
what I'm trying to say is that it does not matter how's right or wrong.
Yes, you can say your campain gains people on the GNU/Linux side, and
you are correct -- it would in any case, it's just the law of large
numbers. You can view that as a gain, and I don't dispute that, but
that gain comes at a huge price: you greatly erode your credibility
and stature within the community. You can use your influence within
the community in ways that would server the FSF a _lot_ more effectively.
Yes, you will say, but we are _right_. Well, you might be. But the
world is not a fair place, and sometimes you have to accept that.
There is unfairness all over the place: you take credit for other
people's work by putting under the GNU umbrella a lot of stuff you
did not write. That's unfair. Is it fair that Alexandre Julliard,
the Wine (http://www.winehq.org) project leader is listed in a list
together with 200+ other developers that contributed a tiny fraction
of what Alexandre did? No, it's not. There are endless examples of
these in the free software world. Once can not simply state the names
and importance (and _how_ would you gauge *that*?) of every single
contributor when you refer to the system.
And because people like a simple mnemonic, they chose one: Linux.
You would have liked they pick the acronym you invented, but they
didn't. People have chosen. It's a tiny detail in the grand scheme
of things, let's be all happy that a catchy acronym was invented
and addopted, and move on!
--
Dimi.
^ permalink raw reply
* Re: length match problem
From: Jörg Esser @ 2003-01-09 7:53 UTC (permalink / raw)
To: netfilter
In-Reply-To: <200301091039.44259.fabrice@netfilter.org>
Fabrice MARIE wrote:
>Hello Joerg,
>
>On Thursday 09 January 2003 06:14, Jackfritt wrote:
>
>
>>Ok I have the following problem.
>>iptables -A OUTPUT -o ppp0 -p tcp -m length --length :40 -j MARK --set-mark 10
>>That should mark all ACK's or not ?
>>When I try to do this I get the error:
>>iptables: Invalid argument
>>[...]
>>So now my question is what am I doin wrong ?
>>
>>
>
>Typically when the only error message from iptables
>is 'Invalid Argument', the actual error message would
>be most of the time in the kernel log.
>i.e. If I run your command above, it tells me
>
># dmesg
>MARK: can only be called from "mangle" table, not "filter"
>
>
Hmm forget to look there (Just a newbie ;)
>So, you should be using a -t mangle in front..
>
>
Thx that did it.
>Have a nice day,
>
>
You too.
^ permalink raw reply
* Re: Gauntlet Set NOW!
From: Jeff Garzik @ 2003-01-09 7:50 UTC (permalink / raw)
To: Richard Stallman; +Cc: linux-kernel
In-Reply-To: <E18WX7P-0001cV-00@fencepost.gnu.org>
On Thu, Jan 09, 2003 at 02:28:47AM -0500, Richard Stallman wrote:
> That's not the FSF's view. Our view is that just using structure
> definitions, typedefs, enumeration constants, macros with simple
> bodies, etc., is NOT enough to make a derivative work. It would take
> a substantial amount of code (coming from inline functions or macros
> with substantial bodies) to do that.
Richard,
Thanks much for posting this. I admit I have been skipping this entire
thread pretty much :) but the above is worth highlighting.
Unfortunately, while helpful, this doesn't necessarily solve the problem
in Linux; the things that are inlined are quite often fairly "smart"
pieces of code and not just things as simple as wrapper functions, or
structures and typedefs.
Regardless, thanks again to posting the above.
Regards,
Jeff
^ permalink raw reply
* RE: [parisc-linux] CONFIG_IP_ADVANCE_ROUTER?
From: jsoe0708 @ 2003-01-09 7:40 UTC (permalink / raw)
To: parisc-linux
In-Reply-To: <3E0085D000001FAA@ocpmta5.freegates.net>
Hi all,
>
>Does somebody have already tested a pa kernel 2.4.20 configured as 'adva=
nce
>router'.
>Does it have some chance that it works?
>
>Thanks in advance,
> Joel
>
>PS: This is to configure a b180 as a small gateway-proxy :) and this is
>requested in GIpTable?
>
Just test and seems to works fine :-))
Joel
********************************************
Promo Tiscali ADSL: 35 Euros/mois, 1er mois et activation =3D 0 Euro http=
://adsl.tiscali.be
^ permalink raw reply
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.