SuSe firewall settings

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 DEBIAN

vlan-interfaces

VLAN-INTERFACES(5)						   File formats 						VLAN-INTERFACES(5)

NAME

       /etc/network/interfaces (vlan) - vlan extensions for the interfaces(5) file format

DESCRIPTION

       /etc/network/interfaces	contains  network  interface  configuration  information  for  the  ifup(8)  and ifdown(8) commands.  This manpage
       describes the vlan extensions to the standard interfaces(5) file format.

       Primary extensions exist to make and destroy vlan interfaces, secondary extensions exist for ipv4 interface manipulation which  are  gener-
       ally needed when using (a lot of) vlans.

VLAN CREATION

       Vlan  interface	definitions  exist  of the vlan interface name, and an optional 'raw-device' parameter.  Vlan interfaces are numbered 1 to
       4095.  You have the option to have interface names zero-padded to 4 numbers, or just the plain digits without leading zero.  The  following
       example shows four ways to create a vlan with id 1 on interface eth0.  They all result in different names.

	iface eth0.1 inet static
	    address 192.168.1.1
	    netmask 255.255.255.0

	iface vlan1 inet static
	    vlan-raw-device eth0
	    address 192.168.1.1
	    netmask 255.255.255.0

	iface eth0.0001 inet static
	    address 192.168.1.1
	    netmask 255.255.255.0

	iface vlan0001 inet static
	    vlan-raw-device eth0
	    address 192.168.1.1
	    netmask 255.255.255.0

	# We don't have br support out of the box
	iface br0.2 inet static
	    vlan-raw-device br0
	    address 192.168.1.1
	    netmask 255.255.255.0

	# Aliases are ignored
	iface br0.2:1 inet static
	    address 192.168.1.1
	    netmask 255.255.255.255

EXTRA IFACE OPTIONS

       Usually someone who uses vlans also wants to do some other manipulations with the ip stack or interface.

       vlan-raw-device devicename
	      Indicates the device to create the vlan on.  This is ignored when the devicename is part of the vlan interface name.

       ip-proxy-arp 0|1
	      Turn proxy-arp off or on for this specific interface.  This also works on plain ethernet like devices.

       ip-rp-filter 0|1|2
	      Set the return path filter for this specific interface.  This also works on plain ethernet like devices.

       hw-mac-address mac-address
	      This sets the mac address of the interface before bringing it up.  This works on any device that allows setting the hardware address
	      with the ip command.

AUTHOR

       This manpage was adapted from interfaces(5) by Ard van Breemen <ard@kwaak.net>

SEE ALSO

       vconfig(8) interfaces(5)

vlan								 September 30 2007						VLAN-INTERFACES(5)

Cybersecurity