Sponsored Content
Special Forums IP Networking redirect routing on non-default interface Post 302268872 by docawk on Tuesday 16th of December 2008 12:45:52 PM
Old 12-16-2008
Both tables T3 and ADSL are mostly the same, except for the default route which is set to T3 or ADSL interface accordingly.
The main table contains all routing information like also T3 and ADSL tables do, but also contains iprules to use specific tables for incoming traffic on T3 or ADSL interface.
The T3 interface is connected with a static IP router to the providers network (and internet). The ADSL interface is connected via a common DSL modem/router.

Code:
firewall:~# ip route list
XXX.XXX.250.185 dev eth1  scope link  src XXX.XXX.250.186
XXX.XXX.250.184/29 dev eth2  scope link  src XXX.XXX.250.186
192.168.11.0/24 dev eth3  scope link  src 192.168.11.9
192.168.10.0/24 dev eth0  scope link  src 192.168.10.9
default via 192.168.11.92 dev eth3

firewall:~# ip route list table ADSL
XXX.XXX.250.185 dev eth1  scope link  src XXX.XXX.250.186
XXX.XXX.250.184/29 dev eth2  scope link  src XXX.XXX.250.186
192.168.11.0/24 dev eth3  scope link  src 192.168.11.9
192.168.10.0/24 dev eth0  scope link  src 192.168.10.9
127.0.0.0/8 dev lo  scope link  src 127.0.0.1
default via 192.168.11.92 dev eth3

firewall:~# ip route list table T3
XXX.XXX.250.185 dev eth1  scope link  src XXX.XXX.250.186
XXX.XXX.250.184/29 dev eth2  scope link  src XXX.XXX.250.186
192.168.11.0/24 dev eth3  scope link  src 192.168.11.9
192.168.10.0/24 dev eth0  scope link  src 192.168.10.9
127.0.0.0/8 dev lo  scope link  src 127.0.0.1
default via XXX.XXX.250.185 dev eth1

 

7 More Discussions You Might Find Interesting

1. Solaris

Command line Interface or GUI Interface not shown on solaris

Dear all, I am a newbie in solaris and I need your advice. I have a Solaris version 5.9 installed on Sunfire V240. I am able to ssh the machine from putty remotely. My problem is that I cannot see the display from KVM switch I have connected to it. I need also to be able to see the GUI... (2 Replies)
Discussion started by: mbouster
2 Replies

2. SCO

Change SCO - GUI or Desktop interface to DOS based interface

Hi all I have installed a demo version of SCO OpenServer 5.0.2, I finally found it is Desktop Interface, I would like to know how to change its interface to dos based interface? If you have any ideas, please tell me then. Thank you (2 Replies)
Discussion started by: TinhNhi
2 Replies

3. IP Networking

Need a bridge from an ethernet interface to a serial interface

This is my situation DOS pc serial cable (sl0) Linux Pc eth1 192.168.0.10 <-------------------->192.168.0.2 <------------>192.168.0.1 (router) I connected the linux pc and the dos pc with a SLIP (serial line internet protocol), so they can communicate in the sl0 interface. ... (3 Replies)
Discussion started by: mghis
3 Replies

4. Solaris

Traffic routing through wrong interface

Solaris-9 server is having one primary IP 10.41.161.14 on qfe0 and 10.41.116.0 on qfe3:1. Traffic is going through virtual interface instead of physical interface. How should I force traffic to go with primary interface. root@smtsrvn01:/# netstat -nr Routing Table: IPv4 Destination ... (2 Replies)
Discussion started by: solaris_1977
2 Replies

5. IP Networking

Linux load balancer ping redirect to other interface

Im configuring centos with load balance with ip route and ip rule Eth0 192.168.1.5 Eth1 192.168.5.128 # ip route 192.168.5.0/24 dev eth1 scope link src 192.168.5.128 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.5 169.254.0.0/16 dev eth1 scope link # ip route show... (2 Replies)
Discussion started by: hadinetcat
2 Replies

6. UNIX for Dummies Questions & Answers

Adding a network interface to a bonded interface

I have a RHEL 5 system with a bonded interface configure using only one network port (eth0). So I have config file for ifcfg-bond0 and ifcfg-eth. I'd like to configure eth5 to be the second SLAVE in the bond. My question is, after I modify ifcfg-eth5, can I add eth5 to the bond0 interface without... (1 Reply)
Discussion started by: westmoreland
1 Replies

7. IP Networking

Port based multi interface routing

Hello, I wanted to setup routing certain traffic (http/s) out via a second (faster) interface, like described in the following docs (may not post urls): linux-ip.net /html/adv-multi-internet.html thegeekstuff.com /2014/08/add-route-ip-command/ I already had this working years ago on... (0 Replies)
Discussion started by: hyphan
0 Replies
SHOREWALL6-PROVIDER(5)						  [FIXME: manual]					    SHOREWALL6-PROVIDER(5)

NAME
providers - Shorewall6 Providers file SYNOPSIS
/etc/shorewall6/providers DESCRIPTION
This file is used to define additional routing tables. You will want to define an additional table if: o You have connections to more than one ISP or multiple connections to the same ISP o You run Squid as a transparent proxy on a host other than the firewall. o You have other requirements for policy routing. Each entry in the file defines a single routing table. If you wish to omit a column entry but want to include an entry in the next column, use "-" for the omitted entry. The columns in the file are as follows. NAME - name The provider name. Must be a valid shell variable name. The names 'local', 'main', 'default' and 'unspec' are reserved and may not be used as provider names. NUMBER - number The provider number -- a number between 1 and 15. Each provider must be assigned a unique value. MARK (Optional) - value A FWMARK value used in your shorewall6-tcrules(5)[1] file to direct packets to this provider. If HIGH_ROUTE_MARKS=Yes in shorewall6.conf(5)[2], then the value must be a multiple of 256 between 256 and 65280 or their hexadecimal equivalents (0x0100 and 0xff00 with the low-order byte of the value being zero). Otherwise, the value must be between 1 and 255. Each provider must be assigned a unique mark value. This column may be omitted if you don't use packet marking to direct connections to a particular provider. DUPLICATE - routing-table-name The name of an existing table to duplicate to create this routing table. May be main or the name of a previously listed provider. You may select only certain entries from the table to copy by using the COPY column below. INTERFACE - interface The name of the network interface to the provider. Must be listed in shorewall6-interfaces(5)[3]. GATEWAY - {-|address|detect} The IP address of the provider's gateway router. You can enter "detect" here and Shorewall6 will attempt to detect the gateway automatically. For PPP devices, you may omit this column. OPTIONS (Optional) - [-|option[,option]...] A comma-separated list selected from the following. The order of the options is not significant but the list may contain no embedded whitespace. balance Added in Shorewall 4.4.25. Causes a default route to this provider's gateway to be added to the main routing table (USE_DEFAULT_RT=No) or to the balance routing table (USE_DEFAULT_RT=Yes). At most one provider can specify this option. fallback Added in Shorewall 4.4.25. Causes a default route to this provider's gateway to be added to the default routing table.At most one provider can specify this option. track If specified, inbound connections on this interface are to be tracked so that responses may be routed back out this same interface. You want to specify track if internet hosts will be connecting to local servers through this provider. Beginning with Shorewall 4.4.3, track defaults to the setting of the TRACK_PROVIDERS option in shorewall6.conf[4] (5). If you set TRACK_PROVIDERS=Yes and want to override that setting for an individual provider, then specify notrack (see below). loose Shorewall6 normally adds a routing rule for each IP address on an interface which forces traffic whose source is that IP address to be sent using the routing table for that interface. Setting loose prevents creation of such rules on this interface. notrack Added in Shorewall 4.4.3. When specified, turns off track. optional (deprecated for use with providers that do not share an interface) If the interface named in the INTERFACE column is not up and configured with an IPv4 address then ignore this provider. If not specified, the value of the optional option for the INTERFACE in shorewall6-interfaces(5)[3] is assumed. Use of that option is preferred to this one, unless an address is provider in the INTERFACE column. src=source-address Specifies the source address to use when routing to this provider and none is known (the local client has bound to the 0 address). May not be specified when an address is given in the INTERFACE column. If this option is not used, Shorewall6 substitutes the primary IP address on the interface named in the INTERFACE column. mtu=number Specifies the MTU when forwarding through this provider. If not given, the MTU of the interface named in the INTERFACE column is assumed. tproxy Added in Shorewall 4.5.4. Used for supporting the TPROXY action in shorewall-tcrules(5). See http://www.shorewall.net/Shorewall_Squid_Usage.html. When specified, the MARK, DUPLICATE and GATEWAY columns should be empty, INTERFACE should be set to 'lo' and tproxy should be the only OPTION. Only one tproxy provider is allowed. COPY - [{none|interface[,interface]...}] A comma-separated list of other interfaces on your firewall. Wildcards specified using an asterisk ("*") are permitted (e.g., tun* ). Usually used only when DUPLICATE is main. Only copy routes through INTERFACE and through interfaces listed here. If you only wish to copy routes through INTERFACE, enter none in this column. EXAMPLES
Example 1: You run squid in your DMZ on IP address 2002:ce7c:92b4:1::2. Your DMZ interface is eth2 #NAME NUMBER MARK DUPLICATE INTERFACE GATEWAY OPTIONS Squid 1 1 - eth2 2002:ce7c:92b4:1::2 - Example 2: eth0 connects to ISP 1. The ISP's gateway router has IP address 2001:ce7c:92b4:1::2. eth1 connects to ISP 2. The ISP's gateway router has IP address 2001:d64c:83c9:12::8b. eth2 connects to a local network. #NAME NUMBER MARK DUPLICATE INTERFACE GATEWAY OPTIONS COPY ISP1 1 1 main eth0 2001:ce7c:92b4:1::2 track eth2 ISP2 2 2 main eth1 2001:d64c:83c9:12::8b track eth2 FILES
/etc/shorewall6/providers SEE ALSO
http://shorewall.net/MultiISP.html http://shorewall.net/configuration_file_basics.htm#Pairs shorewall6(8), shorewall6-accounting(5), shorewall6-actions(5), shorewall6-blacklist(5), shorewall6-hosts(5), shorewall6-interfaces(5), shorewall6-maclist(5), shoewall6-netmap(5),shorewall6-params(5), shorewall6-policy(5), shorewall6-rtrules(5), shorewall6-routestopped(5), shorewall6-rules(5), shorewall6.conf(5), shorewall6-secmarks(5), shorewall6-tcclasses(5), shorewall6-tcdevices(5), shorewall6-tcrules(5), shorewall6-tos(5), shorewall6-tunnels(5), shorewall6-zones(5) NOTES
1. shorewall6-tcrules(5) http://www.shorewall.net/manpages6/shorewall6-tcrules.html 2. shorewall6.conf(5) http://www.shorewall.net/manpages6/shorewall6.conf.html 3. shorewall6-interfaces(5) http://www.shorewall.net/manpages6/shorewall6-interfaces.html 4. shorewall6.conf http://www.shorewall.net/manpages6/shorwewall6.conf.html [FIXME: source] 06/28/2012 SHOREWALL6-PROVIDER(5)
All times are GMT -4. The time now is 12:52 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy