[ Date Index ] [ Thread Index ] [ <= Previous by date / thread ] [ Next by date / thread => ]
On 08/05/17 08:38, Julian Hall wrote:
On 08/05/17 02:52, mr meowski wrote:On 08/05/17 02:26, Julian Hall wrote:First, how is your network configured on Circe? Systemd, NetworkManager,manually...The only configuration I have done is to setup the network name, give all wired devices fixed IPs, and then added the NAS manually into the fstab. That's pretty much it.Maybe I should have explained that a little better... I mean how exactly did you configure the network settings on just your main PC, Circe? Did you do it by manually editing the /etc/network/interfaces file, setting up a systemd unit file with systemctl/netctl or by using whichever GUI comes with your choice of Desktop Environment (probably NetworkManager, by default)? It makes a big difference as to whether your network is being brought up by a system service during early boot (desirable) or only after you've logged in as a user (undesirable). I was also presuming that the NAS would always be up and running, at least when you were testing or using NFS mounting on your PC. If you're not sure about how/when your network is starting up we can usesystemd-analyze to figure out what's wrong with the boot process instead.CheersAh.. my mistake, I used a GUI to set it up. Julian
Hi,I found a website guide on setting up a network manually. I /haven't/ touched anything as yet, but I followed the commands to see exactly what my network set-up is at the moment:
julian@Cerce ~ $ hostname Cerce julian@Cerce ~ $ ip addr1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp0s10: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
state UP group default qlen 1000
link/ether 00:19:66:f7:4b:1c brd ff:ff:ff:ff:ff:ff
inet 192.168.1.2/24 brd 192.168.1.255 scope global dynamic enp0s10
valid_lft 84463sec preferred_lft 84463sec
inet6 fe80::b118:b03f:5f:9e28/64 scope link
valid_lft forever preferred_lft forever
julian@Cerce ~ $
I'm confused why eth0 isn't listed.. is that due to the method I used to
set it up?
This is the content of my current /etc/network/interfaces # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback Judging by the website's example (below) mine has nothing useful in it. auto eth0 iface eth0 inet dhcp auto eth1 iface eth1 inet static address 192.168.1.100 netmask 255.255.255.0 gateway 192.168.1.1 dns-nameservers 8.8.8.8 My guess is mine should be something like this: auto eth0 iface eth0 inet dhcp auto eth1 iface eth1 inet static address 192.168.1.3 # The static IP it has now netmask 255.255.255.0 gateway 192.168.1.1 #coincidentally the same dns-nameservers 194.168.4.100 #Virginmedia's DNS primary server. Kind regards, Julian -- The Mailing List for the Devon & Cornwall LUG https://mailman.dclug.org.uk/listinfo/list FAQ: http://www.dcglug.org.uk/listfaq