On Thu, 3 Sep 2015 09:50:21 -0700 Tom Eastep <[email protected]> wrote:
> > 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? > > No idea. I changed traffic direction - started Steam on the previous client PC, so that it is now the sending one. It has only the one network interface, so no netns is used. Broadcast is seen by the receiving PC (previous sending PC). I examined traffic dump with a sniffer - the broadcast packet has Dst IP 192.168.1.255 and MAC ff:ff:ff:ff:ff:ff. Now I changed direction back again. The broadcast packet has Dst IP 192.168.1.255 and MAC 00:1b:21:0e:xx:xx. It is the MAC of my local ethernet interface. How do I make it ff:ff:ff:ff:ff:ff? For the reference, the shorewall rule is: DNAT loc loc:192.168.1.255 udp 27036 27036 5.20.215.255 Regards, Nerijus ------------------------------------------------------------------------------ _______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
