I am in a LAN with 10 hosts, but only my PC (192.168.0.10) and 192.168.0.13 is on.
The ip of the router is 192.168.0.1.
But I am capturing strange packages. There are many public IPs is sending to port 11935 of 192.168.0.9. But 192.168.0.9 does'nt exist in my LAN, so it does'nt reply any package.
Hi All
I am doing a locate <file_name> on my Redhat 7 System. I am unable to get the output. All the keep getting is:
locate: this is not a vlaid slocate database: /var/lib/locate/slocate.db
What des this mean? Is my system compromised?
Thanks in advance.
KS (13 Replies)
Hi all,
Thanks for any replies and for reading in advance.
We have upgraded one of our database instances to 10g on a Solaris 8 box, anyhow the other day it started trying to ping loads of weird IP addresses that we don't use, since our systems all run on pretty similar IP's. It all behind... (0 Replies)
Cannot find which packages install:
The executable:
sharemgr
The service:
smb/server
Anyone knows?
Background, I want to setup CIFS on ZFS.
Solaris 10. (1 Reply)
Hi,
I used the following command to retrieve a list of packages and saved them into a file:
rpm -q --queryformat "%{NAME}-%{VERSION}-%{RELEASE} (%{ARCH}) \n" binutils compat-libstdc++-33 elfutils-libelf elfutils-libelf-devel gcc gcc-c++ glibc glibc-common glibc-devel-2.5 libaio libaio-devel... (0 Replies)
Hi there
i wonder if someone can help, i have 2 servers (serverA and serverB). on A i have 147 packages, on server B i have 714 packages installed. i need server A to have the same packages as server B. how do i compile a list of only the packages i need? so in other words the list should be... (0 Replies)
Hi there
i wonder if someone can help, i have 2 servers (serverA and serverB). on A i have 147 packages, on server B i have 714 packages installed. i need server A to have the same packages as server B. how do i compile a list of only the packages i need? so in other words the list should be... (2 Replies)
Hi!
Let me introduce a project for find and download Slackware packages and browse Slackware repositories.
The site provides following features:
* Large, daily updated database with RPM, DEB, TGZ, TXZ packages for well-known repositories of the Slackware, Fedora, CentOS, RHEL, Debian,... (2 Replies)
Hello,
I am running vertica on my VMware which has Centos 5.5. I wanted to add some packages to the OS as I am working on some user defined functions.
The packages which I need are
openldap-devel
glibc-devel
glibc-common
libidn-devel
openssl-devel
The Centos version is Centos 5.5... (4 Replies)
Need this packages RHEL 5.6, Please help
Hey all,
I need these packages for RHEL 5.6
libyaml
libyaml-devel
libffi
libffi-devel
uname -mx86_64uname -mx86_64
Please tell me from which site I can get these packages
My OS is RHEL 5.6 64 bit.
Thanks,
Manali (1 Reply)
good morning,
I am new to Solaris, and I am trying to ultimately get qiime and other bioinformatic tools loaded onto Solaris 11.
Currently I am trying to load git
root@Cluster-1:~# pkgadd -d "website cannot post it since I am a noob" /opt/csw/bin/pkgutil -U /opt/csw/bin/pkgutil -y... (2 Replies)
Discussion started by: rdjack
2 Replies
LEARN ABOUT DEBIAN
shorewall-exclusion
SHOREWALL-EXCLUSION(5) [FIXME: manual] SHOREWALL-EXCLUSION(5)NAME
exclusion - Exclude a set of hosts from a definition in a shorewall configuration file.
SYNOPSIS
!address-or-range[,address-or-range]...
!zone-name[,zone-name]...
DESCRIPTION
The first form of exclusion is used when you wish to exclude one or more addresses from a definition. An exclaimation point is followed by
a comma-separated list of addresses. The addresses may be single host addresses (e.g., 192.168.1.4) or they may be network addresses in
CIDR format (e.g., 192.168.1.0/24). If your kernel and iptables include iprange support, you may also specify ranges of ip addresses of the
form lowaddress-highaddress
No embedded whitespace is allowed.
Exclusion can appear after a list of addresses and/or address ranges. In that case, the final list of address is formed by taking the first
list and then removing the addresses defined in the exclusion.
Beginning in Shorewall 4.4.13, the second form of exclusion is allowed after all and any in the SOURCE and DEST columns of
/etc/shorewall/rules. It allows you to omit arbitrary zones from the list generated by those key words.
Warning
If you omit a sub-zone and there is an explicit or explicit CONTINUE policy, a connection to/from that zone can still be matched by the
rule generated for a parent zone.
For example:
/etc/shorewall/zones:
#ZONE TYPE
z1 ip
z2:z1 ip
...
/etc/shorewall/policy:
#SOURCE DEST POLICY
z1 net CONTINUE
z2 net REJECT
/etc/shorewall/rules:
#ACTION SOURCE DEST PROTO DEST
# PORT(S)
ACCEPT all!z2 net tcp 22
In this case, SSH connections from z2 to net will be accepted by the generated z1 to net ACCEPT rule.
In most contexts, ipset names can be used as an address-or-range. Beginning with Shorewall 4.4.14, ipset lists enclosed in +[...] may also
be included (see shorewall-ipsets[1] (5)). The semantics of these lists when used in an exclusion are as follows:
o !+[set1,set2,...setN] produces a packet match if the packet does not match at least one of the sets. In other words, it is like NOT
match set1 OR NOT match set2 ... OR NOT match setN.
o +[!set1,!set2,...!setN] produces a packet match if the packet does not match any of the sets. In other words, it is like NOT match set1
AND NOT match set2 ... AND NOT match setN.
EXAMPLES
Example 1 - All IPv4 addresses except 192.168.3.4
!192.168.3.4
Example 2 - All IPv4 addresses except the network 192.168.1.0/24 and the host 10.2.3.4
!192.168.1.0/24,10.1.3.4
Example 3 - All IPv4 addresses except the range 192.168.1.3-192.168.1.12 and the network 10.0.0.0/8
!192.168.1.3-192.168.1.12,10.0.0.0/8
Example 4 - The network 192.168.1.0/24 except hosts 192.168.1.3 and 192.168.1.9
192.168.1.0/24!192.168.1.3,192.168.1.9
Example 5 - All parent zones except loc
any!loc
FILES
/etc/shorewall/hosts
/etc/shorewall/masq
/etc/shorewall/rules
/etc/shorewall/tcrules
SEE ALSO shorewall(8), shorewall-accounting(5), shorewall-actions(5), shorewall-blacklist(5), shorewall-hosts(5), shorewall_interfaces(5),
shorewall-ipsets(5), shorewall-maclist(5), shorewall-masq(5), shorewall-nat(5), shorewall-netmap(5), shorewall-params(5),
shorewall-policy(5), shorewall-providers(5), shorewall-proxyarp(5), shorewall-rtrules(5), shorewall-routestopped(5), shorewall-rules(5),
shorewall.conf(5), shorewall-secmarks(5), shorewall-tcclasses(5), shorewall-tcdevices(5), shorewall-tcrules(5), shorewall-tos(5),
shorewall-tunnels(5), shorewall-zones(5)NOTES
1. shorewall-ipsets
http://www.shorewall.net/manpages/shorewall-ipsets.html
[FIXME: source] 06/28/2012 SHOREWALL-EXCLUSION(5)