SuSe firewall settings

Tags

security

Special Forums Cybersecurity SuSe firewall settings

07-30-2005

Registered User

1, 0

Join Date: Jul 2005

Last Activity: 30 July 2005, 10:24 AM EDT

Posts: 1

Thanks Given: 0

Thanked 0 Times in 0 Posts

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?

MadonnaC

View Public Profile for MadonnaC

Find all posts by MadonnaC

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...

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...

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...

4. BSD

settings in rc.firewall

LEARN ABOUT FREEBSD

nos-tun

NOS-TUN(8)						    BSD System Manager's Manual 						NOS-TUN(8)

NAME

     nos-tun -- implement ``nos'' or ``ka9q'' style IP over IP tunnel

SYNOPSIS

     nos-tun -t tunnel -s source -d destination -p protocol_number [source] target

DESCRIPTION

     The nos-tun utility is used to establish an nos style tunnel, (also known as ka9q or IP-IP tunnel) using a tun(4) kernel interface.

     Tunnel is the name of the tunnel device /dev/tun0 for example.

     Source and destination are the addresses used on the tunnel device.  If you configure the tunnel against a cisco router, use a netmask of
     ``255.255.255.252'' on the cisco.	This is because the tunnel is a point-to-point interface in the FreeBSD end, a concept cisco does not
     really implement.

     Protocol number sets tunnel mode.	Original KA9Q NOS uses 94 but many people use 4 on the worldwide backbone of ampr.org.

     Target is the address of the remote tunnel device, this must match the source address set on the remote end.

EXAMPLES

     This end, a FreeBSD box on address 192.168.59.34:

	   nos-tun -t /dev/tun0 -s 192.168.61.1 -d 192.168.61.2 192.168.56.45

     Remote cisco on address 192.168.56.45:

	   interface tunnel 0
	   ip address 192.168.61.2 255.255.255.252
	   tunnel mode nos
	   tunnel destination 192.168.59.34
	   tunnel source 192.168.56.45

AUTHORS

     Nickolay N. Dudorov <nnd@itfs.nsk.su> wrote the program, Poul-Henning Kamp <phk@FreeBSD.org> wrote the man-page.  Isao SEKI
     <iseki@gongon.com> added a new flag, IP protocol number.

BUGS

     We do not allow for setting our source address for multihomed machines.

BSD
								  April 11, 1998							       BSD

Cybersecurity