search for: spts

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

...g the automatic extent (to the data of the last layer added) OFF? I'm trying something like: drawOverviewMap<-function(){ p2<-ggplot(xlimits=c(2,20),ylimits=c(43,50))+coord_map(project="azequalarea") p2<-p2+geom_path(data=wa,mapping=aes(x=x,y=y)) p2<-p2+geom_point(data=spts,mapping=aes(x=Lon,y=Lat)) return(p2) } If I plot this in cartesian coordinates, it will zoom to the extent of the country boundaries "wa", plus some extra space around it (since this is the dataset with the widest range). This extent can be fixed with the "limits=..." paramete...

...ISHED,RELATED -j ACCEPT; iptables --list ACCEPT tcp -- anywhere anywhere tcp spt:domain state ESTABLISHED ACCEPT udp -- anywhere anywhere udp spt:domain state ESTABLISHED ACCEPT udp -- anywhere anywhere udp spts:netbios-ns:netbios-ssn state RELATED,ESTABLISHED ACCEPT tcp -- anywhere anywhere tcp spts:netbios-ns:netbios-ssn state RELATED,ESTABLISHED ACCEPT udp -- anywhere anywhere udp spt:microsoft-ds state RELATED,ESTABLISHED ACCEPT tcp -- a...

Hi, I''m testing out Xen on FC4. I''m using bridging for networking, as well as iptables to firewall, configured with the standard Fedora ''system-config-security-level'' tool. However I have really strange problem with conntrack not seeming to catch outbound connections. This prevents outbound connections working from dom0. Connections from domU''s

...retain it until the HVM domain is destroyed?" Well I don''t. I simply pre-allocate a pool of SPTI''s. It can be quite a large pool but certainly not one-SPTI per MFN. SPTIs are allocated on demand (when a guest page needs to be shadowed) and, when the pool runs low, the LRU SPTs are torn down and their SPTIs recycled. Currently I allocate about 5% of system memory for this purpose (this includes the SPT, its snapshot and the backlink pages) and, with that reasonable investment, we get very good performance. With more study, I''m sure things could be tuned even be...

...e # iptables classify /sbin/iptables -A POSTROUTING -t mangle -p udp -s 172.16.0.185/32 --sport 10000:10100 -d 172.16.1.0/24 -j CLASSIFY --set-class 2:44 Now the statistics: bridge:~# iptables -L -t mangle -v 34302 2415K CLASSIFY udp -- any any 172.16.0.185 172.16.1.0/24 udp spts:10000:10100 CLASSIFY set 2:44 bridge:~# tc -s cl sh dev eth1 class htb 2:44 parent 2:1 prio 1 rate 64000bit ceil 72000bit burst 1023b cburst 1608b Sent 0 bytes 0 pkts (dropped 0, overlimits 0) lended: 0 borrowed: 0 giants: 0 tokens: 131070 ctokens: 183067 class htb 2:1 root rate 3584Kbit c...

...t would oops through a double-free (see bug #440). Now a rule like iptables -A INPUT -p tcp -m multiport --dport 45,47 -m multiport --sport 45:48 actually ends up as: 0 0 tcp -- * * 0.0.0.0/0 0.0.0.0/0 multiport sports multiport sports tcp spts:45:48 As you can see, the matchinfo computed by the last multiport match is 'copied' over the previous ones. IIRC, this is caused by the matchinfo being attached to the match plugin, rather to the instance of a match plugin. -- Configure bugmail: https://bugzilla.netfilter.org/bugzilla...

...- anywhere anywhere state NEW tcp dpt:ssh REJECT all -- anywhere anywhere reject-with icmp-host-prohibited ACCEPT tcp -- anywhere anywhere tcp dpts:49152:49215 ACCEPT tcp -- anywhere anywhere tcp spts:49152:49215 Chain FORWARD (policy ACCEPT) target prot opt source destination ACCEPT all -- anywhere 192.168.122.0/24 state RELATED,ESTABLISHED ACCEPT all -- 192.168.122.0/24 anywhere ACCEPT all -- anywhere anywhere REJECT all...

...- anywhere anywhere state NEW tcp dpt:ssh REJECT all -- anywhere anywhere reject-with icmp-host-prohibited ACCEPT tcp -- anywhere anywhere tcp dpts:49152:49215 ACCEPT tcp -- anywhere anywhere tcp spts:49152:49215 Chain FORWARD (policy ACCEPT) target prot opt source destination ACCEPT all -- anywhere 192.168.122.0/24 state RELATED,ESTABLISHED ACCEPT all -- 192.168.122.0/24 anywhere ACCEPT all -- anywhere anywhere REJECT all...

...where anywhere ACCEPT all -- client200-122.dsl.intrex.net 10.0.0.0/24 ACCEPT all -- 10.0.0.0/24 10.0.0.0/24 drop-and-log-it all -- anywhere 10.0.0.0/24 ACCEPT udp -- anywhere anywhere udp spts:netbios-ns:netbios-ssn ACCEPT tcp -- anywhere anywhere tcp spt:netbios-ssn ACCEPT all -- client200-122.dsl.intrex.net anywhere drop-and-log-it all -- anywhere anywhere Chain drop-and-log-it (5 references) target prot opt...

...ype.js" type="text/javascript"></script> <script src="js/scriptaculous.js" type="text/javascript"></script> <script type="text/javascript"> // <![CDATA[ function spt_form_submit() { document.spt_main_form.spts.value= Sortable.sequence("secondlist").join("'' . ''_'' . ''"); return true; } // ]]> </script>''; (Following defines the two boxes, selectable ("firstlist") and selected ("secondlist&...

Having study a number of documents on linux traffic shaper, I started to setup my shaping rules in my network. My linux box is running RH AS3 U3, shorewall 2.0.9. It is using PPPoE connected to the Internet firewall: eth0: connect to the adsl modem eth1: private net ppp0: virtual dial up interface for pppoe There is a ftp server on the private net It is listen for port 21 and configured

Hi all iam trying to deploy loadbalance and failover My setup description --Fedora Core 4 --Linux 2.6.12.3 #1 SMP Mon Jul 25 22:37:34 IST 2005 i686 i686 i386 GNU/Linux --tc utility, iproute2-ss050314 --ip utility, iproute2-ss050314 --iptables v1.3.0 And i had deployed Following configuration #table main with priority 50, the highest one ip rule add prio 50 table main #table 201 ip rule add

Good day to all. I don''t like to Post unless I am really stuck. Guess what? Redhat with Shorewall. Been using this for years. I have a new client that we have setup with Redhat and Shorewall. The problem is that his outside address (ETH0 = NET) is dynamic (i.e. DHCP enabled). All the rules work fine when we use a STATIC address on Eth0, so we know the rules, filters, tos etc work fine