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
oidentd_masq.conf(5)						File Formats Manual					      oidentd_masq.conf(5)

NAME
oidentd_masq.conf - oidentd IP masquerading/NAT configuration file. DESCRIPTION
If you are using IP masquerading or NAT, oidentd can optionally return a username for connections from other machines. Support for this is specified by calling oidentd with the -m (or --masq) flag and by creating an /etc/oidentd_masq.conf file. oidentd can also forward requests for an IP masqueraded connection to the machine from which connection originates by way of the -f option. This will only work if the host to which the connection is forwarded is running oidentd with the -P (proxy) flag, or if the host's ident daemon will return a valid reply regardless of the input supplied by and the address of the host requesting the info (some ident daemons for windows do this, maybe others). FORMAT
<IP Address|Hostname>[/<Mask>] <Ident Response> <System Type> The first field contains the IP address or the hostname of a machine that IP masquerades through the machine on which oidentd runs. The mask parameter can be either a network mask or a mask in CIDR notation. A mask of 24 is equivalent to 255.255.255.0, a mask of 16 is equivalent to 255.255.0.0, etc. The second field specifies the reply that oidentd will return for lookups to the host matching the IP address specified in the first param- eter. The third field specifies the operating system the machine matching the first parameter is running. EXAMPLES
<Host>[/<Mask>] <Ident Response> <System Type> 192.168.1.1 someone UNIX 192.168.1.2 noone WINDOWS 192.168.1.1/32 user1 UNIX 192.168.1.0/24 user3 UNIX 192.168.0.0/16 user4 UNIX somehost user5 UNIX 192.168.1.0/255.255.255.0 user6 UNIX AUTHOR
Ryan McCabe <ryan@numb.org> http://dev.ojnk.net SEE ALSO
oidentd(8) oidentd.conf(5) version 2.0.8 13 Jul 2003 oidentd_masq.conf(5)