10-29-2005
route add -net 192.56.76.0 netmask 255.255.255.0 dev eth0
adds a route to the network 192.56.76.x via "eth0". The Class C netmask modifier is not really necessary here because 192.* is a Class C IP address. The word "dev" can be omit-ted here.
do a man on route for more info...(man is your friend)
10 More Discussions You Might Find Interesting
1. IP Networking
I have SCO Unix. I have 2 routers. as it is now, when someone telnets to UNIX and goes through router #1 everything is fine. The users who go through router #2 can not connect at all. I talked to CISCO and they said I need to set up a second Gateway on UNIX. They said what is happening is that... (1 Reply)
Discussion started by: john fli
1 Replies
2. IP Networking
ok i configured my gateway and IP address(es) using ifconfig and route.. but how can i bind unique IPs to users ? (im using FreeBSD 4.2 RELEASE #3) (9 Replies)
Discussion started by: DevilGREEN
9 Replies
3. Linux
How to use NAT Router in linux Redhat 6 ? and what
packages and configuration are required ? (1 Reply)
Discussion started by: salhoub
1 Replies
4. Red Hat
:mad: I have just recently got into using Linux RedHat 9. So far I love it, I have set it up on a server I am running. Right now I have set up Samba and am running a file server for my house. I have four computers, the linux box is connected to the internet through a switch I have. There are two... (5 Replies)
Discussion started by: xTHESEUSx
5 Replies
5. Red Hat
I have just recently got into using Linux RedHat 9. So far I love it, I have set it up on a server I am running. Right now I have set up Samba and am running a file server for my house. I have four computers, the linux box is connected to the internet through a switch I have. There are two NICS in... (1 Reply)
Discussion started by: xTHESEUSx
1 Replies
6. Linux
Hello Friends
I have two network cards
eth0 192.168.100.1
eth1 10.0.0.1
There NIC connect with diff. LAN
I want to make my Linux machine as a Router, Please tell me
using
IPTABLES command
ROUTE command
:) (2 Replies)
Discussion started by: jaibw
2 Replies
7. Linux
Hello All,
I know it's a tricky probably stupid question but I'm stuck.... :(
Is there any way to route different protocols through different eth cards for the same destination in Linux? With route add or something like it?
For instance:
FTP to/from 192.168.1.1 goes through eth0 - gw2... (1 Reply)
Discussion started by: pmpx
1 Replies
8. UNIX for Dummies Questions & Answers
(3 Replies)
Discussion started by: samnyc
3 Replies
9. IP Networking
I am having problems configuring bridged networking on Proxmox3.2/Debian7.0
I have 2 bridges - vmbr0 and vmbr1. I want to attach a gateway/firewall running in a virtual machine between the 2 and use it to connect out to the WAN through vmbr0.
I have removed the IP, mask and gateway from... (0 Replies)
Discussion started by: OSSVirt
0 Replies
10. IP Networking
Hello. I want to Communicate 2 VLAN with router like this solution:
http://8pic.ir/images/83m0ouih8mmm9s1sfl56.jpg
For this purpose I'm configuring 2 Linux system as a switch and connect 4 host to them. Then a router is added to scenario.
The configuration of the switches is:
On DUT1(Linux):... (1 Reply)
Discussion started by: zsn
1 Replies
LEARN ABOUT MOJAVE
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)