Sponsored Content
Full Discussion: IPv4 LSRR Option
Top Forums Programming IPv4 LSRR Option Post 302198006 by aamirglb on Thursday 22nd of May 2008 04:41:18 AM
Old 05-22-2008
IPv4 LSRR Option

Hello Friends,
I have one doubt regarding LSRR (Loose Source and Record Route) IP option.
Whether IPv4 optoins will be processed only by Router or they can be processed by any PC within the network??
What i'm trying is: i'm giving a list of IP address in the option using setsockopt system call, say:

IP-1 => 192.168.0.1
IP-2 => 192.168.0.2
IP-1 => 192.168.0.3
IP-2 => 192.168.0.4 ==> This is the destination PC

All these system are connected in a LAN and are running Windows OS. But the system on which this program is run has Linux.
If I send a datagram using SOCK_DGRAM socket, I'm able to receive the packet only in 192.168.0.1. This PC (192.168.0.1) is not forwarding the IP packet to the next PC in the list i.e., 192.168.0.2.

Can please any one clarify whether ip options can be processed by all the PC or only Routers can process it.

Thanks in Advance.

Regards,
Md. Aamir Ali
Bangalore
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

option followed by : taking next option if argument missing with getopts

Hi all, I am parsing command line options using getopts. The problem is that mandatory argument options following ":" is taking next option as argument if it is not followed by any argument. Below is the script: while getopts :hd:t:s:l:p:f: opt do case "$opt" in -h|-\?)... (2 Replies)
Discussion started by: gurukottur
2 Replies

2. UNIX for Advanced & Expert Users

convert from ipv4 to ipv6

hello i'm working on aix 5300-05-03 hacmp ver 5.4 well my issue is that when firewall (gateway to internet ) goes down my machine start to work very very slowly!!! the output of the sniffer is that on the output card , my machine try to convert ipv4 to ipv6 0.0.2.0 my machine is not configure... (1 Reply)
Discussion started by: ariec
1 Replies

3. AIX

convert ipv4 ti ipv6

hello i'm working on AIX 5300-05-03 P520 hacmp 5.4 when connection to the internet is going down , firewall down, my application work verey verey slowly!!! and on the sliffer output i'm got trys of my serevr to do convert from ipv4 ipv6 ( 0.0.2.0 and AAAAAAAA). some one have an idea why... (1 Reply)
Discussion started by: ariec
1 Replies

4. IP Networking

Modifying IPv4 headers

Hi, My query is: I need to set the IPv4 header fields(like TOS, TTL, Precedence and Flags) in the linux kernel using the system calls. I tried setting the fields using the setsockopt() call using sockets but it is not reflecting the actual IPv4 header fields. Is it possible to modify these... (0 Replies)
Discussion started by: kiran_4u
0 Replies

5. Shell Programming and Scripting

recently introduced to the newer option for find...does an older option exist?

To find all the files in your home directory that have been edited in some way since the last tar file, use this command: find . -newer backup.tar.gz Is anyone familiar with an older solution? looking to identify files older then 15mins across several directories. thanks, manny (2 Replies)
Discussion started by: mr_manny
2 Replies

6. Shell Programming and Scripting

[ASK] How to check whether ipv4 or ipv6 and ping those IP

I have perl script that I use to check and ping a list of ip, The problem is, I didnt understand how to ping ipv6 on perl, Could I use Ping::External??And how could I get the ping result (reply or not)? This is my code #!/usr/bin/perl -- use Net::Ping; use Data::Validate::IP; use... (3 Replies)
Discussion started by: franzramadhan
3 Replies

7. AIX

IPv6/IPv4 Only in AIX

Hi all, I have setup ipv6 in AIX machine using autoconf6 command. I was successfull in doing this. after execution of the command local link address was assigned to one of the interfaces (en1).But I have to setup the following environment as well. 1) Machine with only IPv6 support(IPv4... (0 Replies)
Discussion started by: ard
0 Replies

8. Programming

IPv4 string->int

Does anyone know how to convert a IP address given as 'string' into a 'u_int32_t'? Are there any build any functions already? (1 Reply)
Discussion started by: Freaky123
1 Replies

9. Solaris

Ntp between ipv4 and ipv6

Hi, I am looking for a solution to configure ntp between ipv4 ( ntp server ) to ipv6 ( client) . I had google, but lot many sites suggest to have dual stock or tunnaling. my issue is I have client has only ipv6 address ans server has ipv4 address. is it possible to sync time,... (4 Replies)
Discussion started by: naveen.surisett
4 Replies

10. Red Hat

Disable IPV4

Hi im using Redhat Ver 6.4 is it possible to disable IPV4 and use only IPV6? how can i do that? thanks Guy (2 Replies)
Discussion started by: guy3145
2 Replies
routeadm(1M)															      routeadm(1M)

NAME
routeadm - IP forwarding and routing configuration SYNOPSIS
routeadm [-p] routeadm [-R root-dir] [-e option...] [-d option...] [-r option...] [-s var=value] routeadm [-u] The routeadm command is used to administer system-wide configuration for IP forwarding and routing. IP forwarding is the passing of IP packets from one network to another; IP routing is the use of a routing protocol to determine routes. routeadm is used to enable or disable each function independently, overriding any system default setting for each function. The first usage, above, reports the current configuration. The following command-line options are supported: -p Print the configuration in parseable format. -R root-dir Specify an alternate root directory where routeadm applies changes. This can be useful from within JumpStart scripts, where the root directory of the system being modified is mounted elsewhere. Note - The root file system of any non-global zones must not be referenced with the -R option. Doing so might damage the global zone's file system, might compromise the security of the global zone, and might damage the non-global zone's file system. See zones(5). -e option... Enable the specified option. -d option... Disable the specified option. -r option... Revert the specified option to the system default. The system defaults are specified in the description of each option. -u Apply the currently configured options to the running system. Enable or disable IP forwarding, and/or launch or kill routing daemons. It does not alter the state of the system for those settings that have been set to default. This option is meant to be used by adminis- trators who do not want to reboot to apply their changes. -s var=value Specify string values for specific variables in a comma-separated list with no intervening spaces. If invalid options are specified, a warning message is printed and the program exits. The following variables can be specified: ipv4-routing-daemon=<full_path_to_routing_daemon> Specifies the routing daemon to be started when ipv4-routing is enabled. The routing daemon specified must be an executable binary or shell-script. Default: "/usr/sbin/in.routed" ipv4-routing-daemon-args=<args> Specifies the startup arguments to be passed to the ipv4-routing-daemon when ipv4-routing is enabled. Default: no arguments ipv4-routing-stop-cmd=<command> Specifies the command to be executed to stop the routing daemon when ipv4-routing is disabled. <command> may be an executable binary or shell-script, or a string that can be parsed by system(3C). Default: "kill -TERM `cat /var/run/in.routed.pid`" ipv6-routing-daemon=<full_path_to_routing_daemon> Specifies the routing daemon to be started when ipv6-routing is enabled. The routing daemon specified must be an executable binary or shell-script. Default: "/usr/lib/inet/in.ripngd" ipv6-routing-daemon-args=<args> Specifies the startup arguments to be passed to the ipv6-routing-daemon when ipv6-routing is enabled. Default: "-s" ipv6-routing-stop-cmd=<command> Specifies the command to be executed to stop the routing daemon when ipv6-routing is disabled. <command> can be an executable binary or shell-script, or a string that can be parsed by system(3C). Default: "kill -TERM `cat /var/run/in.ripngd.pid`" Note that, if you change the routing daemon and stop commands from their defaults, routeadm does not monitor these daemons or commands. This is because the status of these programs depends on user configuration. When non-default daemons or stop commands are in use, routeadm always returns a status of "unknown". Multiple -e, -d, and -r options can be specified on the command line. Changes made by -e, -d, and -r are persistent, but are not applied to the running system unless routeadm is called later with the -u option. Use the following options as arguments to the -e, -d, and -r options (shown above as option...). ipv4-forwarding Controls the global forwarding configuration for all IPv4 interfaces. The system default is disabled. If enabled, IP will forward IPv4 packets to and from interfaces when appropriate. If disabled, IP will not forward IPv4 packets to and from interfaces when appropriate. ipv4-routing Determines whether or not an IPv4 routing daemon is run. The system default is enabled unless the /etc/defaultrouter file exists, in which case the default is disabled. The routing daemon for IPv4 is /usr/sbin/in.routed. ipv6-forwarding Controls the global forwarding configuration for all IPv6 interfaces. The system default is disabled. If enabled, IP will forward IPv6 packets to and from interfaces when appropriate. If disabled, IP will not forward IPv6 packets to and from interfaces when appropriate. ipv6-routing Determines whether or not an IPv6 routing daemon is run. The system default is disabled. The routing daemon for IPv6 is /usr/lib/inet/in.ripngd. If not set, the system boot scripts' current default logic determines whether or not to run in.ripngd. Note that even if this option is enabled, an IPv6 routing daemon will run only if ipv6-forwarding is enabled. The forwarding and routing settings are related but not mutually dependent. For example, a router will typically forward IP packets and use a routing protocol, but nothing would prevent an administrator from configuring a router that forwards packets and does not use a routing protocol. In that case, the administrator would enable forwarding, disable routing, and populate the router's routing table with static routes. The forwarding settings are global settings. Each interface also has an IFF_ROUTER forwarding flag that determines whether packets can be forwarded to or from a particular interface. That flag can be independently controlled by means of ifconfig(1M)'s router option. When the global forwarding setting is changed (that is, -u is issued to change the value from enabled to disabled or vice-versa), all interface flags in the system are changed simultaneously to reflect the new global policy. Interfaces configured by means of DHCP automatically have their interface-specific IFF_ROUTER flag cleared. When a new interface is plumbed by means of ifconfig(1M), the value of the interface-specific forwarding flag is set according to the cur- rent global forwarding value. Thus, the forwarding value forms the "default" for all new interfaces. The following exit values are returned: 0 Successful completion. !=0 An error occurred while obtaining or modifying the system configuration. Example 1: Enabling IPv4 Forwarding IPv4 forwarding is disabled by default. The following command enables IPv4 forwarding: example# routeadm -e ipv4-forwarding Example 2: Apply Configured Settings to the Running System In the previous example, a system setting was changed, but will not take effect until the next reboot unless a command such as the follow- ing is used: example# routeadm -u Example 3: Making a Setting Revert to its Default To make the setting changed in the first example revert to its default, enter the following: example# routeadm -r ipv4-forwarding example# routeadm -u Example 4: Starting in.routed with the -q Flag The following sequence of commands starts in.routed with the -q flag: example# routeadm -s ipv4-routing-daemon-args="-q" example# routeadm -u See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ |Interface Stability |Stable | +-----------------------------+-----------------------------+ ifconfig(1M), in.routed(1M), gateways(4), attributes(5) 8 Apr 2005 routeadm(1M)
All times are GMT -4. The time now is 11:19 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy