-
Notifications
You must be signed in to change notification settings - Fork 54
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
Telnet not enabling after editing grub.cfg #193
Comments
Using the Ventoy flash drive you created can you boot ShredOS on a system with keyboard & monitor, then ALT F2 for the virtual terminal and type Then with a RJ45 network plugged in, can you type 'ifconfig' and post the output. Thanks. |
BOOT_IMAGE=/boot/shredos console=tty3 loglevel=3 telnetd=enable nomodeset noapic eth0 Link encap:Ethernet HWaddr B0:6E:BF:2A:FA:50 lo Link encap:Local Loopback also, i saw in the dmesg output the following (after it reads the grub.cfg) [ 0.035840] Kernel command line: BOOT_IMAGE=/boot/shredos console=tty3 loglevel=3 telnetd=enable nomodeset noapic |
Thanks, it looks like the telnetd package in busybox some how got deselected in the last update as the S50telnet file is missing from /etc/init.d/ I'll do another update as soon as I can, I'm currently building a new version which I'll publish as a pre-release. If it all goes ok that may be in the next few days, if not it won't be until after Christmas. In the meantime you can always go back to the previous release if you don't need the PDF support. |
No problem! I will roll back for now, thanks! |
Re-introduced telnetd as part of commit c9346c1 |
After editing both grub.cfg files to add telnetd=enable (using the method within linux of mounting the original shredos.img and editing the grub cfgs then rewriting the image, and using VENTOY), telnet port is not open after successfully booting into shredos.
I have tried this on multiple motherboards, and multiple networks (making sure telnet/port 23 is not being blocked) and I still don't see port 23 open on any of these instances.
Using latest build (v2023.08.2_25.0_x86-64_0.35)
The text was updated successfully, but these errors were encountered: