[GH-ISSUE #56] IP of guests set to 92.168.x.x instead of 192.168.x.x #12

New issue

Closed

opened 2026-02-26 18:43:11 +03:00 by kerem · 4 comments

kerem commented

2026-02-26 18:43:11 +03:00

Owner

Originally created by @C-Fu on GitHub (Dec 3, 2025).
Original GitHub issue: https://github.com/devnullvoid/pvetui/issues/56

Originally assigned to: @devnullvoid on GitHub.

Found out when I wanted to enter the shell of an lxc

All lxcs seem to exhibit the same issue.

Using RPi 3b and downloaded the arm64 deb file from Released location.

Just to add, in the Guest Details pane it shows the correct IP for the lxc(s).

Using PVE 8.4.14.

Originally created by @C-Fu on GitHub (Dec 3, 2025). Original GitHub issue: https://github.com/devnullvoid/pvetui/issues/56 Originally assigned to: @devnullvoid on GitHub. Found out when I wanted to enter the shell of an lxc <img width="831" height="212" alt="Image" src="https://github.com/user-attachments/assets/d65aa82c-f723-4efc-b4f1-e5b264742d14" /> All lxcs seem to exhibit the same issue. Using RPi 3b and downloaded the arm64 deb file from Released location. Just to add, in the Guest Details pane it shows the correct IP for the lxc(s). Using PVE 8.4.14.

kerem closed this issue

2026-02-26 18:43:11 +03:00

kerem commented

2026-02-26 18:43:11 +03:00

Author

Owner

@devnullvoid commented on GitHub (Dec 4, 2025):

thanks for reporting this issue! I'm looking into it, but surprised it hasn't come up before. my IP ranges in testing have all been 192.168.xx.xxx. Since the LXC shell works by SSHing to the PVE node and running pct enter can you confirm that the correct IP shows in the node's details? i.e. 192.168.0.111

@devnullvoid commented on GitHub (Dec 4, 2025): thanks for reporting this issue! I'm looking into it, but surprised it hasn't come up before. my IP ranges in testing have all been 192.168.xx.xxx. Since the LXC shell works by SSHing to the PVE node and running `pct enter` can you confirm that the correct IP shows in the node's details? i.e. 192.168.0.111

kerem commented

2026-02-26 18:43:11 +03:00

Author

Owner

@C-Fu commented on GitHub (Dec 6, 2025):

@devnullvoid Yeah I can confirm it's 192.168.0.111. My range is 192.168.x.x but entering any LXC via pvetui will result in it omitting 1 in 192.

@C-Fu commented on GitHub (Dec 6, 2025): @devnullvoid Yeah I can confirm it's 192.168.0.111. My range is 192.168.x.x but entering any LXC via pvetui will result in it omitting 1 in 192.

kerem commented

2026-02-26 18:43:11 +03:00

Author

Owner

@devnullvoid commented on GitHub (Dec 6, 2025):

that is quite odd! I've made a change in the dev branch to fallback on malformed IP addresses, but I'm not sure if it will have an impact. I've also added some debug logging to help track down where the problem is occurring.

@devnullvoid commented on GitHub (Dec 6, 2025): that is quite odd! I've made a change in the dev branch to fallback on malformed IP addresses, but I'm not sure if it will have an impact. I've also added some debug logging to help track down where the problem is occurring.

kerem commented

2026-02-26 18:43:11 +03:00

Author

Owner

@devnullvoid commented on GitHub (Dec 7, 2025):

@C-Fu I've released the update. If the issue is still present, you can enable debug mode and reproduce the problem -- the log should reveal what's happening. Let me know!

@devnullvoid commented on GitHub (Dec 7, 2025): @C-Fu I've released the update. If the issue is still present, you can enable debug mode and reproduce the problem -- the log *should* reveal what's happening. Let me know!