summaryrefslogtreecommitdiffhomepage
AgeCommit message (Collapse)Author
2014-08-12dhcpv4: implement router configuration optionChristian Mehlis
RFC 2132 defines: 3.5. Router Option The router option specifies a list of IP addresses for routers on the client's subnet. Routers SHOULD be listed in order of preference. The code for the router option is 3. The minimum length for the router option is 4 octets, and the length MUST always be a multiple of 4. Code Len Address 1 Address 2 +-----+-----+-----+-----+-----+-----+-----+-----+-- | 3 | n | a1 | a2 | a3 | a4 | a1 | a2 | ... +-----+-----+-----+-----+-----+-----+-----+-----+--
2014-08-08Make failed to send a notice instead of a warningSteven Barth
2014-08-08Add host-entries for all IPv6 addressesSteven Barth
2014-08-07sync hostfile more oftenSteven Barth
2014-08-07ra: don't send MSR for /64 prefix if DP is /64 as wellSteven Barth
2014-07-23Don't loose routes in managed PDSteven Barth
2014-07-22Revert "rewrite of NDP proxy" for nowSteven Barth
2014-07-21Fix typo in ubus integrationSteven Barth
2014-07-17Fix compilationSteven Barth
2014-07-17Add missing NDP sync featuresSteven Barth
2014-07-16Initial rewrite of NDP proxySteven Barth
2014-07-14odhcpd: only enable packet socket if really neededSteven Barth
2014-07-02Merge pull request #18 from dedeckeh/bugfixessbyx
Improved compliance with RFC3315
2014-07-01Replace option sol_max_rt by inf_max_rt in reply response to information requestHans Dedecker
2014-07-01DHCPv6 destination address checkHans Dedecker
As described in RFC3315 §15 any solicit, confirm, rebind or information request message is discarded if the destination address is unicast Likewise any request (§18.2.1), renew (§18.2.3), release (§18.2.6) or decline (§18.2.7) message is discarded and the server replies with the status code use multicast.
2014-07-01DHCPv4: send DHCPNAK if requested addr != leased addrSteven Barth
2014-07-01Merge pull request #17 from mar-kolya/mastersbyx
leasefile: do not output expired dhcpv6 leases
2014-06-30leasefile: do not output expired dhcpv6 leasesNikolay Martynov
Sometimes ip that is assigned to a host changes, old ip is still kept aroung as 'expired'. This expired ip gets dumped into leasefile and is read by dnsmasq. The result is that hotsname is resolved into expired ip and that confuses clients. This patch prevents expired leases from being written into leasefile.
2014-06-30Fixes compile error with muslSteven Barth
Signed-off-by: Felix Fietkau <nbd@openwrt.org>
2014-06-18Fix DHCPv4 static leases (thanks arnd)Steven Barth
2014-06-17use leaetime as base for T1 and T2 upper boundSteven Barth
2014-06-17backup for notonlinkSteven Barth
2014-06-17Make hostid more convenientSteven Barth
2014-06-17dhcpv6: send NotOnLink status on global levelSteven Barth
2014-06-16add more consistency to host file writingSteven Barth
2014-06-16dhcpv4: update hostfile more oftenSteven Barth
2014-06-16Fix option id for hostnamesSteven Barth
2014-06-16config: accept domains with trailing .Steven Barth
2014-06-12dhcpv4: use search domain instead of domain optionSteven Barth
2014-06-10Fix DHCP settings for /28Steven Barth
2014-06-10Merge pull request #14 from dedeckeh/bugfixessbyx
Fix DHCPv6 relay reply message in case raw DHCPv6 attributes are present
2014-06-09Fix DHCPv6 relay reply message in case raw DHCPv6 attributes are presentHans Dedecker
Use enum to index iov struct
2014-06-07Add default DHCPv4 range for prefixes down to /28Steven Barth
2014-05-30Make filtering customizableSteven Barth
2014-05-29Move dhcpv6 raw attributes to correct placeSteven Barth
2014-05-25Add support for raw DHCPv6 attributesSteven Barth
2014-04-24Merge pull request #13 from dedeckeh/bugfixessbyx
Bugfixes
2014-04-23Add status code ok option in reply to a decline messageHans Dedecker
RFC3315 Section 18.2.7 states a status code OK needs to be returned by the server : After all the addresses have been processed, the server generates a Reply message and includes a Status Code option with the value Success, a Server Identifier option with the server's DUID, and a Client Identifier option with the client's DUID.
2014-04-23Don't return a DHCPv6 reply in response to a confirm without address(es)Hans Dedecker
RFC3315 Section 18.2.2 states no reply must returned by the server in case no address(es) are present : If the server is unable to perform this test (for example, the server does not have information about prefixes on the link to which the client is connected), or there were no addresses in any of the IAs sent by the client, the server MUST NOT send a reply to the client.
2014-04-09config: use correct defaults if interface is not in UCISteven Barth
2014-04-06odhcpd: managed PD wait for 250ms initial periodSteven Barth
2014-04-03Make clang happySteven Barth
2014-04-01Keep managed PD for at least 150 secondsSteven Barth
2014-04-01Wait at least 15 seconds for managed PD to be acknowledgedSteven Barth
2014-04-01don't kill of managed PD too earlySteven Barth
2014-04-01Complete managed PD/CER-ID supportSteven Barth
2014-03-24Managed PD: initial supportSteven Barth
2014-03-20ubus: convert to async callsSteven Barth
2014-03-20ubus: use safe iteratorSteven Barth
2014-03-20ubus: don't redeclare variable cSteven Barth