Various Plugins' Remote Access Stopped Working (Plex,ownCloud, etc)

Status
Not open for further replies.

I3lackR0se

Dabbler
Joined
May 22, 2015
Messages
16
Hey all. I've been trying to tackle this problem myself for about two weeks, but I've hit a wall and need some help figuring out what's happening.

About two weeks ago I lost the ability to remotely connect to various services that required manual port forwarding or UPnP (Noticed it first with Plex, then ownCloud). I can still access the web interfaces for both on the local network fine. I also put my router into DMZ mode, and was still unable to connect to them. By restarting, resetting the interfaces, and doing a fresh install of Plex I was able to get it's connection to return for a couple days, but eventually it stopped connecting and returned to the behavior of the old installation.

One last note on the behavior of plex: If I hit the 'Retry' button in the server connection settings on the Plex Web GUI, it actually becomes remotely available for about 30 seconds, but then immediately disconnects and becomes blocked again.

I've dug through a bunch of different leads, but never got anywhere useful. Here is the system / log information I believe to be useful / relevant to the problem at hand:

Motherboard: Supermicro X10SL7-F
Network Controller: Intel® i210AT dual port GbE Controllers (on the motherboard)
Ifconfig -a output:
igb0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 15
00
options=400b8<VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,VLAN_HWTSO>
ether 0c:c4:7a:69:07:84
inet 192.168.1.170 netmask 0xffffff00 broadcast 192.168.1.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=403bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSU
M,TSO4,TSO6,VLAN_HWTSO>
ether 0c:c4:7a:69:07:85
nd6 options=9<PERFORMNUD,IFDISABLED>
media: Ethernet autoselect
status: no carrier
ipfw0: flags=8801<UP,SIMPLEX,MULTICAST> metric 0 mtu 65536
nd6 options=9<PERFORMNUD,IFDISABLED>
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 0x6
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:09:6c:55:09: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: epair5a flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
ifmaxaddr 0 port 13 priority 128 path cost 2000
member: epair4a flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
ifmaxaddr 0 port 12 priority 128 path cost 2000
member: epair3a flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
ifmaxaddr 0 port 11 priority 128 path cost 2000
member: epair2a flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
ifmaxaddr 0 port 10 priority 128 path cost 2000
member: epair1a flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
ifmaxaddr 0 port 9 priority 128 path cost 2000
member: epair0a flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
ifmaxaddr 0 port 8 priority 128 path cost 2000
member: igb0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
ifmaxaddr 0 port 2 priority 128 path cost 20000
epair0a: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu
1500
options=8<VLAN_MTU>

ether 02:bb:ae:00:08:0a
nd6 options=1<PERFORMNUD>
media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
status: active
epair1a: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu
1500
options=8<VLAN_MTU>
ether 02:e7:c3:00:09:0a
nd6 options=1<PERFORMNUD>
media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
status: active
epair2a: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu
1500
options=8<VLAN_MTU>
ether 02:54:5c:00:0a:0a
nd6 options=1<PERFORMNUD>
media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
status: active
epair3a: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu
1500
options=8<VLAN_MTU>
ether 02:41:fb:00:0b:0a
nd6 options=1<PERFORMNUD>
media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
status: active
epair5a: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu
1500
options=8<VLAN_MTU>
ether 02:46:3e:00:0d:0a
nd6 options=1<PERFORMNUD>
media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
status: active

Potentially relevant Freenas Message Log:
Jan 14 23:55:56 freenas root: /etc/rc: WARNING: failed precmd routine for vmware_guestd
Jan 14 23:55:56 freenas vboxdrv: fAsync=0 offMin=0x2a6 offMax=0xf9c
Jan 14 23:55:58 freenas ntpd[2453]: ntpd 4.2.4p5-a (1)
Jan 14 23:56:02 freenas generate_smb4_conf.py: [common.pipesubr:70] Popen()ing: /usr/local/bin/net getlocalsid
Jan 14 23:56:02 freenas generate_smb4_conf.py: [common.pipesubr:70] Popen()ing: /sbin/sysctl -n 'kern.maxfilesperproc'
Jan 14 23:56:02 freenas generate_smb4_conf.py: [common.pipesubr:70] Popen()ing: zfs list -H -o mountpoint
Jan 14 23:56:02 freenas generate_smb4_conf.py: [common.pipesubr:70] Popen()ing: zfs list -H -o mountpoint
Jan 14 23:56:02 freenas generate_smb4_conf.py: [common.pipesubr:70] Popen()ing: zfs list -H -o mountpoint
Jan 14 23:56:02 freenas generate_smb4_conf.py: [common.pipesubr:70] Popen()ing: zfs list -H -o mountpoint
Jan 14 23:56:02 freenas generate_smb4_conf.py: [common.pipesubr:70] Popen()ing: zfs list -H -o mountpoint
Jan 14 23:56:02 freenas generate_smb4_conf.py: [common.pipesubr:70] Popen()ing: zfs list -H -o mountpoint
Jan 14 23:56:02 freenas generate_smb4_conf.py: [common.pipesubr:70] Popen()ing: zfs list -H -o mountpoint
Jan 14 23:56:02 freenas generate_smb4_conf.py: [common.pipesubr:70] Popen()ing: /usr/local/bin/net getlocalsid
Jan 14 23:56:02 freenas generate_smb4_conf.py: [common.pipesubr:70] Popen()ing: /usr/local/bin/net setlocalsid S-1-5-21-1109067318-1771876051-3100464924
Jan 14 23:56:02 freenas generate_smb4_conf.py: [common.pipesubr:70] Popen()ing: /usr/local/bin/pdbedit -d 0 -i smbpasswd:/tmp/tmpjHHI2I -s /usr/local/etc/smb4.conf -e tdbsam:/var/etc/private/passdb.tdb
Jan 14 23:56:02 freenas generate_smb4_conf.py: [common.pipesubr:70] Popen()ing: /usr/local/bin/smbpasswd -d 'guest'
Jan 14 23:56:02 freenas generate_smb4_conf.py: [common.pipesubr:70] Popen()ing: /usr/local/bin/pdbedit -L
Jan 14 23:56:02 freenas generate_smb4_conf.py: [common.pipesubr:70] Popen()ing: /usr/local/bin/net sam rights grant guest SeTakeOwnershipPrivilege SeBackupPrivilege SeRestorePrivilege
Jan 14 23:56:02 freenas nmbd[2743]: [2016/01/14 23:56:02.879988, 0] ../lib/util/become_daemon.c:136(daemon_ready)
Jan 14 23:56:02 freenas smbd[2746]: [2016/01/14 23:56:02.914000, 0] ../lib/util/become_daemon.c:136(daemon_ready)
Jan 14 23:56:02 freenas smbd[2746]: dnssd_clientstub ConnectToServer: connect()-> No of tries: 1
Jan 14 23:56:02 freenas winbindd[2749]: [2016/01/14 23:56:02.922177, 0] ../source3/winbindd/winbindd_cache.c:3196(initialize_winbindd_cache)
Jan 14 23:56:02 freenas winbindd[2749]: initialize_winbindd_cache: clearing cache and re-creating with version number 2
Jan 14 23:56:02 freenas winbindd[2749]: [2016/01/14 23:56:02.924121, 0] ../lib/util/become_daemon.c:136(daemon_ready)
Jan 14 23:56:03 freenas smbd[2746]: dnssd_clientstub ConnectToServer: connect()-> No of tries: 2
Jan 14 23:56:07 freenas ntpd[2454]: time reset -0.148804 s
Jan 14 23:56:10 freenas bridge0: Ethernet address: 02:09:6c:55:09:00
Jan 14 23:56:10 freenas kernel: bridge0: link state changed to UP
Jan 14 23:56:10 freenas kernel: bridge0: link state changed to UP
Jan 14 23:56:10 freenas kernel: igb0: promiscuous mode enabled
Jan 14 23:56:10 freenas epair0a: Ethernet address: 02:bb:ae:00:08:0a
Jan 14 23:56:10 freenas epair0b: Ethernet address: 02:bb:ae:00:09:0b
Jan 14 23:56:10 freenas kernel: epair0a: link state changed to UP
Jan 14 23:56:10 freenas kernel: epair0a: link state changed to UP
Jan 14 23:56:10 freenas kernel: epair0b: link state changed to UP
Jan 14 23:56:10 freenas kernel: epair0b: link state changed to UP
Jan 14 23:56:11 freenas kernel: igb0: link state changed to DOWN
Jan 14 23:56:11 freenas kernel: igb0: link state changed to DOWN
Jan 14 23:56:11 freenas kernel: epair0a: promiscuous mode enabled
Jan 14 23:56:11 freenas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair0b
Jan 14 23:56:11 freenas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair0b
Jan 14 23:56:15 freenas kernel: igb0: link state changed to UP
Jan 14 23:56:15 freenas kernel: igb0: link state changed to UP
Jan 14 23:56:15 freenas epair1a: Ethernet address: 02:e7:c3:00:09:0a
Jan 14 23:56:15 freenas epair1b: Ethernet address: 02:e7:c3:00:0a:0b
Jan 14 23:56:15 freenas kernel: epair1a: link state changed to UP
Jan 14 23:56:15 freenas kernel: epair1a: link state changed to UP
Jan 14 23:56:15 freenas kernel: epair1b: link state changed to UP
Jan 14 23:56:15 freenas kernel: epair1b: link state changed to UP
Jan 14 23:56:15 freenas kernel: epair1a: promiscuous mode enabled
Jan 14 23:56:15 freenas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair1b
Jan 14 23:56:15 freenas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair1b
Jan 14 23:56:23 freenas epair2a: Ethernet address: 02:54:5c:00:0a:0a
Jan 14 23:56:23 freenas epair2b: Ethernet address: 02:54:5c:00:0b:0b
Jan 14 23:56:23 freenas kernel: epair2a: link state changed to UP
Jan 14 23:56:23 freenas kernel: epair2a: link state changed to UP
Jan 14 23:56:23 freenas kernel: epair2b: link state changed to UP
Jan 14 23:56:23 freenas kernel: epair2b: link state changed to UP
Jan 14 23:56:23 freenas kernel: epair2a: promiscuous mode enabled
Jan 14 23:56:23 freenas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair2b
Jan 14 23:56:23 freenas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair2b
Jan 14 23:56:25 freenas nmbd[2743]: STATUS=daemon 'nmbd' finished starting up and ready to serve connections*****
Jan 14 23:56:25 freenas nmbd[2743]:
Jan 14 23:56:25 freenas nmbd[2743]: Samba name server FREENAS is now a local master browser for workgroup WORKGROUP on subnet 192.168.1.170
Jan 14 23:56:25 freenas nmbd[2743]:
Jan 14 23:56:25 freenas nmbd[2743]: *****
Jan 14 23:56:33 freenas epair3a: Ethernet address: 02:41:fb:00:0b:0a
Jan 14 23:56:33 freenas epair3b: Ethernet address: 02:41:fb:00:0c:0b
Jan 14 23:56:33 freenas kernel: epair3a: link state changed to UP
Jan 14 23:56:33 freenas kernel: epair3a: link state changed to UP
Jan 14 23:56:33 freenas kernel: epair3b: link state changed to UP
Jan 14 23:56:33 freenas kernel: epair3b: link state changed to UP
Jan 14 23:56:33 freenas kernel: epair3a: promiscuous mode enabled
Jan 14 23:56:33 freenas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair3b
Jan 14 23:56:33 freenas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair3b
Jan 14 23:56:38 freenas epair4a: Ethernet address: 02:14:79:00:0c:0a
Jan 14 23:56:38 freenas epair4b: Ethernet address: 02:14:79:00:0d:0b
Jan 14 23:56:38 freenas kernel: epair4a: link state changed to UP
Jan 14 23:56:38 freenas kernel: epair4a: link state changed to UP
Jan 14 23:56:38 freenas kernel: epair4b: link state changed to UP
Jan 14 23:56:38 freenas kernel: epair4b: link state changed to UP
Jan 14 23:56:38 freenas kernel: epair4a: promiscuous mode enabled
Jan 14 23:56:38 freenas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair4b
Jan 14 23:56:38 freenas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair4b
Jan 14 23:56:44 freenas epair5a: Ethernet address: 02:46:3e:00:0d:0a
Jan 14 23:56:44 freenas epair5b: Ethernet address: 02:46:3e:00:0e:0b
Jan 14 23:56:44 freenas kernel: epair5a: link state changed to UP
Jan 14 23:56:44 freenas kernel: epair5a: link state changed to UP
Jan 14 23:56:44 freenas kernel: epair5b: link state changed to UP
Jan 14 23:56:44 freenas kernel: epair5b: link state changed to UP
Jan 14 23:56:44 freenas kernel: epair5a: promiscuous mode enabled
Jan 14 23:56:44 freenas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair5b
Jan 14 23:56:44 freenas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair5b
Jan 14 23:57:37 freenas dhclient: New IP Address (igb0): 192.168.1.170
Jan 14 23:57:37 freenas dhclient: New Subnet Mask (igb0): 255.255.255.0
Jan 14 23:57:37 freenas dhclient: New Broadcast Address (igb0): 192.168.1.255
Jan 14 23:57:37 freenas dhclient: New Routers (igb0): 192.168.1.1
Jan 14 23:57:38 freenas dhclient: New Routers (igb0): 192.168.1.1

I've also attached my latest Plex logs from my last session, since the behavior on that plug-in seems very specific to the problem and might provide more insight into what's happening.

Any help that anyone can provide would be very, very greatly appreciated. I had been running Freenas for over half a year without a hitch before this happened out of no where, so I'm hoping the problem is ultimately small and/or simple and that I can get things back to running smoothly. I have various other logs saved, if one of them would be useful to debugging the issue.
 

Attachments

  • Plex Media ServerRedacted.log.1.txt
    1.3 MB · Views: 55,783
  • Plex Media ServerRedacted.log.txt
    70.5 KB · Views: 401
  • Plex Media ServerRedacted.log.2.txt
    983.5 KB · Views: 1,594
  • Plex Media ServerRedacted.log.3.txt
    981 KB · Views: 34,466

SweetAndLow

Sweet'NASty
Joined
Nov 6, 2013
Messages
6,421
Do you have any firewalls or packet inspection happening at your firewall?
 

depasseg

FreeNAS Replicant
Joined
Sep 16, 2014
Messages
2,874
Try it without using UPNP. And make sure your jail networks are operational.

Looks like a lot of these errors:
Code:
[0x80aa01c00] WARN - NetworkServiceBrowser: Error sending out discover packet: send_to: Can't assign requested address (spammed many times, reduced to 1 line to save file space)
{This warning repeats about an additional 120 or so times. Trimmed to reduce file size}
[0x80aa01c00] WARN - NetworkServiceBrowser: Error sending out discover packet: send_to: Can't assign requested address (spammed many times, reduced to 1 line to save file space)
 

SweetAndLow

Sweet'NASty
Joined
Nov 6, 2013
Messages
6,421
Looks like bad ip address in some way. Either conflict or netmask messed up. Just my guess.
 

I3lackR0se

Dabbler
Joined
May 22, 2015
Messages
16
Do you have any firewalls or packet inspection happening at your firewall?

I have some firewall rules setup in one of my other jails, but not one that Plex or ownCloud is running through. I don't believe any packet inspection is occurring in even that one, I didn't set anything like that up (to my knowledge, anyway).


Try it without using UPNP. And make sure your jail networks are operational.

Looks like a lot of these errors:
Code:
[0x80aa01c00] WARN - NetworkServiceBrowser: Error sending out discover packet: send_to: Can't assign requested address (spammed many times, reduced to 1 line to save file space)
{This warning repeats about an additional 120 or so times. Trimmed to reduce file size}
[0x80aa01c00] WARN - NetworkServiceBrowser: Error sending out discover packet: send_to: Can't assign requested address (spammed many times, reduced to 1 line to save file space)

Yea, there were a couple Megabytes of lines in the log file of just those. I didn't mess with disabling UPnP before since the DMZ didn't even let it through. I just now tried it and added a manual port forward, but it looks like it didn't fix the issue.

As for checking the jail networks, I successfully ran a "ping www.google.com" and "dig www.ibm.com" in all the affected jails, so as far as I can tell they are operational. Is there something further I can/should do to verify their networks?


Looks like bad ip address in some way. Either conflict or netmask messed up. Just my guess.


I suspected an IP conflict as well, but one of my affected jails is running a static IP (and the others aren't in the DHCP range, and the router itself doesn't show any other devices that claim to have those IPs), so I don't *think* that is it. Is there a way for me to check whether the netmask being messed up is the root of the problem?

And thanks everyone for the help so far!
 

I3lackR0se

Dabbler
Joined
May 22, 2015
Messages
16
Didn't see anything that jumped out to me, but here's the ifconfig, netstat, and contents of etc/resolv.conf in the plex jail (if anything jumps out to anyone else):
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 0x1
inet 127.0.0.1 netmask 0xff000000
nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
epair4b: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=8<VLAN_MTU>
ether 02:9c:6b:00:0d:0b
inet 192.168.1.5 netmask 0xffffff00 broadcast 192.168.1.255
nd6 options=9<PERFORMNUD,IFDISABLED>
media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
status: active

Active Internet connections (including servers)
Proto Recv-Q Send-Q Local Address Foreign Address (state)
tcp4 0 0 plexmediaserver_.32400 192.168.1.104.51118 ESTABLISHED
tcp4 0 0 localhost.42432 *.* LISTEN
tcp4 0 0 plexmediaserver_.32400 192.168.1.104.51117 ESTABLISHED
tcp4 0 0 *.32469 *.* LISTEN
tcp4 0 0 *.1040 *.* LISTEN
tcp4 0 0 plexmediaserver_.16368 li1021-206.membe.https ESTABLISHED
tcp4 0 0 localhost.58528 localhost.39111 CLOSE_WAIT
tcp4 0 0 localhost.39111 *.* LISTEN
tcp4 0 0 localhost.32401 *.* LISTEN
tcp4 0 0 *.32400 *.* LISTEN
tcp4 0 0 plexmediaserver_.12350 *.* LISTEN
udp4 0 0 *.64113 *.*
udp4 0 0 *.59571 *.*
udp4 0 0 *.6376 *.*
udp4 0 0 *.15655 *.*
udp4 0 0 *.1900 *.*
udp4 0 0 plexmediaserver_.63324 *.*
udp4 0 0 localhost.47375 *.*
udp4 0 0 plexmediaserver_.37804 *.*
udp4 0 0 localhost.32281 *.*
udp4 0 0 *.32413 *.*
udp4 0 0 *.32412 *.*
udp4 0 0 *.32410 *.*
udp4 0 0 plexmediaserver_.57234 google-public-dn.domai
udp4 0 0 plexmediaserver_.54209 google-public-dn.domai
udp4 0 0 *.32414 *.*
udp4 0 0 *.15712 *.*
udp4 0 0 *.syslog *.*
udp6 0 0 *.syslog *.*
Active UNIX domain sockets
Address Type Recv-Q Send-Q Inode Conn Refs Nextref Addr
fffffe01075bcc30 dgram 0 0 0 fffffe01075bcd20 fffffe01075bcd20
0
fffffe01075bcd20 dgram 0 0 0 fffffe01075bcc30 fffffe01075bcc30
0
fffffe01075bce10 dgram 0 0 0 fffffe000ecafd20 fffffe000ecafd20
0
fffffe000ecafd20 dgram 0 0 0 fffffe01075bce10 fffffe01075bce10
0
fffffe000ecaf960 dgram 0 0 0 fffffe000ecaf870 fffffe000ecaf870
0
fffffe000ecaf870 dgram 0 0 0 fffffe000ecaf960 fffffe000ecaf960
0
fffffe000ecaf780 dgram 0 0 0 fffffe000ecaf5a0 fffffe000ecaf5a0
0
fffffe000ecaf5a0 dgram 0 0 0 fffffe000ecaf780 fffffe000ecaf780
0
fffffe000ecaf4b0 dgram 0 0 0 fffffe000ecaf3c0 fffffe000ecaf3c0
0
fffffe000ecaf3c0 dgram 0 0 0 fffffe000ecaf4b0 fffffe000ecaf4b0
0
fffffe000ecaf000 dgram 0 0 0 fffffe000ecaf0f0 fffffe000ecaf0f0
0
fffffe000ecaf0f0 dgram 0 0 0 fffffe000ecaf000 fffffe000ecaf000
0
fffffe000ecaf1e0 dgram 0 0 0 fffffe000ecaf2d0 fffffe000ecaf2d0
0
fffffe000ecaf2d0 dgram 0 0 0 fffffe000ecaf1e0 fffffe000ecaf1e0
0
fffffe003262b000 dgram 0 0 0 fffffe003267a5a0 0
0
fffffe003267a5a0 dgram 0 0 fffffe001f1c15e8 0 fffffe003262b000
0 /var/run/logpriv
fffffe003267a4b0 dgram 0 0 fffffe001f1c17e0 0 0
0 /var/run/log

search local
nameserver 8.8.8.8
nameserver 8.8.8.8
nameserver 8.8.8.8

Edit: Hello. I just an interesting output when restarting the plex jail from the command line:
[root@freenas ~]# warden stop plexmediaserver_1
jexec 5 /usr/pbi/plexmediaserver-amd64/control stop
Stoppingthejail....arp: writing to routing socket: Invalid argument
Unmounting user-supplied file-systems
Stopping jail with: /etc/rc.shutdown
...Done[root@freenas ~]# warden start plexmediaserver_1
Mounting user-supplied file-systems
jail -c path=/mnt/plexpool/plexdataset/plexmediaserver_1 name=plexmediaserver_1
host.hostname=plexmediaserver_1 allow.raw_sockets=true persist vnet=new
Setting IPv4 address: 192.168.1.5/24
arp: invalid Ethernet address ''
inet6_enable: YES -> YES
ip6addrctl_enable: YES -> YES
add net default: gateway 192.168.1.1
Starting jail with: /etc/rc
jexec 7 /usr/pbi/plexmediaserver-amd64/control start 192.168.1.5 12350

I'm not sure what " arp: invalid Ethernet address '' " means, but it looks like something is missing that shouldn't be
 
Last edited:
Status
Not open for further replies.
Top