02-08-2011
Hey
I reverted to an old VM Snapshot in the end
I still do not know what went wrong however I have a feeling I may have made a mistake somewhere along the way.
I am going to run my Implementation Procedure (Oracle ASM) once more and see if the error occurs again.
Thanks
G.
10 More Discussions You Might Find Interesting
1. OS X (Apple)
Hi,
I have issues with running graphical interfaces on my computer being remotely logged into a network via the -X option of ssh. My .cshrc shows DISPLAY=hostname:0 and I think there should be a different number instead of the 0. I changed the ssh_config file already to 'X11 forwarding yes', which... (0 Replies)
Discussion started by: ginese
0 Replies
2. Debian
I have 2 Debian boxes.
In my ssh.com client and my putty client, I have X11 fowarding turned
on for both boxes.
When I connect one, I can xterm with no problem back to my pc.
On the other, I keep getting:
xterm Xt error: Can't open display:
xterm: DISPLAY is not set
On both... (3 Replies)
Discussion started by: natter
3 Replies
3. UNIX for Dummies Questions & Answers
Hi,
I am using Putty, enabled SSH X11 forwarding and entered the X11 display location as "localhost:0". However I encountered the following error:
------------------------------------
# xclock &
2941
# X connection to localhost:10.0 broken (explicit kill or server shutdown).
+ Exit 1... (4 Replies)
Discussion started by: panggou
4 Replies
4. Red Hat
X11 forwarding problem between 2 RHEL4 machines with SSH
Already configured the following on both machines under /etc/ssh
Under sshd_config:
UsePAM no
AllowTcpForwarding yes
Under ssh_config:
ForwardAgent yes
ForwardX11 yes
ForwardX11Trusted yes
-----------------------------
Using... (1 Reply)
Discussion started by: panggou
1 Replies
5. HP-UX
Hi,
We've been facing a strange issue. Clients use X11 forwarding via SSH on HP server and sometimes the same DISPLAY is assigned to two (maybe more) sessions. As a result, some users can't open their applications, and some have their windows redirected to somebody else.
It looks as if sshd... (1 Reply)
Discussion started by: piooooter
1 Replies
6. UNIX for Dummies Questions & Answers
Hello. I installed a Debian box, and its installed remotely. I need to boot up iceweasel from there to do a quick test.
I log on using:
ssh root@<IP> -X
I have modified the /etc/ssh/sshd_config file, and added the X11Forwarding yes flag
And yet I still get:
Error: cannot open... (10 Replies)
Discussion started by: dynelight
10 Replies
7. Red Hat
Is it possible to launch an X11 application and have it use an X11 server on the other side of a bastion host? Specifically, here's my setup:
my laptop ------------- bastion -------------- remote host
I have putty installed on my laptop. The bastion is rhel 6.5 and the remote host is... (1 Reply)
Discussion started by: tsreyb
1 Replies
8. IP Networking
I would like to disable X11 session forcefully. I have tried the following things:
1. Setting appropriate DISPLAY variable in the /etc/environment file to be "0.0"
2. I have tried setting the sshd_config parameter X11Forwarding to be "no"
This session communication is happening by exchanging... (2 Replies)
Discussion started by: vaibhavvsk
2 Replies
9. UNIX for Beginners Questions & Answers
Unable to get X11 activated on my login even after Unix admin has enabled it (2 Replies)
Discussion started by: tomsayer1977
2 Replies
10. Red Hat
hi,
I'm trying to run a bash script that starts GUI. Though it says application started when I run this bash script doesn't show up any GUI. Here is what I've tried so far and please let me know if I'm missing something with the X11 set up here.
cat /etc/redhat-release
Red Hat Enterprise... (8 Replies)
Discussion started by: fop4658
8 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)