similar to: when to drop or reject?

I''m wondering if is is posable to do something like . /etc/shorewall/somefile from inside the blacklist file is a future release. is is this sort of thing already available and I''m just doing it wrong? -- Brad Wyman |\ _,,,---,,_ bradw@sta-care.com /,`.-''`'' -. ;-;;,_ Network Admin |,4- ) )-,_. ,\ ( `''-'' Sta-Care,

Hi, I''ve fiddled around with xen running on Ubuntu, Debian and now PCLinuxOS. I am running XEN on a very basic network setup: eth0 is a standard ethernet link, and the loopback device lo: eth0 Link encap:Ethernet HWaddr 00:17:08:40:DF:D3 inet addr:192.168.101.1 Bcast:192.168.101.255 Mask:255.255.255.0 inet6 addr: fe80::217:8ff:fe40:dfd3/64

Thank you all for you replies! For anyone following the fedora xen quickstart guide here are the steps to follow to get your eth0 working. At rawhide mkdir /lib/modules/2.6.12-1.1411_FC4xen0 depmod -a At the domain0 (make sure rawhide is down) mount -o loop /root/fedora.img /mnt cd /mnt cp /etc/sysconfig/network-scripts/ifcfg-eth0 etc/sysconfig/network-scripts/ifcfg-eth0 cp

--Apple-Mail-27-953181986 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; format=flowed a possible bug with survival analysis - either in R or in SPSS... find more details in bug.doc, and the data in bug.txt best Pius Korner --Apple-Mail-27-953181986 Content-Disposition: attachment Content-Type: multipart/appledouble; boundary=Apple-Mail-28-953181987

Hello, I''m currently running Puppet 0.25.5-1 on CentOS 5.5. Everything has been going swimmingly until a couple of weeks ago, when I began receiving errors on one of my nodes. The node in question is also my puppetmaster, but the errors seem client-related. The errors are: err: //yumrepos::centosbase/Yumrepo[addons]: Failed to retrieve current state of resource: A section with name

First: Long-time samba user (since 2004), and my first reach-out to everyone, so thank you for the great work! New issue: Both joining an AD domain and smbd fail with a segmentation fault on the Mac. I’ve tried to debug it the best I can but I’m not a C developer and can’t figure out what is the cause. For smbd, I have the log errors and the stack trace from it which I hope will provide some

I am attempting to use the Knock.pm from http://www.shorewall.net/ManualChains.html I am not having much luck making the DNAT- knock work for some reason. Anyone else using this on 4.4.4 that can verify if this still works as documented? Thanks ------------------------------------------------------------------------------ Return on Information: Google Enterprise Search pays you back Get the

I have an office setup with shorewall and when there''s bandwidth problems, I''d like to know who''s hogging my bandwidth and how (port). What would be the best approach to have shorewall show me something like: IP | Port | Bytes In | Bytes Out I have 20 PCs connected via DHCP. I looked at the documentation and thought that accounting may be close, but accounting

I?m afraid there is a possibility that your setup only works by chance ? I don?t think Dovecot LMTP is SMTPUTF8-capable according to RFC 6531. It needs to advertise the SMTPUTF8 extension but doesn?t. # nc -U /var/spool/postfix/private/dovecot-lmtp 220 mail.my.org Dovecot ready. LHLO mail.my.org 250-mail.my.org 250-STARTTLS 250-8BITMIME 250-ENHANCEDSTATUSCODES 250 PIPELINING -- David

Iam new to Xen and I am trying to FC4 and FC4 domains. I came across a problem when my newly created domain never gets a network. When I start the domain I get a fatal error that leads me to believe that thios might be the reason why I don''t have networking with the bridge: Checking for new hardwaremodprobe: FATAL: Could not load /lib/modules/2.6.12-1.1411_FC4xen0/modules.dep: No such

Hi Karthik, thanks for taking a look at this. I'm not working with gluster long enough to make heads or tails out of the logs. The logs are attached to this mail and here is the other information: # gluster volume info home Volume Name: home Type: Replicate Volume ID: fe6218ae-f46b-42b3-a467-5fc6a36ad48a Status: Started Snapshot Count: 1 Number of Bricks: 1 x 3 = 3 Transport-type: tcp