SuSe firewall settings


 
Thread Tools Search this Thread
Special Forums Cybersecurity SuSe firewall settings
# 1  
Old 07-30-2005
SuSe firewall settings

I am trying to set up a home network, with router for internet access
All computers, in both windows and Suse 9.3 can get to the internet.

Gateway 192.168.2.1

Computers on static IPs 192.168.2.2-5
When I go into Suse, the samba shares can be seen, and used, so that part is working, but there is no connection to other programs/games, and they report timeouts.

How do I open everything up for internal IP ranges, while keeping the standard rules for internet access?
Login or Register to Ask a Question

Previous Thread | Next Thread

4 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Help with firewall settings

Hi all, I am confusing myself with trying to set up a firewall and hope someone here can help me progress. I have a small cluster of three Raspberry PI's running NOOBS, which I believe is a Debian fork. I have a "Gateway" machine, if that is the right phrase, that has a USB Wifi dongle... (0 Replies)
Discussion started by: steadyonabix
0 Replies

2. SuSE

Suse Security Settings

1) PermitEmptyPasswords is set to No # grep "^PermitEmptyPasswords" /etc/ssh/sshd_config PermitEmptyPasswords no If there is no output does it implies 'As parameter was not set mean system will also not accepted emptypassword.' 2) Users is not allowed to set... (2 Replies)
Discussion started by: alvinoo
2 Replies

3. IP Networking

settings in rc.firewall

Hi everyone. I'm trying to setup eMule and torrents on the local network behind the BSD server. And everything seems to work except one detail - it works as long as ${fwcmd} add deny log tcp from any to any in via ${oif} setup is commented out. Meaning that not only required ports are open, but... (2 Replies)
Discussion started by: reality
2 Replies

4. BSD

settings in rc.firewall

Hi everyone. I'm trying to setup eMule and torrents on the local network behind the BSD server. And everything seems to work except one detail - it works as long as ${fwcmd} add deny log tcp from any to any in via ${oif} setup is commented out. Meaning that not only required ports are open,... (1 Reply)
Discussion started by: reality
1 Replies
Login or Register to Ask a Question
tgt-setup-lun(8)					      System Manager's Manual						  tgt-setup-lun(8)

NAME
tgt-setup-lun - creates a target, adds a device to the target and defines initiators that can connect to the target SYNOPSIS
tgt-setup-lun -d device -n target_name [initiator_IP1 initiator_IP2 ...] [-h] DESCRIPTION
Starts tgtd if necessary and creates a target according to the supplied target_name. The format of the target name is as follows: iqn.2001-04.com.<hostname>-<target_name> The target name must be unique. The script then adds the requested device to the target. If specific IP addresses are defined, it adds them to the list of allowed initia- tors for that target. If no IP addresses is defined, it defines that the target accepts any initiator. EXAMPLES
Create a target that uses /dev/sdb1 and allows connections only from 192.168.10.81: tgt-setup-lun -d /dev/sdb1 -n my_target 192.168.10.81 Create a target that uses /dev/sdb1 and allows connections only from 192.168.10.81 and 192.168.10.82: tgt-setup-lun -d /dev/sdb1 -n my_target 192.168.10.81 192.168.10.82 Create a target that uses /dev/sdb1 and allows connections from any initiator: tgt-setup-lun -d /dev/sdb1 -n my_target Display help: tgt-setup-lun -h AUTHOR
Written by Erez Zilber REPORTING BUGS
Report bugs to <stgt@vger.kernel.org> COPYRIGHT
Copyright (C) Voltaire Ltd. 2008. tgt-setup-lun(8)