Ignacio Valdes Implementation Log/Episode7: Difference between revisions

From VistApedia
Jump to navigationJump to search
 
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
==The Intracare Implementation Log [[Episode5|(Back to Episode 5)]] [[Intracare Implementation Log|(Back to Log Homepage)]] [[Episode8|(On to Episode 8)]]==
==The Intracare Implementation Log 7 [[Episode6|(Back to Episode 6)]] [[Intracare Implementation Log|(Back to Log Homepage)]] [[Episode8|(On to Episode 8)]]==
[[Category:Intracare Implementation Log]]
[[Category:Intracare Implementation Log]]


Line 6: Line 6:
Ignacio Valdes Date: Mon, 28 Jul 2008 16:41:48 -0500
Ignacio Valdes Date: Mon, 28 Jul 2008 16:41:48 -0500


So we had the server up and running but could only get CPRS running by
So we had the server up and running but could only get CPRS running by
ssh tunnel at first. We had to open a port on the Linux server as
ssh tunnel at first. We had to open a port on the Linux server as
well. Congruency of port numbers for both client and server are
well. Congruency of port numbers for both client and server are
necessary. Something like 9330 which should be present in the CPRS P=
necessary. Something like 9330 which should be present in the CPRS P=
parameter list and in the xinetd listening port. We used a TCP, not a
parameter list and in the xinetd listening port. We used a TCP, not a
UDP port so step 2 below is not necessary if you are using TCP only.
UDP port so step 2 below is not necessary if you are using TCP only.
The following commands taken from this page:
The following commands taken from this page:
http://blog.eukhost.com/webhosting/how-to-open-port-on-server where
http://web.archive.org/web/20140501133838/https://www.blog.eukhost.com/webhosting/how-to-open-port-on-server
needed to open our port on the Fedora 9 server so that we could use
where needed to open our port on the Fedora 9 server so that we could use
CPRS from any client without the tunnel:
CPRS from any client without the tunnel:
 
you can verify the port with
you can verify the port with
 
netstat -nap | grep :
netstat -nap | grep :
 
1.you can open TCp port with
1.you can open TCp port with  
 
iptables -A INPUT -p tcp –dport 9330 -j ACCEPT
iptables -A INPUT -p tcp –dport 9330 -j ACCEPT
 
2. You can open UDP port with
2. You can open UDP port with
 
iptables -A INPUT -p udp –sport -j ACCEPT
iptables -A INPUT -p udp –sport -j ACCEPT
 
after that
after that
 
3. service iptables save
3. service iptables save
 
and for flushhing iptables us
and for flushhing iptables us
 
4. iptables -F  
4. iptables -F  
 
[[Episode5|Episode 5]] [[Intracare Implementation Log|Log Homepage]] [[Episode8|Episode 8]]
[[Episode6|Episode 6]] [[Intracare Implementation Log|Log Homepage]] [[Episode8|Episode 8]]

Latest revision as of 04:33, 13 November 2020

The Intracare Implementation Log 7 (Back to Episode 6) (Back to Log Homepage) (On to Episode 8)

iptables and other useful port commands

Ignacio Valdes Date: Mon, 28 Jul 2008 16:41:48 -0500

So we had the server up and running but could only get CPRS running by
ssh tunnel at first. We had to open a port on the Linux server as
well. Congruency of port numbers for both client and server are
necessary. Something like 9330 which should be present in the CPRS P=
parameter list and in the xinetd listening port. We used a TCP, not a
UDP port so step 2 below is not necessary if you are using TCP only.
The following commands taken from this page:
http://web.archive.org/web/20140501133838/https://www.blog.eukhost.com/webhosting/how-to-open-port-on-server
where needed to open our port on the Fedora 9 server so that we could use
CPRS from any client without the tunnel:

you can verify the port with

netstat -nap | grep :

1.you can open TCp port with 

iptables -A INPUT -p tcp –dport 9330 -j ACCEPT

2. You can open UDP port with

iptables -A INPUT -p udp –sport -j ACCEPT

after that

3. service iptables save

and for flushhing iptables us

4. iptables -F 

Episode 6 Log Homepage Episode 8