Sponsored Content
Top Forums UNIX for Dummies Questions & Answers Routes being automatically added Post 302171465 by Conutmonky on Thursday 28th of February 2008 03:15:51 PM
Old 02-28-2008
Routes being automatically added

Hello,

I have two AIX 5.3 servers that are supposedly set up exactly the same. The problem I am having is on one of the servers, it seems dynamic routes are being added mysteriously and non-periodically. This only happens on one server and not the other. Also, there doesn't seem to be a specific event that occurs (such as reboot) that causes this to happen.

Any ideas as to why this could be happening?

Thanks,
Mike
 

10 More Discussions You Might Find Interesting

1. IP Networking

Multiple Interfaces and Routes

I have a Unix box with 2 network interfaces on the same IP subnet and would like to add a host route via a specific interface. Any assistance would be greatly appreciated. (3 Replies)
Discussion started by: diemos
3 Replies

2. UNIX for Dummies Questions & Answers

there was a strange character(^M) been added automatically in UNIX

I used Notepad to compile my txt file and then I transferred this file to UNIX. When I use vi to open the file, I found that at the end of each line there was a "^M" character. In the original txt file there was not this character. Why this character would been added automatically in UNIX? (4 Replies)
Discussion started by: Jasmine
4 Replies

3. UNIX for Dummies Questions & Answers

How to add 2 gateway routes?

I need some help adding routes in sco. I am using SCO Openserver 5.0.4. Basically I have 2 gateways here. The first is 10.15.1.1 and allows me access to the rest of the computers in the office and in other offices. The other gateway is 10.15.10.2 and is the sonicwall that will allow access... (3 Replies)
Discussion started by: cstovall
3 Replies

4. Debian

Setting Routes and such

Ok, I made changes to my routing tables..... which file do I modify to make the routes initialize correctly when the machine boots up? I work with all flavours of Unix/Linux... but this is an older box... Linux, Release 2.2.14-5.0. I did a grep for the default route in /etc, but didnt find... (2 Replies)
Discussion started by: djsal
2 Replies

5. AIX

Multiple Default routes

Hi All, I have a AIX server running v5.2 and its having multiple default routes configured to two seperate gateway. Here's the output of -- netstat -rn Routing tables Destination Gateway Flags Refs Use If PMTU Exp Groups Route Tree for Protocol Family 2... (2 Replies)
Discussion started by: rramanuj
2 Replies

6. Solaris

Where are routes stored ?

Hi there When adding a route (or indeed deleting a route) which file is amended ? I am moving a box from one network to another and when it starts up it tries to connect run 'add net 192.x.x.x' etc etc ...but i dont want it to do that where do I edit these route additions cheers (5 Replies)
Discussion started by: hcclnoodles
5 Replies

7. Solaris

adding routes in Solaris

Solaris Guru's What is the proper way to add routes in the routing table so after a node reboot the routes will not be lost. I understand the /etc/defaultrouter for the default router and the <route add> command but using this command routes will be removed once the node reboots. Thanks (7 Replies)
Discussion started by: Brad_52000
7 Replies

8. Solaris

vfstab enteries automatically added during live upgrade

i am trying to patch a solaris 10 server using live upgrade. issue is, when i create a new BE and activate it during reboot the file system that are mounted but doesnt have an entry in vfstab are automatically added in vfstab of new BE. looks like live upgrade uses df -h output as reference... (0 Replies)
Discussion started by: chidori
0 Replies

9. Solaris

Problem with routes in Solaris 10

Hello All, I have a Solaris 10 machine with 4 physical network interfaces configured viz. igb0, e1000g0, igb2 and e1000g2. Out of these interfaces, I am routing all my normal monitoring and O&M activities via. igb0 and e1000g0 interfaces. However, I am facing an issue on one of the... (4 Replies)
Discussion started by: mystition
4 Replies

10. IP Networking

Packet going out of wrong interface due to OS automatically added cache route with lower metric

RHEL 7.0, IPV6 Scenario: I have routed specific network using network scripts. 1. "ip -6 route show" shows that route has been added. ( with metric 1024) 2. Ping of the specific IP through that route is successful. 3. Now after few days, for some reason, we see that cache route appears for... (3 Replies)
Discussion started by: msr1981
3 Replies
smcroute(8)						      System Manager's Manual						       smcroute(8)

NAME
SMCRoute - Static Multicast Router (-Interface) - Version 0.95 SYNOPSIS
smcroute < options > < commands > options -d - start daemon -v - verbose output -D - enable debug logging commands - common -h - print help -k - kill daemon commands - multicast routing related -a <InputIntf> <OriginIpAdr> <McGroupAdr> <OutputIntf> [<OutputIntf>] ... - add route -r <InputIntf> <OriginIpAdr> <McGroupAdr> - remove route commands - multicast signaling related -j <InputIntf> <McGroupAdr> - join MC group -l <InputIntf> <McGroupAdr> - leave MC group DESCRIPTION
SMCRoute is a command line tool to manipulate the multicast routes of the Linux kernel. It supports both IPv4 and IPv6 multicast routing. SMCRoute can be used as an alternative to dynamic multicast routers like 'mrouted' in situations where static multicast routes should be maintained and/or no proper IGMP or MLD signaling exists. Generally multicast routes exists in the kernel only as long as smcroute or another multicast routing daemon is running. Only one multicast routing daemon can be active at a time, so it's impossible to run smcroute and e.g. 'mrouted' at the same time. The -d option smcroute is used to start the smcroute daemon. Otherwise, smcroute searches for an already running smcroute daemon and passes the commands to it. The -k option will terminate a running daemon. Multicast routes can be added with the -a command and removed with the -r command. A multicast route is defined by an input interface (<IntputIntf>), a unicast IP origin address (<OriginIpAdr>), a multicast group (<McGroupAdr>) and a list of output interfaces (<OutputIntf> ...). The origin and multicast group addresses must both be IPv4 addresses or IPv6 addresses. If IPv4 addresses are specified then SMCRoute will operate on the IPv4 multicast routes. If IPv6 addresses are specified then SMCRoute will operate on the IPv6 multicast routes. The output interfaces must not be given with the -r as the first three parameter are sufficient to identify the route to remove. The intention of SMCRoute is to help in situation where dynamic multicast routing does not work properly, but dynamic multicast routing is in nearly all cases the preferred solution. SMCRoute supports dynamic multicast routing with the multicast group 'join' -j and 'leave' -l commands. For both commands the input interface on which the multicast sessions should be received (<InputIntf>) and the multicast group address <McGroupAdr> must be given. The <McGroupAdr> may be an IPv4 or IPv6 address. Superuser rights are necessary to start the smcroute daemon or to communicate with the daemon. OPTIONS
-d Starts the smcroute daemon before any of the optional following commands are executed. -v Gives verbose output in some error situations (don't expect too much, check syslog instead). -D Gives additional debug messages in normal use (don't expect too much, see syslog instead). COMMANDS
-a <InputIntf> <OriginIpAdr> <McGroupAdr> <OutputIntf> [<OutputIntf>] ... The command is passed to the daemon that adds the given multicast route to the kernel's routing table. <InputIntf> can be any net- work interface as listed by 'ifconfig' or 'ip link list' (incl. tunnel interfaces), but not the loopback interface. <OriginIpAdr> is the source IP address of the multicast packets that will be routed by this entry. It is a unicast IPv4 or IPv6 address and not a multicast IP address. <McGroupAdr> is the IPv4 or IPv6 address of the multicast group that will be forwarded. <OutputIntf> [<Out- putIntf>] ... is a list of one or more network interfaces to which the multicast packets will be forwarded. The same rules for the selection of output interfaces applies as for the input interface. Warning, by using multiple output interfaces (traffic multiplication), using the input interface also as output interface (direct loop) or constructing some other forms of indirect loop you can flood you network. -r <InputIntf> <OriginIpAdr> <McGroupAdr> The command is passed to the daemon that removes a multicast route previously added with the -a command. The parameters are identi- cal except to the omitted list of <OutputIntf>. -j <InputIntf> <McGroupAdr> The command is passed to the daemon that passes it to the kernel. The kernel then tries to join the multicast group <McGroupAdr> on interface <InputIntf> by starting IGMP (or MLD if <McGroupAdr> is an IPv6 address) signaling on <InputIntf>. This signaling may be received by routers connected to <InputIntf>'s network that support IGMP/MLD multicast signaling and then hopfuly start forwarding of the requested multicast session to <InputIntf>'s network. With this command smcroute allows the integration of nodes that needs static multicast routing into dynamic multicast routing net- works. -l <InputIntf> <McGroupAdr> The command is passed via the daemon to the kernel that initiate a 'leave' for a previously 'joined' multicast group. LIMITS
The current version compiles and runs fine with the Linux kernel version 2.4. The known limits are: Multicast routes: more then 200 Multicast group membership: max. 20 FILES
/proc/net/ip_mr_cache - contains the active IPv4 multicast routes /proc/net/ip_mr_vif - contains the IPv4 'virtual' interfaces used by the active multicast routing daemon /proc/net/ip6_mr_cache - contains the active IPv6 multicast routes /proc/net/ip6_mr_vif - contains the IPv6 'virtual' interfaces used by the active multicast routing daemon /var/run/smcroute - IPC socket created by the smcroute daemon SEE ALSO
mrouted BUGS
The English wording of this man page. AUTHORS
smcroute was originally written by Carsten Schill <carsten@cschill.de>, support for IPv6 was added by Todd Hayton <todd.hayton@gmail.com>, support for FreeBSD was added by Micha Lenk <micha@debian.org>. The source code is now maintained by Todd Hayton <todd.hayton@gmail.com>, Micha Lenk <micha@debian.org> and Julien BLACHE <jblache@debian.org>. The current version is available at: http://alioth.debian.org/projects/smcroute TIPS
A lot of extra information is sent under the daemon facility and the debug priority to the syslog daemon. August 08, 2011 smcroute(8)
All times are GMT -4. The time now is 07:31 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy