한국어

네트워킹

온누리070 플레이스토어 다운로드
    acrobits softphone
     온누리 070 카카오 프러스 친구추가온누리 070 카카오 프러스 친구추가친추
     카카오톡 채팅 상담 카카오톡 채팅 상담카톡
    
     라인상담
     라인으로 공유

     페북공유

   ◎위챗 : speedseoul


  
     PAYPAL
     
     PRICE
     

pixel.gif

    before pay call 0088 from app


http://www.datastax.com/support-forums/topic/iptables-rules-for-datastax-enterprise




There is no official guide on how to configure iptables with DSE...mostly because there is no one way to do it. There are several different ports that are used for different purposes. Some absolutely must be opened in firewall for internode communication, others are optional depending on the tools that you want to use and from where. I'm afraid that the document you quoted is a little too harsh in its wording on requiring all of those ports open for Cassandra to function.

Note: all the ports listed below are TCP ports.

For internode communication:

You must have port 7000 open between all nodes.

Other ports:

7199, 1024+ (the most annoying line for any firewall admin) - These ports are used to open a JMX connection to the cassandra node. So, if you want to use a JMX client to connect to a cassandra node, you need to open these ports for the source IP address of the machine the client is running on. Examples of JMX clients are: JConsole and nodetool. You could have one trusted machine which you run these commands from and have all of the cassandra nodes open these TCP ports to *only* this trusted machine (or small set of machines).

9160 - This is the thrift client port. It is used by utilities like cqlsh, the cassandra-jdbc driver, pycassa and other thrift clients. This port will have to be opened for communications between machines these clients are operating on and the cassandra nodes.

About how to configure iptables. Here is what I usually do (it may or may not work for your level of paranoia, but it will give you a start):

So, first, a bit on TCP and UDP communications: UDP messages are stateless and do not require any set up of a connection before sending a message. TCP on the other hand are stateful. A connection must be set up before any messages containing data are accepted (by the machine's kernel). So, when setting up a firewall for TCP connections, if you do not let the message that sets up the connection through the firewall, you are effectively disallowing any data packets to the port in question. The packet that sets up the connection is a TCP packet with the SYN bit set, and the ACK, RST, and FIN bits cleared. This packet needs to be stopped in order to stop a connection from being set up. So, for TCP, I usually allow all packets except for ones with the SYN bit set (and ACK, RST, and FIN cleared) whose destination port is not to be opened.

Another note. iptables has several tables and chains in these tables. We will be modifying the default table of: filter and chain: INPUT.

For example to close all ports except for SSH (port 22) to the machine from anywhere, you can use the following rules:

iptables --append INPUT --proto tcp --destination-port 22 --syn -j ACCEPT
iptables --append INPUT --proto tcp --syn -j DROP

It creates the following rules:

# iptables -L
Chain INPUT (policy ACCEPT)
target     prot opt source               destination
ACCEPT     tcp  --  anywhere             anywhere             tcp dpt:sshflags: FIN,SYN,RST,ACK/SYN
DROP       tcp  --  anywhere             anywhere             tcpflags: FIN,SYN,RST,ACK/SYN

Note, the default policy is still ACCEPT. This means accept all packets for already connected TCP connections, and drop all new connection requests except for to port 22 from any source IP address. You could also specify a source IP address in your iptables rule to open port 22 (in order to make it more restrictive):

iptables --append INPUT --proto tcp --destination-port 22 --source address[/mask][,...] --syn -j ACCEPT

So, for cassandra, you need to open 7000 on each cassandra node to other nodes in the cluster. You can specify the source by individual machines or by a whole subnet.

조회 수 :
16773
등록일 :
2014.02.26
15:33:32 (*.251.139.148)
엮인글 :
http://webs.co.kr/index.php?document_srl=38852&act=trackback&key=839
게시글 주소 :
http://webs.co.kr/index.php?document_srl=38852
List of Articles
번호 제목 글쓴이 날짜sort 조회 수
61 Using Windows RDP to Access your Ubuntu Instance admin 2014-12-21 10391
60 Install GUI on Ubuntu Server admin 2014-12-21 10518
59 How to start GUI from command line? admin 2014-12-21 11195
58 Download all files in a directory using WGET admin 2014-12-16 10132
57 문서 편집기 vi vim command 명령어 정리 admin 2014-10-29 14865
56 find 명령 사용 예제들 admin 2014-10-29 11905
55 특정 IP 엑세스 못하게 하는방법 admin 2014-10-29 13160
54 scp 명령어를 이용한 파일 복사 및 전송 admin 2014-10-29 15712
53 [리눅스] 소프트웨어 레이드의 리빌딩 및 리싱킹 속도를 높이는 5가지 방법 admin 2014-10-17 12044
52 /bin/false, /sbin/nologin 의 차이점 admin 2014-10-13 15330
51 리눅스 시스템 유저 추가 명령어 useradd 사용하기 admin 2014-08-09 12833
50 리눅스 시스템 시작시에 자동 실행할 파일 등록하기 admin 2014-03-22 82944
49 linux 에티터 명령어 정리 포그라운드 전환 : ctrl + z 다시 vi 모드로 돌아오려면 fg admin 2014-03-05 37694
48 Linux Memory Management – Virtual Memory and Demand Paging admin 2014-03-03 15655
» iptables rules tcp drop all port except tcp 22 admin 2014-02-26 16773
46 seagate HD 시게이트 하드 디스크 A/S 에이에스 기간 조회 및 받는 3가지 방법 admin 2013-12-09 19755
45 SSH Without Authentication Using Key Files (CentOS 5.6) admin 2013-11-22 15236
44 Getting started with SSH public key cryptography admin 2013-09-05 40072
43 암호 없이 SSH 접속하기 admin 2013-09-05 17873
42 Linux Date Command Examples to Display and Set System Date Time admin 2013-07-11 20488
41 FreeRADIUS 설치(freeradius-sever-2.1.8) admin 2013-04-19 50460
40 Radius를 이용한 ssh 인증 서버 구축하기 admin 2013-04-19 36544
39 CentOS 5.4에서 RADIUS 서버 설치하기 admin 2013-04-19 50774
38 Event IP 20187 admin 2013-04-08 16008
37 리눅스에서 자바(JDK) 설치하기 admin 2013-04-08 18246
36 리눅스 네트워크 설정 멸령어 Linux admin 2013-04-08 17157
35 [linux]리눅스 버전및 CPU등 환경정보 확인하기 admin 2013-04-08 78958
34 Linux 시스템 백업과 복원 admin 2013-04-04 26527
33 tar로 전체시스템 백업 LINUX Backup admin 2013-04-04 64375
32 다운된 리눅스서버 응급복구 admin 2013-03-28 32357