similar to: imq0 not being detected

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

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

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

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

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

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

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

Christian, make sure your domU Kernel Modules under /lib/modules/<KernelVersion> have the same vermagic and modversion as your domU Kernel ! Or try loading the ipt_filter module manually with "modprobe -f" also see "man modprobe" Regards, Markus -----Ursprüngliche Nachricht----- Von: xen-users-bounces@lists.xensource.com [mailto:xen-users-bounces@lists.xensource.com] Im

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

-- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ teastep@shorewall.net PGP Public Key \ https://lists.shorewall.net/teastep.pgp.key

https://bugzilla.netfilter.org/cgi-bin/bugzilla/show_bug.cgi?id=68 ------- Additional Comments From laforge@netfilter.org 2003-03-20 10:55 ------- This looks strange. The BUG in slab.c tells us that there is a GFP_ATOMIC missing. This means that we are allocating kernel memory from softirq context with only GFP_KERNEL. If I understand your backtrace correctly, what happens is: - you are

I recently did a set up where I replaced a simple D-link home router that was having trouble processing a T1's worth of bandwidth with a linux machine running iptables. the kernel was 2.6.29-r5 and I chose the SIP connection tracking modules from the menuconfig. Router worked fine for normal traffic, but I was unable to get the SIP phones to work. Using ngrep it was plain to see

Hi! Already searched for it and asked in IRC channel but all replies talk about ip_conntrack_irc and ip_nat_irc. I have a rule in 'NEW' section of 'shorewall/rules' to irc: ACCEPT fw net tcp 6667 #IRC and 'lsmod|grep irc' shows: ip_nat_irc 3648 0 ip_nat 22572 8 [...] ip_conntrack_irc

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:

I''m trying to setup Shorewall 2.0.8 with the one-interface settings on my LFS (kernel 2.6.5) system. I''ve read the troubleshooting guide, recompiled my kernel with just about every netfilter/iptables module I could find, but I''m still getting this error: # tail /tmp/trace + prefix=Shorewall:smurfs:DROP: + ''['' 22 -gt 29 '']'' +

ok I've got Starcraft loaded in wine...works fine ;-) I have IPX installed within the kernel.. and have the following commandline.. modprobe ne2k-pci ifconfig eth0 192.168.0.1 netmask 255.255.255.0 up route add -net 192.168.0.0 netmask 255.255.255.0 eth0 ipx_interface add -p eth0 802.3 0x12345678 but it seems that Starcraft cant see the IPX thingo..err anyone know how to get starcraft to

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

https://bugzilla.netfilter.org/cgi-bin/bugzilla/show_bug.cgi?id=91 mschwendt@users.sf.net changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED | ------- Additional Comments From mschwendt@users.sf.net

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