summaryrefslogtreecommitdiff
path: root/src/conf_mode/dhcpv6_relay.py
AgeCommit message (Collapse)Author
2020-04-27template: T2388: move mkdir/chmod/chown within render()Thomas Mangin
2020-04-13dhcpv6-relay: T2185: fix wrong call to os libraryChristian Poessinger
Commit 5892d51 ("dhcpv6-relay: T2185: migrate from SysVinit to systemd") accidently called the non existent function os.file.exists instead of os.path.exists.
2020-04-13dhcpv6-relay: T2185: migrate from SysVinit to systemdChristian Poessinger
2020-04-12template: T2230: use render to generate templatesThomas Mangin
convert all call to jinja to use template.render
2020-04-09util: T2226: os.system was wrongly converted to runThomas Mangin
os.system does print the ouput of the command, run() does not. A new function called call() does the printing and return the error code.
2020-04-06util: T2226: covert most calls from os.system to utilThomas Mangin
As little change a possible but the function call The behaviour should be totally unchanged.
2020-04-05dhcpv6-relay: T2230: move inlined templates to dedicated filesChristian Poessinger
2019-07-25T1541 Fix: adding additional checkEshenko Dmitriy
2019-04-06[dhcpv6-relay] T1322: bugfix on multiple listen interfacesChristian Poessinger
Same cause as with commit c6988bb4110541478dad74d0b892fd4643ed530a
2019-04-03[dhcpv6-relay] T1322: support multiple upstream serversChristian Poessinger
Add support for relaying a DHCPv6 packet to multiple servers on one upstream interface.
2019-04-03[dhcpv6-relay] T1322: bugfix on multiple upstream interfacesChristian Poessinger
When generation the configuration for multiple upstream interfaces a whitespace was missing in the generated configuration: OPTIONS="-6 -l 2001:db8::ffff%eth1 -u 2001:db8:1:ffff%eth2-u 2001:db8:2:ffff%eth3" ^--- This caused an error when starting up the DHCPv6 relay service
2018-11-02T939: Remove possibility to specify DHCP relay portChristian Poessinger
2018-10-25T938: do not bind DHCP relay to default port if unspecifiedChristian Poessinger
Binding isc-dhcp-relay to its default port (67 e.g. for IPv4) will result in an error when starting up the service: bad: ---- $ dhcrelay -q -4 -p 67 -c 10 -A 576 -m discard -i eth0.21 -i eth0 10.253.253.1 binding to user-specified port 67 good: ----- $ dhcrelay -q -4 -c 10 -A 576 -m discard -i eth0.21 -i eth0 10.253.253.1 Setting removed from the IPv6 implementation, too!
2018-10-19dhcpv6-relay: added missing verify() step for listen and upstream interfacesChristian Poessinger
2018-10-17T913: DHCP relay service XML/Python rewrite for IPv6Christian Poessinger