07-07-2008
well tried that also and the problem persists. It doesn't really bother me but I just wanna fix it. I'm trying to to fix every single problem I encounter. Running out of ideas troubleshooting it..
10 More Discussions You Might Find Interesting
1. Programming
Hello Experts,
Happy New Year to all of us,
In AIX 4.3.3 I am trying to figure out how is possible to find out the IP address that a telnet session - user uses to login in to host machine. My objective is by finding the login IP address to allow the user to login or not.
All users uses the... (6 Replies)
Discussion started by: sszago
6 Replies
2. UNIX for Advanced & Expert Users
I am using Tru64UX 5.1a on alphaserver 4100.
Users access the application through Telnet sessions to this server.
My requirement is to limit the users login through their PCs only.
Is there any way I can accomplish this on the unix box ?
I want to include a script in the .profile ( or... (1 Reply)
Discussion started by: shauche
1 Replies
3. IP Networking
The situation:
a Unix system (UnixWare 7.1.3) to which are connected other systems;
various p.c. on the LAN that they connect Unix to the system via TelNet.
The problem:
I need to intercept the address IP of the p.cs. connected via telnet to the Unix system.
Particularly, I have to know the... (2 Replies)
Discussion started by: paololrp
2 Replies
4. HP-UX
Hello,
I am a new member of this forum. I am trying to solve a following problem with CDE in HPUX 11. The error is Error: XDMCP timed out. State=4 (CollectBroadcastQuery). I have uncommented the following lines from the Xaccess file -
* grant service to all remote displays
* ... (0 Replies)
Discussion started by: shad
0 Replies
5. Solaris
Hi Friends,
I am not able to login through X browser from Windows Machine to Sun Fire V890 server. Solaris 10 is installed on this machine.
Please suggest me what changes need to be done in Solaris Server.
Thanks in Advance (2 Replies)
Discussion started by: durgaprasadr13
2 Replies
6. Solaris
Hi,
i got the following error when i tried to access the cygwin x server from a windows XP PC.
"xdmcp fatal error session failed session 23 failed for display"
Alternatively, when i tried to access the same Cygwin X Server from another windows XP PC which is on a different LAN... (3 Replies)
Discussion started by: HarishKumarM
3 Replies
7. Solaris
Hello all, I just post here to expose an issue I have encountered two days ago and finally successfully solve just right now using info on this site( but not only).
Config : Two SUN/ORACLE sparc Solaris 10 system.
Purpose : do a remote CDE login from host one to the host two.
method: from... (0 Replies)
Discussion started by: sunsunsun
0 Replies
8. Shell Programming and Scripting
I have a ksh script and would like to validate a MAC address that is input by the user:
00:14:4F:FC:00:49
example:
MAC=`/usr/bin/ckint -p "Enter MAC address"`
echo $MAC
echo " "
Obviously chkint will not work, but does anyone have any suggestions?
Thanks (9 Replies)
Discussion started by: hxman
9 Replies
9. Ubuntu
Hello. I previously had my xdm server running and it allowed me to use cygwin to run remote desktop with X -query x.x.x.x :1
But recently i noticed it had stopped working.
I get an error as shown in image, and i noticed that it mentions a 169.x.x.x. address.
I am wondering if anyone had had this... (1 Reply)
Discussion started by: duxbuz
1 Replies
10. What is on Your Mind?
Today, I noticed some errors in our SSL cert renewal log files, mostly related to domains where the IP address had changed. Concerned about this, rebuilt out SSL cert, which normally goes well without a hiccup.
However, for today, for some reason which I cannot explain, there was a PHP error... (0 Replies)
Discussion started by: Neo
0 Replies
LEARN ABOUT CENTOS
tcprules
tcprules(1) General Commands Manual tcprules(1)
NAME
tcprules - compile rules for tcpserver
SYNOPSIS
tcprules rules.cdb rules.tmp
OVERVIEW
tcpserver optionally follows rules to decide whether a TCP connection is acceptable. For example, a rule of
18.23.0.32:deny
prohibits connections from IP address 18.23.0.32.
tcprules reads rules from its standard input and writes them into rules.cdb in a binary format suited for quick access by tcpserver.
tcprules can be used while tcpserver is running: it ensures that rules.cdb is updated atomically. It does this by first writing the rules
to rules.tmp and then moving rules.tmp on top of rules.cdb. If rules.tmp already exists, it is destroyed. The directories containing
rules.cdb and rules.tmp must be writable to tcprules; they must also be on the same filesystem.
If there is a problem with the input, tcprules complains and leaves rules.cdb alone.
The binary rules.cdb format is portable across machines.
RULE FORMAT
A rule takes up one line. A file containing rules may also contain comments: lines beginning with # are ignored.
Each rule contains an address, a colon, and a list of instructions, with no extra spaces. When tcpserver receives a connection from that
address, it follows the instructions.
ADDRESSES
tcpserver starts by looking for a rule with address TCPREMOTEINFO@TCPREMOTEIP. If it doesn't find one, or if TCPREMOTEINFO is not set, it
tries the address TCPREMOTEIP. If that doesn't work, it tries shorter and shorter prefixes of TCPREMOTEIP ending with a dot. If none of
them work, it tries the empty string.
For example, here are some rules:
joe@127.0.0.1:first
18.23.0.32:second
127.:third
:fourth
::1:fifth
If TCPREMOTEIP is 10.119.75.38, tcpserver will follow the fourth instructions.
If TCPREMOTEIP is ::1, tcpserver will follow the fifth instructions. Note that you cannot detect IPv4 mapped addresses by matching
"::ffff", as those addresses will be converted to IPv4 before looking at the rules.
If TCPREMOTEIP is 18.23.0.32, tcpserver will follow the second instructions.
If TCPREMOTEINFO is bill and TCPREMOTEIP is 127.0.0.1, tcpserver will follow the third instructions.
If TCPREMOTEINFO is joe and TCPREMOTEIP is 127.0.0.1, tcpserver will follow the first instructions.
ADDRESS RANGES
tcprules treats 1.2.3.37-53:ins as an abbreviation for the rules 1.2.3.37:ins, 1.2.3.38:ins, and so on up through 1.2.3.53:ins. Similarly,
10.2-3.:ins is an abbreviation for 10.2.:ins and 10.3.:ins.
INSTRUCTIONS
The instructions in a rule must begin with either allow or deny. deny tells tcpserver to drop the connection without running anything.
For example, the rule
:deny
tells tcpserver to drop all connections that aren't handled by more specific rules.
The instructions may continue with some environment variables, in the format ,VAR="VALUE". tcpserver adds VAR=VALUE to the current envi-
ronment. For example,
10.0.:allow,RELAYCLIENT="@fix.me"
adds RELAYCLIENT=@fix.me to the environment. The quotes here may be replaced by any repeated character:
10.0.:allow,RELAYCLIENT=/@fix.me/
Any number of variables may be listed:
127.0.0.1:allow,RELAYCLIENT="",TCPLOCALHOST="movie.edu"
SEE ALSO
tcprulescheck(1), tcpserver(1), tcp-environ(5)
tcprules(1)