Re: [Shorewall-users] WireGuard Port Forwarding

2018-12-23 Thread C. Cook
On 12/23/18 12:29 PM, C. Cook wrote: > On 12/23/18 11:59 AM, C. Cook wrote: >> In the router I am trying to DNAT an IP that should be _encapsulated >> in the tunnel_.  It must be that I should DNAT the LAN address of the >> WG server. >> >> *DOH!!* >> >> Now it is fscking pinging the WG server 10.1

Re: [Shorewall-users] WireGuard Port Forwarding

2018-12-23 Thread C. Cook
On 12/23/18 11:59 AM, C. Cook wrote: > In the router I am trying to DNAT an IP that should be _encapsulated > in the tunnel_.  It must be that I should DNAT the LAN address of the > WG server. > > *DOH!!* > > Now it is fscking pinging the WG server 10.1.5.16  from the phone! > > But I can't ping th

Re: [Shorewall-users] WireGuard Port Forwarding

2018-12-23 Thread C. Cook
On 12/23/18 11:12 AM, Justin Pryzby wrote: > On Sun, Dec 23, 2018 at 10:49:30AM -0800, C. Cook wrote: >> On 12/23/18 9:04 AM, Tom Eastep wrote: >>> Clearly, your routing table indicates that the packet should be sent out >>> of eth0 rather than eth1, and since eth0 doesn't have the 'routeback' >>>

Re: [Shorewall-users] WireGuard Port Forwarding

2018-12-23 Thread Justin Pryzby
On Sun, Dec 23, 2018 at 10:49:30AM -0800, C. Cook wrote: > On 12/23/18 9:04 AM, Tom Eastep wrote: > > Clearly, your routing table indicates that the packet should be sent out > > of eth0 rather than eth1, and since eth0 doesn't have the 'routeback' > > option, the packet is being dropped in the FOR

Re: [Shorewall-users] WireGuard Port Forwarding

2018-12-23 Thread C. Cook
On 12/22/18 5:04 PM, Justin Pryzby wrote: > On Sat, Dec 22, 2018 at 04:17:59PM -0800, C. Cook wrote: >> I've set up WireGuard on a VM in my LAN.  In the LAN's router I am >> port-forwarding my chosen (UDP) WireGuard port to the WireGuard server >> in the LAN. (All CentOS 7.6)  I've forwarded the sh

Re: [Shorewall-users] WireGuard Port Forwarding

2018-12-23 Thread C. Cook
On 12/23/18 9:04 AM, Tom Eastep wrote: > Clearly, your routing table indicates that the packet should be sent out > of eth0 rather than eth1, and since eth0 doesn't have the 'routeback' > option, the packet is being dropped in the FORWARD chain (see Shorewall > FAQ 17). > > -Tom Ok on the router

Re: [Shorewall-users] WireGuard Port Forwarding

2018-12-23 Thread Tom Eastep
On 12/22/18 4:17 PM, C. Cook wrote: > I've set up WireGuard on a VM in my LAN.  In the LAN's router I am > port-forwarding my chosen (UDP) WireGuard port to the WireGuard server > in the LAN. (All CentOS 7.6)  I've forwarded the shorewall.dmp from the > WG server to Tom. > > For the life of me I c

Re: [Shorewall-users] WireGuard Port Forwarding

2018-12-22 Thread Justin Pryzby
On Sat, Dec 22, 2018 at 04:17:59PM -0800, C. Cook wrote: > I've set up WireGuard on a VM in my LAN.  In the LAN's router I am > port-forwarding my chosen (UDP) WireGuard port to the WireGuard server > in the LAN. (All CentOS 7.6)  I've forwarded the shorewall.dmp from the > WG server to Tom. What