Iohyve Pi-hole network problem

[Jetro]

Hello,

I've installed iohyve on a version of ubuntu 14 on my freenas 9.10.1-U4.
Pi-hole is running fine as a dns and blocking adds for my conputers. There is also a version of crashplan running on the server and wich is working fine.
I can connect fine with putty, but when i tried 'sudo-apt udate', I got time outs on all the server adresses.
I can ping the ip's from my LAN network ok. Pinging external ip's doesn't seem to work also.
I tried some playing with the dns settings, but it doesn't seem to do anything.

Has anybody any idee what might be missing?

/etc/network/interfaces:

Code:

 # The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto eth0
iface eth0 inet static
		address 10.0.0.140
		netmask 255.255.255.0
		gateway 10.0.0.137
		dns-nameservers 10.0.0.137 8.8.8.8

/etc/resolv.conf:

Code:

nameserver 127.0.0.1

iohyve :

Code:

Getting pihole iohyve properties...
bargs		  -A_-H_-P
boot		   1
brags		  -A_-H_-P_-S
con			nmdm0
cpu			1
description	Thu Sep  8 12:58:18 PDT 2016
install		no
loader		 grub-bhyve
name		   pihole
os			 linux
persist		1
ram			512
size		   20G
tap			tap0

 

[Sakuru]

Is 10.0.0.137 actually your gateway? Typically it's .1, so 10.0.0.1. It's definitely possible to have a gateway that isn't .1, just unusual.

 

[Jetro]

Yeah, it's something left over from my old thompson speedtouch or so i think.
I'm not a noob with network stuff, it's just the linux that has me puzzled a bit.
Strange that it can relay dns querries, but can't connect to internet.
does Pi-hole use differen settings than the host system? or does it 'occupie' the network addapter?

 

[Sakuru]

Please run these commands in the VM:

Code:

route
arp -a
ifconfig
ping -c 4 10.0.0.137

 

[Jetro]

route :
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
default 10.0.0.137 0.0.0.0 UG 0 0 0 eth0
default 10.0.0.137 0.0.0.0 UG 202 0 0 eth0
10.0.0.0 * 255.255.255.0 U 202 0 0 eth0
pihole localhost 255.255.255.255 UGH 202 0 0 lo

arp -a
? (10.0.0.137) at 6c:2e:85:22:42:8c [ether] on eth0
? (10.0.0.56) at 44:8a:5b:ce:68:a9 [ether] on eth0
? (10.0.0.1) at d0:50:99:8e:8e:21 [ether] on eth0
? (10.0.0.54) at 00:22:6c:26:f6:1d [ether] on eth0
? (10.0.0.57) at <incomplete> on eth0
? (10.0.0.2) at 20:cf:30:9c:08:e7 [ether] on eth0
? (10.0.0.55) at 48:51:b7:96:dd:ef [ether] on eth0

ifconfig
eth0 Link encap:Ethernet HWaddr 00:a0:98:3f:93:34
inet addr:10.0.0.140 Bcast:10.0.0.255 Mask:255.255.255.0
inet6 addr: fe80::2a0:98ff:fe3f:9334/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:179905 errors:0 dropped:0 overruns:0 frame:0
TX packets:98980 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:129333309 (129.3 MB) TX bytes:60208060 (60.2 MB)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:2663 errors:0 dropped:0 overruns:0 frame:0
TX packets:2663 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:191924 (191.9 KB) TX bytes:191924 (191.9 KB)

ping -c 4 10.0.0.137
PING 10.0.0.137 (10.0.0.137) 56(84) bytes of data.

--- 10.0.0.137 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 2999ms


PING 10.0.0.1 (10.0.0.1) 56(84) bytes of data.
64 bytes from 10.0.0.1: icmp_seq=1 ttl=64 time=0.062 ms
64 bytes from 10.0.0.1: icmp_seq=2 ttl=64 time=0.057 ms
64 bytes from 10.0.0.1: icmp_seq=3 ttl=64 time=0.049 ms
64 bytes from 10.0.0.1: icmp_seq=4 ttl=64 time=0.056 ms

--- 10.0.0.1 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3000ms
rtt min/avg/max/mdev = 0.049/0.056/0.062/0.004 ms

 

[Jetro]

Seems normal, not. except for the no connection problem then.