-
Notifications
You must be signed in to change notification settings - Fork 75
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Big Fork. #57
Comments
Hi, thanks for your ping! Your changes look impressive! The time when I started this project, async code was not a thing. So I'm totally in favor of going a step forward. I have to test your fork and look into the code in greater detail. But all your improvements are long-awaited and I would look forward integrating these features :) Did you make any cuts in terms of generalizability, which were only useful for your very use-case? What would be your idea of integrating your fork into the main branch? Can it be seen as a full replacement? If not, would you like to work with me together on bringing these features into the main branch? Robert |
Why are you using a dual licence ? |
I chose a dual license to match different requirements. Practically, it's MIT, but to embed it into an environment where GPL is used, you can use the GPL part. |
Broken here when try test:
or? |
extract from package.json:
debonce is here, so maybe you should make a new npm install. |
I have just finish my heavy refactor. Leases are now completely new, and leaseStatic support tags, like dnsmask. |
anyone know how works Options id I use this page to find some data: But some optionId are vendor dependent ... some more change and this project will be able to compete old school classic DHCP server. |
I see it had still some typo but now got running. Tried with WinXP laptop and it has still failure to give correct DHCP Offer message so it fails. |
Okey, you should wait some days, to let me finish my devs. |
Sure! Sorry and thanks. |
I have just setup the dhcp server, but It do not receved any discover multicast message. the mail UDP socket is initialied with: but there is no reference to an interface name. I make all my developpement on a windows host, the production is is an ubuntu server. |
As far as i know there is no specific interface and you need manually setup IP for that Ethernet port (i mean IP, netmask 255.255.255.0 or same you congifured in config, and router IP). IP and router IP need be same and same on config file for server. It listens 0.0.0.0 as to get messages which means all IPv4 messages on host machine... When i originally loaded project there was broken broadcast address which was not passed correctly to dhcp.js file which too made it not working. And if you try pass via config file ip with assigned mac address it is broken still by this day until mac styling is fixed to be same on everywhere on project (including hard coded test files which uses hyphen styling for not any specific reason as far as i know as linux supports colons too). |
If I bind socket 10.5.0.1, I do not receive any DHCP Discover. Update: If I bind socket 0.0.0.0, I receive all DHCP Discover.... My set is:
But I only want to reply to DHCP on enp1s0. an Idea ? |
update it's not multicast but broadcast. socket.setBroadcast(true); should be the only needed call but it do not work's to continue my test I use an basic iptables:
|
Hi,
|
Any chances you will get this work completed and maybe make an npm package from it? |
I need a to bind an UDP pour on a specific interface. I wish deno will support interface binding, so I will move to it. for now I'm stuck. |
@UrielCh You can use the Check out this stackoverflow thread and this package. |
Thx for the link, But for now, I'm switching from NodeJS to Deno, So can not check that. |
Hi,
Thank for this project.
I'm trying to replace my ugly dnsmask configuration + nodejs front, by an pure nodejs solution.
I forked your source for some changes, but I make a loooooooot of changes.
the final version should be a kind of pure typescript router (PAC + http-proxy + dhcp + dynamic public IP switch + live http blocking features)
on the dhcp server the change include:
I think that this fork solve 3 of the current opened issue.
special:
Maybe we will be able to merge one day, but you will have to switch to typescript.
I plane to deploy a first version next week.
https://github.com/UrielCh/node-dhcp
give me your feedback
The text was updated successfully, but these errors were encountered: