virtualbox.org

Hi,

I moved a FreePBX distro (CentOS, Asterisk) to Virtualbox (4.2.18) on Windows 7.

The transfer worked fine, but I am haveing some kind of Network issue.

FreePBX has a static IP assigned. I can ping in and out and TCP connections work. DNS works.

But somehow there seems to be trouble with UDP.

Some UDP traffic forwared does not reach the VM.

I have set the Network mode to Bridging. No idea what else I need to do. Windows Firewall is off. Anything I need to do with the “Virtual Host only Network Adapter” ?

Any other hints ?

Thanks
Stephan

The "host only" virtual adapter isn't relevant if you're bridging to a physical adapter.

I'm not sure what you mean by "some UDP traffic forwarded". There's no packet forwarding going on if you use "bridged" - your VM is a peer on the same network as your host. Your router and your host should see the VM as just another PC.

However, the other mods know more about networking than I do, so I'll let them comment.

Thanks. Yes, that what I thought on the bridging.

Let me tell you my problem more specific.

I have Asterisk running on that CentOS. On a standalone machine it works totally fine. Once I moved it into the virtualbox only my SIP extensions work, but my IAX trunk stops working (unreachable).

I have also tried to set up a full new installation into VB - exact same problem.

As SIP also works through TCP but IAX2 does not - well thats why Í thought it might be a UDP problem.

On the router the UDP is forwarded.

As I said, I did not change a byte in the installation, kept the same IP ect. (and switched off the standalone box).

I have played around with the Network adapter settings for hours now.

No idea anymore what to do.

STEPHANK wrote:As I said, I did not change a byte in the installation, kept the same IP ect. (and switched off the standalone box).

Did you reset the router, and/or was the "standalone box" on the same router port? I imagine that a router's routing tables might get confused if the same IP appears on two different ports.

Thank you very much for your help.

I had thought about this before, but as the internal connections were there fast, I did not realize that they do not have to go though a (NAT) routing table.

Also I had waited for a long time (30 min or so), but it looks as if the trunks do not come back up automaticly once they are down.

Anyway, I restarted the router and now it works.

THANK YOU SO MUCH !

Glad you got it working, thanks for telling us.