<html><body><div style="color:#000; background-color:#fff; font-family:verdana, helvetica, sans-serif;font-size:10pt"><div><span>It works now.</span></div><div style="color: rgb(0, 0, 0); font-size: 13.3333px; font-family: verdana,helvetica,sans-serif; background-color: transparent; font-style: normal;"><span><br></span></div><div style="color: rgb(0, 0, 0); font-size: 13.3333px; font-family: verdana,helvetica,sans-serif; background-color: transparent; font-style: normal;"><span>Thank you,</span></div><div style="color: rgb(0, 0, 0); font-size: 13.3333px; font-family: verdana,helvetica,sans-serif; background-color: transparent; font-style: normal;"><span>Mihai<br></span></div><div><br></div><blockquote style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; margin-top: 5px; padding-left: 5px;"> <div style="font-family: verdana, helvetica, sans-serif; font-size: 10pt;"> <div style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial,
Lucida Grande, sans-serif; font-size: 12pt;"> <div dir="ltr"> <hr size="1"> <font face="Arial" size="2"> <b><span style="font-weight:bold;">From:</span></b> Phil Whineray <phil@sanewall.org><br> <b><span style="font-weight: bold;">To:</span></b> Mihai Hanor <mhanor@yahoo.com> <br><b><span style="font-weight: bold;">Cc:</span></b> "firehol-support@lists.firehol.org" <firehol-support@lists.firehol.org> <br> <b><span style="font-weight: bold;">Sent:</span></b> Sunday, July 27, 2014 2:28 PM<br> <b><span style="font-weight: bold;">Subject:</span></b> Re: [Firehol-support] DHCPv6 source port<br> </font> </div> <div class="y_msg_container"><br>Hi Mihai<br clear="none"><div class="qtdSeparateBR"><br><br></div><div class="yqt2618836650" id="yqtfd28671"><br clear="none">On Thu, Jul 24, 2014 at 04:19:51AM -0700, Mihai Hanor wrote:<br clear="none">> I have encountered a situation with Firehol and the dhcpv6 service.<br clear="none">>
Apparently, the standard that defines how DHCPv6 works, doesn't specify<br clear="none">> what source port, a request or a response, must have. Firehol doesn't<br clear="none">> handle this situation, with the current definition of the dhcpv6 service.<br clear="none">> I'm currently using dibbler-server as a DHCPv6 server, instead of<br clear="none">> wide-dhcpv6-server, because wide-dhcpv6-server responds to requests,<br clear="none">> from a random UDP port. See here my initial attempt to resolve the issue<br clear="none">> with the wide-dhcpv6-server, which got an answer<br clear="none">> today: <a shape="rect" href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751407" target="_blank">https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751407 </a></div><br clear="none"><br clear="none">Seems fairly clear-cut. I originally took the DHCPv6 service from the <br clear="none">DHCP one in FireHOL but a close reading of the RFC shows
that the<br clear="none">source ports are not fixed in DHCPv6 as they were originally.<br clear="none"><br clear="none">I have updated the FireHOL service definition and I would be grateful if<br clear="none">you could give it a go from the latest build:<br clear="none"> <a shape="rect" href="http://firehol.org/download/unsigned/master/" target="_blank">http://firehol.org/download/unsigned/master/</a><br clear="none"><br clear="none">and let me know how you get on.<br clear="none"><br clear="none">Thanks<br clear="none">Phil<div class="yqt2618836650" id="yqtfd94618"><br clear="none"></div><br><br></div> </div> </div> </blockquote><div></div> </div></body></html>