udhcpc failure - route: SIOCADDRT: Invalid argument

[Denys Vlasenko]

On Thursday 12 March 2009 06:28:50 pm Tallam, Sreenivas wrote:
> Hi Denys,
> 
> Thanks for the reply.
> I have captured the logs as you requested them.
> 
> Please find the attach for 2 scenarios.
> 1. UDHCPC default script modified with your changes + DHCPv4 + IPv6

You added debug output around wrong "route":

Running: route add default gw  dev eth0 metric 0
route: resolving dev
### entering none listen mode
#
#
#
# cat /tmp/route.log
execve("/sbin/route", ["route", "add", "default", "gw", "dev", "eth0", "metric", "1"], [/* 15 vars */]) = 0

See above: "metric", "1" doesnt match "metric 0" above.


> 2  UDHCPC default script modified with your changes + DHCPv4 ( No IPv6)

Running: route add default gw  dev eth0 metric 0 <=== this one succeeds!
route: resolving dev
### entering none listen mode
route: SIOCADDRT: Invalid argument <=== thre is ANOTHER route run which fails
#
#
#
#


# cat /tmp/route.log
execve("/sbin/route", ["route", "add", "default", "gw", "dev", "eth0", "metric", "1"], [/* 15 vars */]) = 0
...
close(3)                                = 0
write(2, "route: resolving dev\n", 21)  = 21
exit_group(1)                           = ?

This is a strace from the earlier route run which worked, not one which failed.


> Please let me know if I can provide you with more information.

Try to find where is the failing route called, and instrument it too.
(in strace, use "strace -o /tmp/strace$RANDOM.log to not overwrite
strace logs of many runs)
--
vda