12-12-2013
I assume you're using Linux?
Quote:
Linux implements a weak host model: even if an address is configured on a given interface, this does not guarantee that packets generated on the host with that address as source will leave the host by that interface. Simply put, the destination IP address of the packet is used as the main key to select the best available route (gateway, interface) from the routing table.
You can make this happen using Linux Policy Routing. I've messed with this when I had two Internet connections and it can be a headache.
Here is a howto I found with Google that explains the steps I think you need:
A Quick Introduction to Linux Policy Routing
This User Gave Thanks to neutronscott For This Post:
10 More Discussions You Might Find Interesting
1. Cybersecurity
Hello,
I am currently trying to limit incoming UDP length 20 packets on a per IP basis to 5 a second using IPTables on a Linux machine (CentOS 5.2).
Basically, if an IP is sending more than 5 length 20 UDP packet a second to the local machine, I would like the machine to drop the excess... (1 Reply)
Discussion started by: tomboy123
1 Replies
2. Solaris
Hi All,
yesterday I was trying to add a network route to my solaris 8 host using 'route add'. Everytime I tried, I kept getting the response 'network is unreachable'.
I was trying all kinds of different methods, however I eventually got it to work after bouncing the interface that I was... (2 Replies)
Discussion started by: badoshi
2 Replies
3. 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
4. UNIX for Dummies Questions & Answers
Hi all,
I am new to Linux kernel.
we have a c file that counts the no. of sends and received packets in each interface, and indicate the user about the error/drop ration of incoming and outgoing packets.
in our Linux box , the incoming packets are dropped at random interval.
we have our... (1 Reply)
Discussion started by: kannandv
1 Replies
5. Solaris
Please , I have a problem
I have add a statis route on Solaris 10, but after this, the network interface of Server was Offline.
The system is in cluster mode (3.2)
route add -net 10.10.1.128 -netmask 255.255.255.128 10.10.1.51
-------------------
lo0:... (1 Reply)
Discussion started by: Ruggero
1 Replies
6. 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
7. IP Networking
hello,
can anyone suggest how to delay the incoming packets ??
or how the packets are prossed inside the kernal and a way to make the packets wait a while??
it wud be vry helpful
regards
sameer (7 Replies)
Discussion started by: sameer kulkarni
7 Replies
8. Linux
I am looking for an iptables command to allow incoming UDP packets for my Linux server
also is there a command I can use to set the default action for outgoing packets to accept?
Thank you (1 Reply)
Discussion started by: crimputt
1 Replies
9. IP Networking
Hi,
I'm quite new to unix networking and ip tables. I'm running a debian (htpc) server with two NIC's; eth0 and wlan0.
I'm trying to set it up in a way that eth0 is the default interface for internet, but some processes should run through wlan0.
For example, I'm using eth0 for downloads... (2 Replies)
Discussion started by: Subbeh
2 Replies
10. IP Networking
Hi folks,
I have a debian server running an Apache daemon on the eth0 interface. Now from time to time the server has to open an openvpn connection (tun0) to other networks to get some data from there. During this period the Apache is no longer reachable under it's IP address on eth0 because all... (6 Replies)
Discussion started by: flyingwalrus
6 Replies
LEARN ABOUT BSD
xnsrouted
XNSROUTED(8) System Manager's Manual XNSROUTED(8)
NAME
XNSrouted - NS Routing Information Protocol daemon
SYNOPSIS
/sbin/XNSrouted [ -s ] [ -q ] [ -t ] [ logfile ]
DESCRIPTION
XNSrouted is invoked at boot time to manage the Xerox NS routing tables. The NS routing daemon uses the Xerox NS Routing Information Pro-
tocol in maintaining up to date kernel routing table entries.
In normal operation XNSrouted listens for routing information packets. If the host is connected to multiple NS networks, it periodically
supplies copies of its routing tables to any directly connected hosts and networks.
When XNSrouted is started, it uses the SIOCGIFCONF ioctl to find those directly connected interfaces configured into the system and marked
``up'' (the software loopback interface is ignored). If multiple interfaces are present, it is assumed the host will forward packets
between networks. XNSrouted then transmits a request packet on each interface (using a broadcast packet if the interface supports it) and
enters a loop, listening for request and response packets from other hosts.
When a request packet is received, XNSrouted formulates a reply based on the information maintained in its internal tables. The response
packet generated contains a list of known routes, each marked with a ``hop count'' metric (a count of 16, or greater, is considered ``infi-
nite''). The metric associated with each route returned provides a metric relative to the sender.
Response packets received by XNSrouted are used to update the routing tables if one of the following conditions is satisfied:(1) No routing table entry exists for the destination network or host, and the metric indicates the destination is ``reachable'' (i.e.
the hop count is not infinite).
(2) The source host of the packet is the same as the router in the existing routing table entry. That is, updated information is being
received from the very internetwork router through which packets for the destination are being routed.(3) The existing entry in the routing table has not been updated for some time (defined to be 90 seconds) and the route is at least as
cost effective as the current route.(4) The new route describes a shorter route to the destination than the one currently stored in the routing tables; the metric of the
new route is compared against the one stored in the table to decide this.
When an update is applied, XNSrouted records the change in its internal tables and generates a response packet to all directly connected
hosts and networks. Routed waits a short period of time (no more than 30 seconds) before modifying the kernel's routing tables to allow
possible unstable situations to settle.
In addition to processing incoming packets, XNSrouted also periodically checks the routing table entries. If an entry has not been updated
for 3 minutes, the entry's metric is set to infinity and marked for deletion. Deletions are delayed an additional 60 seconds to insure the
invalidation is propagated to other routers.
Hosts acting as internetwork routers gratuitously supply their routing tables every 30 seconds to all directly connected hosts and net-
works.
Supplying the -s option forces XNSrouted to supply routing information whether it is acting as an internetwork router or not. The -q
option is the opposite of the -s option. If the -t option is specified, all packets sent or received are printed on the standard output.
In addition, XNSrouted will not divorce itself from the controlling terminal so that interrupts from the keyboard will kill the process.
Any other argument supplied is interpreted as the name of file in which XNSrouted's actions should be logged. This log contains informa-
tion about any changes to the routing tables and a history of recent messages sent and received which are related to the changed route.
SEE ALSO
``Internet Transport Protocols'', XSIS 028112, Xerox System Integration Standard.
idp(4P)
4.3 Berkeley Distribution November 1, 1996 XNSROUTED(8)