01-25-2011
The reason is quite simple: you've placed the VM in the 192.168.50.0/24 network, but the host machine is in the 172.20.3.0/24 network. To establish communication between these the default gateway (172.20.3.2) would have to know how to route between these.
Put the VM into the correct network and connections should work without problems.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi, dear all, I am rather new to Unix and have this problem where I cant seem to ping from 1 host to another. The scenerio is as follows: -
1 QNX host->Eth->1 SCO host
the SCO host is configured with it's IP
the QNX host is configured with another IP
both in the same domain, ie, 172.20.3.XX... (3 Replies)
Discussion started by: gavon
3 Replies
2. 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
3. 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
4. Solaris
Hello
I have a server in it.siroe.com
I added it.siroe.com in /etc/resolv.conf.
I still can't ping the server.
any service to restart here?
any other file to edit?
thx (4 Replies)
Discussion started by: melanie_pfefer
4 Replies
5. UNIX for Dummies Questions & Answers
Hi all,
I have a VM on Solaris 10 setup on a windows vista host machine.
1) Vista host i configure
VMnet 1: 10.1.1.10
Mask : 255.255.255.0
Subnet : 10.1.1.2
DNS : 10.1.1.100
2) Solaris on VM
Network device is on Custom(VMNET1)
IP : 10.1.1.4
Mask : 255.255.255.0
... (8 Replies)
Discussion started by: JuveZzZ
8 Replies
6. Windows & DOS: Issues & Discussions
Hello All,
I have searched and searched, but I am not finding any answers. Any help would be very welcome.
I have a home LAN centered around an Untangle gateway (up to date).
I have a Windows 7 PC and a Snow Leopard Mac
I also have two virtualized instances of windows (xp and 7) running... (1 Reply)
Discussion started by: toadtilley
1 Replies
7. Linux
Hi,
I am using win7 on my PC and installed VMware on it on which i am running linux
I am unable to ping my linux guest from my win machine,
but i can ping my windows host from linux guest :
Below is my system configuration
Linux
root@localhost ~]# ifconfig
eth0 Link... (9 Replies)
Discussion started by: chander_1987
9 Replies
8. 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
9. Solaris
Dear,
I hope you all will be ok.
I have an issue with Solaris box running on x86 Blade.
I am unable to ping a node neither traceroute. I am able to do traceroute from oce0:6 port which have IP and subnet of same type which oce0:1 has.
details are as follows:
Problem:
root@rinams02:/#... (3 Replies)
Discussion started by: khaniqshahid
3 Replies
10. Solaris
Hello All,
Host - Windows 7 64 BIT
Guest OS - Solaris 10 64 on VMWARE workstation
Problem : I can not ping solaris VM from my host OS. please suggest the solution.
Host OS:ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : INPS01900LT
... (5 Replies)
Discussion started by: sunil_1111
5 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)