similar to: multicast forwarding

I am trying to set up my Shorewall box to forward multicast packets to my local net. I do have some problems with mrouted (see below), but I can join and add routes using smcroute. Multicast works when shorewall is disabled. I got a lot of help from the following. http://lists.shorewall.net/pipermail/shorewall-users/2005-January/016674.html I cannot get the multicast packets to pass the fw when

I have a standard 3 interface shorewall setup and I want to receive multicast stuff from ''net'' -> ''loc''. This requires me, first, to do an IGMP join which involves 192.168.1.x -> 224.0.0.x being NATed out as the ''net'' interface''s IP address. Obviously replies have to be NATed back to ''loc'' addresses. Can

Hi, all! Can I enable multicasting via shorewall? I have router with Gentoo Linux (one interface to ISP, one with alises - to local network). Shorewall work perfect! But now I need setup Quagga (zebra) for dynamic routing between one more router via another provider. All routers daemons (zebra, ripd, ospf) used multicasting. In my configuration already enabled allowBcast and etc.

(non-subscriber -- please CC: any responses to me, thanks.) I need to have port forwarding to an external interface''s IP address enabled from the behind the firewall, but I don''t want all internal traffic routed through the firewall as per http://www.shorewall.net/FAQ.htm#faq2a , just the traffic to two ports. Is there any way to do this? (I know this is more properly handled

yes, ip_forward was turned on. iptables is defaulted to ACCEPT policy on all the 3 chains. On Sat, May 14, 2016 at 1:24 AM, Guus Sliepen <guus at tinc-vpn.org> wrote: > On Sat, May 14, 2016 at 12:06:51AM +0800, Terry T wrote: > > > I have a Debian 8 64-bit machine set up as a server and apt-got the tinc > > package. I configured tinc as a bridge and everything seems

On Sat, May 14, 2016 at 12:06:51AM +0800, Terry T wrote: > I have a Debian 8 64-bit machine set up as a server and apt-got the tinc > package. I configured tinc as a bridge and everything seems normal except > that the tunnel does not forward multicast traffic. Did you enable forwarding (echo 1 >/proc/sys/net/ipv4/ip_forward) and allow forwarding in your iptables rules? -- Met

Hello, I recently setup Shorewall 2.0.9 on a RedHat 9 machine using the two interface quick start guide. ip addr show: 1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 brd 127.255.255.255 scope host lo 2: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 100 link/ether 00:20:ed:76:dc:82 brd

(if this post gets line-feed-mangled please read http://www.dl.reneschmidt.de/shorewallxenpost.txt - that''s an unmangled version, thank you) Hello, first I would like to thank the Mr. Eastep and contributors for this great piece of software and superb documentation. I have a SOHO server (Debian testing) that I''m using for several purposes so I''ve set up a Xen

Hello all, Yesterday I noticed that my system was "leaking" traffic towards the 10/8 network, I have shorewall installed on multiple machines ranging from single interface devices to ones with 10+ interfaces. I tested all the boxes and they are showing the same behavior. All systems are CentOS 3.4, 2.4.21-27.0.2.ELsmp. Shorewall version: 2.2.1 For the host mentioned is a single

Hello, I have a question regarding my shorewall setup. I?m not yet subscribed to the mailing list. My firewall has two interfaces: eth0 Link encap:Ethernet HWaddr 00:04:76:96:B7:1A inet addr:10.48.20.30 Bcast:10.48.31.255 Mask:255.255.240.0 inet6 addr: fe80::204:76ff:fe96:b71a/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX

Hello! So i got this problem. I have a debian sarge (with 2.6 kernel) box with shorewall up and network something like this: (net-ip)adsl-router(10.0.0.2)->(10.0.0.5)debian(192.168.0.1)->(192.168.0.x)lan-machines Everything works just great but i cant get port forwarding to work. shorewall show nat shows the traffic (to port 2002) but the machine (192.168.0.3) isnt getting it.. I have

I have a Debian 8 64-bit machine set up as a server and apt-got the tinc package. I configured tinc as a bridge and everything seems normal except that the tunnel does not forward multicast traffic. I used tcpdump to examine the br0, eth0 and tap interfaces. I could see multicast packets on both br0 and eth0, but there is no such packet present on the tap interface. I don't quite know why

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I am forwarding your post to the Debian Shorewall maintainer -- none of the code involved in Shorewall startup under Debian is part of the standard Shorewall distribution. - -Tom - -------- Original Message -------- Subject: [Shorewall-users] Problems with Firewall start at Boot time Date: Mon, 06 Sep 2004 16:48:16 -0400 From: Stewart Outram

On Sat, May 14, 2016 at 01:27:10AM +0800, Terry T wrote: > yes, ip_forward was turned on. > > iptables is defaulted to ACCEPT policy on all the 3 chains. Hm. What is generating the multicast traffic? Could it be that the TTL on the pacets is set to 1, so it will not be forwarded? -- Met vriendelijke groet / with kind regards, Guus Sliepen <guus at tinc-vpn.org>

> tap0 Link encap:Ethernet HWaddr ae:a2:e1:cd:aa:68 > inet6 addr: fe80::aca2:e1ff:fecd:aa68/64 Scope:Link > UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:2336 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:500 > RX

Hi all, I have a problem to get my Linux machine to masquerade for other computers on the network. My main machine is connect to the ADSL modem on eth0. The machine also has another network card, eth1 which connects directly to the other computer. Both machines can ping each other fine, but I can''t access the net from the other (Windows) system. IP Configuration on the linux

Hi, Whilst doing some QA work on XORP on my desktop, which has fxp0 and msk0, fxp0 got totally hosed. I was running PIM-SM and IGMPv2 router-mode on the box at the time. I wonder if this is related to the problems with fxp multicast transmission I saw back in April. I'm a bit concerned about this as fxp is still a very widespread and useful network chip. I am running

Hello, I have started playing around with docker (https://www.docker.io/) and am having trouble to integrate the "docker0" bridge it creates on the fly into my shorewall setup (version 4.5.16.1) on debian testing. IP forwarding is on and I have defined a "doc" ipv4 zone and the interfaces has an entry like so, > doc docker0

Hi folks, Has anyone out there done port forwarding or DNAT for UDP packets that are normally sent to the broadcast address (255.255.255.255)? I have to support a nasty database application called FileMaker Pro (those of you who know it are probably groaning about now), which uses broadcasts to locate the database server. Theoretically, i can get around this requirement by using LDAP lookups

Hi!, I have Fedora 2 installed (Kernel 2.6), 3 interfaces (eth0,eth1,eth2), in the eth1 i have my local network and eth0 the Internet conection, when i do masquerading (eth1 out by eth0) only works for a few minutes. I dont know what i?m doing wrong, or only is an incompability or error between the OS Fedora 2 and the shorewall 2.0.7...i restart the shorewall service ones works anothers doesnt.