top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

OpenSuse blocks outgoing connections to 3260 port. IPTABLES is not configured

+1 vote

I use OpenSuse 12.2. IPTABLES is not configured. I could connect to any port from the server except 3260. What could be the problem?

The server is a qemu guest. From the guest, I cannot make outgoing connections to port 3260. Connections to other ports are working fine.

posted Aug 17, 2013 by anonymous

Share this question
Facebook Share Button Twitter Share Button LinkedIn Share Button
one place u are saying IPTABLES is configured and other place it is not. Put more detail to comment anything.
Thanks.  I've now corrected the post.

1 Answer

0 votes

I assume that this is not in the network environment, one clue is that 3260 is iSCSI target.

answer Aug 17, 2013 by Salil Agrawal
Yes.. It's iscsi-target...

Problem is connection to iscsi-target also is not sent out from the server. There are another set of servers with same config and they can communicate to iscsi-targets without any problem.
It is something to do with the network, not with the SuSe machine. But looks that you need to do debug.
Similar Questions
+1 vote

If you have an 'accept' rule for a service that is not currently running, is it possible to have iptables to simply not respond instead of reporting the port as 'closed'? During a port scan at, if the router doesn't reply the port will be reported as 'stealth'.

+1 vote

I have a problem with iptables on CentOS 6.2.

I configured:

chkconfig iptables on
and the file /etc/sysconfig/iptables

If you reboot the machine configurations are not loaded. iptables-L gives me the default configurations (not assigned) if I (a machine booted): service iptables start then then it works. How can I fix?

0 votes

I'm playing around with iptables and have inserted a few new rules. Now, I want to flush them all so I use

iptables -F

Then, I restart the firewall with

service iptables restart

and everything looks like it's restarting alright. But when I list the rules using

iptables -L

I get a list of rules THAT INCLUDE all of the rules I've defined before the flush! Am I reading this wrong or is something weird with my iptables?

+2 votes

Can someone help on how to replace the next iptables rule with nft:

iptables -t raw -A PREROUTING -i eth0 -j CT --notrack

Is this possible with nft or not?

+3 votes

consider this scenario:

PC1 wants to telnet to SRV1 tcp 40000.

I would like to put a proxy in the middle that receives the connection, rewrites the destination, sends packet to a local socks proxy (redsocks).

So the scenario would be:

PC1 --> PROXY tcp 20000 [iptables rewrites destination to SRV tcp 40000 --> redsocks tcp 12345] --> SRV1 tcp 40000

I tried:
iptables -t nat -A PREROUTING -p tcp -s $MYSOURCEIP --dport 20000 -j DNAT --to $SRV1:40000

It works, but I know it doesn't go through redsocks. I just changed the destination for the packets but how can I force them to flow into redsocks?