On Mon, 31 Aug 2015 10:24:03 -0700 Tom Eastep <[email protected]> wrote:
> > It should send broadcasts to 192.168.1.255 and not 5.20.215.255.
> > I don't know how steam knows my WAN broadcast address if I use namespaces.
>
> What is the output of:
>
> ip netns exec steam ip addr ls
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group
default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
19: veth0@if18: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state
UP group default qlen 1000
link/ether 66:74:09:4c:ad:e8 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.11/24 brd 192.168.1.255 scope global veth0
valid_lft forever preferred_lft forever
inet6 fe80::6474:9ff:fe4c:ade8/64 scope link
valid_lft forever preferred_lft forever
> ip netns exec steam ip route ls
default via 192.168.1.10 dev veth0
192.168.1.0/24 dev veth0 proto kernel scope link src 192.168.1.11
> > A question - is it possible to redirect broadcast destined to 5.20.215.255
> > to 192.168.1.255?
> > I quickly tried to use the following rule unsuccessfully:
>
> > DNAT loc loc:192.168.1.255 udp 27036 27036 5.20.215.255
>
> Did that rule change the destination address?
No, sniffer output was the same.
> You also need to SNAT the broadcasts and to DNAT any responses
> (Netfilter doesn't do that automatically).
I suspect that if the Steam client on another PC sees at least one broadcast,
it will contact the sending PC directly and they will see each other.
Regards,
Nerijus
------------------------------------------------------------------------------
_______________________________________________
Shorewall-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/shorewall-users
