All of lore.kernel.org
 help / color / mirror / Atom feed
* Problems with IRC code
From: Michael A. Nunes @ 2002-12-12 15:10 UTC (permalink / raw)
  To: netfilter

Background: I currently do NOT build my kernel with any modules, as my linux
box is only used as a firewall/router.  I have no need to be able to
dynamically load/unload parts of the kernel.  Therefore, I build all
netfilter code directly into my kernel.

Problem: Up until 2.4.20 it has always been possible for me to hard-code
ports into ip_conntrack_irc.c and ip_nat_irc.c by simply adding the
following:

if (ports[0] == 0) {
                ports[0] = 4646;
                ports[1] = 5190;
                ports[2] = 5554;
                ports[3] = 6667;
                ports[4] = 6868;
                ports[5] = 7000;

in the respect parts of either file.  Like I said, this has ALWAYS worked up
until 2.4.20.  DCCs in/out on any ports in the above list would always work.
With 2.4.20 after adding the above the only thing that works is DCCs IN!
DCCs going out from a NAT'd box no longer make it through!

Question: What in the IRC code has changed so drastically that
I can no longer use the above method for "hard-coding" ports?

--
Michael A. Nunes
/p at pcmike dot net
http://pcmike.net/



^ permalink raw reply

* Re: [Alsa-user] fm801 driver status?
From: Takashi Iwai @ 2002-12-12 15:08 UTC (permalink / raw)
  To: Friedrich Ewaldt; +Cc: alsa-user, alsa-devel
In-Reply-To: <3DF8A109.2030206@gmx.de>

At Thu, 12 Dec 2002 15:45:29 +0100,
Friedrich Ewaldt wrote:
> 
> Hi!
> 
> I've got a fm801 based sound card which locks my computer completely 
> some seconds after loading the alsa driver module. I compiled drivers 
> with debug=detect -- please see my mail(s) from 12/09/2002 on alsa 
> userlist for more info. What else could I do? Meanwhile I found several 
> reports describing the same problem.
> Therefore my question(s): Should it be possible to run a fm801 soundcard 
> using the 0.9.0rc6 or cvs driver? Anyone who has installed such a card 
> successfully? Any ideas what I'm doing wrong? (I have installed some 
> other soundcards using alsa09 without problems.)

it looks like a hardware problem rather than the driver itself.
as lspci shows, your fm801 card has no resources at all.
something wrong with either the soundcard itself or the combination
with the mobo...
can you verify the hardware?


Takashi


-------------------------------------------------------
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility 
Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/

^ permalink raw reply

* ospmd or acpid
From: Matthew Tippett @ 2002-12-12 15:05 UTC (permalink / raw)
  To: acpi-devel-pyega4qmqnRoyOMFzWx49A

Hello people,

Just a quick question regarding the user space daemons for ACPI.  There 
is ospmd which is part of the acpi project, and there is acpid which is 
a seperate project which Andrew is a member of both.

Regards,

Matthew


-- 
Matthew Tippett - matthew.tippett-rieW9WUcm8FFJ04o6PK0Fg@public.gmane.org - (416) 435-4118
Technology Forum - http://www.technology-forum.org/
Commercial Open Source - http://www.commercialos.org/


-----

The information contained in this message is proprietary of Casero Inc.,
protected from disclosure, and may be privileged. The information is
intended to be conveyed only to the designated recipient(s) of the
message. If the reader of this message is not the intended recipient,
you are hereby notified that any dissemination, use, distribution or
copying of this communication is strictly prohibited and may be
unlawful. If you have received this communication in error, please
notify us immediately by replying to the message and deleting it from
your computer. Thank you.



-------------------------------------------------------
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility 
Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/

^ permalink raw reply

* Re: Linux 2.4.21-pre1
From: Adrian Bunk @ 2002-12-12 15:12 UTC (permalink / raw)
  To: Alex Davis; +Cc: linux-kernel
In-Reply-To: <20021211035837.60633.qmail@web40512.mail.yahoo.com>

[-- Attachment #1: Type: text/plain, Size: 602 bytes --]

On Tue, Dec 10, 2002 at 07:58:37PM -0800, Alex Davis wrote:

> >The ac IDE merge broke the compilation of hd.c (it was already broken in 
> >ac):
> 
> ><--  snip  -->
> 
> Hmm.. I was able to build it with no problem. Can you
> post your .config??

It's attached (it's a compile-as-much-as-possible-statically .config 
to find compile errors).

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


[-- Attachment #2: .config --]
[-- Type: text/plain, Size: 38781 bytes --]

#
# Automatically generated make config: don't edit
#
CONFIG_X86=y
# CONFIG_SBUS is not set
CONFIG_UID16=y

#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y

#
# Loadable module support
#
# CONFIG_MODULES is not set

#
# Processor type and features
#
# CONFIG_M386 is not set
# CONFIG_M486 is not set
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
# CONFIG_M686 is not set
# CONFIG_MPENTIUMIII is not set
# CONFIG_MPENTIUM4 is not set
CONFIG_MK6=y
# CONFIG_MK7 is not set
# CONFIG_MELAN is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP2 is not set
# CONFIG_MWINCHIP3D is not set
# CONFIG_MCYRIXIII is not set
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_CMPXCHG=y
CONFIG_X86_XADD=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
# CONFIG_RWSEM_GENERIC_SPINLOCK is not set
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_X86_L1_CACHE_SHIFT=5
CONFIG_X86_ALIGNMENT_16=y
CONFIG_X86_HAS_TSC=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
CONFIG_X86_MCE=y
CONFIG_TOSHIBA=y
CONFIG_I8K=y
CONFIG_MICROCODE=y
CONFIG_X86_MSR=y
CONFIG_X86_CPUID=y
# CONFIG_NOHIGHMEM is not set
# CONFIG_HIGHMEM4G is not set
CONFIG_HIGHMEM64G=y
CONFIG_HIGHMEM=y
CONFIG_X86_PAE=y
CONFIG_HIGHIO=y
CONFIG_MATH_EMULATION=y
CONFIG_MTRR=y
CONFIG_SMP=y
CONFIG_X86_NUMA=y
CONFIG_X86_NUMAQ=y
CONFIG_X86_CLUSTERED_APIC=y
CONFIG_MULTIQUAD=y
CONFIG_X86_SUMMIT=y
CONFIG_X86_CLUSTERED_APIC=y
# CONFIG_X86_TSC_DISABLE is not set
CONFIG_X86_TSC=y
CONFIG_HAVE_DEC_LOCK=y

#
# General setup
#
CONFIG_NET=y
CONFIG_X86_IO_APIC=y
CONFIG_X86_LOCAL_APIC=y
CONFIG_PCI=y
# CONFIG_PCI_GOBIOS is not set
# CONFIG_PCI_GODIRECT is not set
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
CONFIG_ISA=y
CONFIG_PCI_NAMES=y
CONFIG_EISA=y
CONFIG_MCA=y
CONFIG_HOTPLUG=y

#
# PCMCIA/CardBus support
#
CONFIG_PCMCIA=y
CONFIG_CARDBUS=y
CONFIG_TCIC=y
CONFIG_I82092=y
CONFIG_I82365=y

#
# PCI Hotplug Support
#
CONFIG_HOTPLUG_PCI=y
CONFIG_HOTPLUG_PCI_COMPAQ=y
CONFIG_HOTPLUG_PCI_COMPAQ_NVRAM=y
CONFIG_HOTPLUG_PCI_IBM=y
CONFIG_HOTPLUG_PCI_ACPI=y
CONFIG_SYSVIPC=y
CONFIG_BSD_PROCESS_ACCT=y
CONFIG_SYSCTL=y
CONFIG_KCORE_ELF=y
# CONFIG_KCORE_AOUT is not set
CONFIG_BINFMT_AOUT=y
CONFIG_BINFMT_ELF=y
CONFIG_BINFMT_MISC=y
CONFIG_PM=y
CONFIG_ACPI=y
CONFIG_ACPI_DEBUG=y
CONFIG_ACPI_BUSMGR=y
CONFIG_ACPI_SYS=y
CONFIG_ACPI_CPU=y
CONFIG_ACPI_BUTTON=y
CONFIG_ACPI_AC=y
CONFIG_ACPI_EC=y
CONFIG_ACPI_CMBATT=y
CONFIG_ACPI_THERMAL=y
CONFIG_APM=y
CONFIG_APM_IGNORE_USER_SUSPEND=y
CONFIG_APM_DO_ENABLE=y
CONFIG_APM_CPU_IDLE=y
CONFIG_APM_DISPLAY_BLANK=y
CONFIG_APM_RTC_IS_GMT=y
CONFIG_APM_ALLOW_INTS=y
CONFIG_APM_REAL_MODE_POWER_OFF=y

#
# Memory Technology Devices (MTD)
#
CONFIG_MTD=y
CONFIG_MTD_DEBUG=y
CONFIG_MTD_DEBUG_VERBOSE=0
CONFIG_MTD_PARTITIONS=y
CONFIG_MTD_CONCAT=y
CONFIG_MTD_REDBOOT_PARTS=y

#
# User Modules And Translation Layers
#
CONFIG_MTD_CHAR=y
CONFIG_MTD_BLOCK=y
CONFIG_FTL=y
CONFIG_NFTL=y
CONFIG_NFTL_RW=y

#
# RAM/ROM/Flash chip drivers
#
CONFIG_MTD_CFI=y
CONFIG_MTD_JEDECPROBE=y
CONFIG_MTD_GEN_PROBE=y
CONFIG_MTD_CFI_ADV_OPTIONS=y
# CONFIG_MTD_CFI_NOSWAP is not set
CONFIG_MTD_CFI_BE_BYTE_SWAP=y
# CONFIG_MTD_CFI_LE_BYTE_SWAP is not set
CONFIG_MTD_CFI_GEOMETRY=y
CONFIG_MTD_CFI_B1=y
CONFIG_MTD_CFI_B2=y
CONFIG_MTD_CFI_B4=y
CONFIG_MTD_CFI_I1=y
CONFIG_MTD_CFI_I2=y
CONFIG_MTD_CFI_I4=y
CONFIG_MTD_CFI_INTELEXT=y
CONFIG_MTD_CFI_AMDSTD=y
CONFIG_MTD_RAM=y
CONFIG_MTD_ROM=y
CONFIG_MTD_ABSENT=y
CONFIG_MTD_OBSOLETE_CHIPS=y
CONFIG_MTD_AMDSTD=y
CONFIG_MTD_SHARP=y
CONFIG_MTD_JEDEC=y

#
# Mapping drivers for chip access
#
CONFIG_MTD_PHYSMAP=y
CONFIG_MTD_PHYSMAP_START=8000000
CONFIG_MTD_PHYSMAP_LEN=4000000
CONFIG_MTD_PHYSMAP_BUSWIDTH=2
CONFIG_MTD_PNC2000=y
CONFIG_MTD_SC520CDP=y
CONFIG_MTD_NETSC520=y
CONFIG_MTD_SBC_GXX=y
CONFIG_MTD_ELAN_104NC=y
CONFIG_MTD_DILNETPC=y
CONFIG_MTD_DILNETPC_BOOTSIZE=80000
CONFIG_MTD_MIXMEM=y
CONFIG_MTD_OCTAGON=y
CONFIG_MTD_VMAX=y
CONFIG_MTD_SCx200_DOCFLASH=y
CONFIG_MTD_L440GX=y
CONFIG_MTD_AMD766ROM=y
CONFIG_MTD_ICH2ROM=y
CONFIG_MTD_PCI=y

#
# Self-contained MTD device drivers
#
CONFIG_MTD_PMC551=y
CONFIG_MTD_PMC551_BUGFIX=y
CONFIG_MTD_PMC551_DEBUG=y
CONFIG_MTD_SLRAM=y
CONFIG_MTD_MTDRAM=y
CONFIG_MTDRAM_TOTAL_SIZE=4096
CONFIG_MTDRAM_ERASE_SIZE=128
CONFIG_MTDRAM_ABS_POS=0
CONFIG_MTD_BLKMTD=y

#
# Disk-On-Chip Device Drivers
#
CONFIG_MTD_DOC1000=y
CONFIG_MTD_DOC2000=y
CONFIG_MTD_DOC2001=y
CONFIG_MTD_DOCPROBE=y
CONFIG_MTD_DOCPROBE_ADVANCED=y
CONFIG_MTD_DOCPROBE_ADDRESS=0
CONFIG_MTD_DOCPROBE_HIGH=y
CONFIG_MTD_DOCPROBE_55AA=y

#
# NAND Flash Device Drivers
#
CONFIG_MTD_NAND=y
CONFIG_MTD_NAND_ECC=y
CONFIG_MTD_NAND_VERIFY_WRITE=y

#
# Parallel port support
#
CONFIG_PARPORT=y
CONFIG_PARPORT_PC=y
CONFIG_PARPORT_PC_CML1=y
CONFIG_PARPORT_SERIAL=y
CONFIG_PARPORT_PC_FIFO=y
CONFIG_PARPORT_PC_SUPERIO=y
CONFIG_PARPORT_PC_PCMCIA=y
# CONFIG_PARPORT_AMIGA is not set
# CONFIG_PARPORT_MFC3 is not set
# CONFIG_PARPORT_ATARI is not set
# CONFIG_PARPORT_GSC is not set
# CONFIG_PARPORT_SUNBPP is not set
CONFIG_PARPORT_OTHER=y
CONFIG_PARPORT_1284=y

#
# Plug and Play configuration
#
CONFIG_PNP=y
CONFIG_ISAPNP=y

#
# Block devices
#
CONFIG_BLK_DEV_FD=y
CONFIG_BLK_DEV_PS2=y
CONFIG_BLK_DEV_XD=y
CONFIG_PARIDE=y
CONFIG_PARIDE_PARPORT=y

#
# Parallel IDE high-level drivers
#
CONFIG_PARIDE_PD=y
CONFIG_PARIDE_PCD=y
CONFIG_PARIDE_PF=y
CONFIG_PARIDE_PT=y
CONFIG_PARIDE_PG=y

#
# Parallel IDE protocol modules
#
CONFIG_PARIDE_ATEN=y
CONFIG_PARIDE_BPCK=y
CONFIG_PARIDE_BPCK6=y
CONFIG_PARIDE_COMM=y
CONFIG_PARIDE_DSTR=y
CONFIG_PARIDE_FIT2=y
CONFIG_PARIDE_FIT3=y
CONFIG_PARIDE_EPAT=y
CONFIG_PARIDE_EPATC8=y
CONFIG_PARIDE_EPIA=y
CONFIG_PARIDE_FRIQ=y
CONFIG_PARIDE_FRPW=y
CONFIG_PARIDE_KBIC=y
CONFIG_PARIDE_KTTI=y
CONFIG_PARIDE_ON20=y
CONFIG_PARIDE_ON26=y
CONFIG_BLK_CPQ_DA=y
CONFIG_BLK_CPQ_CISS_DA=y
CONFIG_CISS_SCSI_TAPE=y
CONFIG_BLK_DEV_DAC960=y
CONFIG_BLK_DEV_UMEM=y
CONFIG_BLK_DEV_LOOP=y
CONFIG_BLK_DEV_NBD=y
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_SIZE=4096
CONFIG_BLK_DEV_INITRD=y
CONFIG_BLK_STATS=y

#
# Multi-device support (RAID and LVM)
#
CONFIG_MD=y
CONFIG_BLK_DEV_MD=y
CONFIG_MD_LINEAR=y
CONFIG_MD_RAID0=y
CONFIG_MD_RAID1=y
CONFIG_MD_RAID5=y
CONFIG_MD_MULTIPATH=y
CONFIG_BLK_DEV_LVM=y

#
# Networking options
#
CONFIG_PACKET=y
CONFIG_PACKET_MMAP=y
CONFIG_NETLINK_DEV=y
CONFIG_NETFILTER=y
CONFIG_NETFILTER_DEBUG=y
CONFIG_FILTER=y
CONFIG_UNIX=y
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
CONFIG_IP_ADVANCED_ROUTER=y
CONFIG_IP_MULTIPLE_TABLES=y
CONFIG_IP_ROUTE_FWMARK=y
CONFIG_IP_ROUTE_NAT=y
CONFIG_IP_ROUTE_MULTIPATH=y
CONFIG_IP_ROUTE_TOS=y
CONFIG_IP_ROUTE_VERBOSE=y
CONFIG_IP_ROUTE_LARGE_TABLES=y
CONFIG_IP_PNP=y
CONFIG_IP_PNP_DHCP=y
CONFIG_IP_PNP_BOOTP=y
CONFIG_IP_PNP_RARP=y
CONFIG_NET_IPIP=y
CONFIG_NET_IPGRE=y
CONFIG_NET_IPGRE_BROADCAST=y
CONFIG_IP_MROUTE=y
CONFIG_IP_PIMSM_V1=y
CONFIG_IP_PIMSM_V2=y
CONFIG_ARPD=y
CONFIG_INET_ECN=y
CONFIG_SYN_COOKIES=y

#
#   IP: Netfilter Configuration
#
CONFIG_IP_NF_CONNTRACK=y
CONFIG_IP_NF_FTP=y
CONFIG_IP_NF_IRC=y
CONFIG_IP_NF_QUEUE=y
CONFIG_IP_NF_IPTABLES=y
CONFIG_IP_NF_MATCH_LIMIT=y
CONFIG_IP_NF_MATCH_MAC=y
CONFIG_IP_NF_MATCH_PKTTYPE=y
CONFIG_IP_NF_MATCH_MARK=y
CONFIG_IP_NF_MATCH_MULTIPORT=y
CONFIG_IP_NF_MATCH_TOS=y
CONFIG_IP_NF_MATCH_ECN=y
CONFIG_IP_NF_MATCH_DSCP=y
CONFIG_IP_NF_MATCH_AH_ESP=y
CONFIG_IP_NF_MATCH_LENGTH=y
CONFIG_IP_NF_MATCH_TTL=y
CONFIG_IP_NF_MATCH_TCPMSS=y
CONFIG_IP_NF_MATCH_HELPER=y
CONFIG_IP_NF_MATCH_STATE=y
CONFIG_IP_NF_MATCH_CONNTRACK=y
CONFIG_IP_NF_MATCH_UNCLEAN=y
CONFIG_IP_NF_MATCH_OWNER=y
CONFIG_IP_NF_FILTER=y
CONFIG_IP_NF_TARGET_REJECT=y
CONFIG_IP_NF_TARGET_MIRROR=y
CONFIG_IP_NF_NAT=y
CONFIG_IP_NF_NAT_NEEDED=y
CONFIG_IP_NF_TARGET_MASQUERADE=y
CONFIG_IP_NF_TARGET_REDIRECT=y
CONFIG_IP_NF_NAT_LOCAL=y
CONFIG_IP_NF_NAT_SNMP_BASIC=y
CONFIG_IP_NF_NAT_IRC=y
CONFIG_IP_NF_NAT_FTP=y
CONFIG_IP_NF_MANGLE=y
CONFIG_IP_NF_TARGET_TOS=y
CONFIG_IP_NF_TARGET_ECN=y
CONFIG_IP_NF_TARGET_DSCP=y
CONFIG_IP_NF_TARGET_MARK=y
CONFIG_IP_NF_TARGET_LOG=y
CONFIG_IP_NF_TARGET_ULOG=y
CONFIG_IP_NF_TARGET_TCPMSS=y
CONFIG_IP_NF_ARPTABLES=y
CONFIG_IP_NF_ARPFILTER=y
CONFIG_IPV6=y

#
#   IPv6: Netfilter Configuration
#
CONFIG_IP6_NF_QUEUE=y
CONFIG_IP6_NF_IPTABLES=y
CONFIG_IP6_NF_MATCH_LIMIT=y
CONFIG_IP6_NF_MATCH_MAC=y
CONFIG_IP6_NF_MATCH_MULTIPORT=y
CONFIG_IP6_NF_MATCH_OWNER=y
CONFIG_IP6_NF_MATCH_MARK=y
CONFIG_IP6_NF_MATCH_LENGTH=y
CONFIG_IP6_NF_MATCH_EUI64=y
CONFIG_IP6_NF_FILTER=y
CONFIG_IP6_NF_TARGET_LOG=y
CONFIG_IP6_NF_MANGLE=y
CONFIG_IP6_NF_TARGET_MARK=y
CONFIG_KHTTPD=y
CONFIG_ATM=y
CONFIG_ATM_CLIP=y
CONFIG_ATM_CLIP_NO_ICMP=y
CONFIG_ATM_LANE=y
CONFIG_ATM_MPOA=y
CONFIG_ATM_BR2684=y
CONFIG_ATM_BR2684_IPFILTER=y
CONFIG_VLAN_8021Q=y

#
#  
#
CONFIG_IPX=y
CONFIG_IPX_INTERN=y
CONFIG_ATALK=y

#
# Appletalk devices
#
CONFIG_DEV_APPLETALK=y
CONFIG_LTPC=y
CONFIG_COPS=y
CONFIG_COPS_DAYNA=y
CONFIG_COPS_TANGENT=y
CONFIG_IPDDP=y
CONFIG_IPDDP_ENCAP=y
CONFIG_IPDDP_DECAP=y
CONFIG_DECNET=y
CONFIG_DECNET_SIOCGIFCONF=y
CONFIG_DECNET_ROUTER=y
CONFIG_DECNET_ROUTE_FWMARK=y
CONFIG_BRIDGE=y
CONFIG_X25=y
CONFIG_LAPB=y
CONFIG_LLC=y
CONFIG_NET_DIVERT=y
CONFIG_ECONET=y
CONFIG_ECONET_AUNUDP=y
CONFIG_ECONET_NATIVE=y
CONFIG_WAN_ROUTER=y
CONFIG_NET_FASTROUTE=y
CONFIG_NET_HW_FLOWCONTROL=y

#
# QoS and/or fair queueing
#
CONFIG_NET_SCHED=y
CONFIG_NET_SCH_CBQ=y
CONFIG_NET_SCH_HTB=y
CONFIG_NET_SCH_CSZ=y
CONFIG_NET_SCH_ATM=y
CONFIG_NET_SCH_PRIO=y
CONFIG_NET_SCH_RED=y
CONFIG_NET_SCH_SFQ=y
CONFIG_NET_SCH_TEQL=y
CONFIG_NET_SCH_TBF=y
CONFIG_NET_SCH_GRED=y
CONFIG_NET_SCH_DSMARK=y
CONFIG_NET_SCH_INGRESS=y
CONFIG_NET_QOS=y
CONFIG_NET_ESTIMATOR=y
CONFIG_NET_CLS=y
CONFIG_NET_CLS_TCINDEX=y
CONFIG_NET_CLS_ROUTE4=y
CONFIG_NET_CLS_ROUTE=y
CONFIG_NET_CLS_FW=y
CONFIG_NET_CLS_U32=y
CONFIG_NET_CLS_RSVP=y
CONFIG_NET_CLS_RSVP6=y
CONFIG_NET_CLS_POLICE=y

#
# Network testing
#
CONFIG_NET_PKTGEN=y

#
# Telephony Support
#
CONFIG_PHONE=y
CONFIG_PHONE_IXJ=y
CONFIG_PHONE_IXJ_PCMCIA=y

#
# ATA/IDE/MFM/RLL support
#
CONFIG_IDE=y

#
# IDE, ATA and ATAPI Block devices
#
CONFIG_BLK_DEV_IDE=y

#
# Please see Documentation/ide.txt for help/info on IDE drives
#
CONFIG_BLK_DEV_HD_IDE=y
CONFIG_BLK_DEV_HD=y
CONFIG_BLK_DEV_IDEDISK=y
CONFIG_IDEDISK_MULTI_MODE=y
CONFIG_IDEDISK_STROKE=y
CONFIG_BLK_DEV_IDECS=y
CONFIG_BLK_DEV_IDECD=y
CONFIG_BLK_DEV_IDETAPE=y
CONFIG_BLK_DEV_IDEFLOPPY=y
CONFIG_BLK_DEV_IDESCSI=y
CONFIG_IDE_TASK_IOCTL=y
CONFIG_IDE_TASKFILE_IO=y

#
# IDE chipset support/bugfixes
#
CONFIG_BLK_DEV_CMD640=y
CONFIG_BLK_DEV_CMD640_ENHANCED=y
CONFIG_BLK_DEV_ISAPNP=y
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_BLK_DEV_GENERIC=y
CONFIG_IDEPCI_SHARE_IRQ=y
CONFIG_BLK_DEV_IDEDMA_PCI=y
CONFIG_BLK_DEV_OFFBOARD=y
CONFIG_BLK_DEV_IDEDMA_FORCED=y
CONFIG_IDEDMA_PCI_AUTO=y
CONFIG_IDEDMA_ONLYDISK=y
CONFIG_BLK_DEV_IDEDMA=y
CONFIG_IDEDMA_PCI_WIP=y
CONFIG_BLK_DEV_ADMA=y
CONFIG_BLK_DEV_AEC62XX=y
CONFIG_BLK_DEV_ALI15X3=y
CONFIG_WDC_ALI15X3=y
CONFIG_BLK_DEV_AMD74XX=y
CONFIG_AMD74XX_OVERRIDE=y
CONFIG_BLK_DEV_CMD64X=y
CONFIG_BLK_DEV_CY82C693=y
CONFIG_BLK_DEV_CS5530=y
CONFIG_BLK_DEV_HPT34X=y
CONFIG_HPT34X_AUTODMA=y
CONFIG_BLK_DEV_HPT366=y
CONFIG_BLK_DEV_PIIX=y
CONFIG_BLK_DEV_NFORCE=y
CONFIG_BLK_DEV_NS87415=y
CONFIG_BLK_DEV_OPTI621=y
CONFIG_BLK_DEV_PDC202XX_OLD=y
CONFIG_PDC202XX_BURST=y
CONFIG_BLK_DEV_PDC202XX_NEW=y
CONFIG_PDC202XX_FORCE=y
CONFIG_BLK_DEV_RZ1000=y
CONFIG_BLK_DEV_SC1200=y
CONFIG_BLK_DEV_SVWKS=y
CONFIG_BLK_DEV_SIIMAGE=y
CONFIG_BLK_DEV_SIS5513=y
CONFIG_BLK_DEV_SLC90E66=y
CONFIG_BLK_DEV_TRM290=y
CONFIG_BLK_DEV_VIA82CXXX=y
CONFIG_IDE_CHIPSETS=y

#
# Note: most of these also require special kernel boot parameters
#
CONFIG_BLK_DEV_4DRIVES=y
CONFIG_BLK_DEV_ALI14XX=y
CONFIG_BLK_DEV_DTC2278=y
CONFIG_BLK_DEV_HT6560B=y
CONFIG_BLK_DEV_PDC4030=y
CONFIG_BLK_DEV_QD65XX=y
CONFIG_BLK_DEV_UMC8672=y
CONFIG_IDEDMA_AUTO=y
CONFIG_IDEDMA_IVB=y
# CONFIG_DMA_NONPCI is not set
CONFIG_BLK_DEV_PDC202XX=y
CONFIG_BLK_DEV_IDE_MODES=y
CONFIG_BLK_DEV_ATARAID=y
CONFIG_BLK_DEV_ATARAID_PDC=y
CONFIG_BLK_DEV_ATARAID_HPT=y

#
# SCSI support
#
CONFIG_SCSI=y

#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=y
CONFIG_SD_EXTRA_DEVS=40
CONFIG_CHR_DEV_ST=y
CONFIG_CHR_DEV_OSST=y
CONFIG_BLK_DEV_SR=y
CONFIG_BLK_DEV_SR_VENDOR=y
CONFIG_SR_EXTRA_DEVS=2
CONFIG_CHR_DEV_SG=y

#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs
#
CONFIG_SCSI_DEBUG_QUEUES=y
CONFIG_SCSI_MULTI_LUN=y
CONFIG_SCSI_CONSTANTS=y
CONFIG_SCSI_LOGGING=y

#
# SCSI low-level drivers
#
CONFIG_BLK_DEV_3W_XXXX_RAID=y
CONFIG_SCSI_7000FASST=y
CONFIG_SCSI_ACARD=y
CONFIG_SCSI_AHA152X=y
CONFIG_SCSI_AHA1542=y
CONFIG_SCSI_AHA1740=y
CONFIG_SCSI_AACRAID=y
CONFIG_SCSI_AIC7XXX=y
CONFIG_AIC7XXX_CMDS_PER_DEVICE=253
CONFIG_AIC7XXX_RESET_DELAY_MS=15000
CONFIG_AIC7XXX_PROBE_EISA_VL=y
CONFIG_AIC7XXX_BUILD_FIRMWARE=y
CONFIG_SCSI_DPT_I2O=y
CONFIG_SCSI_ADVANSYS=y
CONFIG_SCSI_IN2000=y
CONFIG_SCSI_AM53C974=y
CONFIG_SCSI_MEGARAID=y
CONFIG_SCSI_BUSLOGIC=y
CONFIG_SCSI_OMIT_FLASHPOINT=y
CONFIG_SCSI_CPQFCTS=y
CONFIG_SCSI_DMX3191D=y
CONFIG_SCSI_DTC3280=y
CONFIG_SCSI_EATA=y
CONFIG_SCSI_EATA_TAGGED_QUEUE=y
CONFIG_SCSI_EATA_LINKED_COMMANDS=y
CONFIG_SCSI_EATA_MAX_TAGS=16
CONFIG_SCSI_EATA_DMA=y
CONFIG_SCSI_EATA_PIO=y
CONFIG_SCSI_FUTURE_DOMAIN=y
CONFIG_SCSI_FD_MCS=y
CONFIG_SCSI_GDTH=y
CONFIG_SCSI_GENERIC_NCR5380=y
CONFIG_SCSI_GENERIC_NCR53C400=y
CONFIG_SCSI_G_NCR5380_PORT=y
# CONFIG_SCSI_G_NCR5380_MEM is not set
CONFIG_SCSI_IBMMCA=y
CONFIG_IBMMCA_SCSI_ORDER_STANDARD=y
CONFIG_IBMMCA_SCSI_DEV_RESET=y
CONFIG_SCSI_IPS=y
CONFIG_SCSI_INITIO=y
CONFIG_SCSI_INIA100=y
CONFIG_SCSI_PPA=y
CONFIG_SCSI_IMM=y
CONFIG_SCSI_IZIP_EPP16=y
CONFIG_SCSI_IZIP_SLOW_CTR=y
CONFIG_SCSI_NCR53C406A=y
CONFIG_SCSI_NCR_D700=y
CONFIG_53C700_IO_MAPPED=y
CONFIG_SCSI_NCR53C7xx=y
CONFIG_SCSI_NCR53C7xx_sync=y
CONFIG_SCSI_NCR53C7xx_FAST=y
CONFIG_SCSI_NCR53C7xx_DISCONNECT=y
CONFIG_SCSI_SYM53C8XX_2=y
CONFIG_SCSI_SYM53C8XX_DMA_ADDRESSING_MODE=1
CONFIG_SCSI_SYM53C8XX_DEFAULT_TAGS=16
CONFIG_SCSI_SYM53C8XX_MAX_TAGS=64
CONFIG_SCSI_SYM53C8XX_IOMAPPED=y
CONFIG_SCSI_MCA_53C9X=y
CONFIG_SCSI_PAS16=y
CONFIG_SCSI_PCI2000=y
CONFIG_SCSI_PCI2220I=y
CONFIG_SCSI_PSI240I=y
CONFIG_SCSI_QLOGIC_FAS=y
CONFIG_SCSI_QLOGIC_ISP=y
CONFIG_SCSI_QLOGIC_FC=y
CONFIG_SCSI_QLOGIC_FC_FIRMWARE=y
CONFIG_SCSI_QLOGIC_1280=y
CONFIG_SCSI_SEAGATE=y
CONFIG_SCSI_SIM710=y
CONFIG_SCSI_SYM53C416=y
CONFIG_SCSI_DC390T=y
CONFIG_SCSI_DC390T_NOGENSUPP=y
CONFIG_SCSI_T128=y
CONFIG_SCSI_U14_34F=y
CONFIG_SCSI_U14_34F_LINKED_COMMANDS=y
CONFIG_SCSI_U14_34F_MAX_TAGS=8
CONFIG_SCSI_ULTRASTOR=y
CONFIG_SCSI_DEBUG=y

#
# PCMCIA SCSI adapter support
#
CONFIG_SCSI_PCMCIA=y

#
# Fusion MPT device support
#
CONFIG_FUSION=y
CONFIG_FUSION_BOOT=y
CONFIG_FUSION_MAX_SGE=40
CONFIG_FUSION_LAN=y
CONFIG_NET_FC=y

#
# IEEE 1394 (FireWire) support (EXPERIMENTAL)
#
CONFIG_IEEE1394=y

#
# Device Drivers
#
CONFIG_IEEE1394_PCILYNX=y
CONFIG_IEEE1394_OHCI1394=y

#
# Protocol Drivers
#
CONFIG_IEEE1394_VIDEO1394=y
CONFIG_IEEE1394_SBP2=y
CONFIG_IEEE1394_SBP2_PHYS_DMA=y
CONFIG_IEEE1394_ETH1394=y
CONFIG_IEEE1394_DV1394=y
CONFIG_IEEE1394_RAWIO=y
CONFIG_IEEE1394_CMP=y
CONFIG_IEEE1394_AMDTP=y
CONFIG_IEEE1394_VERBOSEDEBUG=y

#
# I2O device support
#
CONFIG_I2O=y
CONFIG_I2O_PCI=y
CONFIG_I2O_BLOCK=y
CONFIG_I2O_LAN=y
CONFIG_I2O_SCSI=y
CONFIG_I2O_PROC=y

#
# Network device support
#
CONFIG_NETDEVICES=y

#
# ARCnet devices
#
CONFIG_ARCNET=y
CONFIG_ARCNET_1201=y
CONFIG_ARCNET_1051=y
CONFIG_ARCNET_RAW=y
CONFIG_ARCNET_COM90xx=y
CONFIG_ARCNET_COM90xxIO=y
CONFIG_ARCNET_RIM_I=y
CONFIG_ARCNET_COM20020=y
CONFIG_ARCNET_COM20020_ISA=y
CONFIG_ARCNET_COM20020_PCI=y
CONFIG_DUMMY=y
CONFIG_BONDING=y
CONFIG_EQUALIZER=y
CONFIG_TUN=y
CONFIG_ETHERTAP=y
CONFIG_NET_SB1000=y

#
# Ethernet (10 or 100Mbit)
#
CONFIG_NET_ETHERNET=y
# CONFIG_SUNLANCE is not set
CONFIG_HAPPYMEAL=y
# CONFIG_SUNBMAC is not set
# CONFIG_SUNQE is not set
CONFIG_SUNGEM=y
CONFIG_NET_VENDOR_3COM=y
CONFIG_EL1=y
CONFIG_EL2=y
CONFIG_ELPLUS=y
CONFIG_EL16=y
CONFIG_EL3=y
CONFIG_3C515=y
CONFIG_ELMC=y
CONFIG_ELMC_II=y
CONFIG_VORTEX=y
CONFIG_LANCE=y
CONFIG_NET_VENDOR_SMC=y
CONFIG_WD80x3=y
CONFIG_ULTRAMCA=y
CONFIG_ULTRA=y
CONFIG_ULTRA32=y
CONFIG_SMC9194=y
CONFIG_NET_VENDOR_RACAL=y
CONFIG_NI5010=y
CONFIG_NI52=y
CONFIG_NI65=y
CONFIG_AT1700=y
CONFIG_DEPCA=y
CONFIG_HP100=y
CONFIG_NET_ISA=y
CONFIG_E2100=y
CONFIG_EWRK3=y
CONFIG_EEXPRESS=y
CONFIG_EEXPRESS_PRO=y
CONFIG_HPLAN_PLUS=y
CONFIG_HPLAN=y
CONFIG_LP486E=y
CONFIG_ETH16I=y
CONFIG_NE2000=y
CONFIG_SKMC=y
CONFIG_NE2_MCA=y
CONFIG_IBMLANA=y
CONFIG_NET_PCI=y
CONFIG_PCNET32=y
CONFIG_ADAPTEC_STARFIRE=y
CONFIG_AC3200=y
CONFIG_APRICOT=y
CONFIG_CS89x0=y
CONFIG_TULIP=y
CONFIG_TULIP_MWI=y
CONFIG_TULIP_MMIO=y
CONFIG_DE4X5=y
CONFIG_DGRS=y
CONFIG_DM9102=y
CONFIG_EEPRO100=y
CONFIG_E100=y
CONFIG_LNE390=y
CONFIG_FEALNX=y
CONFIG_NATSEMI=y
CONFIG_NE2K_PCI=y
CONFIG_NE3210=y
CONFIG_ES3210=y
CONFIG_8139CP=y
CONFIG_8139TOO=y
CONFIG_8139TOO_PIO=y
CONFIG_8139TOO_TUNE_TWISTER=y
CONFIG_8139TOO_8129=y
# CONFIG_8139_OLD_RX_RESET is not set
CONFIG_SIS900=y
CONFIG_EPIC100=y
CONFIG_SUNDANCE=y
CONFIG_SUNDANCE_MMIO=y
CONFIG_TLAN=y
CONFIG_TC35815=y
CONFIG_VIA_RHINE=y
CONFIG_VIA_RHINE_MMIO=y
CONFIG_WINBOND_840=y
CONFIG_NET_POCKET=y
CONFIG_ATP=y
CONFIG_DE600=y
CONFIG_DE620=y

#
# Ethernet (1000 Mbit)
#
CONFIG_ACENIC=y
CONFIG_ACENIC_OMIT_TIGON_I=y
CONFIG_DL2K=y
CONFIG_E1000=y
# CONFIG_MYRI_SBUS is not set
CONFIG_NS83820=y
CONFIG_HAMACHI=y
CONFIG_YELLOWFIN=y
CONFIG_R8169=y
CONFIG_SK98LIN=y
CONFIG_TIGON3=y
CONFIG_FDDI=y
CONFIG_DEFXX=y
CONFIG_SKFP=y
CONFIG_HIPPI=y
CONFIG_ROADRUNNER=y
CONFIG_ROADRUNNER_LARGE_RINGS=y
CONFIG_PLIP=y
CONFIG_PPP=y
CONFIG_PPP_MULTILINK=y
CONFIG_PPP_FILTER=y
CONFIG_PPP_ASYNC=y
CONFIG_PPP_SYNC_TTY=y
CONFIG_PPP_DEFLATE=y
CONFIG_PPP_BSDCOMP=y
CONFIG_PPPOE=y
CONFIG_PPPOATM=y
CONFIG_SLIP=y
CONFIG_SLIP_COMPRESSED=y
CONFIG_SLIP_SMART=y
CONFIG_SLIP_MODE_SLIP6=y

#
# Wireless LAN (non-hamradio)
#
CONFIG_NET_RADIO=y
CONFIG_STRIP=y
CONFIG_WAVELAN=y
CONFIG_ARLAN=y
CONFIG_AIRONET4500=y
CONFIG_AIRONET4500_NONCS=y
CONFIG_AIRONET4500_PNP=y
CONFIG_AIRONET4500_PCI=y
CONFIG_AIRONET4500_ISA=y
CONFIG_AIRONET4500_I365=y
CONFIG_AIRO=y
CONFIG_HERMES=y
CONFIG_PLX_HERMES=y
CONFIG_PCI_HERMES=y

#
# Wireless Pcmcia cards support
#
CONFIG_PCMCIA_HERMES=y
CONFIG_AIRO_CS=y
CONFIG_NET_WIRELESS=y

#
# Token Ring devices
#
CONFIG_TR=y
CONFIG_IBMTR=y
CONFIG_IBMOL=y
CONFIG_IBMLS=y
CONFIG_3C359=y
CONFIG_TMS380TR=y
CONFIG_TMSPCI=y
CONFIG_TMSISA=y
CONFIG_ABYSS=y
CONFIG_MADGEMC=y
CONFIG_SMCTR=y
CONFIG_NET_FC=y
CONFIG_IPHASE5526=y
CONFIG_RCPCI=y
CONFIG_SHAPER=y

#
# Wan interfaces
#
CONFIG_WAN=y
CONFIG_COMX=y
CONFIG_COMX_HW_COMX=y
CONFIG_COMX_HW_LOCOMX=y
CONFIG_COMX_HW_MIXCOM=y
CONFIG_COMX_HW_MUNICH=y
CONFIG_COMX_PROTO_PPP=y
CONFIG_COMX_PROTO_LAPB=y
CONFIG_COMX_PROTO_FR=y
CONFIG_FARSYNC=y
CONFIG_LANMEDIA=y
CONFIG_ATI_XX20=y
CONFIG_SYNCLINK_SYNCPPP=y
CONFIG_HDLC=y
CONFIG_HDLC_PPP=y
CONFIG_HDLC_X25=y
CONFIG_N2=y
CONFIG_C101=y
CONFIG_DLCI=y
CONFIG_DLCI_COUNT=24
CONFIG_DLCI_MAX=8
CONFIG_SDLA=y
CONFIG_WAN_ROUTER_DRIVERS=y
CONFIG_VENDOR_SANGOMA=y
CONFIG_WANPIPE_CHDLC=y
CONFIG_WANPIPE_FR=y
CONFIG_WANPIPE_X25=y
CONFIG_WANPIPE_PPP=y
CONFIG_WANPIPE_MULTPPP=y
CONFIG_CYCLADES_SYNC=y
CONFIG_CYCLOMX_X25=y
CONFIG_LAPBETHER=y
CONFIG_X25_ASY=y
CONFIG_SBNI=y
CONFIG_SBNI_MULTILINE=y

#
# PCMCIA network device support
#
CONFIG_NET_PCMCIA=y
CONFIG_PCMCIA_3C589=y
CONFIG_PCMCIA_3C574=y
CONFIG_PCMCIA_FMVJ18X=y
CONFIG_PCMCIA_PCNET=y
CONFIG_PCMCIA_AXNET=y
CONFIG_PCMCIA_NMCLAN=y
CONFIG_PCMCIA_SMC91C92=y
CONFIG_PCMCIA_XIRC2PS=y
CONFIG_ARCNET_COM20020_CS=y
CONFIG_PCMCIA_XIRCOM=y
CONFIG_PCMCIA_XIRTULIP=y
CONFIG_NET_PCMCIA_RADIO=y
CONFIG_PCMCIA_RAYCS=y
CONFIG_PCMCIA_NETWAVE=y
CONFIG_PCMCIA_WAVELAN=y
CONFIG_AIRONET4500_CS=y

#
# ATM drivers
#
CONFIG_ATM_TCP=y
CONFIG_ATM_LANAI=y
CONFIG_ATM_ENI=y
CONFIG_ATM_ENI_DEBUG=y
CONFIG_ATM_ENI_TUNE_BURST=y
CONFIG_ATM_ENI_BURST_TX_16W=y
CONFIG_ATM_ENI_BURST_TX_8W=y
CONFIG_ATM_ENI_BURST_TX_4W=y
CONFIG_ATM_ENI_BURST_TX_2W=y
CONFIG_ATM_ENI_BURST_RX_16W=y
CONFIG_ATM_ENI_BURST_RX_8W=y
CONFIG_ATM_ENI_BURST_RX_4W=y
CONFIG_ATM_ENI_BURST_RX_2W=y
CONFIG_ATM_FIRESTREAM=y
CONFIG_ATM_ZATM=y
CONFIG_ATM_ZATM_DEBUG=y
CONFIG_ATM_ZATM_EXACT_TS=y
CONFIG_ATM_NICSTAR=y
CONFIG_ATM_NICSTAR_USE_SUNI=y
CONFIG_ATM_NICSTAR_USE_IDT77105=y
CONFIG_ATM_IDT77252=y
CONFIG_ATM_IDT77252_DEBUG=y
CONFIG_ATM_IDT77252_RCV_ALL=y
CONFIG_ATM_IDT77252_USE_SUNI=y
CONFIG_ATM_AMBASSADOR=y
CONFIG_ATM_AMBASSADOR_DEBUG=y
CONFIG_ATM_HORIZON=y
CONFIG_ATM_HORIZON_DEBUG=y
CONFIG_ATM_IA=y
CONFIG_ATM_IA_DEBUG=y
CONFIG_ATM_FORE200E_MAYBE=y
CONFIG_ATM_FORE200E_PCA=y
CONFIG_ATM_FORE200E_PCA_DEFAULT_FW=y
CONFIG_ATM_FORE200E_TX_RETRY=16
CONFIG_ATM_FORE200E_DEBUG=0
CONFIG_ATM_FORE200E=y

#
# Amateur Radio support
#
CONFIG_HAMRADIO=y

#
# Packet Radio protocols
#
CONFIG_AX25=y
CONFIG_AX25_DAMA_SLAVE=y
CONFIG_NETROM=y
CONFIG_ROSE=y

#
# AX.25 network device drivers
#

#
# AX.25 network device drivers
#
CONFIG_MKISS=y
CONFIG_6PACK=y
CONFIG_BPQETHER=y
CONFIG_DMASCC=y
CONFIG_SCC=y
CONFIG_SCC_DELAY=y
CONFIG_SCC_TRXECHO=y
CONFIG_BAYCOM_SER_FDX=y
CONFIG_BAYCOM_SER_HDX=y
CONFIG_BAYCOM_PAR=y
CONFIG_BAYCOM_EPP=y
CONFIG_SOUNDMODEM=y
CONFIG_SOUNDMODEM_SBC=y
CONFIG_SOUNDMODEM_WSS=y
CONFIG_SOUNDMODEM_AFSK1200=y
CONFIG_SOUNDMODEM_AFSK2400_7=y
CONFIG_SOUNDMODEM_AFSK2400_8=y
CONFIG_SOUNDMODEM_AFSK2666=y
CONFIG_SOUNDMODEM_HAPN4800=y
CONFIG_SOUNDMODEM_PSK4800=y
CONFIG_SOUNDMODEM_FSK9600=y
CONFIG_YAM=y

#
# IrDA (infrared) support
#
CONFIG_IRDA=y

#
# IrDA protocols
#
CONFIG_IRLAN=y
CONFIG_IRNET=y
CONFIG_IRCOMM=y
CONFIG_IRDA_ULTRA=y

#
# IrDA options
#
CONFIG_IRDA_CACHE_LAST_LSAP=y
CONFIG_IRDA_FAST_RR=y
CONFIG_IRDA_DEBUG=y

#
# Infrared-port device drivers
#

#
# SIR device drivers
#
CONFIG_IRTTY_SIR=y
CONFIG_IRPORT_SIR=y

#
# Dongle support
#
CONFIG_DONGLE=y
CONFIG_ESI_DONGLE=y
CONFIG_ACTISYS_DONGLE=y
CONFIG_TEKRAM_DONGLE=y
CONFIG_GIRBIL_DONGLE=y
CONFIG_LITELINK_DONGLE=y
CONFIG_MCP2120_DONGLE=y
CONFIG_OLD_BELKIN_DONGLE=y
CONFIG_ACT200L_DONGLE=y
CONFIG_MA600_DONGLE=y

#
# FIR device drivers
#
CONFIG_USB_IRDA=y
CONFIG_NSC_FIR=y
CONFIG_WINBOND_FIR=y
CONFIG_TOSHIBA_FIR=y
CONFIG_SMC_IRCC_FIR=y
CONFIG_ALI_FIR=y
CONFIG_VLSI_FIR=y

#
# ISDN subsystem
#
CONFIG_ISDN=y
CONFIG_ISDN_BOOL=y
CONFIG_ISDN_PPP=y
CONFIG_ISDN_PPP_VJ=y
CONFIG_ISDN_MPP=y
CONFIG_ISDN_PPP_BSDCOMP=y
CONFIG_ISDN_AUDIO=y
CONFIG_ISDN_TTY_FAX=y
CONFIG_ISDN_X25=y

#
# ISDN feature submodules
#
CONFIG_ISDN_DRV_LOOP=y
CONFIG_ISDN_DIVERSION=y

#
# low-level hardware drivers
#

#
# Passive ISDN cards
#
CONFIG_ISDN_DRV_HISAX=y
CONFIG_ISDN_HISAX=y

#
#   D-channel protocol features
#
CONFIG_HISAX_EURO=y
CONFIG_DE_AOC=y
CONFIG_HISAX_NO_SENDCOMPLETE=y
CONFIG_HISAX_NO_LLC=y
CONFIG_HISAX_NO_KEYPAD=y
CONFIG_HISAX_1TR6=y
CONFIG_HISAX_NI1=y
CONFIG_HISAX_MAX_CARDS=8

#
#   HiSax supported cards
#
CONFIG_HISAX_16_0=y
CONFIG_HISAX_16_3=y
CONFIG_HISAX_AVM_A1=y
CONFIG_HISAX_IX1MICROR2=y
CONFIG_HISAX_ASUSCOM=y
CONFIG_HISAX_TELEINT=y
CONFIG_HISAX_HFCS=y
CONFIG_HISAX_SPORTSTER=y
CONFIG_HISAX_MIC=y
CONFIG_HISAX_ISURF=y
CONFIG_HISAX_HSTSAPHIR=y
CONFIG_HISAX_TELESPCI=y
CONFIG_HISAX_S0BOX=y
CONFIG_HISAX_FRITZPCI=y
CONFIG_HISAX_AVM_A1_PCMCIA=y
CONFIG_HISAX_ELSA=y
CONFIG_HISAX_DIEHLDIVA=y
CONFIG_HISAX_SEDLBAUER=y
CONFIG_HISAX_NETJET=y
CONFIG_HISAX_NETJET_U=y
CONFIG_HISAX_NICCY=y
CONFIG_HISAX_BKM_A4T=y
CONFIG_HISAX_SCT_QUADRO=y
CONFIG_HISAX_GAZEL=y
CONFIG_HISAX_HFC_PCI=y
CONFIG_HISAX_W6692=y
CONFIG_HISAX_HFC_SX=y
CONFIG_HISAX_ENTERNOW_PCI=y
CONFIG_HISAX_DEBUG=y
CONFIG_HISAX_SEDLBAUER_CS=y
CONFIG_HISAX_ELSA_CS=y
CONFIG_HISAX_AVM_A1_CS=y
CONFIG_HISAX_ST5481=y
CONFIG_HISAX_FRITZ_PCIPNP=y

#
# Active ISDN cards
#
CONFIG_ISDN_DRV_ICN=y
CONFIG_ISDN_DRV_PCBIT=y
CONFIG_ISDN_DRV_SC=y
CONFIG_ISDN_DRV_ACT2000=y
CONFIG_ISDN_DRV_EICON=y
CONFIG_ISDN_DRV_EICON_DIVAS=y
CONFIG_ISDN_DRV_TPAM=y
CONFIG_ISDN_CAPI=y
CONFIG_ISDN_DRV_AVMB1_VERBOSE_REASON=y
CONFIG_ISDN_CAPI_MIDDLEWARE=y
CONFIG_ISDN_CAPI_CAPI20=y
CONFIG_ISDN_CAPI_CAPIFS_BOOL=y
CONFIG_ISDN_CAPI_CAPIFS=y
CONFIG_ISDN_CAPI_CAPIDRV=y
CONFIG_ISDN_DRV_AVMB1_B1ISA=y
CONFIG_ISDN_DRV_AVMB1_B1PCI=y
CONFIG_ISDN_DRV_AVMB1_B1PCIV4=y
CONFIG_ISDN_DRV_AVMB1_T1ISA=y
CONFIG_ISDN_DRV_AVMB1_B1PCMCIA=y
CONFIG_ISDN_DRV_AVMB1_AVM_CS=y
CONFIG_ISDN_DRV_AVMB1_T1PCI=y
CONFIG_ISDN_DRV_AVMB1_C4=y
# CONFIG_HYSDN_CAPI is not set

#
# Old CD-ROM drivers (not SCSI, not IDE)
#
CONFIG_CD_NO_IDESCSI=y
CONFIG_AZTCD=y
CONFIG_GSCD=y
CONFIG_SBPCD=y
CONFIG_SBPCD2=y
CONFIG_SBPCD3=y
CONFIG_SBPCD4=y
CONFIG_MCD=y
CONFIG_MCD_IRQ=11
CONFIG_MCD_BASE=300
CONFIG_MCDX=y
CONFIG_OPTCD=y
CONFIG_CM206=y
CONFIG_SJCD=y
CONFIG_ISP16_CDI=y
CONFIG_CDU31A=y
CONFIG_CDU535=y

#
# Input core support
#
CONFIG_INPUT=y
CONFIG_INPUT_KEYBDEV=y
CONFIG_INPUT_MOUSEDEV=y
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
CONFIG_INPUT_JOYDEV=y
CONFIG_INPUT_EVDEV=y

#
# Character devices
#
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_SERIAL=y
CONFIG_SERIAL_CONSOLE=y
CONFIG_SERIAL_EXTENDED=y
CONFIG_SERIAL_MANY_PORTS=y
CONFIG_SERIAL_SHARE_IRQ=y
CONFIG_SERIAL_DETECT_IRQ=y
CONFIG_SERIAL_MULTIPORT=y
CONFIG_HUB6=y
CONFIG_SERIAL_NONSTANDARD=y
CONFIG_COMPUTONE=y
CONFIG_ROCKETPORT=y
CONFIG_CYCLADES=y
CONFIG_CYZ_INTR=y
CONFIG_DIGIEPCA=y
CONFIG_ESPSERIAL=y
CONFIG_MOXA_INTELLIO=y
CONFIG_MOXA_SMARTIO=y
CONFIG_SYNCLINK=y
CONFIG_SYNCLINKMP=y
CONFIG_N_HDLC=y
CONFIG_RISCOM8=y
CONFIG_SPECIALIX=y
CONFIG_SPECIALIX_RTSCTS=y
CONFIG_SX=y
CONFIG_RIO=y
CONFIG_RIO_OLDPCI=y
CONFIG_STALDRV=y
CONFIG_STALLION=y
CONFIG_ISTALLION=y
CONFIG_UNIX98_PTYS=y
CONFIG_UNIX98_PTY_COUNT=256
CONFIG_PRINTER=y
CONFIG_LP_CONSOLE=y
CONFIG_PPDEV=y

#
# I2C support
#
CONFIG_I2C=y
CONFIG_I2C_ALGOBIT=y
CONFIG_I2C_PHILIPSPAR=y
CONFIG_I2C_ELV=y
CONFIG_I2C_VELLEMAN=y
CONFIG_I2C_ALGOPCF=y
CONFIG_I2C_ELEKTOR=y
CONFIG_I2C_CHARDEV=y
CONFIG_I2C_PROC=y

#
# Mice
#
CONFIG_BUSMOUSE=y
CONFIG_ATIXL_BUSMOUSE=y
CONFIG_LOGIBUSMOUSE=y
CONFIG_MS_BUSMOUSE=y
CONFIG_MOUSE=y
CONFIG_PSMOUSE=y
CONFIG_82C710_MOUSE=y
CONFIG_PC110_PAD=y
CONFIG_MK712_MOUSE=y

#
# Joysticks
#
CONFIG_INPUT_GAMEPORT=y
CONFIG_INPUT_NS558=y
CONFIG_INPUT_LIGHTNING=y
CONFIG_INPUT_PCIGAME=y
CONFIG_INPUT_CS461X=y
CONFIG_INPUT_EMU10K1=y
CONFIG_INPUT_SERIO=y
CONFIG_INPUT_SERPORT=y

#
# Joysticks
#
CONFIG_INPUT_ANALOG=y
CONFIG_INPUT_A3D=y
CONFIG_INPUT_ADI=y
CONFIG_INPUT_COBRA=y
CONFIG_INPUT_GF2K=y
CONFIG_INPUT_GRIP=y
CONFIG_INPUT_INTERACT=y
CONFIG_INPUT_TMDC=y
CONFIG_INPUT_SIDEWINDER=y
CONFIG_INPUT_IFORCE_USB=y
CONFIG_INPUT_IFORCE_232=y
CONFIG_INPUT_WARRIOR=y
CONFIG_INPUT_MAGELLAN=y
CONFIG_INPUT_SPACEORB=y
CONFIG_INPUT_SPACEBALL=y
CONFIG_INPUT_STINGER=y
CONFIG_INPUT_DB9=y
CONFIG_INPUT_GAMECON=y
CONFIG_INPUT_TURBOGRAFX=y
CONFIG_QIC02_TAPE=y
CONFIG_QIC02_DYNCONF=y

#
#   Setting runtime QIC-02 configuration is done with qic02conf
#

#
#   from the tpqic02-support package.  It is available at
#

#
#   metalab.unc.edu or ftp://titus.cfw.com/pub/Linux/util/
#

#
# Watchdog Cards
#
CONFIG_WATCHDOG=y
CONFIG_WATCHDOG_NOWAYOUT=y
CONFIG_ACQUIRE_WDT=y
CONFIG_ADVANTECH_WDT=y
CONFIG_ALIM7101_WDT=y
CONFIG_SC520_WDT=y
CONFIG_PCWATCHDOG=y
CONFIG_EUROTECH_WDT=y
CONFIG_IB700_WDT=y
CONFIG_WAFER_WDT=y
CONFIG_I810_TCO=y
CONFIG_MIXCOMWD=y
CONFIG_60XX_WDT=y
CONFIG_SC1200_WDT=y
CONFIG_SCx200_WDT=y
CONFIG_SOFT_WATCHDOG=y
CONFIG_W83877F_WDT=y
CONFIG_WDT=y
CONFIG_WDTPCI=y
CONFIG_WDT_501=y
CONFIG_WDT_501_FAN=y
CONFIG_MACHZ_WDT=y
CONFIG_AMD7XX_TCO=y
CONFIG_SCx200_GPIO=y
CONFIG_AMD_RNG=y
CONFIG_INTEL_RNG=y
CONFIG_AMD_PM768=y
CONFIG_NVRAM=y
CONFIG_RTC=y
CONFIG_DTLK=y
CONFIG_R3964=y
CONFIG_APPLICOM=y
CONFIG_SONYPI=y

#
# Ftape, the floppy tape device driver
#
CONFIG_FTAPE=y
CONFIG_ZFTAPE=y
CONFIG_ZFT_DFLT_BLK_SZ=10240

#
#   The compressor will be built as a module only!
#
CONFIG_ZFT_COMPRESSOR=m
CONFIG_FT_NR_BUFFERS=3
CONFIG_FT_PROC_FS=y
CONFIG_FT_NORMAL_DEBUG=y
# CONFIG_FT_FULL_DEBUG is not set
# CONFIG_FT_NO_TRACE is not set
# CONFIG_FT_NO_TRACE_AT_ALL is not set

#
# Hardware configuration
#
CONFIG_FT_STD_FDC=y
# CONFIG_FT_MACH2 is not set
# CONFIG_FT_PROBE_FC10 is not set
# CONFIG_FT_ALT_FDC is not set
CONFIG_FT_FDC_THR=8
CONFIG_FT_FDC_MAX_RATE=2000
CONFIG_FT_ALPHA_CLOCK=0
CONFIG_AGP=y
CONFIG_AGP_INTEL=y
CONFIG_AGP_I810=y
CONFIG_AGP_VIA=y
CONFIG_AGP_AMD=y
CONFIG_AGP_AMD_8151=y
CONFIG_AGP_SIS=y
CONFIG_AGP_ALI=y
CONFIG_AGP_SWORKS=y
CONFIG_DRM=y
# CONFIG_DRM_OLD is not set

#
# DRM 4.1 drivers
#
CONFIG_DRM_NEW=y
CONFIG_DRM_TDFX=y
CONFIG_DRM_R128=y
CONFIG_DRM_RADEON=y
CONFIG_DRM_I810=y
# CONFIG_DRM_I810_XFREE_41 is not set
CONFIG_DRM_I830=y
CONFIG_DRM_MGA=y
CONFIG_DRM_SIS=y

#
# PCMCIA character devices
#
CONFIG_PCMCIA_SERIAL_CS=y
CONFIG_PCMCIA_CHRDEV=y
CONFIG_SYNCLINK_CS=y
CONFIG_MWAVE=y

#
# Multimedia devices
#
CONFIG_VIDEO_DEV=y

#
# Video For Linux
#
CONFIG_VIDEO_PROC_FS=y
CONFIG_I2C_PARPORT=y

#
# Video Adapters
#
CONFIG_VIDEO_BT848=y
CONFIG_VIDEO_PMS=y
CONFIG_VIDEO_BWQCAM=y
CONFIG_VIDEO_CQCAM=y
CONFIG_VIDEO_W9966=y
CONFIG_VIDEO_CPIA=y
CONFIG_VIDEO_CPIA_PP=y
CONFIG_VIDEO_CPIA_USB=y
CONFIG_VIDEO_SAA5249=y
CONFIG_TUNER_3036=y
CONFIG_VIDEO_STRADIS=y
CONFIG_VIDEO_ZORAN=y
CONFIG_VIDEO_ZORAN_BUZ=y
CONFIG_VIDEO_ZORAN_DC10=y
CONFIG_VIDEO_ZORAN_LML33=y
CONFIG_VIDEO_ZR36120=y
CONFIG_VIDEO_MEYE=y

#
# Radio Adapters
#
CONFIG_RADIO_CADET=y
CONFIG_RADIO_RTRACK=y
CONFIG_RADIO_RTRACK_PORT=20f
CONFIG_RADIO_RTRACK2=y
CONFIG_RADIO_RTRACK2_PORT=30c
CONFIG_RADIO_AZTECH=y
CONFIG_RADIO_AZTECH_PORT=350
CONFIG_RADIO_GEMTEK=y
CONFIG_RADIO_GEMTEK_PORT=34c
CONFIG_RADIO_GEMTEK_PCI=y
CONFIG_RADIO_MAXIRADIO=y
CONFIG_RADIO_MAESTRO=y
CONFIG_RADIO_MIROPCM20=y
CONFIG_RADIO_MIROPCM20_RDS=y
CONFIG_RADIO_SF16FMI=y
CONFIG_RADIO_TERRATEC=y
CONFIG_RADIO_TERRATEC_PORT=590
CONFIG_RADIO_TRUST=y
CONFIG_RADIO_TRUST_PORT=350
CONFIG_RADIO_TYPHOON=y
CONFIG_RADIO_TYPHOON_PROC_FS=y
CONFIG_RADIO_TYPHOON_PORT=316
CONFIG_RADIO_TYPHOON_MUTEFREQ=87500
CONFIG_RADIO_ZOLTRIX=y
CONFIG_RADIO_ZOLTRIX_PORT=20c

#
# File systems
#
CONFIG_QUOTA=y
CONFIG_AUTOFS_FS=y
CONFIG_AUTOFS4_FS=y
CONFIG_REISERFS_FS=y
CONFIG_REISERFS_CHECK=y
CONFIG_REISERFS_PROC_INFO=y
CONFIG_ADFS_FS=y
CONFIG_ADFS_FS_RW=y
CONFIG_AFFS_FS=y
CONFIG_HFS_FS=y
CONFIG_BEFS_FS=y
CONFIG_BEFS_DEBUG=y
CONFIG_BFS_FS=y
CONFIG_EXT3_FS=y
CONFIG_JBD=y
CONFIG_JBD_DEBUG=y
CONFIG_FAT_FS=y
CONFIG_MSDOS_FS=y
CONFIG_UMSDOS_FS=y
CONFIG_VFAT_FS=y
CONFIG_EFS_FS=y
CONFIG_JFFS_FS=y
CONFIG_JFFS_FS_VERBOSE=0
CONFIG_JFFS_PROC_FS=y
CONFIG_JFFS2_FS=y
CONFIG_JFFS2_FS_DEBUG=0
CONFIG_CRAMFS=y
CONFIG_TMPFS=y
CONFIG_RAMFS=y
CONFIG_ISO9660_FS=y
CONFIG_JOLIET=y
CONFIG_ZISOFS=y
CONFIG_JFS_FS=y
CONFIG_JFS_DEBUG=y
CONFIG_JFS_STATISTICS=y
CONFIG_MINIX_FS=y
CONFIG_VXFS_FS=y
CONFIG_NTFS_FS=y
CONFIG_NTFS_RW=y
CONFIG_HPFS_FS=y
CONFIG_PROC_FS=y
CONFIG_DEVFS_FS=y
CONFIG_DEVFS_MOUNT=y
CONFIG_DEVFS_DEBUG=y
CONFIG_DEVPTS_FS=y
CONFIG_QNX4FS_FS=y
CONFIG_QNX4FS_RW=y
CONFIG_ROMFS_FS=y
CONFIG_EXT2_FS=y
CONFIG_SYSV_FS=y
CONFIG_UDF_FS=y
CONFIG_UDF_RW=y
CONFIG_UFS_FS=y
CONFIG_UFS_FS_WRITE=y

#
# Network File Systems
#
CONFIG_CODA_FS=y
CONFIG_INTERMEZZO_FS=y
CONFIG_NFS_FS=y
CONFIG_NFS_V3=y
CONFIG_ROOT_NFS=y
CONFIG_NFSD=y
CONFIG_NFSD_V3=y
CONFIG_NFSD_TCP=y
CONFIG_SUNRPC=y
CONFIG_LOCKD=y
CONFIG_LOCKD_V4=y
CONFIG_SMB_FS=y
CONFIG_SMB_NLS_DEFAULT=y
CONFIG_SMB_NLS_REMOTE="cp437"
CONFIG_NCP_FS=y
CONFIG_NCPFS_PACKET_SIGNING=y
CONFIG_NCPFS_IOCTL_LOCKING=y
CONFIG_NCPFS_STRONG=y
CONFIG_NCPFS_NFS_NS=y
CONFIG_NCPFS_OS2_NS=y
CONFIG_NCPFS_SMALLDOS=y
CONFIG_NCPFS_NLS=y
CONFIG_NCPFS_EXTRAS=y
CONFIG_ZISOFS_FS=y

#
# Partition Types
#
CONFIG_PARTITION_ADVANCED=y
CONFIG_ACORN_PARTITION=y
CONFIG_ACORN_PARTITION_ICS=y
CONFIG_ACORN_PARTITION_ADFS=y
CONFIG_ACORN_PARTITION_POWERTEC=y
CONFIG_ACORN_PARTITION_RISCIX=y
CONFIG_OSF_PARTITION=y
CONFIG_AMIGA_PARTITION=y
CONFIG_ATARI_PARTITION=y
CONFIG_MAC_PARTITION=y
CONFIG_MSDOS_PARTITION=y
CONFIG_BSD_DISKLABEL=y
CONFIG_MINIX_SUBPARTITION=y
CONFIG_SOLARIS_X86_PARTITION=y
CONFIG_UNIXWARE_DISKLABEL=y
CONFIG_LDM_PARTITION=y
CONFIG_LDM_DEBUG=y
CONFIG_SGI_PARTITION=y
CONFIG_ULTRIX_PARTITION=y
CONFIG_SUN_PARTITION=y
CONFIG_EFI_PARTITION=y
CONFIG_SMB_NLS=y
CONFIG_NLS=y

#
# Native Language Support
#
CONFIG_NLS_DEFAULT="iso8859-1"
CONFIG_NLS_CODEPAGE_437=y
CONFIG_NLS_CODEPAGE_737=y
CONFIG_NLS_CODEPAGE_775=y
CONFIG_NLS_CODEPAGE_850=y
CONFIG_NLS_CODEPAGE_852=y
CONFIG_NLS_CODEPAGE_855=y
CONFIG_NLS_CODEPAGE_857=y
CONFIG_NLS_CODEPAGE_860=y
CONFIG_NLS_CODEPAGE_861=y
CONFIG_NLS_CODEPAGE_862=y
CONFIG_NLS_CODEPAGE_863=y
CONFIG_NLS_CODEPAGE_864=y
CONFIG_NLS_CODEPAGE_865=y
CONFIG_NLS_CODEPAGE_866=y
CONFIG_NLS_CODEPAGE_869=y
CONFIG_NLS_CODEPAGE_936=y
CONFIG_NLS_CODEPAGE_950=y
CONFIG_NLS_CODEPAGE_932=y
CONFIG_NLS_CODEPAGE_949=y
CONFIG_NLS_CODEPAGE_874=y
CONFIG_NLS_ISO8859_8=y
CONFIG_NLS_CODEPAGE_1250=y
CONFIG_NLS_CODEPAGE_1251=y
CONFIG_NLS_ISO8859_1=y
CONFIG_NLS_ISO8859_2=y
CONFIG_NLS_ISO8859_3=y
CONFIG_NLS_ISO8859_4=y
CONFIG_NLS_ISO8859_5=y
CONFIG_NLS_ISO8859_6=y
CONFIG_NLS_ISO8859_7=y
CONFIG_NLS_ISO8859_9=y
CONFIG_NLS_ISO8859_13=y
CONFIG_NLS_ISO8859_14=y
CONFIG_NLS_ISO8859_15=y
CONFIG_NLS_KOI8_R=y
CONFIG_NLS_KOI8_U=y
CONFIG_NLS_UTF8=y

#
# Console drivers
#
CONFIG_VGA_CONSOLE=y
CONFIG_VIDEO_SELECT=y
CONFIG_MDA_CONSOLE=y

#
# Frame-buffer support
#
CONFIG_FB=y
CONFIG_DUMMY_CONSOLE=y
CONFIG_FB_RIVA=y
CONFIG_FB_CLGEN=y
CONFIG_FB_PM2=y
CONFIG_FB_PM2_FIFO_DISCONNECT=y
CONFIG_FB_PM2_PCI=y
CONFIG_FB_PM3=y
CONFIG_FB_CYBER2000=y
CONFIG_FB_VESA=y
CONFIG_FB_VGA16=y
CONFIG_FB_HGA=y
CONFIG_VIDEO_SELECT=y
CONFIG_FB_MATROX=y
CONFIG_FB_MATROX_MILLENIUM=y
CONFIG_FB_MATROX_MYSTIQUE=y
CONFIG_FB_MATROX_G100=y
CONFIG_FB_MATROX_I2C=y
CONFIG_FB_MATROX_MAVEN=y
CONFIG_FB_MATROX_G450=y
CONFIG_FB_MATROX_MULTIHEAD=y
CONFIG_FB_ATY=y
CONFIG_FB_ATY_GX=y
CONFIG_FB_ATY_CT=y
CONFIG_FB_RADEON=y
CONFIG_FB_ATY128=y
CONFIG_FB_SIS=y
CONFIG_FB_SIS_300=y
CONFIG_FB_SIS_315=y
CONFIG_FB_NEOMAGIC=y
CONFIG_FB_3DFX=y
CONFIG_FB_VOODOO1=y
CONFIG_FB_TRIDENT=y
CONFIG_FB_VIRTUAL=y
CONFIG_FBCON_ADVANCED=y
CONFIG_FBCON_MFB=y
CONFIG_FBCON_CFB2=y
CONFIG_FBCON_CFB4=y
CONFIG_FBCON_CFB8=y
CONFIG_FBCON_CFB16=y
CONFIG_FBCON_CFB24=y
CONFIG_FBCON_CFB32=y
CONFIG_FBCON_AFB=y
CONFIG_FBCON_ILBM=y
CONFIG_FBCON_IPLAN2P2=y
CONFIG_FBCON_IPLAN2P4=y
CONFIG_FBCON_IPLAN2P8=y
CONFIG_FBCON_MAC=y
CONFIG_FBCON_VGA_PLANES=y
CONFIG_FBCON_VGA=y
CONFIG_FBCON_HGA=y
CONFIG_FBCON_FONTWIDTH8_ONLY=y
CONFIG_FBCON_FONTS=y
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y
CONFIG_FONT_SUN8x16=y
CONFIG_FONT_PEARL_8x8=y
CONFIG_FONT_ACORN_8x8=y

#
# Sound
#
CONFIG_SOUND=y
CONFIG_SOUND_ALI5455=y
CONFIG_SOUND_BT878=y
CONFIG_SOUND_CMPCI=y
CONFIG_SOUND_CMPCI_FM=y
CONFIG_SOUND_CMPCI_FMIO=388
CONFIG_SOUND_CMPCI_FMIO=388
CONFIG_SOUND_CMPCI_MIDI=y
CONFIG_SOUND_CMPCI_MPUIO=330
CONFIG_SOUND_CMPCI_JOYSTICK=y
CONFIG_SOUND_CMPCI_CM8738=y
CONFIG_SOUND_CMPCI_SPDIFINVERSE=y
CONFIG_SOUND_CMPCI_SPDIFLOOP=y
CONFIG_SOUND_CMPCI_SPEAKERS=2
CONFIG_SOUND_EMU10K1=y
CONFIG_MIDI_EMU10K1=y
CONFIG_SOUND_FUSION=y
CONFIG_SOUND_CS4281=y
CONFIG_SOUND_ES1370=y
CONFIG_SOUND_ES1371=y
CONFIG_SOUND_ESSSOLO1=y
CONFIG_SOUND_MAESTRO=y
CONFIG_SOUND_MAESTRO3=y
CONFIG_SOUND_FORTE=y
CONFIG_SOUND_ICH=y
CONFIG_SOUND_RME96XX=y
CONFIG_SOUND_SONICVIBES=y
CONFIG_SOUND_TRIDENT=y
# CONFIG_SOUND_MSNDCLAS is not set
# CONFIG_SOUND_MSNDPIN is not set
CONFIG_SOUND_VIA82CXXX=y
CONFIG_MIDI_VIA82CXXX=y
CONFIG_SOUND_OSS=y
CONFIG_SOUND_TRACEINIT=y
CONFIG_SOUND_DMAP=y
CONFIG_SOUND_AD1816=y
CONFIG_SOUND_SGALAXY=y
CONFIG_SOUND_ADLIB=y
CONFIG_SOUND_ACI_MIXER=y
CONFIG_SOUND_CS4232=y
CONFIG_SOUND_SSCAPE=y
CONFIG_SOUND_GUS=y
CONFIG_SOUND_GUS16=y
CONFIG_SOUND_GUSMAX=y
CONFIG_SOUND_VMIDI=y
CONFIG_SOUND_TRIX=y
# CONFIG_TRIX_HAVE_BOOT is not set
CONFIG_SOUND_MSS=y
CONFIG_SOUND_MPU401=y
CONFIG_SOUND_NM256=y
CONFIG_SOUND_MAD16=y
CONFIG_MAD16_OLDCARD=y
CONFIG_SOUND_PAS=y
CONFIG_PAS_JOYSTICK=y
CONFIG_SOUND_PSS=y
CONFIG_PSS_MIXER=y
# CONFIG_PSS_HAVE_BOOT is not set
CONFIG_SOUND_SB=y
CONFIG_SOUND_AWE32_SYNTH=y
CONFIG_SOUND_MAUI=y
# CONFIG_MAUI_HAVE_BOOT is not set
CONFIG_SOUND_YM3812=y
CONFIG_SOUND_OPL3SA1=y
CONFIG_SOUND_OPL3SA2=y
CONFIG_SOUND_YMFPCI=y
CONFIG_SOUND_YMFPCI_LEGACY=y
CONFIG_SOUND_UART6850=y
CONFIG_SOUND_AEDSP16=y
CONFIG_SC6600=y
CONFIG_SC6600_JOY=y
CONFIG_SC6600_CDROM=4
CONFIG_SC6600_CDROMBASE=0
CONFIG_AEDSP16_SBPRO=y
CONFIG_AEDSP16_MPU401=y
CONFIG_SOUND_TVMIXER=y
CONFIG_INPUT_GAMEPORT=y

#
# USB support
#
CONFIG_USB=y
CONFIG_USB_DEBUG=y

#
# Miscellaneous USB options
#
CONFIG_USB_DEVICEFS=y
CONFIG_USB_BANDWIDTH=y
CONFIG_USB_LONG_TIMEOUT=y

#
# USB Host Controller Drivers
#
CONFIG_USB_EHCI_HCD=y
CONFIG_USB_UHCI_ALT=y
CONFIG_USB_OHCI=y

#
# USB Device Class drivers
#
CONFIG_USB_AUDIO=y
CONFIG_USB_EMI26=y

#
#   USB Bluetooth can only be used with disabled Bluetooth subsystem
#
CONFIG_USB_MIDI=y
CONFIG_USB_STORAGE=y
CONFIG_USB_STORAGE_DEBUG=y
CONFIG_USB_STORAGE_DATAFAB=y
CONFIG_USB_STORAGE_FREECOM=y
CONFIG_USB_STORAGE_ISD200=y
CONFIG_USB_STORAGE_DPCM=y
CONFIG_USB_STORAGE_HP8200e=y
CONFIG_USB_STORAGE_SDDR09=y
CONFIG_USB_STORAGE_SDDR55=y
CONFIG_USB_STORAGE_JUMPSHOT=y
CONFIG_USB_ACM=y
CONFIG_USB_PRINTER=y

#
# USB Human Interface Devices (HID)
#
CONFIG_USB_HID=y
CONFIG_USB_HIDINPUT=y
CONFIG_USB_HIDDEV=y
CONFIG_USB_AIPTEK=y
CONFIG_USB_WACOM=y
CONFIG_USB_POWERMATE=y

#
# USB Imaging devices
#
CONFIG_USB_DC2XX=y
CONFIG_USB_MDC800=y
CONFIG_USB_SCANNER=y
CONFIG_USB_MICROTEK=y
CONFIG_USB_HPUSBSCSI=y

#
# USB Multimedia devices
#
CONFIG_USB_IBMCAM=y
CONFIG_USB_OV511=y
CONFIG_USB_PWC=y
CONFIG_USB_SE401=y
CONFIG_USB_STV680=y
CONFIG_USB_VICAM=y
CONFIG_USB_DSBR=y
CONFIG_USB_DABUSB=y

#
# USB Network adaptors
#
CONFIG_USB_PEGASUS=y
CONFIG_USB_RTL8150=y
CONFIG_USB_KAWETH=y
CONFIG_USB_CATC=y
CONFIG_USB_CDCETHER=y
CONFIG_USB_USBNET=y

#
# USB port drivers
#
CONFIG_USB_USS720=y

#
# USB Serial Converter support
#
CONFIG_USB_SERIAL=y
CONFIG_USB_SERIAL_DEBUG=y
CONFIG_USB_SERIAL_GENERIC=y
CONFIG_USB_SERIAL_BELKIN=y
CONFIG_USB_SERIAL_WHITEHEAT=y
CONFIG_USB_SERIAL_DIGI_ACCELEPORT=y
CONFIG_USB_SERIAL_EMPEG=y
CONFIG_USB_SERIAL_FTDI_SIO=y
CONFIG_USB_SERIAL_VISOR=y
CONFIG_USB_SERIAL_IPAQ=y
CONFIG_USB_SERIAL_IR=y
CONFIG_USB_SERIAL_EDGEPORT=y
CONFIG_USB_SERIAL_EDGEPORT_TI=y
CONFIG_USB_SERIAL_KEYSPAN_PDA=y
CONFIG_USB_SERIAL_KEYSPAN=y
CONFIG_USB_SERIAL_KEYSPAN_USA28=y
CONFIG_USB_SERIAL_KEYSPAN_USA28X=y
CONFIG_USB_SERIAL_KEYSPAN_USA28XA=y
CONFIG_USB_SERIAL_KEYSPAN_USA28XB=y
CONFIG_USB_SERIAL_KEYSPAN_USA19=y
CONFIG_USB_SERIAL_KEYSPAN_USA18X=y
CONFIG_USB_SERIAL_KEYSPAN_USA19W=y
CONFIG_USB_SERIAL_KEYSPAN_USA19QW=y
CONFIG_USB_SERIAL_KEYSPAN_USA19QI=y
CONFIG_USB_SERIAL_KEYSPAN_USA49W=y
CONFIG_USB_SERIAL_MCT_U232=y
CONFIG_USB_SERIAL_KLSI=y
CONFIG_USB_SERIAL_PL2303=y
CONFIG_USB_SERIAL_CYBERJACK=y
CONFIG_USB_SERIAL_XIRCOM=y
CONFIG_USB_SERIAL_OMNINET=y

#
# USB Miscellaneous drivers
#
CONFIG_USB_RIO500=y
CONFIG_USB_AUERSWALD=y
CONFIG_USB_TIGL=y
CONFIG_USB_BRLVGER=y
CONFIG_USB_LCD=y

#
# Bluetooth support
#
CONFIG_BLUEZ=y
CONFIG_BLUEZ_L2CAP=y
CONFIG_BLUEZ_SCO=y
CONFIG_BLUEZ_RFCOMM=y
CONFIG_BLUEZ_RFCOMM_TTY=y
CONFIG_BLUEZ_BNEP=y
CONFIG_BLUEZ_BNEP_MC_FILTER=y
CONFIG_BLUEZ_BNEP_PROTO_FILTER=y

#
# Bluetooth device drivers
#
CONFIG_BLUEZ_HCIUSB=y
CONFIG_BLUEZ_USB_ZERO_PACKET=y
CONFIG_BLUEZ_HCIUART=y
CONFIG_BLUEZ_HCIUART_H4=y
CONFIG_BLUEZ_HCIUART_BCSP=y
CONFIG_BLUEZ_HCIUART_BCSP_TXCRC=y
CONFIG_BLUEZ_HCIDTL1=y
CONFIG_BLUEZ_HCIBT3C=y
CONFIG_BLUEZ_HCIBLUECARD=y
CONFIG_BLUEZ_HCIBTUART=y
CONFIG_BLUEZ_HCIVHCI=y

#
# Kernel hacking
#
CONFIG_DEBUG_KERNEL=y
CONFIG_DEBUG_STACKOVERFLOW=y
CONFIG_DEBUG_HIGHMEM=y
CONFIG_DEBUG_SLAB=y
CONFIG_DEBUG_IOVIRT=y
CONFIG_MAGIC_SYSRQ=y
CONFIG_DEBUG_SPINLOCK=y
CONFIG_FRAME_POINTER=y

#
# Library routines
#
CONFIG_ZLIB_INFLATE=y
CONFIG_ZLIB_DEFLATE=y

^ permalink raw reply

* Advice needed: changing the incoming network interface for a packet ?
From: Cédric de Launois @ 2002-12-12 15:03 UTC (permalink / raw)
  To: Netfilter Development Mailinglist

Recently someone asked the list for some technique to change a packet's
arriving interface. For example : when a pkt comes from eth0, we'd like
to make it come from eth1. But, nobody could give him a technique for
that.
I can easily add this feature in the ROUTE target, but I've got some
questions which need your advice :

1) Is it already possible to do that with the current netfilter and
   iproute2 code ? (seems not)

2) Is this feature really useful ? Seems yes, see the Jason Liao's mail
   on 06 Dec 2002.

3) Is this feature desirable ? One could think this feature could be
   dangerous, because it could introduce loops in routing.

Any opinion ?

Cédric de Launois

PS: the ROUTE target is used to do unusual routing with packets. It
can force selected packets to go out through a specified interface or
to be sent to a special gateway. The ROUTE target never modifies the
packets.

^ permalink raw reply

* multilink using Cable and ADSL.
From: tinozaure @ 2002-12-12 15:00 UTC (permalink / raw)
  To: netfilter
In-Reply-To: <3DF86BDD.2090505@istitutocolli.org>

Hello
I try to use a Cable ISP and ADSL ISP together on the same gateway to have
benefit from low latency cable and High Bandwith ADSL at the same time.

In this way I read lot of docs and essentialy the advanced routing HOWTO
which explain how to mark packets to route them on an interface or another.

I tried the examples but these doesn't work.

My Goal is to use Cable for low latency application and ADSL for all other
applications.

I need some help to understand how to proceed to realise this.


This is my actual situation.
eth0= 192.168.1.254 (DMZ )
eth1= 192.168.0.254 (LAN)
eth2= dynamic public ip (Cable ISP)
ppp0= dynamic public ip (ADSL ISP)

This is my simple iptables script for NAT

----------------START---------------
IPTABLES="/sbin/iptables"

echo "1" > /proc/sys/net/ipv4/ip_forward
echo "1" > /proc/sys/net/ipv4/ip_dynaddr
# Remise a Zero des regles du firewall au cas ou
$IPTABLES -F
$IPTABLES -t nat -F

echo Init des regles par defaut
$IPTABLES -P INPUT ACCEPT
$IPTABLES -P OUTPUT ACCEPT
$IPTABLES -P FORWARD ACCEPT


echo Debut des regles de filtrage

$IPTABLES -t nat -A POSTROUTING -s 192.168.0.0/23 -o ppp0 -j MASQUERADE

#Fin des regles de routage
echo "Firewall installé."
----------------END---------------

Thanks.



^ permalink raw reply

* Re: Linux 2.5.51
From: Eric W. Biederman @ 2002-12-12 15:02 UTC (permalink / raw)
  To: James Simmons
  Cc: Benjamin Herrenschmidt, Stian Jordet, Allan Duncan, linux-kernel
In-Reply-To: <Pine.LNX.4.33.0212110720540.2617-100000@maxwell.earthlink.net>

James Simmons <jsimmons@infradead.org> writes:

> Unfortunely ATI doesn't like to release info on what needs to be done to
> initialize without frimware. I really wish this was the case. I did see
> email back about someone getting a mach64 card working without firmware.
> They used a bus analysiser to do this. I will see what kind of patches I
> can dig up.

Thanks.

Eric


^ permalink raw reply

* Re: Linux 2.5.51
From: Eric W. Biederman @ 2002-12-12 15:01 UTC (permalink / raw)
  To: Benjamin Herrenschmidt
  Cc: James Simmons, Stian Jordet, Allan Duncan, linux-kernel
In-Reply-To: <1039602072.3539.42.camel@zion>

Benjamin Herrenschmidt <benh@kernel.crashing.org> writes:

> On Wed, 2002-12-11 at 10:25, Eric W. Biederman wrote:
> > > Well, I'm not sure it quite works yet. Maybe unaccelerated, but anyway,
> > > my version of radeonfb for 2.5 isn't accelerated yet anyway. I'll work
> > > on that (or Ani will) now that the API is stable enough.
> > 
> > How well does this driver work if you don't have a firmware
> > driver initialize the card? aka a pci option ROM.
> 
> Probably not at all

Well it was worth asking.
  
> > I am interested because with LinuxBIOS it is still a pain to run
> > PCI option roms, and I don't necessarily even have then if it a
> > motherboard with video.  There are some embedded/non-x86 platforms
> > with similar issues.  
> 
> Well, at least r128's and radeon's need the memory controller and PLLs
> initialized by the BIOS/firmware, we don't have documentation about how
> to acheive that ourselves (and this can depend on the specific wiring of
> a given card anyway).

I believe those actions have to be taken.  I haven't seen how flexible
the chips are with respect to which memory they take, which is
generally where most of the complexity comes in.

I have written northbridge memory initialization code that generally
does not depend on the motherboard, I would be very surprised to find
out that video card are generally more difficult (except in the area
of documentation).

> > My primary interest is in the cheap ATI Rage XL chip that is on many
> > server board. PCI Vendor/device  id 1002:4752 (rev 27) from lspci.
> > 
> > If nothing else if some one could point me to some resources on
> > how to get the appropriate documentation from the video chipset
> > manufacturers I would be happy.
> > 
> > But I did want to at least point that running a system with out bios
> > initialized video was certainly among the cases that are used.
> 
> This is not possible with most modern cards without specific POST code
> provided by the chip manufacturer.

Without documentation surely.  Though for that aspect of things
I primarily care about the cheap controllers that are used for onboard
video.  Which I suspect is a much simpler case to handle.  

Eric




^ permalink raw reply

* Re: orinoco_cs not working in 2.5.51
From: John M Flinchbaugh @ 2002-12-12 15:02 UTC (permalink / raw)
  To: Thomas Molina; +Cc: linux-kernel
In-Reply-To: <1039654621.1410.4.camel@lap>

[-- Attachment #1: Type: text/plain, Size: 635 bytes --]

On Wed, Dec 11, 2002 at 06:56:44PM -0600, Thomas Molina wrote:
> cs: memory probe 0x0c0000-0x0fffff: excluding 0xc0000-0xcbfff 
0xe0000-0xfffff
> orinoco_cs: RequestIRQ: Resource in use

i haven't completely tested my orinoco card with 2.5.51 yet, but i
know i've caused myself the same problems in previous kernels.

make sure you have ISA bus enabled.  those 16-bit cards apparently use
ISA.  that solved the problem for me before.
-- 
____________________}John Flinchbaugh{______________________
| glynis@hjsoft.com         http://www.hjsoft.com/~glynis/ |
~~Powered by Linux: Reboots are for hardware upgrades only~~

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

^ permalink raw reply

* Re: Aic7xxx v6.2.22 and Aic79xx v1.3.0Alpha2 Released
From: James Bottomley @ 2002-12-12 14:51 UTC (permalink / raw)
  To: Andrew Morton
  Cc: James Bottomley, Christoph Hellwig, Justin T. Gibbs, linux-scsi,
	Alan Cox, Marcelo Tosatti, Linus Torvalds
In-Reply-To: <3DF823FF.B3F2D5E5@digeo.com>

akpm@digeo.com said:
> Well I would test (and distribute) it too, but the above format is
> useless to me, as it is to most others.

If someone has an ftp server they could lend me, I'll dump patches against 
2.5.51 (or the later BK's) on it.  Alternatively, I could use my 
hansenpartnership website, but I don't want to run up against my (rather low) 
bandwidth limits.

James



^ permalink raw reply

* Floppy operation blocks ATA transfer ?
From: David Balazic @ 2002-12-12 14:55 UTC (permalink / raw)
  To: linux-kernel@vger.kernel.org

Hi!

While I was performing a "badblocks -nvs /dev/hdb" on VT1,
I did a "mcopy some.300k.file a:" and noticed that while the
file was written to the floppy, the badblocks process was
effectively blocked. The displayed sector number did not advance
and the drive LED was not blinking ( or lit ). After the "mcopy"
finished, "badblocks" continued. Is this normal and expected
behavior ? ( I sure did not expect it )

This is on a RHL 8.0 ( Psyche ) system with kernel-2.4.18-18.8.0

HW is :
Athlon 900, SiS 745 chipset
hda : Teac CD-W540E ( CD-RW )
hdb : Maxtor DiamondMax ( 4D040H2 ) 5400RPM , 40GB ATA100 harddrive
hdc : Teac CD-532E-B CDROM
hdd : IBM Deskstar 120GXP , 60GB harddrive

The "some.300k.file" was on /mnt/x which is /dev/hdd2 ( FAT32 )

I know this is a redhat patched kernel, but if any of you has
60 seconds time, please test this on your vanilla-linus ( or
any other version for that matter ) kernel and tell me if it
happens for you too.

Many thanks !
And please CC me with answers.

Regards,
David "only-amiga-can-really-multitask" Balazic

^ permalink raw reply

* Re: Agressive selective pre-allocation
From: Hans Reiser @ 2002-12-12 14:46 UTC (permalink / raw)
  To: Ragnar Kjørstad; +Cc: reiserfs-list
In-Reply-To: <20021212094754.S26400@vestdata.no>

Ragnar Kjørstad wrote:

>On Tue, Dec 10, 2002 at 12:12:28PM +0100, Stefan Fleiter wrote:
>  
>
>>>mbox's aren't an issue, if you have them then you probably don't care too
>>>much about performance anyway.
>>>      
>>>
>>I switched some large mailing lists with thousands of messages from mbox to
>>maildir with mutt. Changing mailboxes lasted maybe 2 or 3 times longer,
>>so I switched back to mbox *for speed*.
>>    
>>
>
>Yes, maildir is not always faster.
>
>First problem is disk-layout. The way it works with reiserfs3.6 and
>default hashes the inodes and files are written in different orders and
>the disk does a lot of unneeded seeks. 
>
You mean the names are written in an order different from the stat data 
and file bodies, and the stat data and file bodies have the same order.

This is because we sort filenames by filename, and  sort stat data and 
file bodies by objectid which tends to be ordered by creation time.

We should implement a plugin that sorts filenames by creation time, and 
that will cause our performance to resemble ext2 more (meaning that for 
large directories the performance will fall apart, but for small 
directories there might be some advantage from not sorting by name).  I 
think that sorting file bodies by filename would require a larger key, 
so I hesitate at that, but maybe it would be interesting to explore also.

>A workaround is to use a hash
>that automagicly orders inodes and files the same way. A better way is
>probably to store the stat-data with the directory-data. I think that is
>on the schedule, is it not?
>
No, not yet, it didn't make the 4.0 code freeze....  patches are 
welcomed....

>
>It is also important that readdir-order matches the ondisk layout, but
>that is perhaps already the case?
>
If you copy a directory, then after the copy the readdir order matches 
the ondisk layout.

>
>Possible the overhead of the systemcalls is also significant, but my
>guess is that it is negletable compared to io-performance.
>
>Next problem is readahead. When the whole mailbox is in a single file
>the OS is able to use readahead to improve performance, but it doesn't
>seem to work as well when reading a whole directory. This is perhaps the
>thoughest one to solve, IMHO.
>
It is not very hard to solve if we use packing locality readahead.

>
>
>However, the single most important fix would be the mail-clients. If I'm
>not mistaken mutt reads the whole mail, and that's simply not required.
>It should only read the headers. That will speed things up by a huge
>factor when you have mails with attachments and so on.  It must also learn 
>that it shouldn't reread the folder everytime it's updated!
>
>Right now the case is pretty much that none or few of the potential
>performance-benefits of maildir are made use of, and the drawbacks are
>hitting much harder then they ought to. I bet it's only temporary
>though. Reiserfs has the potential to make faster mailsystems with
>the use of maildir! :-)
>
>
>
>  
>



^ permalink raw reply

* fm801 driver status?
From: Friedrich Ewaldt @ 2002-12-12 14:45 UTC (permalink / raw)
  To: alsa-user, alsa-devel

Hi!

I've got a fm801 based sound card which locks my computer completely 
some seconds after loading the alsa driver module. I compiled drivers 
with debug=detect -- please see my mail(s) from 12/09/2002 on alsa 
userlist for more info. What else could I do? Meanwhile I found several 
reports describing the same problem.
Therefore my question(s): Should it be possible to run a fm801 soundcard 
using the 0.9.0rc6 or cvs driver? Anyone who has installed such a card 
successfully? Any ideas what I'm doing wrong? (I have installed some 
other soundcards using alsa09 without problems.)
Thanks a lot in advance!
fe



-------------------------------------------------------
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility 
Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/

^ permalink raw reply

* Re: Re: [LARTC] VRRPD (rfc2338)
From: Dmitry Golubev @ 2002-12-12 14:44 UTC (permalink / raw)
  To: lartc

Hello,

But as far as I know, there is no VRRP implementations that fully comply
with rfc2338 as it requires multiple MAC addresses for the one poor linux
box's interface. Maybe, someone can suggest a working solution of this
problem?

I have seen one idea, but haven't tested it yet (hope someone can try it out):

To bridge the physical iface with TAP on which the vrrpd (or keepalived) is
running. In that case we could make the VRRP-router that fully comply with RFC.

For more info see: http://www.math.leidenuniv.nl/pipermail/bridge/2002-June/002021.html

BR, Dmitry

==== At 2002-12-11, 03:56:00 you wrote: ===
>The daemon at http://www.keepalived.org/ is the VRRPd implementation 
>that's supposed to be the best. It's actually part of the Linux Virtual 
>Server project (layer 4 load balancer), but the author claims you should 
>be able to use it as a pure VRRP daemon -- although when I've read the 
>doc, I couldn't figure out how. (But don't be discouraged by my 
>impatience. :) It's supposed to be the most mature and ready-for-production.
>
>There's also Jerome Etienne's reference implementation (don't have a 
>URL, but it's easy to Google). However, I've heard from more than place 
>that this is too proof-of-concept and perhaps not production-worthy. 
>Here's a link to a paper about running VRRPd as the hotspare protocol 
>for linux firewalls (uses Jerome Etienne's implementation): 
>http://www.gnusec.com/resource/security/docs/HAFirewallLinux-VRRP.pdf.
>
>BTW, keep in mind that if you intend to use VRRP in an environment with 
>Cisco routers, you'll need to do some work on them too. Cisco routers do 
>not accept multicast MAC addresses as legit ARP replies by default. 
>Unfortunately, the VRRP RFC and all implementations use multicast MACs. 
>What that means is that you'll need to either 1) turn the switch on the 
>Cisco routers that makes them accept multicast MAC ARP replies (good), 
>or 2) put a static ARP entry in the Cisco routers for the VRRP multicast 
>MACs (better).
>
>Hope that helps.
>
>-S
>
>
>Anton Tinchev wrote:
>
>>Can someone point me for good VRRPD (rfc2338) implementation on linux.
>>Some stable and live project
>>Thanks
>>
>>_______________________________________________
>>LARTC mailing list / LARTC@mailman.ds9a.nl
>>http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
>>  
>>
>
>_______________________________________________
>LARTC mailing list / LARTC@mailman.ds9a.nl
>http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

			



_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

^ permalink raw reply

* Re: Filter by IP address problems
From: Joel Newkirk @ 2002-12-12 14:39 UTC (permalink / raw)
  To: Damon Brinkley, stewart.thompson; +Cc: netfilter
In-Reply-To: <1039702392.6682.14.camel@damon.betcolan>

On Thursday 12 December 2002 09:13 am, Damon Brinkley wrote:
> Thanks Stu but I'm still doing something wrong.
>
> Here's the rules I have now.
>
> ###############################
>
> echo 0 > /proc/sys/net/ipv4/ip_forward
>
> /sbin/modprobe iptable_nat
> /sbin/modprobe ip_conntrack
> /sbin/modprobe ip_conntrack_ftp
>
> /sbin/iptables -F
> /sbin/iptables -t nat -F
> /sbin/iptables -X
> /sbin/iptables -t nat -X
>
> /sbin/iptables -P INPUT DROP
> /sbin/iptables -P OUTPUT DROP
> /sbin/iptables -P FORWARD DROP
>
> # INPUT CHAIN
> # NONUSERS = 172.17.0.0/20
> /sbin/iptables -A INPUT -s $NONUSERS -j ACCEPT
>
> # FORWARD CHAIN
> /sbin/iptables -A FORWARD -s $NONUSERS -j ACCEPT
>
> # POSTROUTING
> /sbin/iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
>
> echo 1 > /proc/sys/net/ipv4/ip_forward
>
> ######################################
>
> This should give my laptop, IP 172.17.0.244, complete access but I get
> Request timed out when pinging www.yahoo.com
>
> Here's what I get when running iptables -nL

You can also run "iptables -t nat -nL" to show the nat table chains.  As 
with most iptables calls, if you don't specify it assumes filter table.

anyway, make sure you are also doing:
echo 1 > /proc/sys/net/ipv4/ip_dynaddr
so that it will actually have (and maintain) the current IP address for 
masquerading.

Finally, you are not allowing any return connection back to the laptop 
through the FORWARD chain.  Try adding:

/sbin/iptables -A FORWARD -d $NONUSERS -m state \
--state ESTABLISHED -j ACCEPT

and it should work for browsing.  If you use "ESTABLISHED,RELATED" 
instead then it should be more reliable, since it will allow icmp 
traffic related to the browsing.

Also, you are allowing the laptop to communicate to the firewall box 
local processes (INPUT) but not allowing anything back from it to the 
laptop (OUTPUT).  If you need them to communicate with each other, apart 
from the firewall forwarding (separate issues) then you need to allow 
communications in OUTPUT that go to the laptop as well, either simply 
ACCEPTing appropriate traffic, or using a state rule as above in OUTPUT 
to allow local processes on the firewall box to reply, but not initiate 
connections to the laptop.

I've never worked with ipchains, just iptables, but I gather that with 
ipchains it was necessary to allow traffic through INPUT in order to 
forward.  (I've seen this a lot this past week :^)  With iptables the 
packets hit prerouting then netfilter decides whether the packet is 
destined for the local box, or forwarding, and it goes to EITHER one or 
the other, but not both.  INPUT and OUTPUT are for the local box itself, 
and don't have any affect at all on forwarding, SNAT/DNAT, etc.

j



^ permalink raw reply

* Re: qlogic FC driver in 2.5
From: Matthew Jacob @ 2002-12-12 14:39 UTC (permalink / raw)
  To: Anton Blanchard; +Cc: linux-scsi
In-Reply-To: <20021212135124.GF6278@krispykreme>

I want to puclicly thank you for whipping this out so quick! I'll be
gratefully incorporating this all next week into the actual blob.

p.s.: alternate source for the driver blob is

	bk://bitkeeper.feral.com:9002






^ permalink raw reply

* Re: bbram access problems
From: Jörn Engel @ 2002-12-12 15:09 UTC (permalink / raw)
  To: Tobias Otto-Adamczak; +Cc: linux-mtd, Geoffroy Stevenne
In-Reply-To: <Pine.LNX.4.31.0212121456200.22502-100000@www.optixsoft.de>

On Thu, 12 December 2002 15:09:11 +0100, Tobias Otto-Adamczak wrote:
> [joern's ignorance of braindead pc hardware removed]
> 
> Other question: does the slram driver map this area in when it is
> already covered by the kernel ?

To my knowledge, yes. The driver is unaware of linux memory management
and simply ioremaps physical memory. If the kernel already uses this
area, you are in trouble.
But I think to remember that for i386 architecture the first 1MB of
memory has special treatment. Might be worth a look.

Jörn

-- 
Fantasy is more important than knowlegde. Knowlegde is limited,
while fantasy embraces the whole world.
-- Albert Einstein

^ permalink raw reply

* Re: QoS using HTB and SFQ ...
From: Tom Eastep @ 2002-12-12 14:34 UTC (permalink / raw)
  To: raymondl, Netfilter Mailing List
In-Reply-To: <1039684623.4085.47.camel@rayw.knowledgefactory.co.za>



--On Thursday, December 12, 2002 11:17:03 AM +0200 Raymond Leach 
<raymondl@knowledgefactory.co.za> wrote:

> Hi
>
> Does anyone have any experience (good or bad) with using htb and sfq to
> do QoS using 2.4.20 kernels?
>
> I compiled the kernel, installed the image, but tc tells me that htb is
> an unknown qdisc. I checked that I did select htb in the QoS section.
>

Works for me. Does the copy of tc that you are running have htb support?

-Tom
--
Tom Eastep   \ Shorewall - iptables made easy
Shoreline,    \ http://shorewall.sf.net
Washington USA \ teastep@shorewall.net



^ permalink raw reply

* DROP Fin Scan
From: Dade @ 2002-12-12 14:27 UTC (permalink / raw)
  To: netfilter
In-Reply-To: <20021124093933.24186.71076.Mailman@kashyyyk>

: 

Hi, 
I'd like to block all FIN SCAN type. In Internet I find the following method: 

iptables -A INPUT -p tcp --tcp-flags FIN,SYN FIN,SYN -j DROP 

but for me is better to write: 

iptables -A FORWARD -m state -state NEW -p tcp --tcp-flags FIN FIN -j DROP 

that means blocking all packets with flag FIN active regarding only packets 
belonging to new TCP connections. 
Are you agree? 
Thanks in advance, 
Davide

 
 





Scrive netfilter-request@lists.netfilter.org:

> Send netfilter mailing list submissions to
> 	netfilter@lists.netfilter.org
> 
> To subscribe or unsubscribe via the World Wide Web, visit
> 	https://lists.netfilter.org/mailman/listinfo/netfilter
> or, via email, send a message with subject or body 'help' to
> 	netfilter-request@lists.netfilter.org
> 
> You can reach the person managing the list at
> 	netfilter-admin@lists.netfilter.org
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of netfilter digest..."
> 
> 
> Today's Topics:
> 
>    1. Re: Am I making a bone-headed mistake with patch-o-matic ? (Brandon
> Broyles)
>    2. Packet filtering on the application layer (James Stickland)
>    3. Re: SNAT & Squence Numbers (Dax Kelson)
>    4. =?iso-8859-1?Q?Iptables_with_IP_Alias?=
> (=?iso-8859-1?Q?Juliano_Dapper?=)
>    5. cannot open shared object file: no such file or directory (James
> Stickland)
>    6. Re: [squid-users] How to allow traffic other than http (Colin
> Campbell)
>    7. DNAT to localhost (Nix N. Nix)
>    8. Re: Time based rules ... (Chris Poupart)
>    9. Netfilter 1.2.7a (debian), rule (DNAT) problems (040)
>   10. Re: Trojaned tcpdump and libpcap (Michael H. Warfield)
>   11. New to IP Tables (David Reta)
> 
> --__--__--
> 
> Message: 1
> From: "Brandon Broyles" <netfilter@drbroyles.com>
> To: <fabrice@netfilter.org>,
> 	<netfilter@lists.netfilter.org>
> Subject: Re: Am I making a bone-headed mistake with patch-o-matic ?
> Date: Sun, 24 Nov 2002 00:53:26 -0500
> 
> 
> ----- Original Message ----- 
> From: "Fabrice MARIE" <fabrice@netfilter.org>
> To: <netfilter@drbroyles.com>; <netfilter@lists.netfilter.org>
> Sent: Saturday, November 23, 2002 11:43 PM
> Subject: Re: Am I making a bone-headed mistake with patch-o-matic ?
> 
> > There is a problem though (fixed in the CVS, but not yet updated on the
> HTML page..)
> > you shouldn't run # make patch-o-matic, but instead from the
> patch-o-matic
> directory,
> > you should run the ./runme script with the patch suite you want to apply
> as a parameter.
> > The corrected SGML source of the document is there :
> >
> http://cvs.netfilter.org/cgi-bin/cvsweb/~checkout~/netfilter/documentation/H
> OWTO/netfilter-extensions-HOWTO.sgml
> 
> 
> From what I read in the above link, I think something may be wrong with my
> patch-o-matic I got via CVS.  I ran a (./runme base) and I got the
> following
> output.  In this output the only thing that is "Already applied:" is the
> first line.  Nothing else seems to be applied after that.  Plus, that link
> above references  switches ( Do you want to apply this patch [N/y/t/f/q/?]
> )
> that I am not getting.
> 
> *********************************************************************
> Each patch is a new feature: many have minimal impact, some do not.
> Almost every one has bugs, so I don't recommend applying them all!
> -------------------------------------------------------
> Already applied: submitted/2.4.18
>                  submitted/ahesp-static
>                  submitted/arptables
>                  submitted/config-cleanup
>                  submitted/conntrack?helper-unregister
>                  submitted/conntrack
>                  submitted/dscp
>                  submitted/DSCP
>                  submitted/ecn
>                  submitted/ECN
>                  submitted/helper
>                  submitted/ip6tables-export-symbols
>                  submitted/ip6tables-exthdr-bug-ipv6
>                  submitted/ip_conntrack_protocol_destroy
>                  submitted/ip_conntrack_protocol_unregister
>                  submitted/ip_nat_irc-srcaddr-fix
>                  submitted/ipt_MIRROR-ttl
>                  submitted/ipt_REJECT-checkentry
>                  submitted/ipt_unclean-ecn
>                  submitted/ipv6-agr-ipv6
>                  submitted/irc-dcc-mask
>                  submitted/length-ipv6
>                  submitted/local-nat
>                  submitted/log-tunnel-fix-ipv6
>                  submitted/macro-trailing-semicolon-fix
>                  submitted/mangle5hooks
>                  submitted/nat-export_symbols
>                  submitted/nat-memoryleak-fix
>                  submitted/netfilter-arp
>                  submitted/ownercmd
>                  submitted/pkttype
>                  submitted/REJECT-dont_fragment
>                  submitted/REJECT_mark
>                  submitted/remove_no_version
>                  submitted/skb_clone_copy
>                  submitted/TOS-oops-fix
>                  submitted/ulog-module-unload
>                  submitted/ulog-nlgroup-shift-fix
>                  submitted/ulog-sparc-bitops-fix
>                  submitted/unclean-udpchecksum
>                  submitted/z-newnat16
>                  submitted/z-newnat_assertfix
>                  submitted/z-newnat_changeexpect-lockfix
>                  pending/newnat-udp-helper
>                  base/ahesp6-ipv6
>                  base/frag6-ipv6
>                  base/fuzzy
>                  base/iplimit
>                  base/ipt_unclean-ubit
>                  base/ipv4options
>                  base/IPV4OPTSSTRIP
>                  base/ipv6header-ipv6
>                  base/mport
>                  base/NETLINK
>                  base/NETMAP
>                  base/nth
>                  base/opts6-ipv6
>                  base/pool
>                  base/psd
>                  base/quota
>                  base/random
>                  base/realm
>                  base/REJECT-ipv6
>                  base/route6-ipv6
>                  base/SAME
>                  base/time
>                  base/TTL
> 
> -----------------------------------------------------------------
> No more patches to apply! Q to Quit or ? for options [Q/a/r/b/?]
> Excellent! Kernel is now ready for compilation.
> *********************************************************************
> 
> I never get a chance to choose which patches I wish to install.  Before I
> wrote that first message to this mail list, I had already tried recompiling
> the kernel and iptables after I ran (./runme base).  Does it look like my
> patch-o-matic is working incorrectly?
> 
> Thanks,
> Brandon Broyles
> 
> 
> 
> 
> --__--__--
> 
> Message: 2
> Date: Mon, 11 Nov 2002 23:25:35 -0500 (EST)
> From: James Stickland <jimmy@sympatico.ca>
> To:  <netfilter@lists.netfilter.org>
> Subject: Packet filtering on the application layer
> 
> Is there any way with linux (or just netfilter) to filter out packets
> based upon whats analyzed in the application layer of a packet?
> 
> 
> 
> 
> --__--__--
> 
> Message: 3
> Subject: Re: SNAT & Squence Numbers
> From: Dax Kelson <Dax.Kelson@gurulabs.com>
> To: mike bramm <mike.bramm@bomberjacketproductions.com>
> Cc: netfilter@lists.netfilter.org
> Organization: Guru Labs
> Date: 12 Nov 2002 01:22:42 -0700
> 
> On Mon, 2002-11-11 at 10:23, mike bramm wrote:
> > Hi, 
> >     I'm a Router/PIX guy that is just getting into the Linux/IPTables
> > scene. I've read the man pages and searched the web for information on
> > IPTables. And I'm not able to find answers to some of my questions.
> > Maybe you can help? 
> >       * If SNAT is configured for many to one (PAT), then I would
> >         presume that the connections are tracked by sequence numbers.
> >         Are the sequence numbers picked randomly, like the PIX? And is
> >         there a range in with they are picked from? What mod does
> >         this?
> 
> AFAIK, the sequence numbers are left intact. I could be wrong though. A
> quick check with a packet sniffer should answer this.
> 
> >       * A syntax question. I've looked at alot of syntax examples and
> >         I've noticed one character that I can't seem to match up with
> >         any of the tutorials or man
> >         pages.                                                             
>                                            $IPTABLES -A INPUT $WAN_IFACE \ -j
> DROP   What the heck is "\"? It looks like it would be used to separate the
> match and the target, but is not really necessary. Is this just a personal
> preference or is it needed?
> 
> This isn't iptables syntax at all. 
> 
> The "\" at the end of a line is known as the continuation character.
> This is bourne shell syntax. It means that the next line should be
> treated as a continuation of the current line. The "\" character NOT at
> the end of the line, is the escape character and removes any special
> treatment of the following character and causes it to be treated
> literally.
> 
> Dax
> 
> 
> 
> --__--__--
> 
> Message: 4
> Date: Wed, 13 Nov 2002 01:12:17 +0000
> Subject: =?iso-8859-1?Q?Iptables_with_IP_Alias?=
> From: "=?iso-8859-1?Q?Juliano_Dapper?=" <fjdapper@terra.com.br>
> To: "=?iso-8859-1?Q?netfilter?=" <netfilter@lists.netfilter.org>
> 
> What's iptables not accept rules in ip alias, eth0:0, eth0:1?=0D=0AI have=
>  a linux box with 2 ips and i have create ruls to redirect traffic to int=
> ernal machine,ex:=0D=0Aiptables -t nat -A PREROUTING -p tcp -i eth0 --dpo=
> rt 25 -j DNAT --to 192.168.0.1=0D=0Aiptables -t nat -A PREROUTING -p tcp =
> -i etho:0 --dport 80 -j DNAT --to=0D=0A192.168.0.2=0D=0Aeth0 - 200.200.20=
> 0.1=0D=0Aeth0:0 - 200.200.200.2=0D=0A=0D=0ATkz...=0D=0A=0D=0A=0D=0A=0D=0A=
> 
> 
> 
> 
> --__--__--
> 
> Message: 5
> Date: Tue, 12 Nov 2002 21:27:38 -0500 (EST)
> From: James Stickland <jimmy@sympatico.ca>
> To:  <netfilter@lists.netfilter.org>
> Subject: cannot open shared object file: no such file or directory
> 
> Hi, i recently ran patch-o-matic to patch my kernel for the string match
> from the extra patches.
> 
> I ran patch-o-matic, and it copied the string files to
> /usr/src/linux/net/ipv4/netfilter.  Ok, so far so good.
> 
> I went to compile my kernel, and have ipt_string as a module.  I did so by
> adding the line CONFIG_IP_NF_MATCH_STRING=m in my /usr/src/linux/.config.
> 
> I proceeded to do the standard make dep ; make modules ; make
> modules_install ; make bzImage.  THe kernel compiled, i rebooted, and was
> successfully able to modprobe ipt_string.
> (/lib/modules/2.4.19/kernel/net/ipv4/netfilter/ipt_string.o)
> 
> However, when i went to make use of the ipt_string match in an iptables
> rule, i was given the following error:
> 
> iptables v1.2.7a: Couldn't load match
> `string':/usr/local/lib/iptables/libipt_st
> ring.so: cannot open shared object file: No such file or directory
> 
> Upon inspection, the libipt_string.so did not exist in
> /usr/local/lib/iptables.  How do i get this netfilter library to exist?
> 
> I had this problem the last time i patched my kernel to support ipt_psd,
> but i cannot recall how i was able to get the psd library to exist.
> 
> Did i miss a step while patching this time?  Anyone with help please
> respond to the list and my email directly - jamesstickland@sympatico.ca
> 
> Thank you.
> 
> 
> 
> 
> 
> 
> --__--__--
> 
> Message: 6
> Date: Wed, 13 Nov 2002 16:34:21 +1000 (EST)
> From: Colin Campbell <sgcccdc@citec.qld.gov.au>
> To: Glen Spidal <glens@cybercorpinc.com>
> Cc: Net Filter <netfilter@lists.netfilter.org>,
>    Squid Users <squid-users@squid-cache.org>
> Subject: Re: [squid-users] How to allow traffic other than http
> 
> On Tue, 12 Nov 2002, Glen Spidal wrote:
> 
> > I have servers set up as diagramed below.  Proxied web traffic work fine.
> > Email fails.
> > I can send mail from the Linux box via Pine.  Email server is at external
> > ISP.
> 
> Squid is an HTTP proxy. Either run an MTA (sendmail, postfix, exim, qmail,
> ....) on the squid server or let the wintel clients talk to the ISP's mail
> server  by routing (and natting?) through the squid server.
> 
>  Colin
> --
> Colin Campbell
> Unix Support/Postmaster/Hostmaster
> CITEC
> +61 7 3227 6334
> 
> 
> 
> --__--__--
> 
> Message: 7
> Subject: DNAT to localhost
> From: "Nix N. Nix" <nix@go-nix.ca>
> To: netfilter@lists.samba.org
> Organization: 
> Date: 13 Nov 2002 03:45:54 -0500
> 
> Why doesn't this work ?
> 
> /sbin/iptables -t nat -A PREROUTING -p udp --destination 192.168.1.1/32
> --dport 80 -j DNAT --to-destination 127.0.0.1:8080
> 
> The idea is:  The Web server listens solely on 127.0.0.1:8080 .  This
> allows me to run a Web server as a non-root user.  But then, I want
> ${OUTSIDE_IP}:80 and 192.168.1.1:80 (my interface) to be forwarded to
> 127.0.0.1:8080 .  I'm sure you've guessed by now that I'm running the
> Web server on my firewall ;o)
> 
> Anyway, I tried setting /proc/sys/net/ipv4/conf/lo/rp_filter to 0, but
> that didn't help either.
> 
> IMHO, the reason this doesn't work is that the above rule is added at
> the PREROUTING stage of the game.  So, when the packet is routed, the
> routing decision is based on 
> +----------------------+
> |  Packet              |
> +----------------------+
> |source:<192.168.1.xxx>|
> |dest:  <127.0.0.1>    |
> +----------------------+
> and, of course, somewhere, this packet gets dropped, because nothing
> should be able to reach 127.0.0.0/8 but 127.0.0.0/8, right ?  But hell,
> I'm no expert.
> 
> So, is there any way to forward TCP ports from local interfaces to the
> loopback interface ?
> 
> 
> 
> Thanks for your advice.
> 
> 
> 
> --__--__--
> 
> Message: 8
> Date: Wed, 13 Nov 2002 11:00:37 -0500
> From: Chris Poupart <chris.poupart@mcgill.ca>
> To: Raymond Leach <raymondl@knowledgefactory.co.za>
> CC: Netfilter Mailing List <netfilter@lists.netfilter.org>
> Subject: Re: Time based rules ...
> 
> 
> This is a cryptographically signed message in MIME format.
> 
> --------------ms030200050104000308010508
> Content-Type: text/plain; charset=us-ascii; format=flowed
> Content-Transfer-Encoding: 7bit
> 
> Couldn't you just use a CRON job to add and remove that rule at the 
> required times?
> 
> -- Chris
> 
> Raymond Leach wrote:
> > Hi
> > 
> > Is there a way to put time restrictions on rules?
> > For eaxmple, something like:
> > 
> > iptables -A FORWARD -i eth0 -p tcp -sport 1024: -dport 1024: -time
> > 0700:1700 -j DROP
> > 
> > It would be nice ...
> > 
> > Ray
> > -- 
> 
> 
> --------------ms030200050104000308010508
> Content-Type: application/x-pkcs7-signature; name="smime.p7s"
> Content-Transfer-Encoding: base64
> Content-Disposition: attachment; filename="smime.p7s"
> Content-Description: S/MIME Cryptographic Signature
> 
> MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIJXDCC
> AwwwggJ1oAMCAQICAwhdizANBgkqhkiG9w0BAQQFADCBkjELMAkGA1UEBhMCWkExFTATBgNV
> BAgTDFdlc3Rlcm4gQ2FwZTESMBAGA1UEBxMJQ2FwZSBUb3duMQ8wDQYDVQQKEwZUaGF3dGUx
> HTAbBgNVBAsTFENlcnRpZmljYXRlIFNlcnZpY2VzMSgwJgYDVQQDEx9QZXJzb25hbCBGcmVl
> bWFpbCBSU0EgMjAwMC44LjMwMB4XDTAyMDkyNzE3MTczNloXDTAzMDkyNzE3MTczNlowSTEf
> MB0GA1UEAxMWVGhhd3RlIEZyZWVtYWlsIE1lbWJlcjEmMCQGCSqGSIb3DQEJARYXY2hyaXMu
> cG91cGFydEBtY2dpbGwuY2EwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQC4eF7z
> tl0IE3iJFRn+QxzBIYj9kv5bkCa3oB0ZcsGxoYoVoTKXPKmiI/CvhpNUKG3EgffmNsO1bsiW
> yoyX29ex3bjSUvXUp7rUdl4z/LlgTsPXOpfuXnt1d719kpn5yAPI3yzCBjjtwrEb1X7XUIcP
> iLW8kAwMn12a6m7ym7UUGuFALwIB3LkOiO0OnT46s5ePDLWwSLgRNamTT+DSgi5thUktZAhk
> jPcOwzrfvYH8+/BPbGpgjtUQjWE/prOI/MwAG+CUnFXFc72OjJsdBpUj0mRKiDpsVH6u0LWe
> lnxtnRWc40zdhl4zYvM3+t110RFmEsf9fl8qig2sc9noV4YBAgMBAAGjNDAyMCIGA1UdEQQb
> MBmBF2NocmlzLnBvdXBhcnRAbWNnaWxsLmNhMAwGA1UdEwEB/wQCMAAwDQYJKoZIhvcNAQEE
> BQADgYEA2R04OiFqWwqdpxeCGJQflyooYzpl7T+vXXizBMOLAcn6ecXf+na9O2AOFTOVLZ83
> kR0jg5vX7GJpvVDM+qBkQqyqCgsDElXxzizOEFwMZwbNcEl3lA1wxLwwcvICZlfAZsn1dNGo
> NZrZ2castGJgIf64I1YmlnxwX82nJDQJ1dQwggMMMIICdaADAgECAgMIXYswDQYJKoZIhvcN
> AQEEBQAwgZIxCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcT
> CUNhcGUgVG93bjEPMA0GA1UEChMGVGhhd3RlMR0wGwYDVQQLExRDZXJ0aWZpY2F0ZSBTZXJ2
> aWNlczEoMCYGA1UEAxMfUGVyc29uYWwgRnJlZW1haWwgUlNBIDIwMDAuOC4zMDAeFw0wMjA5
> MjcxNzE3MzZaFw0wMzA5MjcxNzE3MzZaMEkxHzAdBgNVBAMTFlRoYXd0ZSBGcmVlbWFpbCBN
> ZW1iZXIxJjAkBgkqhkiG9w0BCQEWF2NocmlzLnBvdXBhcnRAbWNnaWxsLmNhMIIBIjANBgkq
> hkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAuHhe87ZdCBN4iRUZ/kMcwSGI/ZL+W5Amt6AdGXLB
> saGKFaEylzypoiPwr4aTVChtxIH35jbDtW7IlsqMl9vXsd240lL11Ke61HZeM/y5YE7D1zqX
> 7l57dXe9fZKZ+cgDyN8swgY47cKxG9V+11CHD4i1vJAMDJ9dmupu8pu1FBrhQC8CAdy5Dojt
> Dp0+OrOXjwy1sEi4ETWpk0/g0oIubYVJLWQIZIz3DsM6372B/PvwT2xqYI7VEI1hP6aziPzM
> ABvglJxVxXO9joybHQaVI9JkSog6bFR+rtC1npZ8bZ0VnONM3YZeM2LzN/rdddERZhLH/X5f
> KooNrHPZ6FeGAQIDAQABozQwMjAiBgNVHREEGzAZgRdjaHJpcy5wb3VwYXJ0QG1jZ2lsbC5j
> YTAMBgNVHRMBAf8EAjAAMA0GCSqGSIb3DQEBBAUAA4GBANkdODohalsKnacXghiUH5cqKGM6
> Ze0/r114swTDiwHJ+nnF3/p2vTtgDhUzlS2fN5EdI4Ob1+xiab1QzPqgZEKsqgoLAxJV8c4s
> zhBcDGcGzXBJd5QNcMS8MHLyAmZXwGbJ9XTRqDWa2dnGrLRiYCH+uCNWJpZ8cF/NpyQ0CdXU
> MIIDODCCAqGgAwIBAgIQZkVyt8x09c9jdkWE0C6RATANBgkqhkiG9w0BAQQFADCB0TELMAkG
> A1UEBhMCWkExFTATBgNVBAgTDFdlc3Rlcm4gQ2FwZTESMBAGA1UEBxMJQ2FwZSBUb3duMRow
> GAYDVQQKExFUaGF3dGUgQ29uc3VsdGluZzEoMCYGA1UECxMfQ2VydGlmaWNhdGlvbiBTZXJ2
> aWNlcyBEaXZpc2lvbjEkMCIGA1UEAxMbVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWlsIENBMSsw
> KQYJKoZIhvcNAQkBFhxwZXJzb25hbC1mcmVlbWFpbEB0aGF3dGUuY29tMB4XDTAwMDgzMDAw
> MDAwMFoXDTA0MDgyNzIzNTk1OVowgZIxCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJu
> IENhcGUxEjAQBgNVBAcTCUNhcGUgVG93bjEPMA0GA1UEChMGVGhhd3RlMR0wGwYDVQQLExRD
> ZXJ0aWZpY2F0ZSBTZXJ2aWNlczEoMCYGA1UEAxMfUGVyc29uYWwgRnJlZW1haWwgUlNBIDIw
> MDAuOC4zMDCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEA3jMypmPHCSVFPtJueCdngcXa
> iBmClw7jRCmKYzUqbXA8+tyu9+50bzC8M5B/+TRxoKNtmPHDT6Jl2w36S/HW3WGl+YXNVZo1
> Gp2Sdagnrthy+boC9tewkd4c6avgGAOofENCUFGHgzzwObSbVIoTh/+zm51JZgAtCYnslGvp
> oWkCAwEAAaNOMEwwKQYDVR0RBCIwIKQeMBwxGjAYBgNVBAMTEVByaXZhdGVMYWJlbDEtMjk3
> MBIGA1UdEwEB/wQIMAYBAf8CAQAwCwYDVR0PBAQDAgEGMA0GCSqGSIb3DQEBBAUAA4GBADGx
> S0dd+QFx5fVTbF151j2YwCYTYoEipxL4IpXoG0m3J3sEObr85vIk65H6vewNKjj3UFWobPcN
> rUwbvAP0teuiR59sogxYjTFCCRFssBpp0SsSskBdavl50OouJd2K5PzbDR+dAvNa28o89kTq
> JmmHf0iezqWf54TYyWJirQXGMYIDJzCCAyMCAQEwgZowgZIxCzAJBgNVBAYTAlpBMRUwEwYD
> VQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUgVG93bjEPMA0GA1UEChMGVGhhd3Rl
> MR0wGwYDVQQLExRDZXJ0aWZpY2F0ZSBTZXJ2aWNlczEoMCYGA1UEAxMfUGVyc29uYWwgRnJl
> ZW1haWwgUlNBIDIwMDAuOC4zMAIDCF2LMAkGBSsOAwIaBQCgggFhMBgGCSqGSIb3DQEJAzEL
> BgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTAyMTExMzE2MDAzN1owIwYJKoZIhvcNAQkE
> MRYEFPPTeVlaU6CriiJOR4LZx+r6wQHOMFIGCSqGSIb3DQEJDzFFMEMwCgYIKoZIhvcNAwcw
> DgYIKoZIhvcNAwICAgCAMA0GCCqGSIb3DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgEo
> MIGtBgsqhkiG9w0BCRACCzGBnaCBmjCBkjELMAkGA1UEBhMCWkExFTATBgNVBAgTDFdlc3Rl
> cm4gQ2FwZTESMBAGA1UEBxMJQ2FwZSBUb3duMQ8wDQYDVQQKEwZUaGF3dGUxHTAbBgNVBAsT
> FENlcnRpZmljYXRlIFNlcnZpY2VzMSgwJgYDVQQDEx9QZXJzb25hbCBGcmVlbWFpbCBSU0Eg
> MjAwMC44LjMwAgMIXYswDQYJKoZIhvcNAQEBBQAEggEAoB1OfLfTqsK2qcx8rvWr2BjmUAf2
> lZptBBFjTllqjMOSSBf1uQW3pkKEgtRInTtpgO8n6GMaOufBeP6qqYL3F/D0lOwcn3R/E7my
> 0o8+dAN59mmI7X/CfKJFqPdob7VqPxTfp6fXr+gVxDcbG3WKfYkdpF2oDU9Z0TFaMKpZ76Zg
> OaF6May1hkzxVsuQgG3YZmzQleelN9X4kDCu4gfMfLSm2uWRjGuPV+EA+0CzIrHMt7kilkfo
> LBnN7NGRqMRZ6aydF6CQ8KS7ptV5KF5xTgMOr4m4IlDwl5PP6QJNZ2I4qFWe2eIHTWNqhiZa
> b7vNjCLgvG42EDyKPdHZfpZw6wAAAAAAAA==
> --------------ms030200050104000308010508--
> 
> 
> 
> --__--__--
> 
> Message: 9
> Date: Wed, 13 Nov 2002 17:41:57 +0100
> To: netfilter@lists.netfilter.org
> From: 040 <madmac@swipnet.se>
> Subject: Netfilter 1.2.7a (debian), rule (DNAT) problems
> 
> Hello.
> 
> First of all my configuration is:
> Debian Linux 3.0r0 w/ kernel 2.4.18-K7 on a x86 AMD Duron on a via KT133A 
> chipset.
> The system is configured with two NIC's, namely two 3Com 3C905C 10/100-TX 
> PCI networking cards and is acting part as
> a server and part as a router. I use it for serving things like web to the 
> outside and a router to enable internet access via it
> from my lan because my ISP only hands me one IP address. if it's of any 
> importance I hand out IP addresses to my lan
> via dhcpd, oh yea, it's a switched 10/100 mbit ethernet network.
> eth1 (dynamic, 217.208.248.*) is connected to the net and eth0 (static, 
> 192.168.0.1) is connected to the lan.
> 
> I've read the NAT HOWTO on netfilter.org and setted up masquadering like 
> (from my ruleset):
> -A POSTROUTING -o eth1 -j MASQUERADE
> and I've also done the following:
> echo 1 > /proc/sys/net/ipv4/ip_forward
> and edited /etc/network/options to correspond with the variable
> ip_forward=yes
> Which works fine, I'm able to access the net via all the clients on my LAN 
> when using the server as my gateway.
> 
> Now I want to add a rule to forward all incoming data on port 4662 (TCP) 
> from the internet (eth1) to
> a server on my LAN, namely host 192.168.0.7 (via eth0), so I add the 
> following rule (under *nat):
> -A PREROUTING -p tcp -m tcp -i eth1 --dport 4662 -j DNAT --to-destination 
> 192.168.0.7:4662
> 
> After reloading iptables and trying to connect or scan the port 4662 on my 
> external IP, nothing happends, i.e. the port is closed (yes, the
> client is listening on 4662 but does not recive any connections from the 
> server's eth0 (192.168.0.1)).
> 
> Anyone have any ideas for me?
> 
> I'm providing a copy of my ruleset made with iptables-save to provide 
> additional techincal information:
> 
> # Generated by iptables-save v1.2.7a on Sun Nov 10 17:58:44 2002
> *nat
> :OUTPUT ACCEPT [0:0]
> :PREROUTING ACCEPT [0:0]
> :POSTROUTING ACCEPT [0:0]
> -A PREROUTING -p tcp -m tcp -i eth1 --dport 4662 -j DNAT --to-destination 
> 192.168.0.7:4662
> -A POSTROUTING -o eth1 -j MASQUERADE
> COMMIT
> 
> 
> Please note, I've tried to fiddle-around with the rules _alot_ so the above
> 
> is not a specific case of not-working rather than just one out of 100
> examples.
> 
> Thanks in advance.
> Henric Blomgren / Sweden.
> 
> 
> 
> --__--__--
> 
> Message: 10
> Date: Wed, 13 Nov 2002 12:10:26 -0500
> From: "Michael H. Warfield" <mhw@wittsend.com>
> To: James Miller <jimm@simutronics.com>
> Cc: netfilter@lists.netfilter.org
> Subject: Re: Trojaned tcpdump and libpcap
> 
> 
> --TA4f0niHM6tHt3xR
> Content-Type: text/plain; charset=us-ascii
> Content-Disposition: inline
> Content-Transfer-Encoding: quoted-printable
> 
> On Wed, Nov 13, 2002 at 10:25:30AM -0600, James Miller wrote:
> > Hello all
> 
> > I have been a long time reader of this list.  An associate passed this
> al=
> ong
> > to me this morning and I wanted to share it with everyone.
> 
> > http://hlug.fscker.com/
> > Latest libpcap & tcpdump sources from tcpdump.org contain a trojan.
> 
> > Affected version are:
> > libpcap-0.7.1.tar.gz
> > tcpdump-3.6.2.tar.gz
> > tcpdump-3.7.1.tar.gz
> 
> 	Downloads from October 30 have been confirmed good.  Downloads
> after November 12 confirmed bad.  Anything in-between is anyone's guess.
> If anyone downloaded those sources between those two dates, please contact
> me with the package md5sums.  I want to narrow down the time frame.
> CVS repository does NOT appear to have been compromised.
> 
> 	Good:
> 
> 03e5eac68c65b7e6ce8da03b0b0b225e  tcpdump-3.7.1.tar.gz
> 0597c23e3496a5c108097b2a0f1bd0c7  libpcap-0.7.1.tar.gz
> 
> 	Bad:
> 
> 3c410d8434e63fb3931fe77328e4dd88  tcpdump-3.7.1.bad.tar.gz
> 73ba7af963aff7c9e23fa1308a793dca  libpcap-0.7.1.bad.tar.gz
> 
> > Regards,
> > Jim
> 
> 	Mike
> --=20
>  Michael H. Warfield    |  (770) 985-6132   |  mhw@WittsEnd.com
>   /\/\|=3Dmhw=3D|\/\/       |  (678) 463-0932   | 
> http://www.wittsend.com/=
> mhw/
>   NIC whois:  MHW9      |  An optimist believes we live in the best of all
>  PGP Key: 0xDF1DD471    |  possible worlds.  A pessimist is sure of it!
> 
> --TA4f0niHM6tHt3xR
> Content-Type: application/pgp-signature
> Content-Disposition: inline
> 
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.1 (GNU/Linux)
> 
> iQCVAwUBPdKHguHJS0bfHdRxAQGAnAQAwNm/9IzDza90dxhposTZoeVtgzjjeipY
> BJlgyhbeyLKvC5DoBMxn7eW29tl7+4e4FFQOsMKkaCyw+sCbc12hb3hWlNLzQeGO
> DrVpeLCaZsFuEZndl9Y7c7dLQvl4jUZVoLgIR8TDUXv9oz0TvjTA+1MUWZ/bEDPP
> xpkiaOEc1yg=
> =gt4S
> -----END PGP SIGNATURE-----
> 
> --TA4f0niHM6tHt3xR--
> 
> 
> --__--__--
> 
> Message: 11
> From: David Reta <DavidR@Narus.com>
> To: "'netfilter@lists.netfilter.org'" <netfilter@lists.netfilter.org>
> Subject: New to IP Tables
> Date: Wed, 13 Nov 2002 16:14:33 -0800
> 
> 	I just started using IP Tables and have a question. I was not able
> to find the answer in any of the docs I've read so far.
> I have a machine that I am using as a router and running Ip Tables on it.
> Here is a list of my tables.
> 
> [root@qa-gate root]# iptables -L
> Chain INPUT (policy ACCEPT)
> target     prot opt source               destination         
> 
> Chain FORWARD (policy ACCEPT)
> target     prot opt source               destination         
> ACCEPT     tcp  --  anywhere             anywhere           tcp dpt:http 
> ACCEPT     tcp  --  anywhere             anywhere           tcp
> dpt:ftp-data
> 
> ACCEPT     tcp  --  anywhere             anywhere           tcp dpt:ftp 
> ACCEPT     tcp  --  anywhere             anywhere           tcp dpt:domain 
> ACCEPT     tcp  --  anywhere             anywhere           tcp dpt:26 
> DROP       tcp  --  anywhere             anywhere           
> 
> Chain OUTPUT (policy ACCEPT)
> target     prot opt source               destination         
> 
> Chain test (0 references)
> target     prot opt source               destination
> 
> I am not able to pass any data through the router. Here is the scenario, I
> want to access a Web Site which is on the other side of the router. The way
> that I interpret this is that the packet will get passed to the first chain
> which is
> ACCEPT     tcp  --  anywhere             anywhere           tcp dpt:http
> and be let through, yet this is not happening. All tcp traffic is being
> blocked which is defined by my 6th rule. I guess I am not understanding
> this, but I would think that the packet would match the first rule and be
> passed through and the following chains would be ignored. My logic is
> probably wrong.
> 
> Thanks,
> David
> 
> 
> 
> 
> 
> --__--__--
> 
> _______________________________________________
> netfilter mailing list
> netfilter@lists.netfilter.org
> https://lists.netfilter.org/mailman/listinfo/netfilter
> 
> 
> End of netfilter Digest
> 






^ permalink raw reply

* Re: [PATCH] 2.5.51 SCSI_IOCTL_GET_IDLUN + _GET_BUS_NUMBER
From: James Bottomley @ 2002-12-12 14:27 UTC (permalink / raw)
  To: dougg, axboe; +Cc: linux-scsi
In-Reply-To: <3DF83E4F.8000704@torque.net>

dougg@torque.net said:
> For disks both the SCSI_IOCTL_GET_IDLUN and SCSI_IOCTL_GET_BUS_NUMBER
> ioctls return the value 0 (type: int) in all cases. The attachment
> removes the dummy definitions of these ioctls in driver/block/
> scsi_ioctl.c so they fall through to the scsi mid level which
> correctly implements them (at least in terms of lk 2.4). 

I'm not sure this is the correct thing to do.  These ioctls may be there 
because cdrecord is using them.  In the new scheme, you can record a CD 
without ever troubling the scsi mid-layer, so if cdrecord wants them, they 
have to be provided in some fashion without relying on a fall through.

I've copied Jens on this mail, since he's the one that knows this stuff and 
should be able to confirm or deny this suspicion.  Jens?

James



^ permalink raw reply

* Re: New error when running script on ReiserFS partition
From: Alexandre Ratti @ 2002-12-12 14:27 UTC (permalink / raw)
  To: Oleg Drokin; +Cc: reiserfs-list
In-Reply-To: <20021212170742.A3110@namesys.com>

Hello Oleg,


At 17:07 12/12/2002 +0300, Oleg Drokin wrote:
>On Thu, Dec 12, 2002 at 02:54:33PM +0100, Alexandre Ratti wrote:
>
> > I got a new error when my backup script ran today. (See [1] for previous
> > message sent on Tuesday). This script runs on a large ReiserFS partition.
> > System is Debian Woody with recompiled 2.4.19 kernel. System did not crash.
> > I saw with ps that the kupdated process was dead (defunct).
> > I'm not sure this is ReiserFS-related, though these errors only seem to
> > happen when the script runs. Can someone confirm, based on this syslog
> > snippet?
>
>While this is certainly a piece of reiserfs code, the crash address makes no
>sence at all.
>Can you please run memtest86 for some time to confirm that your memory is 
>still ok?

It's running now; I'll let you know what the results are. (I last ran 
memtest86 in October when I set up this box and the memory was fine at that 
time.)


Cheers

Alexandre




^ permalink raw reply

* Re: portfw on iptables 2.4 kernel problem.
From: Joel Newkirk @ 2002-12-12 14:25 UTC (permalink / raw)
  To: Rasmus Reinholdt Nielsen, netfilter
In-Reply-To: <5.1.0.14.2.20021212094109.02d83370@of23sm3>

On Thursday 12 December 2002 03:51 am, Rasmus Reinholdt Nielsen wrote:
> Hi
>
> I have the same problem here. Using kernel 2.4.19-pre9, where I just
> can't forward port 80. Port 8080 works for instace fine. I have also
> tried to redirect all requests on port 80 to port 8080, but without
> any luck. When connecting to port 80 the browser just hangs. I can see
> in the apache log on the webserver that it gets the request, so I
> think it is a problem of the packets not getting back through the
> firewall and to the browser.
>
> I just can't see what is wrong. I even tried the following rules to
> see it that would help, but it didn't
>
> iptables -A INPUT -j ACCEPT
> iptables -A FORWARD -j ACCEPT
> iptables -t nat -A POSTROUTING -j MASQUERADE
> iptables -t nat -A PREROUTING -p tcp -i eth1 --dport 80 -j DNAT --to
> <http_ip>:80
> echo 1 > /proc/sys/net/ipv4/ip_forward
>
> This is not my usual firewall script, but I can't think of a more open
> one :)

Just a few observations.  I assume eth1 is your internet connection, so 
you should probably be using:
iptables -t nat -A POSTROUTING -o eth1 -j MASQUERADE
Otherwise it will constantly be checking the IP of every interface and 
masquerading packets outbound on every interface.
and you also need (did you just not list it?)
echo "1" > /proc/sys/net/ipv4/ip_dynaddr
for the MASQ target to work.

> Anybody knows of this might be a problem with the 2.4.19 kernels, I
> have a 2.4.18 firewall as well on which forwarding IS working, with
> the same ruleset.

Is this just DNAT that fails, or all forwarding?  And just to be sure, 
since you didn't say, are you testing it from outside the LAN, or from a 
local machine (or the firewall box itself)?

j


^ permalink raw reply

* Re: [PATCH] cs46xx some few corrections
From: Friedrich Ewaldt @ 2002-12-12 14:24 UTC (permalink / raw)
  To: Benny Sjostrand; +Cc: alsa-devel
In-Reply-To: <3DF7B30D.7000408@cucumelo.org>

Hi!

Too bad Cirrus doesn't like it's circuits to be used. Why can't they
just release the source code of the driver for this CS4624/4630. I
thought this circuit wasn't up to date any more. Maybe there are too
many bugs they don't want to be seen by anyone ;-)

As Cirrus doesn't help in the moment, do you have an idea why I managed
to get perfect sounding SPDIF input (after switching off/on the input 3
times or so) with 0.9.0rc6 and why I don't get undistorted sound with
cvs+latest patch? Could you see what loading the win driver before
booting into linux changes on the card if I would send some proc/asound/
dumps?
Thanks!
fe




-------------------------------------------------------
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility 
Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/

^ permalink raw reply

* Re: Is the scsi-misc-2.5 BK tree corrupted?
From: James Bottomley @ 2002-12-12 14:19 UTC (permalink / raw)
  To: SL Baur; +Cc: linux-scsi
In-Reply-To: <15864.4045.584597.590434@sofia.bsd2.kbnes.nec.co.jp>

steve@kbuxd.necst.nec.co.jp said:
> I am getting the following when attempting to pull from the current
> scsi-misc-2.5 BK tree. 

I have noticed BK do this periodically on other trees (most notably the linux 
ones).  It seems to be related to some type of backup program that bkbits 
runs.  I usually just wait a while and try again, which has worked so far.

James



^ permalink raw reply

* Re: separation of sysctl and tcp-window-tracking patch?
From: Brian J. Murrell @ 2002-12-12 14:14 UTC (permalink / raw)
  To: netfilter-devel

[-- Attachment #1: Type: text/plain, Size: 2332 bytes --]

On Thu, 2002-12-12 at 04:02, Jozsef Kadlecsik wrote: 
> On Thu, 12 Dec 2002, James Ralston wrote:
> 
> > (My specific need is related to DNS service: namely, in many cases, 30
> > seconds to establish a UDP session simply isn't enough time to permit
> > a reply to an outstanding DNS query.  I want to be able to up that
> > timeout to something closer to 60 or 120 seconds.)

I had this problem with the Amanda protocol, but it was with the UDP
streaming timeout.  It was not long enough to allow an Amanda client to
go do it's work and still respond to the server when it was done.

Fortunately (for this situation), the Amanda protocol requires a helper,
so I just upped the timeout on the connection in the helper.  But this
led me to think about UDP timeouts in general.

You might want to refer to this message:

http://lists.netfilter.org/pipermail/netfilter-devel/2002-September/009259.html

> Please note, that the timeout settings via /proc introduced in the
> tcp-window-tracking patch are global. You cannot raise the UDP timeout
> values just for DNS.

Indeed.  I had thought about this when I was doing my Amanda
modification for the UDP streaming timeout on it's connection.  For UDP
timeouts in general I had originally thought of doing this with
load-time module parameters.  Something along the lines of:

# insmod ip_conntrack.o udp_timeouts="53=60,123=10"

which would be added to a table already defined in
ip_conntrack_proto_udp.c with a set of common defaults.

This could be done via proc too however.  Maybe something like:

# cat /proc/sys/net/ipv4/netfilter/udp_timeout
default=30
53=60
123=10

to see the current timeout table and

# echo "default=45,520=30" > /proc/sys/net/ipv4/netfilter/udp_timeout

to set/modify entries in the table.

Of course we have two udp timeouts to deal with, initial UDP connection
setup timeout and the UDP streaming timeout.  Perhaps two different
/proc nodes.

> Also, we have to handle the backward compatibility issue of
> /proc/sys/net/ipv4/ip_conntrack_max, if the introduction of
> /proc/sys/net/ipv4/netfilter/ is accepted.

Right.  But let's not let this be a lone issue holding-up on moving
forward with general netfilter tunables via proc.

b.



-- 

Brian J. Murrell <netfilter@interlinx.bc.ca>

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

^ permalink raw reply


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.