[opensuse] SUSE Firewall blocking LAN traffic
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm trying to setup a web2py server to serve music to the various machines in my house. All the machines live behind a NAT router and they all run openSUSE 13.1 or 13.2. The only way I can get a connection between machines is to stop the Firewall on each machine. What setting in YaST > Firewall do I need to change to allow internal LAN traffic, but still protect each machine from the WAN? TIA Bob - -- Bob Williams System: Linux 3.16.7-7-desktop Distro: openSUSE 13.2 (x86_64) with KDE Development Platform: 4.14.3 Uptime: 06:00am up 7:55, 3 users, load average: 0.16, 0.05, 0.06 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlULG/sACgkQ0Sr7eZJrmU7JIgCeLuFUhgjlL44qx/W467Q4zLW1 RDsAnRzm7w24O3PX8c3ZKoS5cwMXZzMn =WP2A -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/19/2015 02:57 PM, Bob Williams wrote:
I'm trying to setup a web2py server to serve music to the various machines in my house. All the machines live behind a NAT router and they all run openSUSE 13.1 or 13.2. The only way I can get a connection between machines is to stop the Firewall on each machine.
What setting in YaST > Firewall do I need to change to allow internal LAN traffic, but still protect each machine from the WAN?
Since you already have a firewall facing the Internet, you don't need to run a firewall again on each computer. However, you can set up custom rules to allow everything from your local network through. Just go into "Custom Rules" and set up rules to allow Source Network traffic in from your local network. You may have to create rules for both TCP and UDP (and possibly RCP if needed). You shouldn't need to specify source or destination ports. Please note, I haven't tried this, but that's generally what you want. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Thu, Mar 19, 2015 at 03:21:44PM -0400, James Knott wrote:
On 03/19/2015 02:57 PM, Bob Williams wrote:
I'm trying to setup a web2py server to serve music to the various machines in my house. All the machines live behind a NAT router and they all run openSUSE 13.1 or 13.2. The only way I can get a connection between machines is to stop the Firewall on each machine.
What setting in YaST > Firewall do I need to change to allow internal LAN traffic, but still protect each machine from the WAN?
Since you already have a firewall facing the Internet, you don't need to run a firewall again on each computer. However, you can set up custom rules to allow everything from your local network through. Just go into "Custom Rules" and set up rules to allow Source Network traffic in from your local network. You may have to create rules for both TCP and UDP (and possibly RCP if needed). You shouldn't need to specify source or destination ports. Please note, I haven't tried this, but that's generally what you want.
If your machine is in the internal network, you can also just move the network interface to the "INTERNAL" zone, basically opening the firewall. Ciao, MArcus -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 19/03/15 21:48, Marcus Meissner wrote:
On Thu, Mar 19, 2015 at 03:21:44PM -0400, James Knott wrote:
On 03/19/2015 02:57 PM, Bob Williams wrote:
I'm trying to setup a web2py server to serve music to the various machines in my house. All the machines live behind a NAT router and they all run openSUSE 13.1 or 13.2. The only way I can get a connection between machines is to stop the Firewall on each machine.
What setting in YaST > Firewall do I need to change to allow internal LAN traffic, but still protect each machine from the WAN?
Since you already have a firewall facing the Internet, you don't need to run a firewall again on each computer. However, you can set up custom rules to allow everything from your local network through. Just go into "Custom Rules" and set up rules to allow Source Network traffic in from your local network. You may have to create rules for both TCP and UDP (and possibly RCP if needed). You shouldn't need to specify source or destination ports. Please note, I haven't tried this, but that's generally what you want.
If your machine is in the internal network, you can also just move the network interface to the "INTERNAL" zone, basically opening the firewall.
Ciao, MArcus
Thanks to both of you for your advice. That's reassuring. Bob - -- Bob Williams System: Linux 3.16.7-7-desktop Distro: openSUSE 13.2 (x86_64) with KDE Development Platform: 4.14.3 Uptime: 06:00am up 7:55, 3 users, load average: 0.16, 0.05, 0.06 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlULTwcACgkQ0Sr7eZJrmU50OgCdHXjipulIXA6VPgHLHuce+2W4 bqAAn3c4AS8OeckeMwY0UmHw5TCWm8IW =KjKs -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/19/2015 05:48 PM, Marcus Meissner wrote:
If your machine is in the internal network, you can also just move the network interface to the "INTERNAL" zone, basically opening the firewall.
I thought that was just to indicate the trusted network, which means everything will get through, no matter the source address. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (3)
-
Bob Williams -
James Knott -
Marcus Meissner