Big Fork.
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 15/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- node.js, typescript
- Domain
- networking
Research direction
No project files, tests, or entry points are named. Start by reviewing the external fork at https://github.com/UrielCh/node-dhcp and compare its TypeScript DHCP changes with the listed goals; the issue does not define a focused, verifiable definition of done.
Written by the indexing model from the issue text.
Description
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:
- Use async hook, so can use an external database to store lease.
- Static lease are now reserved.
- New free lease detection algorithm.
- Project converted to Typescript.
- Refactor configuration model.
- Datastorage can be share and fill by an external live interface.
- remove auto remove oldest lease.
- Properly handle Offered lease as non validated lease (that expire within a couples of seconds)
- Implement DHCPRELEASE
- Implement DHCP renew
- Speed improvement
- Add Tag support (allow tagging Lease to add common options)
I think that this fork solve 3 of the current opened issue.
- #2
- #4
- #25
special:
- #33 I handle this case in production
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
- Dominant language
- TypeScript
- Stars
- 313
- Forks
- 70
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from rawify/dhcp.js
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
dhcp-proxy Open
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
DHCP Dashboard Openenhancement
Difficulty 5/5 Over a week Newbie friendliness 25/100
Similar issues
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 76/100
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
vercel/react-tweet#225 ·