Network/Hardware changes causing issues?

Status
Not open for further replies.
Joined
Jun 26, 2012
Messages
260
So, I recently changed my 2 Wifi router network to a Google OnHub (TP-Link) and a Google Wifi puck using the "mesh".
For the many months prior to that, once I had gotten everything set up network wise, everything worked like a charm.
I followed Fester's and a few other people's setup info. Had Plex working w/o issues.

Router IP 192.168.0.1
DHCP Address Pool 192.168.0.100 thru 192.168.0.149

Once I changed to the OnHub, I went into settings and tried to mirror those same reservations.
However, I have had some issues with getting the Plex app to work and I noticed that in the
"Plugins>Available" I get a message "No entry has been found", which appears to be a network connectivity issue.

I tried changing the Nameservers (previously had 8.8.8.8 and 8.8.4.4) but now trying my router and google...
Code:
Name IPv4 Address IPv6 Address
igb0 192.168.0.8/24
Nameserver
192.168.0.1
8.8.8.8
Default route
192.168.0.1


Researched a bit and what I'm seeing is it may be some kind of connectivity/network issue.

I tried pinging my router and Google (8.8.8.8) and get this:
Code:
[root@Name ~]# ping 192.168.0.1																									
PING 192.168.0.1 (192.168.0.1): 56 data bytes																					 
64 bytes from 192.168.0.1: icmp_seq=0 ttl=64 time=0.587 ms																		
64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=0.352 ms																		
64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=0.508 ms																		
64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=0.582 ms																		
64 bytes from 192.168.0.1: icmp_seq=4 ttl=64 time=0.625 ms																		
64 bytes from 192.168.0.1: icmp_seq=5 ttl=64 time=0.559 ms																		
64 bytes from 192.168.0.1: icmp_seq=6 ttl=64 time=0.707 ms																		
64 bytes from 192.168.0.1: icmp_seq=7 ttl=64 time=0.441 ms																		
64 bytes from 192.168.0.1: icmp_seq=8 ttl=64 time=0.509 ms																		
64 bytes from 192.168.0.1: icmp_seq=9 ttl=64 time=0.657 ms																		
64 bytes from 192.168.0.1: icmp_seq=10 ttl=64 time=0.453 ms																		
64 bytes from 192.168.0.1: icmp_seq=11 ttl=64 time=0.569 ms																		
64 bytes from 192.168.0.1: icmp_seq=12 ttl=64 time=0.761 ms																		
64 bytes from 192.168.0.1: icmp_seq=13 ttl=64 time=0.532 ms																		
64 bytes from 192.168.0.1: icmp_seq=14 ttl=64 time=0.802 ms																		
64 bytes from 192.168.0.1: icmp_seq=15 ttl=64 time=0.557 ms																		
64 bytes from 192.168.0.1: icmp_seq=16 ttl=64 time=0.487 ms																		
64 bytes from 192.168.0.1: icmp_seq=17 ttl=64 time=0.481 ms																		
64 bytes from 192.168.0.1: icmp_seq=18 ttl=64 time=0.699 ms																		
64 bytes from 192.168.0.1: icmp_seq=19 ttl=64 time=0.688 ms																		
																																  
64 bytes from 192.168.0.1: icmp_seq=20 ttl=64 time=0.659 ms																		
64 bytes from 192.168.0.1: icmp_seq=21 ttl=64 time=0.602 ms																		
64 bytes from 192.168.0.1: icmp_seq=22 ttl=64 time=0.619 ms																		
64 bytes from 192.168.0.1: icmp_seq=23 ttl=64 time=0.541 ms																		
64 bytes from 192.168.0.1: icmp_seq=24 ttl=64 time=0.470 ms																		
64 bytes from 192.168.0.1: icmp_seq=25 ttl=64 time=0.603 ms																		
64 bytes from 192.168.0.1: icmp_seq=26 ttl=64 time=0.479 ms																		
64 bytes from 192.168.0.1: icmp_seq=27 ttl=64 time=0.519 ms																		
64 bytes from 192.168.0.1: icmp_seq=28 ttl=64 time=0.763 ms																		
64 bytes from 192.168.0.1: icmp_seq=29 ttl=64 time=0.586 ms																		
64 bytes from 192.168.0.1: icmp_seq=30 ttl=64 time=0.592 ms																		
64 bytes from 192.168.0.1: icmp_seq=31 ttl=64 time=0.571 ms																		
64 bytes from 192.168.0.1: icmp_seq=32 ttl=64 time=0.395 ms																		
64 bytes from 192.168.0.1: icmp_seq=33 ttl=64 time=0.590 ms																		
64 bytes from 192.168.0.1: icmp_seq=34 ttl=64 time=0.534 ms																		
^C[root@Name ~]# ^C	 


IFCONFIG returns:
Code:
[root@Name ~]# ifconfig																											
igb0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500												
	   options=2400b9<RXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,VLAN_HWTSO,RXCSUM_IPV6>								
	   ether 0c:c4:7a:e3:a3:b2																									
	   inet 192.168.0.8 netmask 0xffffff00 broadcast 192.168.0.255																
	   nd6 options=9<PERFORMNUD,IFDISABLED>																					   
	   media: Ethernet autoselect (1000baseT <full-duplex>)																	   
	   status: active																											
igb1: flags=8c02<BROADCAST,OACTIVE,SIMPLEX,MULTICAST> metric 0 mtu 1500															
	   options=6403bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,VLAN_HWTSO,RXCSUM_IPV6,TXCSUM_IPV6>	
	   ether 0c:c4:7a:e3:a3:b3																									
	   nd6 options=9<PERFORMNUD,IFDISABLED>																					   
	   media: Ethernet autoselect																								
	   status: no carrier																										
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384																 
	   options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>																	 
	   inet6 ::1 prefixlen 128																									
	   inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3																				
	   inet 127.0.0.1 netmask 0xff000000																						 
	   nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>																				 
bridge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500													 
	   ether 02:39:a1:8d:10:00																									
	   nd6 options=1<PERFORMNUD>																								 
	   id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15																
	   maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200																   
	   root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0																   
	   member: epair0a flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>															 
			   ifmaxaddr 0 port 5 priority 128 path cost 2000																	
	   member: igb0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>																
			   ifmaxaddr 0 port 1 priority 128 path cost 20000																	
epair0a: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500											 
	   options=8<VLAN_MTU>																										
	   ether 02:ff:20:00:05:0a																									
	   nd6 options=1<PERFORMNUD>																								 
	   media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)																		
	   status: active 


Thoughts anyone?
 

kdragon75

Wizard
Joined
Aug 7, 2016
Messages
2,457
I went into settings and tried to mirror those same reservations.
Are you using DHCP with reservations or just plain DHCP? 192.168.0.100-192.168.0.149 is a pool or scope that the server is allowed to hand out and generally is first come first serve. Onec a device get an address it will *try* to hang onto it by refreshing the lease when it expires.

You don't explicitly say HOW you connecting to Plex. Are you just going to your jails IP address in your browser? are you trying to go through the Plex website? Are you trying to connect from the same network or from the internet? What is your Plex jails IP address?
 

kdragon75

Wizard
Joined
Aug 7, 2016
Messages
2,457
I tried pinging my router and Google (8.8.8.8) and get this:
I see the output for pining 192.168.0.1 (from a computer named "name" is that your FreeNAS box or the jail?) but not for 8.8.8.8.
 

kdragon75

Wizard
Joined
Aug 7, 2016
Messages
2,457
Your post is so much like information swiss cheese its making me hungry....
 
Joined
Jun 26, 2012
Messages
260
I see the output for pining 192.168.0.1 (from a computer named "name" is that your FreeNAS box or the jail?) but not for 8.8.8.8.
Here...(I just ran this and interrupted as it seemed like it was going to continue...
Code:
root@Name ~]# ping 8.8.8.8																										 
PING 8.8.8.8 (8.8.8.8): 56 data bytes																							   
64 bytes from 8.8.8.8: icmp_seq=0 ttl=57 time=15.863 ms																			 
64 bytes from 8.8.8.8: icmp_seq=1 ttl=57 time=27.552 ms																			 
64 bytes from 8.8.8.8: icmp_seq=2 ttl=57 time=13.735 ms																			 
64 bytes from 8.8.8.8: icmp_seq=3 ttl=57 time=14.831 ms																			 
64 bytes from 8.8.8.8: icmp_seq=4 ttl=57 time=14.754 ms																			 
64 bytes from 8.8.8.8: icmp_seq=5 ttl=57 time=14.854 ms																			 
64 bytes from 8.8.8.8: icmp_seq=6 ttl=57 time=13.780 ms																			 
64 bytes from 8.8.8.8: icmp_seq=7 ttl=57 time=15.964 ms																			 
64 bytes from 8.8.8.8: icmp_seq=8 ttl=57 time=13.104 ms																			 
64 bytes from 8.8.8.8: icmp_seq=9 ttl=57 time=14.356 ms																			 
64 bytes from 8.8.8.8: icmp_seq=10 ttl=57 time=15.033 ms																			
64 bytes from 8.8.8.8: icmp_seq=11 ttl=57 time=14.233 ms																			
64 bytes from 8.8.8.8: icmp_seq=12 ttl=57 time=20.357 ms																			
64 bytes from 8.8.8.8: icmp_seq=13 ttl=57 time=14.725 ms																			
64 bytes from 8.8.8.8: icmp_seq=14 ttl=57 time=13.789 ms																			
64 bytes from 8.8.8.8: icmp_seq=15 ttl=57 time=14.904 ms																			
64 bytes from 8.8.8.8: icmp_seq=16 ttl=57 time=14.880 ms																			
64 bytes from 8.8.8.8: icmp_seq=17 ttl=57 time=15.147 ms																			
64 bytes from 8.8.8.8: icmp_seq=18 ttl=57 time=15.139 ms																			
64 bytes from 8.8.8.8: icmp_seq=19 ttl=57 time=14.190 ms																			
64 bytes from 8.8.8.8: icmp_seq=20 ttl=57 time=16.025 ms																			
64 bytes from 8.8.8.8: icmp_seq=21 ttl=57 time=15.361 ms																			
64 bytes from 8.8.8.8: icmp_seq=22 ttl=57 time=14.176 ms																			
64 bytes from 8.8.8.8: icmp_seq=23 ttl=57 time=15.626 ms																			
64 bytes from 8.8.8.8: icmp_seq=24 ttl=57 time=14.958 ms																			
...
...
																																	
64 bytes from 8.8.8.8: icmp_seq=159 ttl=57 time=15.224 ms																		   
64 bytes from 8.8.8.8: icmp_seq=160 ttl=57 time=15.243 ms																		   
64 bytes from 8.8.8.8: icmp_seq=161 ttl=57 time=14.504 ms																		   
64 bytes from 8.8.8.8: icmp_seq=162 ttl=57 time=14.478 ms																   
64 bytes from 8.8.8.8: icmp_seq=163 ttl=57 time=14.986 ms																		   
64 bytes from 8.8.8.8: icmp_seq=164 ttl=57 time=13.859 ms																		   
64 bytes from 8.8.8.8: icmp_seq=165 ttl=57 time=16.112 ms																		   
^C																																 
--- 8.8.8.8 ping statistics ---																									 
166 packets transmitted, 166 packets received, 0.0% packet loss																	 
round-trip min/avg/max/stddev = 13.104/15.306/27.738/2.346 ms 
 
Joined
Jun 26, 2012
Messages
260
Your post is so much like information swiss cheese its making me hungry....
Sorry, I'll try to give meat and potatoes...but...not quite well versed in this...
 
Joined
Jun 26, 2012
Messages
260
Are you using DHCP with reservations or just plain DHCP? 192.168.0.100-192.168.0.149 is a pool or scope that the server is allowed to hand out and generally is first come first serve. Onec a device get an address it will *try* to hang onto it by refreshing the lease when it expires.

You don't explicitly say HOW you connecting to Plex. Are you just going to your jails IP address in your browser? are you trying to go through the Plex website? Are you trying to connect from the same network or from the internet? What is your Plex jails IP address?
Like I said, I'm not that well versed in this...so hopefully I'm not confusing terminology here...anyway

Jail IP is 192.168.0.10 and I'm trying to connect to that IP via my browser (Plex Web Client) and via PS4 (Plex App there...) and Plex App on my phones/tablets/etc. All have the same
issue where the server is not found. Through my PC, the CIFS? Windows shares are available and accessible.

I'm not sure if the Plex issue is related to the "Plugins - "No Entry Has Been Found" problem, and thus...I ask.
 

kdragon75

Wizard
Joined
Aug 7, 2016
Messages
2,457
Ok, let's try a few basic things. All from within the Plex jail, ping your desktop, your router, and google (8.8.8.8). Let us know how each one of those goes.
 
Joined
Jun 26, 2012
Messages
260
I'll get to this when I can.
Work is a 4 letter word...
Appreciate the help in advance.
 
Joined
Jun 26, 2012
Messages
260
hopefully when you say "from within the Plex jail", this is what you mean...if what I did is not what you mean,
well...assume my knowledge is that of someone who can type and that's about it...
Code:
[root@Name /mnt/Tank/jails/plexmediaserver_1]# ping 8.8.8.8																		 
PING 8.8.8.8 (8.8.8.8): 56 data bytes																							   
64 bytes from 8.8.8.8: icmp_seq=0 ttl=57 time=16.748 ms																			 
64 bytes from 8.8.8.8: icmp_seq=1 ttl=57 time=14.757 ms																			 
64 bytes from 8.8.8.8: icmp_seq=2 ttl=57 time=16.654 ms																			 
64 bytes from 8.8.8.8: icmp_seq=3 ttl=57 time=14.531 ms																			 
64 bytes from 8.8.8.8: icmp_seq=4 ttl=57 time=15.340 ms																			 
64 bytes from 8.8.8.8: icmp_seq=5 ttl=57 time=25.452 ms																			 
64 bytes from 8.8.8.8: icmp_seq=6 ttl=57 time=15.593 ms																			 
64 bytes from 8.8.8.8: icmp_seq=7 ttl=57 time=14.968 ms																			 
^C																																 
--- 8.8.8.8 ping statistics ---																									 
8 packets transmitted, 8 packets received, 0.0% packet loss																		 
round-trip min/avg/max/stddev = 14.531/16.755/25.452/3.375 ms																	   
[root@Name /mnt/Tank/jails/plexmediaserver_1]# ^C																				   
[root@Name /mnt/Tank/jails/plexmediaserver_1]# ping 192.168.0.1																	 
PING 192.168.0.1 (192.168.0.1): 56 data bytes																					   
64 bytes from 192.168.0.1: icmp_seq=0 ttl=64 time=0.719 ms																		 
64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=0.619 ms																		 
64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=0.401 ms																		 
64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=0.659 ms																		 
64 bytes from 192.168.0.1: icmp_seq=4 ttl=64 time=0.519 ms																		 
64 bytes from 192.168.0.1: icmp_seq=5 ttl=64 time=0.490 ms																		 
64 bytes from 192.168.0.1: icmp_seq=6 ttl=64 time=0.555 ms																		 
64 bytes from 192.168.0.1: icmp_seq=7 ttl=64 time=0.527 ms																		 
64 bytes from 192.168.0.1: icmp_seq=8 ttl=64 time=0.558 ms																		 
^C																																 
--- 192.168.0.1 ping statistics ---																								 
9 packets transmitted, 9 packets received, 0.0% packet loss																		 
round-trip min/avg/max/stddev = 0.401/0.561/0.719/0.089 ms																		 
[root@Name /mnt/Tank/jails/plexmediaserver_1]# ping 192.168.0.108																   
PING 192.168.0.108 (192.168.0.108): 56 data bytes																				   
64 bytes from 192.168.0.108: icmp_seq=0 ttl=128 time=0.320 ms																	   
64 bytes from 192.168.0.108: icmp_seq=1 ttl=128 time=0.360 ms																	   
64 bytes from 192.168.0.108: icmp_seq=2 ttl=128 time=0.353 ms																	   
64 bytes from 192.168.0.108: icmp_seq=3 ttl=128 time=0.302 ms																	   
64 bytes from 192.168.0.108: icmp_seq=4 ttl=128 time=0.310 ms																	   
64 bytes from 192.168.0.108: icmp_seq=5 ttl=128 time=0.366 ms																	   
64 bytes from 192.168.0.108: icmp_seq=6 ttl=128 time=0.366 ms																	   
64 bytes from 192.168.0.108: icmp_seq=7 ttl=128 time=0.366 ms																	   
64 bytes from 192.168.0.108: icmp_seq=8 ttl=128 time=0.318 ms																	   
64 bytes from 192.168.0.108: icmp_seq=9 ttl=128 time=0.358 ms																	   
^C																																 
--- 192.168.0.108 ping statistics ---																							   
10 packets transmitted, 10 packets received, 0.0% packet loss																	   
round-trip min/avg/max/stddev = 0.302/0.342/0.366/0.025 ms	 


So...based on my minimal knowledge...it looks like packets are being sent and received, which is nice.
192.168.0.108 is my desktop
192.160.0.1 is my router (the OnHub)
I wonder if I can ping the Google Wifi puck separately...anyway...that's what I got...
 
Joined
Jun 26, 2012
Messages
260
Bump...

Nobody? Haven't figured this out.
 

Jailer

Not strong, but bad
Joined
Sep 12, 2014
Messages
4,977
What is the contents of /etc/resolv.conf in your plex jail?

Also do you have a default gateway listed in your global network configuration?
 
Joined
Jun 26, 2012
Messages
260
What is the contents of /etc/resolv.conf in your plex jail?

Also do you have a default gateway listed in your global network configuration?
Code:
[root@Name /etc]# more resolv.conf																								 
# Generated by resolvconf																										   
search local																													   
nameserver 192.168.0.1																											 
nameserver 8.8.8.8						 

Code:
[root@Name /mnt/Tank/jails/plexmediaserver_1/etc]# more resolv.conf																 
# Generated by resolvconf																										   
search local																													   
nameserver 8.8.8.8																												 
nameserver 8.8.4.4		   


IPV4 Default Gateway is 192.168.0.1
 

Jailer

Not strong, but bad
Joined
Sep 12, 2014
Messages
4,977
Add your gateway to the plex jails resolv.conf file.
 
Joined
Jun 26, 2012
Messages
260
Add your gateway to the plex jails resolv.conf file.
Worked like a charm.
Thanks for that!

Any general thoughts on what happened? Should that file have autoupdated when I changed things around with my Network Hardware and Settings?
Or would I always have to make sure manually that the file has the gateway servers and other Nameservers listed?
 

Jailer

Not strong, but bad
Joined
Sep 12, 2014
Messages
4,977
The jails resolv.conf file is created using the default gateway listed in the FreeNAS GUI at creation time. If the gateway changes it has to be changed manually in each jail. That's with Warden, I'm not sure how things will work with iocage.
 
Status
Not open for further replies.
Top