Fedora 26 vm on Windows 10, wrong router MAC
Posted: 14. Sep 2017, 08:39
I'll explain as simple as I can and preface a couple things. I did search the forums in the forums, I searched Google, I also google specifying virtualbox site, 20 yrs doing this stuff but I don't know what's causing my problem.
Bridged connection, of course.
I was having connectivity issues, basically anything requiring routing, happened in Fedora and Ubuntu on the same Intel NUC system running VirtualBox and might have happened with Hyper-V desktop version but that had other issues so I got rid of that. Summing it up, my router has seemed faulty but it was expensive and I will replace but I have to wait a bit longer and searching everywhere showed others having similar problems but no clear solutions nor anyone listing the same source of the problem, the wrong MAC address for the router.
arp -a on the fedora showed this address combination for the router, not a copy of the output:
192.168.0.1 98:ee:cb:13:61:ba
that's not the right MAC for the router, not the MAC for the virtual NIC, not the MAC for the PC, not the MAC for anything on my network, looked it up in vendor tools got this:
MAC Address/OUI Vendor {Company}
98:EE:CB Wistron Infocomm (Zhongshan) Corporation
Say what? I don't know what that is, here's the Netgear MAC and what is should have, a0:63:91:d1:0c:88
I meant to delete the entry first and try again but I jumped the gun deleting the arp and adding the correct one, which I can again remove but that fixed it immediately as I knew it would.
What I have no idea about is where this fantasy MAC address is coming from this has never happened before. I have virtual CentOS on VMware, Hyper-V, KVM and it's always the same thing again as it should be they have the right MAC no reason to spoof that.
And the perm arp will fix it for good but that doesn't tell me the problem, and why it's like even though I have bridging selected and working mostly, as I always have with VirtualBox for the past 10 years, this behavior seems like it thinks it's suppost to do some NAT, Host only whatever?
Guys, gals I appreciate your time, sorry this was long, it's cursed me for weeks now and I had to vent. If you have any help or have seen it before and know why this is happening let me know.
This happens off a fresh install, no changes have been done to the fedora OS, not yet, just the arp entry, and mostly defaults with VBox settings, bridged networking? That's it.
Thanks
Bridged connection, of course.
I was having connectivity issues, basically anything requiring routing, happened in Fedora and Ubuntu on the same Intel NUC system running VirtualBox and might have happened with Hyper-V desktop version but that had other issues so I got rid of that. Summing it up, my router has seemed faulty but it was expensive and I will replace but I have to wait a bit longer and searching everywhere showed others having similar problems but no clear solutions nor anyone listing the same source of the problem, the wrong MAC address for the router.
arp -a on the fedora showed this address combination for the router, not a copy of the output:
192.168.0.1 98:ee:cb:13:61:ba
that's not the right MAC for the router, not the MAC for the virtual NIC, not the MAC for the PC, not the MAC for anything on my network, looked it up in vendor tools got this:
MAC Address/OUI Vendor {Company}
98:EE:CB Wistron Infocomm (Zhongshan) Corporation
Say what? I don't know what that is, here's the Netgear MAC and what is should have, a0:63:91:d1:0c:88
I meant to delete the entry first and try again but I jumped the gun deleting the arp and adding the correct one, which I can again remove but that fixed it immediately as I knew it would.
What I have no idea about is where this fantasy MAC address is coming from this has never happened before. I have virtual CentOS on VMware, Hyper-V, KVM and it's always the same thing again as it should be they have the right MAC no reason to spoof that.
And the perm arp will fix it for good but that doesn't tell me the problem, and why it's like even though I have bridging selected and working mostly, as I always have with VirtualBox for the past 10 years, this behavior seems like it thinks it's suppost to do some NAT, Host only whatever?
Guys, gals I appreciate your time, sorry this was long, it's cursed me for weeks now and I had to vent. If you have any help or have seen it before and know why this is happening let me know.
This happens off a fresh install, no changes have been done to the fedora OS, not yet, just the arp entry, and mostly defaults with VBox settings, bridged networking? That's it.
Thanks