Re: port based routing

2020-08-08 Thread Tethys
On Mon, Aug 3, 2020 at 12:08 AM Jeffrey Ross wrote: > Now the only issue is I need to force all traffic originated by me (eg > when I'm the client) out eth0 and only use vpn0 when traffic > specifically hits that interface. This is called policy routing and is pretty straightforward. All of the

Re: port based routing

2020-08-04 Thread Gordon Messmer
On 8/3/20 3:25 AM, ToddAndMargo via users wrote: On 2020-08-02 16:03, Gordon Messmer wrote:    firewall-cmd --permanent --direct --add-rule ipv4 raw OUTPUT 100 -p tcp -m tcp --dport 22 -j MARK –set-mark 0x1 Would you mind taking apart all the switches in the above run string and expaining ea

Re: port based routing

2020-08-03 Thread ToddAndMargo via users
On 2020-08-02 16:03, Gordon Messmer wrote: On 8/2/20 12:27 PM, Jeffrey Ross wrote: I'm looking to make routing decisions based upon either the source or destination TCP port and interface/destination IP, in the Cisco world I'd do this via policy based routing. The same is true with iptables

Re: port based routing

2020-08-02 Thread Gordon Messmer
On 8/2/20 12:27 PM, Jeffrey Ross wrote: I'm looking to make routing decisions based upon either the source or destination TCP port and interface/destination IP, in the Cisco world I'd do this via policy based routing. The same is true with iptables and firewalld.  The article you linked is

Re: port based routing

2020-08-02 Thread Jeffrey Ross
I think I found a usable solution utilizing iproute2 I can simply define two separate routing tables, one table for eth0 and one for vpn0 each table has its own default gateway and the table used is based upon the interface traffic is sourced from. Now the only issue is I need to force all tra

Re: port based routing

2020-08-02 Thread Ed Greshko
On 2020-08-03 03:27, Jeffrey Ross wrote: > (System Fedora 31) > > I'm looking to make routing decisions based upon either the source or > destination TCP port and interface/destination IP, in the Cisco world I'd do > this via policy based routing. > > I found an example using iptables > https://

port based routing

2020-08-02 Thread Jeffrey Ross
(System Fedora 31) I'm looking to make routing decisions based upon either the source or destination TCP port and interface/destination IP, in the Cisco world I'd do this via policy based routing. I found an example using iptables https://www.sparksupport.com/blog/2010/10/02/application-base