06-12-2015
Quote:
Originally Posted by
ranjancom2000
I don't understand the logic why it was not working if i put after reject.
It goes through them in order. "If this, do that, if this, jump there, if this, do that, otherwise, reject and quit".
So a REJECT line stops it cold.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I've been googling for a while now, trying to forward port 3000 to port 80....
In the past I used to DLink router to forward port 3000 to 80. I recently finished (well, is it ever done anyhow?) setting up my linux box and got it acting as a router.
I want to continue to run Apache on port 80... (1 Reply)
Discussion started by: meeps
1 Replies
2. Fedora
Hi..
Anyone can help me..I have setup my linux fedora server and i want to restrict access to my server.Basically i control using iptables.I'm not sure how to write an iptables rules to control drop all connection to port 8080 and allow only certain ip can access the instance on port 8080 example... (0 Replies)
Discussion started by: netxus
0 Replies
3. UNIX for Advanced & Expert Users
I would like to copy data flow (not redirect!!!) from 1567 port
to another 1194 port on same computer. The 1567 Port already binded by Scream program (it is bisy). Is it possible to do it by iptables or for it nesessary another programs? Can you help me in the decision of this question? (1 Reply)
Discussion started by: yanat
1 Replies
4. UNIX for Advanced & Expert Users
Hi To All,
I want to Route my web application to Mysql Database through a proxy server.so for this which approach should i use
1)iptables
2)squid
if Iptables how can i make this worked .this is the ip network i'm having
web application---------Proxy server-----------------Mysql Database... (0 Replies)
Discussion started by: kgrvamsi
0 Replies
5. Debian
Hello, the Nat and the forward worked on my debian server up to the reboot of machines.
The following rules*:
/sbin/iptables -t nat -A PREROUTING -p tcp -i eth2 -d xxx.xxx.xxx.xxx --dport 29070 -j DNAT --to-destination 10.0.1.7:29070
/sbin/iptables -A FORWARD -p tcp -i eth2 -o eth0 -d... (0 Replies)
Discussion started by: titoms
0 Replies
6. Red Hat
Hi,
I have a newly built RHEL5 OS that is unable to talk to the DNS server. I am unable to telnet resolv.conf entry over port 53 but apparently this port has been opened.
# telnet 209.212.96.1 53
and.....
# dig www.google.com
; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5_4.2 <<>>... (9 Replies)
Discussion started by: Duffs22
9 Replies
7. Red Hat
Hi,
What iptables command do I need to run in order to open up the following port for incomming traffic on the following server:
# telnet 127.0.0.1 1521
Trying 127.0.0.1...
telnet: connect to address 127.0.0.1: Connection refused
telnet: Unable to connect to remote host: Connection... (3 Replies)
Discussion started by: Duffs22
3 Replies
8. IP Networking
Hi,
On my linux server I have 2 routes:
Code:
nexthop via 123.201.254.5 dev eth0 weight 38 nexthop via 111.93.155.149 dev eth2 weight 36
I have a iptable rule like :
iptables -t nat -A PREROUTING -p tcp -i eth0 -d... (5 Replies)
Discussion started by: ashokvpp
5 Replies
9. UNIX for Dummies Questions & Answers
I want to limit all *outbound* traffic on eth0 (or all *.*) on port 25 to a specific (allowed) range...
I.E.
192.168.1.5 (local ip) tries to connect to 1.2.3.4:25 (outside real world ip)
It can proceed because 1.2.3.0/24 is the allowed range
Now, 192.168.1.5 (local ip) tries to connect to... (1 Reply)
Discussion started by: holyearth
1 Replies
10. Red Hat
Hello All,
I would like to ask you very kindly with /etc/sysconfig/iptables file
I have to setup port forwarding on RHEL6 router. Users from public network must be able to ssh to servers in private network behind RHEL6 router. Problem is that servers in private network must be isolated.
My... (2 Replies)
Discussion started by: oidipus
2 Replies
accept(1M) System Administration Commands accept(1M)
NAME
accept, reject - accept or reject print requests
SYNOPSIS
accept destination...
reject [-r reason] destination...
DESCRIPTION
accept allows the queueing of print requests for the named destinations.
reject prevents queueing of print requests for the named destinations.
Use lpstat -a to check if destinations are accepting or rejecting print requests.
accept and reject must be run on the print server; they have no meaning to a client system.
OPTIONS
The following options are supported for reject:
-r reason Assigns a reason for rejection of print requests for destination. Enclose reason in quotes if it contains blanks. reason
is reported by lpstat -a. By default, reason is unknown reason for existing destinations, and new printer for destinations
added to the system but not yet accepting requests.
OPERANDS
The following operands are supported.
destination The name of the destination accepting or rejecting print requests. Destination specifies the name of a printer or class of
printers (see lpadmin(1M)). Specify destination using atomic name. See printers.conf(4) for information regarding the
naming conventions for atomic names.
EXIT STATUS
The following exit values are returned:
0 Successful completion.
non-zero An error occurred.
FILES
/var/spool/lp/* LP print queue.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWpcu |
+-----------------------------+-----------------------------+
|CSI |Enabled (see NOTES) |
+-----------------------------+-----------------------------+
SEE ALSO
enable(1), lp(1), lpstat(1), lpadmin(1M), lpsched(1M), printers.conf(4), attributes(5)
NOTES
accept and reject affect only queueing on the print server's spooling system. Requests made from a client system remain queued in the
client system's queueing mechanism until they are cancelled or accepted by the print server's spooling system.
accept is CSI-enabled except for the destination name.
SunOS 5.10 8 Feb 1999 accept(1M)