nexusofdoom/lancache-installer

Ip configuration

Closed this issue · 3 comments

marol94 commented

i don't understand if i need to setup the other ip address manually or if the script autoconfigure the ip

nexusofdoom commented

It will auto populate the other ip's in the interface file automatically.

marol94 commented

ok, so if the bare machine is on the 0.1, the script will automatically bind the other ip like 0.2-0.18 right?
on a freshly installed 18.04 server, i need only to launch the script, wait, and point the client dns to the bare metal pc ip right?

btw if i use that script, at the end return

'/usr/local/lancache/lancache-installer/etc/nginx/lancache/proxy-cache' -> '/etc/nginx/lancache/proxy-cache'
'/usr/local/lancache/lancache-installer/etc/nginx/lancache/resolver' -> '/etc/nginx/lancache/resolver'
Configuring sniproxy...
Configuring unbound...
Configuring services to run on boot...
Synchronizing state of nginx.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable nginx
Removed /etc/systemd/system/multi-user.target.wants/nginx.service.
Created symlink /etc/systemd/system/multi-user.target.wants/nginx.service → /etc/systemd/system/nginx.service.
Synchronizing state of nginx.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable nginx
sniproxy.service is not a native service, redirecting to systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable sniproxy
Synchronizing state of unbound.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable unbound
Synchronizing state of netdata.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable netdata
Configuring network interfaces and hosts file...
mv: cannot stat '/etc/netplan/01-netcfg.yaml': No such file or directory
##############################################################################################
Current interface name: enp3s0
enp4s0
##############################################################################################

##############################################################################################
DNS Server IP Address / Point Clients to Use this DNS Server: 192.168.2.166
##############################################################################################

##############################################################################################
Reboot System
##############################################################################################

it's a normal behaviour?

ok maybe i've find something strange,
i see that the other ip are unreacable from the network, my netplan generated file is that

network:
version: 2
renderer: networkd
ethernets:
lc-host-vint:
dhcp4: no
dhcp6: no
addresses: [192.168.2.166/24]
addresses: [192.168.2.176/24]
addresses: [192.168.2.175/24]
addresses: [192.168.2.169/24]
addresses: [192.168.2.170/24]
addresses: [192.168.2.174/24]
addresses: [192.168.2.177/24]
addresses: [192.168.2.173/24]
addresses: [192.168.2.178/24]
addresses: [192.168.2.171/24]
addresses: [192.168.2.167/24]
addresses: [192.168.2.168/24]
addresses: [192.168.2.179/24]
addresses: [192.168.2.180/24]
addresses: [192.168.2.172/24]
addresses: [192.168.2.181/24]
addresses: [192.168.2.182/24]
addresses: [192.168.2.183/24]
gateway4: 192.168.2.3
nameservers:
addresses: [8.8.8.8,4.2.2.2]