Am Samstag, den 17.02.2018, 22:16 +0100 schrieb Samuel Thibault: > Hello, > > Benjamin Drung, on ven. 16 févr. 2018 13:55:03 +0100, wrote: > > Or should the command line option be simpler, but how should it be > > specified > > then? Maybe > > > > -net > > staticroute=10.0.2.0/24via10.0.2.2,staticroute=192.168.0.0/16via10. > > 0.2.2 > > I guess > > > -net > > staticroute=10.0.2.0/24:10.0.2.2,staticroute=192.168.0.0/16:10.0.2. > > 2 > > would be more mainstream.
Okay. I used this syntax to implement the static route support. See the "slirp: Add classless static routes support to DHCP server" patch. > I'm also wondering to which extent we want to extend our dhcp server, > when a tap device can be used to plug (or proxy) an actual dhcp > serveR. I am using slirp's DHCP server to test custom build live images locally. This should be simple to setup and run in contrast to our "real" production environment with real hardware and actual DHCP severs. -- Benjamin Drung System Developer Debian & Ubuntu Developer ProfitBricks GmbH Greifswalder Str. 207 D - 10405 Berlin Email: benjamin.dr...@profitbricks.com URL: https://www.profitbricks.de Sitz der Gesellschaft: Berlin Registergericht: Amtsgericht Charlottenburg, HRB 125506 B Geschäftsführer: Achim Weiss, Matthias Steinberg
