11-10-2011
Standard IP routing will not allow you to route based on port numbers. I think you will have to use IP Filters instead. The "to" option sounds like what you need. From "man -s 4 ipf":
to Causes the packet to be moved to the outbound queue on the specified interface. This can be used to circumvent kernel routing decisions [...]
I've never actually used IP Filters, so I can't be of any more help.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hello Dear Friends, I'm here again
I need to know where is the permanent file for gateway configuration.
I did the following command
route add -net 0.0.0.0 5.0.0.3 ( My Gateway), but when i restart my computer i have to do it again.
What the file can i set the permanent configuration for my... (1 Reply)
Discussion started by: themask
1 Replies
2. Solaris
I am having problems getting this to work, though it seems like it would be simple. I have a host with 2 interfaces, hme0 (192.168.0.132) for the primary interface, and hme1 (192.168.0.16) for backups. I want it to talk to the backup host, which is 192.168.0.21, across the hme1 interface.
Thanks (2 Replies)
Discussion started by: 98_1LE
2 Replies
3. IP Networking
WE are running Unix - Solaris 2.6, we create a subnet. In the windows enviroment we are able to add a static route by using
route add -p 172.16.10.0 mask 255.255.255.0 172.16.17.224, but when we add the route in Solaris as
route add -net 172.16.10.0 255.255.255.0 172.16.17.224, we receive an... (5 Replies)
Discussion started by: cassy
5 Replies
4. IP Networking
I have two networks connected by cisco routers. My first subnet is 192.168.0.0 and my second is 192.168.1.0.
My SCO unix machine is on the 192.168.1.0 subnet with an IP of 192.168.1.231. It can see the entire .1.0 subnet but nothing on the other network.
My cicso router(gateway) to the other... (6 Replies)
Discussion started by: agoodrich
6 Replies
5. Solaris
hi,
i installed solaris 9 on an SPARC server with two network interfaces. behind each interface is a small lan. i can reach every computer in every lan using one of the other interface when i am logged in the solaris. but if a computer from one lan has to connect to a computer on the other lan,... (4 Replies)
Discussion started by: bong02
4 Replies
6. Solaris
Hi,
Any one can help me in this below mentioned issue I am facing in my solaris server?
here the scenario goes....
i have multiple segments in my LAN like remote csr, database, production etc. and all the segments are configured in Windows/CISCo network.
from my all system in remote... (1 Reply)
Discussion started by: Praan
1 Replies
7. Solaris
Hi,
I am new to solaris 10. What is the procedure the os takes if a default route is not configured? I am using a multihomed server with 4 interfaces. It looked strange to me this morning, because i had not defined a default route it defaulted to making one up, with the ip address of another... (9 Replies)
Discussion started by: borderblaster
9 Replies
8. Solaris
Hi there,
I'm trying to configure an additional network interface on Solaris 8 (eri0). The interface has been activated, but all the frames are still routed to the current default interface (ce0) I've tried following command (with various syntaxes...) unsuccessfully so far:
# route add... (2 Replies)
Discussion started by: sreiniche
2 Replies
9. Solaris
Hi,
Every time when i boot my system i have to manually issue the following commands.
ifconfig elxl0 plumb 192.168.200.129 netmask 255.255.255.0 up
route add default 192.168.200.1
I need some help so that it should be configured permanently and i wouldn't have to manually issue... (2 Replies)
Discussion started by: malikshahid85
2 Replies
10. Solaris
Hi Solaris Experts,
I am trying to add a routing table entry on our 5.1 Generic_144488-12 sun4v sparc Solaris 10 SUNW,SPARC-Enterprise-T5220 so that it is possible to ping 10.56.9.34 node
# netstat -rnv
IRE Table: IPv4
Destination Mask Gateway Device Mxfrg Rtt Ref
Flg Out In/Fwd ... (2 Replies)
Discussion started by: gjackson123
2 Replies
LEARN ABOUT MINIX
tc-route
Route classifier in tc(8) Linux Route classifier in tc(8)
NAME
route - route traffic control filter
SYNOPSIS
tc filter ... route [ from REALM | fromif TAG ] [ to REALM ] [ classid CLASSID ] [ action ACTION_SPEC ]
DESCRIPTION
Match packets based on routing table entries. This filter centers around the possibility to assign a realm to routing table entries. For
any packet to be classified by this filter, a routing table lookup is performed and the returned realm is used to decide on whether the
packet is a match or not.
OPTIONS
action ACTION_SPEC
Apply an action from the generic actions framework on matching packets.
classid CLASSID
Push matching packets into the class identified by CLASSID.
from REALM
fromif TAG
Perform source route lookups. TAG is the name of an interface which must be present on the system at the time of tc invocation.
to REALM
Match if normal (i.e., destination) routing returns the given REALM.
EXAMPLES
Consider the subnet 192.168.2.0/24 being attached to eth0:
ip route add 192.168.2.0/24 dev eth0 realm 2
The following route filter will then match packets from that subnet:
tc filter add ... route from 2 classid 1:2
and pass packets on to class 1:2.
NOTES
Due to implementation details, realm values must be in a range from 0 to 255, inclusive. Alternatively, a verbose name defined in
/etc/iproute2/rt_realms may be given instead.
SEE ALSO
tc(8), ip-route(8)
iproute2 21 Oct 2015 Route classifier in tc(8)