#48 IPv4 port forwarding GUI not responding

[Charles Omer]

Hi,

I'm using RemoteBox on Windows via Ubuntu and MobaXterm and all seems to be okay until I try to create IPv4 port forwarding rules. IPv6 seems to be fine.

v3.1

Thank you
Charles

[Ian Chapman]

Thanks Charles. Does there happen to be any output on the command line behind where you've launched RemoteBox? That might be be able to give me some indication. What are the symptoms you're seeing when it's not OK is the GUI hanging or something else? Thanks

[Charles Omer]

Too late to run INIT block at /usr/lib/x86_64-linux-gnu/perl5/5.30/Glib/Object/Introspection.pm line 257.
GLib-LOG **: posix_spawn avoided (fd close requested)  at /usr/lib/x86_64-linux-gnu/perl5/5.30/Glib/Object/Introspection.pm line 67.
GLib-GObject-WARNING **: value "((GtkIconSize) 32)" of type 'GtkIconSize' is invalid or out of range for property 'icon-size' of type 'GtkIconSize' at /usr/lib/x86_64-linux-gnu/perl5/5.30/Glib/Object/Introspection.pm line 67.
GLib-GObject-WARNING **: value "((GtkIconSize) 32)" of type 'GtkIconSize' is invalid or out of range for property 'icon-size' of type 'GtkIconSize' at /usr/lib/x86_64-linux-gnu/perl5/5.30/Glib/Object/Introspection.pm line 67.

(remotebox:109): Gtk-CRITICAL **: 11:19:17.405: gtk_widget_grab_default: assertion 'gtk_widget_get_can_default (widget)' failed

(remotebox:109): Gtk-CRITICAL **: 11:19:17.461: gtk_buildable_get_name: assertion 'GTK_IS_BUILDABLE (buildable)' failed

(remotebox:109): Gtk-CRITICAL **: 11:19:17.461: gtk_buildable_get_name: assertion 'GTK_IS_BUILDABLE (buildable)' failed

(remotebox:109): Gtk-CRITICAL **: 11:19:17.461: gtk_buildable_get_name: assertion 'GTK_IS_BUILDABLE (buildable)' failed

...

The above appears when I start RemoteBox

When I click 'OK' on the port forwarding popup (where you specify the ports themselves) it just hangs and won't respond. Neither the OK or cancel buttons work. If I close it via the Windows X then it does close without saving the change but if I try to modify the port forwarding rule again it just pops up with a blank screen.

[Ian Chapman]

Hi Charles. Ok those messages are benign and can be ignored. I'll see if I can replicate under 20.04

[Charles Omer]

It seems this is an issue with WSL Ubuntu 20.04 since it works with 21.10. Although would it be possible to be able to include port forwarding for just a "NAT" configuration rather than having to create a new "NAT Network"?

[Ian Chapman]

Glad it's working now at least. Creating a NAT Network is simply how VirtualBox works. It lets you create multiple NAT networks for any number of VMs and so RemoteBox essentially has to follow that design.

[Charles Omer]

Yeah, hopefully it can work on 20.04 too :) Although 22.04 will be released soon for WSL I'm guessing so it won't be too long before it's fixed that way

In VirtualBox though you can specify port forwarding from within the VM setting itself, I'm guessing this is just doing the same thing under the hood as a NAT network. Although it does mean you don't have to worry about the IP addresses of the host/guest and it "just works" :)

[Ian Chapman]

Just putting on-hold as I'm undecided longer term if I will change this behaviour due to resourcing.