Skip to contentSkip to conversation

block broadcast traffic

DISCUSSION George Liu 2 participants 2 messages Mar 3, 2005 – Mar 4, 2005

lore
Share & tools
lore

George Liu

author
#0 lore raw

I tried to use iptables to block inbound and outbound netbios broadcast announcement traffic of a system with IP 10.1.1.76. It seems iptables doesn't work. Is this a limitation or rule wrong? Thanks.

*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
:RH-Firewall-1-INPUT - [0:0]
-A INPUT -j RH-Firewall-1-INPUT
-A FORWARD -j RH-Firewall-1-INPUT

-A RH-Firewall-1-INPUT -s 10.1.1.0/22 -p udp -m multiport --ports 135,136,237,138,139,445 -j REJECT -A RH-Firewall-1-INPUT -d 10.1.1.0/22 -p udp -m multiport --ports 135,136,237,138,139,445 -j REJECT -A RH-Firewall-1-INPUT -p udp -m multiport --ports 135,136,237,138,139,445 -j REJECT

#1 lore raw
Quoted 3 lines · George Liu

I tried to use iptables to block inbound and outbound netbios broadcast announcement traffic of a system with IP 10.1.1.76. It seems iptables doesn't work.

i'm pretty sure iptables works...maybe just for me though.

are you applying these rules *on* 10.1.1.76 in an attempt to keep it from sending/receiving netbios packets; or is 10.1.1.76 remote to this machine with the firewall rules?

if it's the first case--you need to be modifying INPUT and OUTPUT, not INPUT and FORWARD...(in any case--broadcast packets are not normally forwarded through routing gateways anyways...)

Quoted 11 lines

Is this a limitation or rule wrong? Thanks.

*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
:RH-Firewall-1-INPUT - [0:0]

(quoted diff) +0 -3
-A INPUT -j RH-Firewall-1-INPUT
-A FORWARD -j RH-Firewall-1-INPUT
 
-A RH-Firewall-1-INPUT -s 10.1.1.0/22 -p udp -m multiport --ports 
Quoted 5 lines

135,136,237,138,139,445 -j REJECT
-A RH-Firewall-1-INPUT -d 10.1.1.0/22 -p udp -m multiport --ports 135,136,237,138,139,445 -j REJECT
-A RH-Firewall-1-INPUT -p udp -m multiport --ports 135,136,237,138,139,445 -j REJECT

ports 135, 139, and 445 in the context of a microsoft network use TCP, not UDP; and are unicast, not broadcast based.

the UDP ports used for name and service broadcasts are UDP 137 and 138, not 237 and 138...

-j

--
"Call this an unfair generalization if you must, but old people are
no good at everything."
--The Simpsons