Port Forwarding tcp/udp conflict

[verbal_666]

How can THIS be a conflict (tcp & udp)? See nfs 4 rules...

[verbal_666]

No reply to my question?

[Perryg]

Minimal information needed to be able to help

[verbal_666]

Virtualbox: 5.0.2 r102096 - guest addon installed
Host: Windows 7/32 (3,5Gb ram)
Guest: Linux Xububtu/32 (but the problem is VB core, Nat/PortForwarding console)

I don't think you need vm log, problem is before launching the vm, inside port forwarding editor. No log is written in vm path dir.

[verbal_666]

I can only translate the msgbox error in Eng... for more understanding!!!

[Perryg]

Post the results of the following from the hosts command window.

Code: Select all

VBoxManage list natnetworks

[Martin]

It seems that VirtualBox doesn't allow port forwarding for both TCP and UDP between the same IP address and ports.
I just tried to configure this combination myself and got the same error message.

[verbal_666]

Code: Select all

#VBoxManage list natnetworks
NetworkName:    NatNetwork
IP:             10.0.2.1
Network:        10.0.2.0/24
IPv6 Enabled:   No
IPv6 Prefix:
DHCP Enabled:   Yes
Enabled:        Yes
Port-forwarding (ipv4)
        nfs udp 1:udp:[10.232.20.175]:111:[10.0.2.4]:111
        nfs udp 2:udp:[10.232.20.175]:2049:[10.0.2.4]:2049
        ssh:tcp:[10.232.20.175]:22:[10.0.2.4]:22
        webmin:tcp:[10.232.20.175]:10000:[10.0.2.4]:10000
loopback mappings (ipv4)
        127.0.0.1=2

[verbal_666]

It seems that VirtualBox doesn't allow port forwarding for both TCP and UDP between the same IP address and ports.
I just tried to configure this combination myself and got the same error message.

This is the "bug" from the 1st post

[Perryg]

I would try it again and this time leave the host address empty. This really should not be needed.

portforward-tcp-udp.png (21.3 KiB) Viewed 4116 times

[Martin]

You can enter the rules, but you get the error message as soon as click the OK button.

[verbal_666]

Same error under Win7/32 host.

[Perryg]

Well Martin I would not have posted that if it had failed for me as well.

If I had the host IP, it did fail. Removing that allowed it to proceed as it should. If you check the actual VBoxManage command it does not list the host IP in the syntax.
VBoxManage modifyvm "VM name" --natpf1 "guestssh,tcp,,2222,,22"

Now here's the rub. There is NAT and NATnetworking. If you create a new NATnetwork you can not use the same address scheme as NAT. The OP seems to be using NATnetworking with the address scheme of NAT. Still don't have enough direct information to prove that though.

[Perryg]

OK look in the network section and see if you have NAT listed to be able to choose from.

Note: I don't need to see a new screenshot showing the same failure.

[Martin]

Well Martin I would not have posted that if it had failed for me as well.

I tried exactly the same config as in your screenshot on a new NatNetwork and got the error message
Vbox 5.0.2 r102096 on RHEL 6.6