# Firewall - Block Port 9300

**URL:** https://discuss.elastic.co/t/firewall-block-port-9300/143629
**Category:** Elasticsearch
**Created:** [August 9, 2018, 4:45am UTC](https://discuss.elastic.co/t/firewall-block-port-9300/143629 "2018-08-09T04:45:08Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![sanket.maru](https://avatars.discourse-cdn.com/v4/letter/s/ee59a6/32.png) [@sanket.maru](https://discuss.elastic.co/u/sanket.maru)
#### Post date: [August 9, 2018, 4:45am UTC](https://discuss.elastic.co/t/firewall-block-port-9300/143629/1 "2018-08-09T04:45:08Z")

</div>

I have a multi node cluster with 3 masters, 4 data nodes, 2 ingest nodes.  
My cluster is working and I am blocking port 9300 on one of the data or master nodes. To block port 9300 which is used communicating between the nodes I am using below command :

sudo ufw deny 9300.

I can see in firewall status that 9300 port has been denied , but still I can see that search, post requests are being served by that node. I have enabled trace logging and can see in logs that every 30 seconds master is pinging data nodes and getting response.

Is this expected behaviour ? How Elastic is serving request even if port has been blocked.

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)
#### Post date: [September 6, 2018, 4:45am UTC](https://discuss.elastic.co/t/firewall-block-port-9300/143629/2 "2018-09-06T04:45:13Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
