11-06-2011
well the ip filter service is disabled on all hosts but those hosts are able to ping and traceroute well..
well have to check the firewall only i guess
10 More Discussions You Might Find Interesting
1. IP Networking
The problem I am facing now is that the QNX host could not ping the SCO host and vice versa. They are in the same domain, ie, 172.20.3.xx. As I am very new to Unix, I guess I must have missed out some important steps. Pls help... Thanx alot (2 Replies)
Discussion started by: gavon
2 Replies
2. UNIX for Advanced & Expert Users
This may be a dumb question, but I've been wondering why programs such as ping and traceroute must be setuid? Are there some restrictions which prevent normal users from accessing the world via sockets?
$ pwd
/bin
$ ls -l ping traceroute
-rwsr-xr-x 1 root root 35616 Apr 7 2005 ping... (1 Reply)
Discussion started by: nathan
1 Replies
3. Shell Programming and Scripting
Hello,
I have config files for my storage where file systems are exported to lots of hosts as root.
I need to write a script in ksh to somehow filter these hosts from the file and ping those and if pingable than do nothing but if not pingable than send an alert to a log file which says:
... (1 Reply)
Discussion started by: za_7565
1 Replies
4. Solaris
Hello,
I have a problem - I created a chrooted jail for one user. When I'm logged in as root, everything work fine, but when I'm logged in as a chrooted user - I have many problems:
1. When I execute the command ping, I get weird results:
bash-3.00$ usr/sbin/ping localhost ... (4 Replies)
Discussion started by: Przemek
4 Replies
5. Shell Programming and Scripting
I want to change the following lines in /etc/hosts on FreeBSD:
::1 localhost localhost.my.domain
127.0.0.1 localhost localhost.my.domain
into the following lines
::1 localhost foo.example.com
127.0.0.1 localhost foo.example.com
I have the following script to do... (5 Replies)
Discussion started by: figaro
5 Replies
6. UNIX for Dummies Questions & Answers
can you provide the command in solaris8 if I wanted to ping,telnet, traceroute an IP address with a port? thanks (1 Reply)
Discussion started by: lhareigh890
1 Replies
7. UNIX for Dummies Questions & Answers
i cannot find a usefull ping and traceroute command from TCP to another TCP server with port.
I usually do only traceroute IP and ping IP..is that enough? I wanted to check its connectivity to an IP address with port..
example:
from ip 1.1.1.1 (TCP port 1234)
destination 2.2.2.2 (TCP... (1 Reply)
Discussion started by: lhareigh890
1 Replies
8. IP Networking
Hi,
I have a weird problem.
when ever I do ping command like for example
ping unix.comI get the following message:
# ping unix.com
ping: unknown host unix.com
but when I use host the computer is able to know the host.
# host unix.com
unix.com has address 81.17.242.186
unix.com mail is... (2 Replies)
Discussion started by: programAngel
2 Replies
9. Solaris
Hi all,
I'm having some trouble identifying what route is being used to talk to a target host. I can figure it out by looking at the routing tables but I want to automate this and don't much feel like scripting the network mask logic when I'd think there'd be a way to have the OS do it for me.... (5 Replies)
Discussion started by: Smiling Dragon
5 Replies
10. Solaris
Hi All,
I am new to solaris environment and we are using Solaris 9
The problem is am unable to ping a particular server from from one of the solaris server
The traceroute also shows only * * * for all the 30 hops
I tried to check all the settings like
1) /etc/hosts -> contains the... (17 Replies)
Discussion started by: Sanjay255
17 Replies
LEARN ABOUT DEBIAN
shorewall6-routestopped
SHOREWALL6-ROUTESTO(5) [FIXME: manual] SHOREWALL6-ROUTESTO(5)
NAME
routestopped - The Shorewall6 file that governs what traffic flows through the firewall while it is in 'stopped' state.
SYNOPSIS
/etc/shorewall6/routestopped
DESCRIPTION
This file is used to define the hosts that are accessible when the firewall is stopped or is being stopped. When shorewall6-shell is being
used, the file also determines those hosts that are accessible when the firewall is in the process of being [re]started.
The columns in the file are as follows (where the column name is followed by a different name in parentheses, the different name is used in
the alternate specification syntax).
INTERFACE - interface
Interface through which host(s) communicate with the firewall
HOST(S) - [-|address[,address]...]
Optional comma-separated list of IP/subnet addresses. If your kernel and ip6tables include iprange match support, IP address ranges are
also allowed.
If left empty or supplied as "-", 0.0.0.0/0 is assumed.
OPTIONS - [-|option[,option]...]
An optional comma-separated list of options. The order of the options is not important but the list can contain no embedded whitespace.
The currently-supported options are:
routeback
Set up a rule to ACCEPT traffic from these hosts back to themselves. Beginning with Shorewall 4.4.9, this option is automatically
set if routeback is specified in shorewall6-interfaces[1] (5) or if the rules compiler detects that the interface is a bridge.
source
Allow traffic from these hosts to ANY destination. Without this option or the dest option, only traffic from this host to other
listed hosts (and the firewall) is allowed. If source is specified then routeback is redundant.
dest
Allow traffic to these hosts from ANY source. Without this option or the source option, only traffic from this host to other listed
hosts (and the firewall) is allowed. If dest is specified then routeback is redundant.
critical
Allow traffic between the firewall and these hosts throughout '[re]start', 'stop' and 'clear'. Specifying critical on one or more
entries will cause your firewall to be "totally open" for a brief window during each of those operations. Examples of where you
might want to use this are:
o 'Ping' nodes with heartbeat.
o LDAP server(s) if you use LDAP Authentication
o NFS Server if you have an NFS-mounted root filesystem.
Note
The source and dest options work best when used in conjunction with ADMINISABSENTMINDED=Yes in shorewall6.conf[2](5).
EXAMPLE
Example 1:
#INTERFACE HOST(S) OPTIONS
eth2 2002:ce7c:92b4::/64
eth0 2002:ce7c:92b4:1::/64
br0 - routeback
eth3 - source
FILES
/etc/shorewall6/routestopped
SEE ALSO
http://shorewall.net/starting_and_stopping_shorewall.htm
http://shorewall.net/configuration_file_basics.htm#Pairs
shorewall6(8), shorewall6-accounting(5), shorewall6-actions(5), shorewall6-blacklist(5), shorewall6-hosts(5), shorewall6-interfaces(5),
shorewall6-maclist(5), shoewall6-netmap(5),shorewall6-params(5), shorewall6-policy(5), shorewall6-providers(5), shorewall6-rtrules(5),
shorewall6-rules(5), shorewall6.conf(5), shorewall6-secmarks(5), shorewall6-tcclasses(5), shorewall6-tcdevices(5), shorewall6-tcrules(5),
shorewall6-tos(5), shorewall6-tunnels(5), shorewall6-zones(5)
NOTES
1. shorewall6-interfaces
http://www.shorewall.net/manpages6/shorewall6-interfaces.html
2. shorewall6.conf
http://www.shorewall.net/manpages6/shorewall6.conf.html
[FIXME: source] 06/28/2012 SHOREWALL6-ROUTESTO(5)