Bridge Networking Support

[semaja2]

Is there plans to add bridged host networking support? Or is this a restriction from the iOS platform

I have some applications that work on layer 2 technologies that won’t work behind the current NAT design

[osy]

Not sure if it’s possible.

[professorUnknown]

This would be useful for a virtual machines running altserver.

[boy13epic]

good

[osy]

Reopening due to apple bug.

[bearnol]

Does the bridged-networking recently added (thanks!) to Mac UTM work with IPv4-only address(s)? I’m trying to run a really old Fedora16 (2011 vintage) i386 VM that knows nothing of IPv6, and so far without achieving network access. For routing purposes the IP address of the VM must be just 192.168.0.205. (When I run ifconfig inside the VM, I think I see only IPv6-type interface(s) listed?? Also, pinging external addresses doesn’t work, and the Fedora networking icon in the status bar at the top lists “No network connection” currently)
[btw, I was impressed with how easily UTM imported and converted the HDD image from original old VirtualBox to qcow2 - cool!].
I’m very new to UTM, having just bought my first M1 Mac mini :), so it may well just be something I haven’t seen yet… ( it took me a little while to work out I had to turn off UEFI on the virtual HDD to get it to boot)
[also btw, emulation speed seems fairly impressive, possibly fast enough for me to use in production, thx again, tho I guess that’s to be hoped/expected with QEMU underneath]
J

[ap46281]

Has anyone got bridge networking on iOS? Been a few months since this was last mentioned and I am not following how to make this work.

[osy]

Sorry bridged networking is a macos only feature. This issue was filed before the macos version was finished so it refers to iOS.

[bearnol]

Does the bridged-networking recently added (thanks!) to Mac UTM work with IPv4-only address(s)? I’m trying to run a really old Fedora16 (2011 vintage) i386 VM that knows nothing of IPv6, and so far without achieving network access. For routing purposes the IP address of the VM must be just 192.168.0.205. (When I run ifconfig inside the VM, I think I see only IPv6-type interface(s) listed?? Also, pinging external addresses doesn’t work, and the Fedora networking icon in the status bar at the top lists “No network connection” currently)
[btw, I was impressed with how easily UTM imported and converted the HDD image from original old VirtualBox to qcow2 - cool!].
I’m very new to UTM, having just bought my first M1 Mac mini :), so it may well just be something I haven’t seen yet… ( it took me a little while to work out I had to turn off UEFI on the virtual HDD to get it to boot)
[also btw, emulation speed seems fairly impressive, possibly fast enough for me to use in production, thx again, tho I guess that’s to be hoped/expected with QEMU underneath]
J

(Replying to my own post :) hope that’s ok)
I found the following page, which may well be helpful - I haven’t tried it yet, but it looks very promising given the exact diagnostics that I saw…
https://boinc.berkeley.edu/trac/wiki/VmServer
ie one needs to change something inside the VM, because of the implicit HD clone and therefore hardware change.
[PS I’ve now also literally just bought my second M1 Mac mini - they’re great!]

[ap46281]

Sorry bridged networking is a macos only feature. This issue was filed before the macos version was finished so it refers to iOS.

Is this a viable feature in the future? Or more of a dream?

[SuperKenVery]

I ran into the same issue, no IPv4, only IPv6. Any ideas?

[bearnol]

Hi, Thanks for your email. Unfortunately I don’t have a definitive answer for you, and in fact shortly after I wrote my first post re ipv4 vs ipv6 I paused investigating the issue. I did later wonder if the problems I was having were actually due to an implicit cloning of my VM, and therefore that the network config file needed tweaking (rather than the problem you/we mention), but I have not checked/confirmed this. Either way good luck with it - if you do get it working pls could you advise me too! :) James (Wanless)

…

Sent from my iPad

On 9 Oct 2022, at 08:54, SuperKenVery ***@***.***> wrote:  I ran into the same issue, no IPv4, only IPv6. Any ideas? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.

[SuperKenVery]

I didn't clone my vm and I tried to tweak my network configuration, with no luck.

https://bugzilla.redhat.com/show_bug.cgi?id=1832723

This seems related but does not solve my problem. My firewall on macOS is off.

Also this:

https://stackoverflow.com/questions/31531235/guest-vm-cant-get-ip-address-with-bridge-mode

Someone said Wireshark has an influence on this. I will try that later.

Not helping either 😭

[bearnol]

Thanks for extra info… J

…

Sent from my iPad

On 9 Oct 2022, at 09:28, SuperKenVery ***@***.***> wrote:  I didn't clone my vm and I tried to tweak my network configuration, with no luck. https://bugzilla.redhat.com/show_bug.cgi?id=1832723 This seems related but does not solve my problem. My firewall on macOS is off. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.

[bearnol]

Bit of hopefully good news on this:
I think I’ve been able to workaround quite nicely simply by selecting “Emulated VLAN” rather than bridged networking as such, and then port-forwarding port 80 from in/outside the VM, to allow the web server inside the VM to become visible to the outside world on the IP of the host.
HTH,
J

[ThijmenDam]

@bearnol great solution!