On Tue, 1 Sep 2015 16:48:45 -0700 Tom Eastep <[email protected]> wrote:
> The dump shows no conntrack entry for the broadcasts; yet it appears > that steam is running. > > Interestingly, one packet has matched the DNAT rule -- I would have > thought that your loc->loc rules would have been the correct one if > steam is running in the steam netns. Did you inadvertently run steam > outside that netns since Shorewall was restarted. I ran Steam under netns when testing, but sometimes I ran it normally when not testing. Today I ran Steam under netns and it sent correct broadcast: 346 6.393202 192.168.1.11 -> 192.168.1.255 UDP 136 Source port: 27036 Destination port: 27036 Then I ran Steam normally and then again under netns, and broadcast became wrong again: 12562 502.839578 192.168.1.11 -> 5.20.215.255 UDP 138 Source port: 27036 Destination port: 27036 So it seams Steam somehow caches incorrect broadcast address. After some time broadcast became right again. But now another problem - Steam sends correct broadcast, but the client PC does not see it. tshark -i wlan0 -Y "tcp.port == 27036 or udp.port == 27036" on the client does not show any output, while the sniffer on the sending PC shows outgoing broadcasts. What could be wrong? Regards, Nerijus ------------------------------------------------------------------------------ Monitor Your Dynamic Infrastructure at Any Scale With Datadog! Get real-time metrics from all of your servers, apps and tools in one place. SourceForge users - Click here to start your Free Trial of Datadog now! http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140 _______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
