search for: ipt_pkttyp

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 11:13:57 fwr last message repeated 2 times Oct 30 11:14:06 fwr root: Shorewall Restarted The "shorewall status" output seems complying with my rules set. Should I worry ? and is there any way to get...

...323 We are running the kernel-2.6.3-15mdk with shorewall-2.0.3a-1mdk. And lsmod | grep ip shows this: ip_nat_h323 4128 0 ip_conntrack_h323 4132 0 ipv6 232416 16 ipt_TOS 2240 12 ipt_MASQUERADE 3424 1 ipt_REJECT 6464 4 ipt_pkttype 1536 4 ipt_LOG 5312 10 ipt_state 1728 25 ipt_multiport 1856 0 ipt_conntrack 2304 0 iptable_mangle 2624 1 ip_nat_irc 4112 0 ip_nat_tftp 3376 0 ip_nat_ftp 4720 0 iptable_nat...

...ackket type match option in iptables/ Netfilter failing to match certain broadcast packets. The result is that the firewall log shows a lot of broadcast packets. Other users have complained of the following message when starting Shorewall: modprobe: cant locate module ipt_pkttype Users experiencing either of these problems can use PKTTYPE=No in shorewall.conf to cause Shorewall to use IP address filtering of broadcasts rather than packet type. 2) The shorewall.conf and zones file are no longer given execute permission by the installer script. 3) ICMP pac...

....o ipt_multiport.o ipt_tcpmss.o ip_conntrack_rpc_tcp.o ipt_DSCP.o ipt_NETLINK.o ipt_TCPMSS.o ip_conntrack_rpc_udp.o ipt_esp.o ipt_nth.o ipt_time.o ip_nat_ftp.o ipt_helper.o ipt_owner.o ipt_tos.o ip_nat_h323.o ipt_IMQ.o ipt_pkttype.o ipt_TOS.o ip_nat_irc.o ipt_ipv4options.o ipt_pool.o ipt_ttl.o ip_nat_snmp_basic.o ipt_length.o ipt_POOL.o ipt_TTL.o ip_pool.o ipt_limit.o ipt_psd.o ipt_ULOG.o ip_queue.o ipt_LOG.o ipt_realm.o ipt_uncle...

...ko ipt_state.ko iptable_filter.ko ip_conntrack_ftp.ko ip_nat_irc.ko ipt_NETMAP.ko ipt_ah.ko ipt_esp.ko ipt_limit.ko ipt_owner.ko ipt_tcpmss.ko iptable_mangle.ko ip_conntrack_irc.ko ip_nat_tftp.ko ipt_REDIRECT.ko ipt_conntrack.ko ipt_helper.ko ipt_mac.ko ipt_pkttype.ko ipt_tos.ko iptable_nat.ko ip_conntrack_tftp.ko ip_tables.ko ipt_REJECT.ko ipt_dscp.ko ipt_iprange.ko ipt_mark.ko ipt_recent.ko ipt_ttl.ko Should one of these modules be loaded to solve the problem?

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

...<1>general protection fault: e7a8 [#3] Modules linked in: i915 drm snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device snd_pcm_oss snd_mixer_oss snd_intel8x0 snd_ac97_codec snd_pcm snd_timer snd_page_alloc snd soundcore lp parport_pc ppdev parport ipt_REJECT ipt_LOG ipt_state ipt_pkttype ipt_set ipt_CONNMARK ipt_MARK ipt_ROUTE ipt_connmark ipt_owner ipt_recent ipt_iprange ipt_physdev ipt_multiport ipt_conntrack iptable_mangle ip_set_portmap ip_set_macipmap ip_set_ipmap ip_set_iphash ip_set ip_nat_irc ip_nat_tftp ip_nat_ftp iptable_nat ip_conntrack_irc ip_conntrack_tftp ip_conntrac...

...kernel scope link src 192.168.1.1 default via 62.58.222.90 dev ppp0 Table default: ARP ? (192.168.1.105) at 00:0C:6E:D7:65:D1 [ether] on eth0 ? (10.0.0.138) at 00:90:D0:39:56:A7 [ether] on eth1 Modules ipt_MASQUERADE 3968 1 ipt_REJECT 6528 4 ipt_LOG 6272 10 ipt_TCPMSS 4480 1 ipt_state 2304 16 ipt_pkttype 2048 4 ipt_recent 10252 0 ipt_iprange 2048 0 ipt_physdev 2320 0 ipt_multiport 2304 2 ipt_conntrack 2816 0 ip_nat_irc 4464 0 ip_nat_tftp 3696 0 ip_nat_ftp 4976 0 ip_conntrack_irc 71600 1 ip_nat_irc ip_conntrack_tftp 3888 0 ip_conntrack_ftp 72240 1 ip_nat_ftp ip_conntrack 32520 10 ipt_MASQUERADE,ipt...

...rnel scope link src 9.132.182.82 > default via 9.132.182.1 dev eth0 > > ARP > > ? (9.132.182.1) at 00:00:0C:07:AC:00 [ether] on eth0 > > Modules > > ipt_REJECT 6912 4 > ipt_LOG 7232 10 > ipt_state 1920 17 > ipt_pkttype 1664 4 > ipt_recent 11276 0 > ipt_iprange 1792 0 > ipt_multiport 2496 0 > ipt_conntrack 2560 4 > ip_nat_irc 2432 0 > ip_nat_ftp 3136 0 > ip_conntrack_irc 72080 1 ip_nat_irc &...

...10 default via 68.57.216.1 dev eth0 metric 10 ARP ? (68.57.216.1) at 00:01:5C:22:92:42 [ether] on eth0 ? (192.168.1.2) at 00:11:95:07:7A:F9 [ether] on eth1 Modules ipt_MASQUERADE 2816 1 ipt_REJECT 4256 4 ipt_LOG 6272 13 ipt_state 1312 13 ipt_pkttype 1184 4 ipt_CONNMARK 1696 0 ipt_MARK 1984 0 ipt_ROUTE 4260 0 ipt_connmark 1216 0 ipt_owner 2432 0 ipt_recent 9292 0 ipt_iprange 1312 0 ipt_physdev 1744 0 ipt_multiport...

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

...] auf br0 ? (192.168.0.47) auf 00:0E:35:54:AE:2C [ether] auf br0 Modules ipt_mac 2048 1 ipt_tcpmss 2368 0 ipt_MASQUERADE 4032 1 ipt_REJECT 7104 4 ipt_LOG 6656 8 ipt_TCPMSS 4480 0 ipt_state 2112 19 ipt_pkttype 1792 4 ipt_recent 11148 0 ipt_iprange 1856 0 ipt_physdev 2192 14 ipt_multiport 2112 2 ipt_conntrack 2688 0 ip_nat_irc 4400 0 ip_nat_tftp 3504 0 ip_nat_ftp 5104 0 ip_conntrack_irc...

Hello, You will find in attachment the layout of my current physical configuration. For now, the Cable ISP is not used. Since it is a dynamic ISP, my mailserver is rejected and my domain name registers on blacklists like ORDB and al. I want it to be used as a default gateway except for my mail server that would be seen as coming from my "honest" ADSL ISP. Here is

...odprobe ++ qt which modprobe ++ which modprobe +++ lsmod +++ grep ip_tables ++ ''['' -z ''ip_tables 23936 19 ipt_ROUTE,ipt_MASQUERADE,ipt_MARK,ipt_mark,ipt_CONNMARK,ipt_connmark,ipt_owner,ipt_recent,ipt_iprange,ipt_physdev,ipt_multiport,ipt_REJECT,ipt_conntrack,ipt_pkttype,ipt_LOG,ipt_state,iptable_mangle,iptable_nat,iptable_filter'' '']'' ++ loadmodule iptable_filter ++ local modulename=iptable_filter ++ local modulefile ++ local suffix ++ moduleloader=modprobe ++ qt which modprobe ++ which modprobe +++ lsmod +++ grep iptable_filter ++ '...

I am getting the following message when Shorewall stops can anybody shed any light on this message and where I should be looking? Thanks root@bobshost:~# shorewall stop Loading /usr/share/shorewall/functions... Processing /etc/shorewall/params ... Processing /etc/shorewall/shorewall.conf... Loading Modules... Stopping Shorewall...Processing /etc/shorewall/stop ... IP Forwarding Enabled