mirror of
https://github.com/jetkvm/kvm.git
synced 2026-03-02 22:58:00 -05:00
Set Static IP #207
Labels
No labels
component/keyboard-layout
component: cloud
component: device screen
component: extensions
component: hid/keyboard
component: hid/mouse
component: network
component: timesync
component: ui
component: updater
component: usb
component: usb/hid
component: usb/storage
component: video
component: webrtc
component: webserver
need-more-details
status: working-in-progress
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/kvm#207
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Yousalc-95 on GitHub (Apr 18, 2025).
Originally assigned to: @ym on GitHub.
I don't understand why this feature isn't added yet.
This is very essential and it should be there from the start.
We constantly have power outages, this KVM is useless without this feature (Setting Static IP)!
Please provide at least a timeline of 1 this feature will be added, as I've seen numerous requests for it. Yet no Progress is happening.
@JackW6809 commented on GitHub (Apr 20, 2025):
I can see some backend code in the repo for statics, I haven't got my hands on my reward yet but when I do I will have a play about and see if I can make a frontend for it and work on some backend if it isn't all fully functional.
github.com/jetkvm/kvm@d79f359c43/internal/network/config.go (L21)github.com/jetkvm/kvm@d79f359c43/ui/src/hooks/stores.ts (L724)github.com/jetkvm/kvm@d79f359c43/ui/src/routes/devices.$id.settings.network.tsx (L217)@joelaulk commented on GitHub (Apr 20, 2025):
What I do is set a DHCP reserved address so this will get the same IP address every time.
Else you can mess with the code, but i got no time for such BS.
Strangely, static IP is such a basic function, but the developer seems to be on a different wavelength.
@JackW6809 commented on GitHub (Apr 20, 2025):
Well of course, setting a reservation is preferable really anyways as if the device is offline something else can grab it's IP.
@IITYWYBMAB commented on GitHub (Apr 20, 2025):
+1 for this being basic functionality most devices, particularly one that has a good chance of needing to be accessed during a system failure, which may include the DHCP server itself.
@JackW6809 commented on GitHub (Apr 21, 2025):
Already started working on it, as soon as I get my device I can do some proper testing
@dseven commented on GitHub (Apr 25, 2025):
There's already an open issue for this: #37
@smaniktahla commented on GitHub (Apr 26, 2025):
Unfortunately this doesn't work because of another issue, which is a randomized MAC address on rebooting the device (https://github.com/jetkvm/kvm/issues/375). So it gets a different IP from DHCP every time it reboots! DHCP reservations don't work on my device for this reason, and it looks like many other people see the same situation.
This thing was not tested properly before shipping. I trust that fixes will be released, but come on. This is basic stuff for a network appliance. Give us a static IP, don't randomize the MAC address.
@joelaulk commented on GitHub (Apr 27, 2025):
Interesting... maybe I'm lucky don't have this random MAC problem. I have powered off/on it many times and the MAC is still the same.
From the other thread it seems to affect new very recent batch of devices ?
@J-o-h-n-M commented on GitHub (Apr 29, 2025):
I have the same issue, the device indeed gets a new MAC at every boot. The router will see it as a new device and just give it a new IP address, not much to be done. Why would it get a random MAC?!
@SemoTech commented on GitHub (Apr 30, 2025):
Did you get your JetKVM and were you able to test your code? If it works, where does it go and will it survive a firmware update?
@JackW6809 commented on GitHub (Apr 30, 2025):
@SemoTech Unfortunately I haven't received it yet. I am in the March batch so hoping to receive my confirmation anytime soon.
@FreunderNacht commented on GitHub (May 2, 2025):
Hi,
I'm having the same problems.
No possibility to assign a static IP address and a reservation of the IP in the DHCP is also not possible due to the random Mac (#375).
See also #375.
See also #37.
@SemoTech commented on GitHub (May 2, 2025):
@FreunderNacht yes, I got mine patched using the info in here and for now it is working as expected and the MAC address is static as it should be. Looks like a large last batch of JetKVM units was rushed out without properly burning a unique MAC into the EEPROM and thus the "firmware" patch will likely be just the same as the fix linked above, only considered official.
@dseven commented on GitHub (May 2, 2025):
Changes relating to the MAC address issue are being committed to https://github.com/jetkvm/rv1106-system/commits/dev/ . I'd suggest holding off for the "official" solution, unless you're in a major panic.
This issue is a duplicate of #37 so I'm not sure there's any value in it at this point.
@JackW6809 commented on GitHub (May 5, 2025):
@SemoTech Got the email to confirm my address so I will be getting it soon then I can do some real testing
@SemoTech commented on GitHub (May 5, 2025):
Nice @JackW6809. Had mine for about a week now and was very disappointed by the MAC Address randomization bug. Ended up doing a manual patch until the official patch came out the other day. Now thats officially fixed, but the MAC is not burned into an EEPROM, it just stored in a text file. I think the last batch was rushed out and they forgot a step...
Aside from that I am still experiencing two other big issues:
1 - HDMI Splitter - see HERE
2 - Mac mini start keys - see HERE
@JackW6809 commented on GitHub (May 12, 2025):
@SemoTech Mine arrived today, got some UI done for some reason the network settings aren't actually applying. They save but DHCP seems to be used instead of the static set. Working on that tomorrow...
@SemoTech commented on GitHub (May 12, 2025):
@JackW6809 You must have a developer build version as the "Keyboard Macros" and "Network" menu options are missing from mine even after enabling Developer Mode in Advanced settings! This is my version and options:
What versions are you running?
@JackW6809 commented on GitHub (May 13, 2025):
@SemoTech 0.3.9 but it is the latest code based off of the dev branch so macros and network are probably coming up in a later build.
@agoodkind commented on GitHub (May 21, 2025):
@JackW6809 can you send me the branch and I can test it out on my JetKVM?
@larsl-net commented on GitHub (May 21, 2025):
@agoodkind it has been released with 0.4.0, wasn't able to test at the moment.
@agoodkind commented on GitHub (May 21, 2025):
I'm on the latest dev branch but it doesn't include any of @JackW6809 changes that are in the screenshot
@SemoTech commented on GitHub (May 21, 2025):
Not sure why, I am on v0.4.0 (auto-updated in the background) and the new settings are live! See screenshot:
I was able to install an SSL certificate as well under "Access" for HTTPS Custom Mode, so lots of progress...
Sadly holding [option] / [alt] key pressed on the virtual keyboard while powering up a Mac mini 2018 I am still unable to access the Boot Selection Manager and the Mac mini just boots through. This makes the "Virtual media" feature only half as useful.
@agoodkind commented on GitHub (May 21, 2025):
Off-topic: I am referring to the static IP settings, which are not live.
@larsl-net commented on GitHub (May 22, 2025):
How do you access your JetKVM? When I go over app.jetkvm.com I also don't see the new options. When accessing over the local IP I see the new options (Network tab), with version 0.4.0.
@SemoTech commented on GitHub (May 22, 2025):
@larsl-net I dont trust the security of cloud services, so I use a local proxy and setup DNS. This way I can access it from anywhere with a self-renewing Let's Encrypt SSL certificate.
@Scrounger117 commented on GitHub (May 30, 2025):
I have multiple JetKVMs and have been generally pleased with them; however, this feature seems so basic and it's still not working in 4.1 from the DEV release channel. When I go to the Network menu, the drop-down menu does not even have a "static" option to select. Am I missing something for this to work? Also, this needs to work for IPv4 and IPv6 IMHO as it's no longer acceptable in 2025 to ignore IPv6 :-).
@gogomickey commented on GitHub (Jun 8, 2025):
Yea come on guys. Being able to assign a static ip address to the jetkvm is essential. It opens up so many more use cases. Why isn't this being addressed? It is such an easy thing to implement.
@gogomickey commented on GitHub (Jun 8, 2025):
One thing to consider:
With this simple update you could steal the entire market for products like startech's kvm crash carts (model NOTECONS02) which currently cost $500-$600.
@IITYWYBMAB commented on GitHub (Jun 11, 2025):
Well, there's a dropdown now, so it seems it's a work in progress, even if the only option in the dropdown is "DHCP", it seems the tooling is slowly getting implemented. Strange to me that other network options are there, like hostname, domain, yet still no IP settings that I can find. I'll assume it's on the way, yet I do agree with the general sentiment, it should have shipped with this feature, it's not a minor thing for a KVM, yet it is a pretty minor change. Regardless, cool device, looking forward to it not being dependent upon a static lease, however.
@BuntlineAtSea commented on GitHub (Jun 27, 2025):
This is exactly what I bought the JetKVM for. So far I haven’t been able to use it. I’m here now because last week I was reminded of it lying useless in my toolbag since March, as I watched a colleague carry a 24” office monitor up a workshop ladder to change bios settings in an industrial PC.
Still hoping they’ll add this basic capability (never would have occurred to me that someone would ship a device without it) eventually, as the JetKVM is a much nicer form factor for temporary field use than the alternatives. But as the wait gets longer, I’m increasingly looking around for something else that actually works.
@touchstonelecram commented on GitHub (Jul 1, 2025):
Same here. The device arrived this week for testing, and I am very impressed with the build quality and performance. However, without the option to set a static IP, the device cannot be used since we have an industrial network without a DHCP server. When we have this option, we would definitely order more for all of our service engineers. Hopefully, this issue can be given the priority it deserves.
@killernat commented on GitHub (Jul 1, 2025):
as others have stated i bought this specifically to simplify headless updates on industrial equipment without needing to barrow extension cords and a monitor well now i use the jet kvm connected to a shitty old home router just to give it an IP address. It works, its smaller than a borrowed monitor but man is it convoluted. I REALLY want to recommend this as a standard tool in my company but i know a lot of service engineers that are not quite as tolerant to working around networks.....although one unintended benefit of this is i can connect to it wireless from a more comfortable area lol
@ricardbejarano commented on GitHub (Jul 2, 2025):
With all due respect, and as a JetKVM user, can we please stop adding noise to this thread?
How does knowing what you bought the device for or how much of a market impact this has get us closer to this feature?
We all get it, this is important, and if your problem is with JetKVM staff not prioritizing this enough feel free to raise that with them elsewhere, but this is a public thread on an open source project: contribute or step aside.
@stratamec commented on GitHub (Jul 31, 2025):
this is listed as a feature that hasn't been assigned to anyone but seem more like a short coming or bug to me, why would you create a ip based remote KVM solution and not allow static IP assignments, very short sighted in my opinion
otherwise I do love the interface, just don't know if I can use this for my clients since no static IP, and I have lots of clients
@adamshiervani commented on GitHub (Aug 4, 2025):
There are two parts of the setting static IP - one in the JetKVM UI and one using the touchscreen. Tracked for the next release, https://github.com/jetkvm/kvm/milestone/1 , we'll implement the static IP setting through the JetKVM UI. In following releases, we'll add support to set static IP through the touchscreen.
Will close this now, and mark as a duplicate of the https://github.com/jetkvm/kvm/issues/37 so we only have one place to follow.