search for: dpts

...gh (about, 30 seconds is not long enough, 45 seconds to 1 minute usually is) and the next time it will be slow once more. Working back through this it turned out that the firewall rule which had previously allowed 137-138 access: ACCEPT tcp -- xxx.xxx.xxx.xxx yyy.yyy.yyy.yyy tcp dpts:137:139 state NEW ACCEPT udp -- xxx.xxx.xxx.xxx yyy.yyy.yyy.yyy udp dpts:137:139 state NEW ACCEPT tcp -- xxx.xxx.xxx.xxx yyy.yyy.yyy.yyy tcp dpts:137:139 ACCEPT udp -- xxx.xxx.xxx.xxx yyy.yyy.yyy.yyy udp dpts:137:139 was no longer being...

...pt source destination Chain POSTROUTING (policy ACCEPT) num target prot opt source destination Table: filter Chain INPUT (policy ACCEPT) num target prot opt source destination 1 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpts:0:65000 2 ACCEPT udp -- 0.0.0.0/0 0.0.0.0/0 udp dpts:0:65000 3 ACCEPT all -- 0.0.0.0/0 0.0.0.0/0 state RELATED,ESTABLISHED 4 ACCEPT all -- 0.0.0.0/0 0.0.0.0/0 5 ACCEPT icmp -- 0.0.0.0/0 0.0.0.0/0...

...tos (1 references) target prot opt source destination Chain pretos (1 references) target prot opt source destination Chain tcfor (1 references) target prot opt source destination MARK udp -- anywhere anywhere udp dpts:8000:30000 MARK set 0xa MARK udp -- anywhere anywhere udp dpts:5060:5069 MARK set 0xa MARK udp -- anywhere anywhere udp dpts:2427:2436 MARK set 0xa MARK tcp -- anywhere anywhere tcp dpt:ssh MARK set 0x14 MA...

...1653 ACCEPT all -- * * 0.0.0.0/0 0.0.0.0/0 ctstate RELATED,ESTABLISHED 0 0 ACCEPT all -- lo * 0.0.0.0/0 0.0.0.0/0 4 1322 ACCEPT udp -- * * 0.0.0.0/0 0.0.0.0/0 udp dpts:67:68 Chain FORWARD (policy DROP 0 packets, 0 bytes) pkts bytes target prot opt in out source destination 0 0 ACCEPT all -- * * 0.0.0.0/0 0.0.0.0/0 ctstate RELATED,ESTABLISHED 0...

I have a data frame in wide format. There are six variables that represent two factors in long format 3x2, Valence and Temperature: > head(dpts) File Subj Time Group PainNeg.hot PainNeg.warm SociNeg.hot SociNeg.warm Positiv.hot Positiv.warm Errors 1 WB101_1_1_dp.txt 101 1 MNP 30.700000 13.75000 16.319048 35.166667 30.18333 14.383333 1 2 WB101_2_1_dp.txt 101 2 MNP 5.266667 -79.60000 -24...

...ect ah -- * * 0.0.0.0/0 0.0.0.0/0 Chain OUTPUT (policy DROP 0 packets, 0 bytes) pkts bytes target prot opt in out source destination 0 0 ACCEPT udp -- * eth0 0.0.0.0/0 0.0.0.0/0 udp dpts:67:68 0 0 ACCEPT udp -- * eth1 0.0.0.0/0 0.0.0.0/0 udp dpts:67:68 0 0 ACCEPT udp -- * eth2 0.0.0.0/0 0.0.0.0/0 udp dpts:67:68 0 0 ACCEPT udp -- * eth3 0.0.0.0/0 0.0.0.0/0...

Hi, I get frequent logfile entries from Shorewall similar to the following: Nov 25 11:22:51 10.0.0.248 kernel: Shorewall:net2mill:DROP:IN=eth2 OUT=eth0 SRC=202.96.117.50 DST=10.0.0.10 LEN=56 TOS=0x00 PREC=0x00 TTL=241 ID=0 PROTO=ICMP TYPE=11 CODE=0 [SRC=10.0.0.10 DST=202.101.167.133 LEN=48 TOS=0x00 PREC=0x00 TTL=1 ID=13591 DF PROTO=TCP INCOMPLETE [8 bytes] ] Could someone explain what the

Hi All, I''m using iptables-1.2.7a on RedHat8 kernel 2.4.20. I wanted to limit the file-sharing traffic to the internet. I marked the packets with iptables: iptables -A FORWARD -t mangle -p tcp -s 192.168.1.1/24 -d ! 192.168.1.1/24 --dport 1024:1862 -j MARK --set-mark 1 iptables -A FORWARD -t mangle -p tcp -s 192.168.1.1/24 -d ! 192.168.1.1/24 --dport 1864:65535 -j MARK --set-mark 1

I've got a test lab set up and im having problems connecting. The first problem is that it takes it a couple of tries before it actually connects the two machines. It complains about bogus data and after trying for a minute or so it connects. kill -USR1 shows that they are connected kill -USR2 only shows the local subnet, not the remote I've tried these versions without any luck: cvs

Hi all, I have done some extensive searching, and drawn a blank so far... Nothing odd is reported in samba logs, or in the syslog file. However, if I try to play an avi straight off the samba server, on an XP client with MP10, it brings the whole deal to its knees after a few mins at the most. I have to hard reset the server. Other than this, all my other uses are flawless (game server,

Hi, Before I go any further, I''m no networking expert, and the sheer volume of documentation on the Shorewall website makes my brain hurt.. Some time ago I moved from an area with cable internet to an ADSL only area. While on cable, I''d set up an old P3 box running Gentoo as a firewall/gateway/file server, running shorewall (currently v2.2.3) and dnsmasq. I''d

...stination 0 0 ACCEPT all -- * lo 0.0.0.0/0 0.0.0.0/0 0 0 DROP !icmp -- * * 0.0.0.0/0 0.0.0.0/0 state INVALID 0 0 ACCEPT udp -- * eth0 0.0.0.0/0 0.0.0.0/0 udp dpts:67:68 12 1366 fw2net all -- * eth0 0.0.0.0/0 0.0.0.0/0 0 0 fw2loc all -- * eth1 0.0.0.0/0 0.0.0.0/0 0 0 common all -- * * 0.0.0.0/0 0.0.0.0/0 0 0 LOG all...

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

...0.0.0/0 0.0.0.0/0 state RELATED,ESTABLISHED 1 84 ACCEPT icmp -- * * 0.0.0.0/0 0.0.0.0/0 0 0 ACCEPT all -- lo * 0.0.0.0/0 0.0.0.0/0 0 0 ACCEPT tcp -- * * 172.22.0.0/16 0.0.0.0/0 tcp dpts:49152:49664 ctstate NEW 0 0 ACCEPT tcp -- * * 10.3.3.0/25 0.0.0.0/0 tcp dpts:49152:49664 ctstate NEW 0 0 ACCEPT tcp -- * * 172.22.0.0/16 0.0.0.0/0 tcp dpt:24007 ctstate NEW 918 55080 ACCEPT tcp -- * * 10.3...

I know this will be trivial for most, but I am having trouble with getting my scenario to work correctly. I want to ''tag'' and ''throttle'' the bandwidth to and from a particular client on my lan side. Better yet, I just want to throttle smtp traffic, per say, for that ip. ----lan----------eth1-[linux.box]-eth0----------internet I have used the technique

...anywhere state NEW DROP all -- anywhere anywhere This are the rules i have after i started my internet connection: Chain INPUT (policy ACCEPT) target prot opt source destination LOG udp -- anywhere anywhere udp dpts:0:1023 LOG level warning LOG tcp -- anywhere anywhere tcp dpts:0:1023 LOG level warning DROP udp -- anywhere anywhere udp dpts:0:1023 DROP tcp -- anywhere anywhere tcp dpts:0:1023 LOG tcp -- anywh...

...* 0.0.0.0/0 0.0.0.0/0 > > Chain OUTPUT (policy DROP 0 packets, 0 bytes) > pkts bytes target prot opt in out source destination > 0 0 ACCEPT udp -- * eth0 0.0.0.0/0 0.0.0.0/0 udp dpts:67:68 > 0 0 ACCEPT udp -- * ppp0 0.0.0.0/0 0.0.0.0/0 udp dpts:67:68 > 0 0 ACCEPT udp -- * ath0 0.0.0.0/0 0.0.0.0/0 udp dpts:67:68 > 0 0 fw2home all -- * eth0 0.0.0.0/0 1...

...p dpt:ftp-data ACCEPT tcp -- anywhere anywhere tcp dpt:ftp ACCEPT tcp -- anywhere anywhere tcp dpt:ssh ACCEPT tcp -- anywhere anywhere tcp dpt:http ACCEPT udp -- anywhere anywhere udp dpts:netbios-ns:netbios-ssn ACCEPT tcp -- anywhere anywhere tcp dpts:netbios-ns:netbios-ssn ACCEPT tcp -- anywhere anywhere tcp dpt:imap ACCEPT tcp -- anywhere anywhere tcp dpt:5901 ACCEPT tcp -- anywhere...

...s bytes target prot opt in out source destination 4654 821K ACCEPT all -- * lo 0.0.0.0/0 0.0.0.0/0 0 0 DROP !icmp -- * * 0.0.0.0/0 0.0.0.0/0 state INVALID 0 0 ACCEPT udp -- * ppp0 0.0.0.0/0 0.0.0.0/0 udp dpts:67:68 533 51169 fw2net all -- * ppp0 0.0.0.0/0 0.0.0.0/0 1354 133K fw2loc all -- * eth0 0.0.0.0/0 0.0.0.0/0 0 0 Reject all -- * * 0.0.0.0/0 0.0.0.0/0 0 0 LOG all -- * * 0.0.0.0/0 0.0.0.0/0 LOG flags 0 leve...

...state RELATED,ESTABLISHED > > 1 84 ACCEPT icmp -- * * 0.0.0.0/0 > 0.0.0.0/0 > > 0 0 ACCEPT all -- lo * 0.0.0.0/0 > 0.0.0.0/0 > > 0 0 ACCEPT tcp -- * * 172.22.0.0/16 > 0.0.0.0/0 tcp dpts:49152:49664 ctstate NEW > > 0 0 ACCEPT tcp -- * * 10.3.3.0/25 > 0.0.0.0/0 tcp dpts:49152:49664 ctstate NEW > > 0 0 ACCEPT tcp -- * * 172.22.0.0/16 > 0.0.0.0/0 tcp dpt:24007 ctstate NEW > > 918 55080 AC...