[prev in list] [next in list] [prev in thread] [next in thread]
List: busybox
Subject: Re: [PATCH] Implemented support for stateless DHCPv6. Udhcpc6 will send Information-Request to reque
From: Eivind Versvik <versvikeivind () gmail ! com>
Date: 2019-08-30 11:43:08
Message-ID: CAN4WHEbpxgqCZrxTYbZgbzrr-c3j0RC-TGUDU=rjHndP3cnh1Q () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
>
> Why "no -d, -r no" command line usage does not work for you?
The intention is to have same behavior as "-r no", but the first dhcpv6
server I tested in stateless mode didn't respond when using solicit without
requesting address. When lease expires the behavior should be same as "-r
no".
This gives no answer from server:
udhcpc6 -b -rno -i eth0 -O dns -O search -p /var/run/udhcpc6.pid -S -s
/etc/udhcpc6.script
udhcpc6: started, v1.29.3
udhcpc6: sending discover
udhcpc6: sending discover
udhcpc6: sending discover
udhcpc6: no lease, forking to background
While with patched busybox using information request gives answer
immediately:
udhcpc6 -b -l -i eth0 -O dns -O search -p /var/run/udhcpc6.pid -S -s
/etc/udhcpc6.script
I, as a user, do not feel like this help text helps much.
>
I can update the text.
First get the IP, then get D6_MSG_INFORMATION_REQUEST?
I think solicit would give you all the information in information request
pluss the address, so not sure I see this as a needed option.
Obvious question - why? A comment would be good to have here.
>
I can add a comment, if I remember correctly the server responds to
multicast address
Users may want to have a different repetition rate. They may even want
> to do it just once.
I think ideally the timer should be controlled by server as in RFC8415
where the server responds with a time between 60 seconds and 86400 seconds (1
day), but I didn't want to do that many changes and looked what needed to
be done according to RFC3315. It would be a small change to add
configurable timer though.
OPT_q (quit after lease) should work the same way whether stateless DHCP is
used or not, so it should already be able to quit after getting information
from server if using -q.
(I managed to use wrong reply button on first email, so it didnt arrive on
mailing list)
[Attachment #5 (text/html)]
<div dir="ltr"><div dir="ltr"><span class="gmail-im" \
style="color:rgb(80,0,80)"><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Why "no -d, -r \
no" command line usage does not work for \
you?</blockquote><div><br></div></span><div>The intention is to have same behavior as \
"-r no", but the first dhcpv6 server I tested in stateless mode didn't \
respond when using solicit without requesting address. When lease expires the \
behavior should be same as "-r no".</div><div><br></div><div>This gives no \
answer from server:</div><div>udhcpc6 -b -rno -i eth0 -O dns -O search -p \
/var/run/udhcpc6.pid -S -s /etc/udhcpc6.script<br>udhcpc6: started, \
v1.29.3<br>udhcpc6: sending discover<br>udhcpc6: sending discover<br>udhcpc6: sending \
discover<br>udhcpc6: no lease, forking to \
background<br></div><div><br></div><div>While with patched busybox using information \
request gives answer immediately: </div><div>udhcpc6 -b -l -i eth0 -O dns -O search \
-p /var/run/udhcpc6.pid -S -s /etc/udhcpc6.script</div><div><br></div><div><span \
class="gmail-im" style="color:rgb(80,0,80)"><blockquote class="gmail_quote" \
style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex">I, as a user, do not feel like this help text \
helps much.<br></blockquote><div><br></div></span><div>I can update the \
text.</div><br class="gmail-m_5343979363012174664m_2255254489144338652m_-5102893335615203782gmail-Apple-interchange-newline"></div><span \
class="gmail-im" style="color:rgb(80,0,80)"><blockquote class="gmail_quote" \
style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex">First get the IP, then get \
D6_MSG_INFORMATION_REQUEST?</blockquote><div><br></div></span><div>I think solicit \
would give you all the information in information request pluss the address, so not \
sure I see this as a needed option.</div><span class="gmail-im" \
style="color:rgb(80,0,80)"><div><br></div><blockquote class="gmail_quote" \
style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex"> Obvious question - why? A comment would be good \
to have here.<br></blockquote></span><div>I can add a comment, if I remember \
correctly the server responds to multicast address</div><span class="gmail-im" \
style="color:rgb(80,0,80)"><div><br></div><blockquote class="gmail_quote" \
style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex">Users may want to have a different repetition \
rate. They may even want<br>to do it just once.</blockquote></span><div>I think \
ideally the timer should be controlled by server as in RFC8415 where the server \
responds with a time between 60 seconds and <span \
style="color:rgb(0,0,0);font-size:13.3333px">86400 seconds (</span>1 day), but I \
didn't want to do that many changes and looked what needed to be done according \
to RFC3315. It would be a small change to add configurable timer \
though.</div><div><br></div><div>OPT_q (quit after lease) should work the same way \
whether stateless DHCP is used or not, so it should already be able to quit after \
getting information from server if using -q.</div><div><br></div><div>(I managed to \
use wrong reply button on first email, so it didnt arrive on mailing \
list)</div></div></div>
_______________________________________________
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic