Sponsored Content
Full Discussion: Inaddr_any
Special Forums IP Networking Inaddr_any Post 302223071 by Ankit_Jain on Friday 8th of August 2008 09:04:46 AM
Old 08-08-2008
Continuation for same....
Suppoose we have configured logical Interface 2.2.2.2 on a server with Primary IP 1.1.1.1.
Now when I am sending a packet from this server, is it possible to make receiver assume that this packet has come from IP 2.2.2.2 and not 1.1.1.1
I think it is possibl using RAW sockets??? but then do we need to modify kernel also...??

Last edited by Ankit_Jain; 08-08-2008 at 10:28 AM..
 

2 More Discussions You Might Find Interesting

1. IP Networking

INADDR_ANY opposite

Hello, is there some way to obtain system's IP adresses to bind socket to every of them separately instead od INADDR_ANY? OR If there is some way to get server's IP to which client has connected, for example: server_app - bind to listen on INADDR_ANY, gets connected client to 1.2.3.4,... (2 Replies)
Discussion started by: d4rkl0rd
2 Replies

2. IP Networking

UDP server socket inaddr_any - How to get the real IP

Hello ! I seem to have the same problem as in https://www.unix.com/ip-networking/91203-inaddr_any-opposite.html#post302262417 But I can't find a solution. I have a UDP server socket bound to 0.0.0.0. The server hosts the addresses IP1, IP2 and IP3. I get an incoming request to IP1. I use... (1 Reply)
Discussion started by: steinwej
1 Replies
RPCBIND(8)						    BSD System Manager's Manual 						RPCBIND(8)

NAME
rpcbind -- universal addresses to RPC program number mapper SYNOPSIS
rpcbind [-adhiLls] DESCRIPTION
The rpcbind utility is a server that converts RPC program numbers into universal addresses. It must be running on the host to be able to make RPC calls on a server on that machine. When an RPC service is started, it tells rpcbind the address at which it is listening, and the RPC program numbers it is prepared to serve. When a client wishes to make an RPC call to a given program number, it first contacts rpcbind on the server machine to determine the address where RPC requests should be sent. The rpcbind utility should be started before any other RPC service. Normally, standard RPC servers are started by port monitors, so rpcbind must be started before port monitors are invoked. When rpcbind is started, it checks that certain name-to-address translation-calls function correctly. If they fail, the network configura- tion databases may be corrupt. Since RPC services cannot function correctly in this situation, rpcbind reports the condition and terminates. The rpcbind utility can only be started by the super-user. OPTIONS
-a When debugging (-d), do an abort on errors. -d Run in debug mode. In this mode, rpcbind will not fork when it starts, will print additional information during operation, and will abort on certain errors if -a is also specified. With this option, the name-to-address translation consistency checks are shown in detail. -f Do not fork and become a background process. -h Specify specific IP addresses to bind to for UDP requests. This option may be specified multiple times and is typically necessary when running on a multi-homed host. If no -h option is specified, rpcbind will bind to INADDR_ANY, which could lead to problems on a multi-homed host due to rpcbind returning a UDP packet from a different IP address than it was sent to. Note that when specifying IP addresses with -h, rpcbind will automatically add 127.0.0.1 and if IPv6 is enabled, ::1 to the list. -i ``Insecure'' mode. Allow calls to SET and UNSET from any host. Normally rpcbind accepts these requests only from the loopback interface for security reasons. This change is necessary for programs that were compiled with earlier versions of the rpc library and do not make those requests using the loopback interface. -l Turn on libwrap connection logging. -s Cause rpcbind to change to the user daemon as soon as possible. This causes rpcbind to use non-privileged ports for outgoing connec- tions, preventing non-privileged clients from using rpcbind to connect to services from a privileged port. -w Cause rpcbind to do a "warm start" by read a state file when rpcbind starts up. The state file is created when rpcbind terminates. NOTES
All RPC servers must be restarted if rpcbind is restarted. SEE ALSO
rpcinfo(8) LINUX PORT
BSD
September 14, 1992 BSD
All times are GMT -4. The time now is 11:26 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy