re now taking.
Simon, I think your codes has so much dependency on "context" objects and
stand on the assumption "context". correct ?
Thanks,
Takayuki Kaiso
P.S.
When a DHCP server has more than one interfaces from which DHCP packets
come in, single context shou
ess, pre-CIDR. Since most people will be using
RFC1918 addresses, that should get the right answer most of the time,
and is probably better than silently ignoring a dhcp-ranges without
netmasks when requests come via a relay. I'll add that code to the next
release, I think.
Cheers,
Simon.
Thanks a lot and cheers.
Takayuki Kaiso
the default value processing and should
all parameters explicitly when people take exceptional configuration like
rfc3527 case." ?
For me at this moment, I will try configure all of these parameters
explicitly.
Thank you, Simon
Takayuki Kaiso
Takayuki Kaiso wrote:
Hi, Simon
rder to avoid executing ioctl() to get the local
interface address again
in rfc2131.c
what is your opinion ?
Please any kind of suggestions.
thanks a lot
Takayuki Kaiso
Takayuki Kaiso wrote:
Hi, Simon
Thank you for your suggestion.
let me explain more details.
< configu
cal
are checked in other places and (ex. line 968 in dhcp.c ) and I thought
setting up those two fields in dhcp.c looks safer for me.
I definitely need your suggestion, Simon.
Thanks
Takayuki Kaiso
Takayuki Kaiso wrote:
Hi,
I needed to apply the following patch to work with decp relay which is
ds in dhcp.c looks safer for me.
I definitely need your suggestion, Simon.
Thanks
Takayuki Kaiso
Takayuki Kaiso wrote:
Hi,
I needed to apply the following patch to work with decp relay which is using
rfc3527 link selection sub option.
As far as I looked around dhcp.c, complete_context() fa
ess specified in link-selection sub option.
I think we also need to do the similar thing also for rfc3011 handling,
and I will take care of it if I get review on this patch by any of you.
Thank you
Takayuki kaiso
P.S. I forgot to remove my debugging line (syslog) from th patch. sorry.
diff -ru a/
