similar to: [Bug 68] Kernel panic

Does anyone keep a known telemarketer caller id database? If not has anyone proposed an Asterisk community project to share this information? Sort of a nation wide blacklist so Asterisk'ers can cut down on the garbage calls... -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi, ok Im all new to this :-) for pasv ftp in your example you say for example to use ports 65500-65535, but i dont see that u open those ports in your example fw scripts..? any hints ? -- Christophe Zwecker mail: doc@zwecker.de Hamburg, Germany fon: +49 179 3994867 http://www.zwecker.de "Who is General Failure ? And why is he reading my disk

On my debian woody (kernel 2.4.31) the tcpdump doesn''t work with imq0 devices. If I try to tcpdump imq devices there is no packet seen: [...] rt1:~# tcpdump -n -i imq0 Warning: arptype 65535 not supported by libpcap - falling back to cooked socket tcpdump: WARNING: imq0: no IPv4 address assigned tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on

this : iptables -A FORWARD -i internal-interface -j ACCEPT iptables -A FORWARD -m state --state ESTABLISHED,RELATED -j ACCEPT iptables -A FORWARD -j DROP doesn''t seem to work for active-ftp .. i even manualy loaded ip_conntrack_ftp but as u see it is unused : # lsmod Module Size Used by Not tainted ip_conntrack_ftp 4272 0 (unused) iptable_nat

I have had a web server listining sql-1433, www 80, ftp-21 using proxy arp with sub-netting in a three interface DMZ. All these ports are in the rules file as ACCEPT. With one exeception that 1433 allows a few host from the net. 21 and 80 allow all net to dmz connections. The policy is DMZ to net ACCEPT This has been working great for about a month or more until I rebooted the

I apologize for the first message. :) --------------------------------------- I have an FTP server running in the DMZ section of my home network. It uses port 23000 for connection and ports 19990 to 19994 for data transfer. I have setup the following rule for outside people to connect to it: DNAT net dmz:192.168.2.2 tcp 23000 I''m at work right now and I can''t use

This is a minor release of Shorewall. WARNING: This release introduces incompatibilities with prior releases. See http://www.shorewall.net/upgrade_issues.htm. Changes are: a) There is now a new NONE policy specifiable in /etc/shorewall/policy. This policy will cause Shorewall to assume that there will never be any traffic between the source and destination zones. b) Shorewall no longer

I''m very new to shorewall. My setup is IP Gateway (CentOS 4 + Shorewall) with 3 NIC cards. Shorewall works great on the firewall machine. Bind also works (local net machines get IPs fine). Under firestarter, all works great. With shorewall, the loc machines can not route past the firewall. They can connect to the firewall, but not past it. Exactly what information should I post to get

mdew:~# tc qdisc add dev imq0 handle 1: root htb default 12 r2q 1 Cannot find device "imq0" mdew:~# lsmod Module Size Used by Not tainted ipt_REDIRECT 728 0 (autoclean) ipt_MARK 728 2 (autoclean) iptable_mangle 2100 1 (autoclean) ipt_REJECT 2712 4 (autoclean) iptable_filter 1672 1 (autoclean)

zaprtc 'load' is failing on my machine (the make was fine, same output as other posts to this list) [xxx@xxx zaptelrtc]# make load sync modprobe zaptel insmod ./zaprtc.o ./zaprtc.o: init_module: Input/output error Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or

Greetings, According to the FAQ "When you load the module and have no circuit/channel bank the LED's should flash red" I get the "knight rider" lights before the module loads, but after the modules are loaded I don't get any lights, other equipment plugged in or not. The card has been on my shelf a while so I wonder if it needs a firmware upgrade ? Can the cards

Hello, I run Shorewall 2.0.3a backport on a debian woody box (with 2.4.18 homemade kernel). When I start shorewall I got the following errors. Oct 30 11:13:12 fwr modprobe: modprobe: Can''t locate module ipt_conntrack Oct 30 11:13:17 fwr modprobe: modprobe: Can''t locate module ipt_pkttype Oct 30 11:13:18 fwr modprobe: modprobe: Can''t locate module ipt_pkttype Oct 30

We have a (supposedly) quite standard setup: 2 Dom0 with drbd-on-lvm and a bunch of DomU, on Quad Xeon Dell servers. We tried with both sid-based and etch-based (+ 3.1 xen hypervisor and drbd 8 from backports.org ) Dom0, and quite consistently have "kernel: invalid opcode: 0000 [1] SMP" errors which freezes Dom0 (during lasts tests a simple start-and-stop loop of 10 DomU can trigger

Hi, on a system RedHat 8.0, only on this, not on other various RedHat8.0, I have see the follow strange error in /var/log/{messages,boot.log} ..... After the boot all it seems to work, the modules is loads.... I have already tried to install other versions of kernel but the problem is always the same one :-(( Someone has some idea of what is happening? Thanks... Dario Lesca

Hi all.. I have found some problems on smbfs module in 2.4.18 kernel. I compiled it by myself (not the very first kernel compilation in my life ;-)) and then I have got it. Looks like it touch smbfs module as when I recompile 2.4.18 modules with smbfs sources changed to sources of smbfs from 2.4.17 problem disappears!! My mainboard is Abit BE6 with Pentium III 450 MHz. I am using SuSE 7.3 with

Hi folks, Has anyone tested the changes to multiple ISPs/load balancing or routestopped in 2.4.0-RC1 yet? We need to talk about what criteria we will use for determining whether 2.4.0 is ready for release. I''ve started configuring a firewall at work with the multiple ISPs support, but its kernel doesn''t have connection marking support, so it''s going to be a couple of

On Sat, Dec 24, 2005 at 11:03:36PM +0300, Andrey J. Melnikoff (TEMHOTA) wrote: > Hello. Hi Andrey, > Please, CC me, i'm not subscribed. > > Kernel 2.6.15-rc6 OOPS: > > kernel: general protection fault: 0000 [#1] > kernel: SMP > kernel: Modules linked in: ipt_REDIRECT ipt_LOG ipt_TOS ipt_TCPMSS ipt_tos > ip_nat_ftp ipt_tcpmss iptable_nat ip_nat iptable_mangle

hi all, i want to try htb3 with imq downloaded & patched imq & htb3 with kernel-2.4.18 on rh7.2 but got STUCK on step 1 :( this are what i did can anyone guide me what went wrong on the first step itself !! [root@cab1 root]# modprobe imq numdevs=1 modprobe: Can''t locate module imq [root@cab1 root]# [root@cab1 root]# tc qdisc add dev imq0 handle 1: root htb default 1 Cannot find

I''m trying to get Shorewall to use ulogd for logging, but I''m not seeing any logging in either the file I set up for logs, nor in /var/log/messages (where the logs used to be). I''m running a stock Debian 3.0 woody system, with a custom 2.4.21 kernel. I used all the settings as described on shorewall.net when configuring the kernel. ulogd (0.97-1) and shorewall

Hi, I have installed tinc-1.0pre7-1.i386.rpm in redhat 7.2, followed the documentation. While running daemon, its giving following error message Jul 1 15:06:18 localhost modprobe: modprobe: Can't locate module char-major-36 Jul 1 15:06:18 localhost tinc.percipia[1292]: Could not open /dev/misc/net/tun: Nos uch device ================== /etc/modules.conf alias char-major-10-200 tun