search

oraclebase / vagrant

Vagrant Builds
https://oracle-base.com/
GNU General Public License v3.0
190 stars 167 forks source link

Correct network interface names to eth1 and eth2 to reflect changes to "bento/oracle-7.5" box configuration. #1

Closed bhaumik04 closed 5 years ago

bhaumik04 commented 5 years ago

Instead of enp0s8 and enp0s9, we should have it eth1 and eth2

oraclebase commented 5 years ago

It seems this is a change in the "bento/oracle-7.5" box. Before I update the box, on Linux and Windows hosts I see this on a freshly built DNS server, which matches the device naming scheme I have in the config file.

[vagrant@localhost ~]$ ifconfig enp0s3: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 10.0.2.15 netmask 255.255.255.0 broadcast 10.0.2.255 inet6 fe80::3fe6:747:fff5:cce4 prefixlen 64 scopeid 0x20 ether 08:00:27:e9:5a:54 txqueuelen 1000 (Ethernet) RX packets 9025 bytes 10543786 (10.0 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1778 bytes 183304 (179.0 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

enp0s8: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.56.100 netmask 255.255.255.0 broadcast 192.168.56.255 inet6 fe80::a00:27ff:fe2f:5229 prefixlen 64 scopeid 0x20 ether 08:00:27:2f:52:29 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 10 bytes 768 (768.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10 loop txqueuelen 0 (Local Loopback) RX packets 4 bytes 328 (328.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 4 bytes 328 (328.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

[vagrant@localhost ~]$

After I run "vagrant box update", then destroy and rebuild the DNS server I see this.

[vagrant@localhost ~]$ ifconfig eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 10.0.2.15 netmask 255.255.255.0 broadcast 10.0.2.255 inet6 fe80::42db:4853:aa23:8a82 prefixlen 64 scopeid 0x20 ether 08:00:27:9b:3e:e7 txqueuelen 1000 (Ethernet) RX packets 9734 bytes 10597513 (10.1 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 2474 bytes 239797 (234.1 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.56.100 netmask 255.255.255.0 broadcast 192.168.56.255 inet6 fe80::a00:27ff:fe62:968c prefixlen 64 scopeid 0x20 ether 08:00:27:62:96:8c txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 10 bytes 768 (768.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10 loop txqueuelen 0 (Local Loopback) RX packets 4 bytes 328 (328.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 4 bytes 328 (328.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

[vagrant@localhost ~]$

Which matches the naming scheme you are seeing.

So it seems a change to the "bento/oracle-7.5" box has caused the ethernet device naming to change.