Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: sabat <sabat@eloan.com>
To: lartc@vger.kernel.org
Subject: [LARTC] Patch for arping
Date: Thu, 13 Feb 2003 09:10:07 +0000	[thread overview]
Message-ID: <marc-lartc-104512745016121@msgid-missing> (raw)

[-- Attachment #1: Type: text/plain, Size: 2514 bytes --]

This is probably the wrong forum for this, a small patch for arping. 
However:

- the guy who wrote arping, part of iputils, also wrote iproute2
- that guy is pretty much unreachable -- or I have to presume so, 
because his ftp site, the main site for his work, has been broken for 
months now
- I don't know where else to send it
- it might be useful to someone else

It's just a fix for an annoyance -- you should be able to arping from a 
source address you don't actually have. Don't ask me why one would want 
to do this; it solves a detailed problem I have, and I can't be the only 
one.

Btw, if you're interested enough to have read this far, this patches 
cleanly over the RedHat 8.0-patched version of arping. It adds one 
option, -B, which means, "don't bother trying to bind, just do your 
business."

-Steve


--- arping.c	2003-02-13 00:45:26.000000000 -0800
+++ arping.c.new	2003-02-13 00:44:45.000000000 -0800
@@ -38,6 +38,7 @@
 char *device="eth0";
 int ifindex;
 char *source;
+int nobind=0;
 struct in_addr src, dst;
 char *target;
 int dad, unsolicited, advert;
@@ -62,7 +63,7 @@
 void usage(void)
 {
 	fprintf(stderr,
- 		"Usage: arping [-fqbDUAV] [-c count] [-w timeout] [-I device] [-s source] destination\n"
+ 		"Usage: arping [-fqbDUAVB] [-c count] [-w timeout] [-I device] [-s source] destination\n"
  		"  -f : quit on first reply\n"
 		"  -q : be quiet\n"
  		"  -b : keep broadcasting, don't go unicast\n"
@@ -70,6 +71,7 @@
 		"  -U : Unsolicited ARP mode, update your neighbours\n"
 		"  -A : ARP answer mode, update your neighbours\n"
 		"  -V : print version and exit\n"
+		"  -B : do not try to bind to source address\n"
 		"  -c count : how many packets to send\n"
 		"  -w timeout : how long to wait for a reply\n"
 		"  -I device : which ethernet device to use (eth0)\n"
@@ -306,7 +308,7 @@
 
 	setuid(uid);
 
-	while ((ch = getopt(argc, argv, "h?bfDUAqc:w:s:I:V")) != EOF) {
+	while ((ch = getopt(argc, argv, "h?bfDUAqc:w:s:I:VB")) != EOF) {
 		switch(ch) {
 		case 'b':
 			broadcast_only=1;
@@ -340,6 +342,9 @@
 		case 's':
 			source = optarg;
 			break;
+		case 'B':
+			nobind = 1;
+			break;
 		case 'V':
 			printf("arping utility, iputils-ss%s\n", SNAPSHOT);
 			exit(0);
@@ -428,7 +433,7 @@
 		saddr.sin_family = AF_INET;
 		if (src.s_addr) {
 			saddr.sin_addr = src;
-			if (bind(probe_fd, (struct sockaddr*)&saddr, sizeof(saddr)) == -1) {
+			if (!nobind && bind(probe_fd, (struct sockaddr*)&saddr, sizeof(saddr)) == -1) {
 				perror("bind");
 				exit(2);
 			}



[-- Attachment #2: Type: text/html, Size: 3063 bytes --]

                 reply	other threads:[~2003-02-13  9:10 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=marc-lartc-104512745016121@msgid-missing \
    --to=sabat@eloan.com \
    --cc=lartc@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox