Jump to content

Recommended Posts

I installed the new DumaOS Development Milestone 1.3 on the R1 and since then the console disconnects from LAN while I play on my console.

After setting up my QoS, when I start to play online Street Fighter V Arcade Edition on my PS4 Pro, Playstation shows a message that it's disconnected from the LAN. The same message appears in loop until I reboot the NetDuma R1 and l restart the PS4 Pro/video game. Once the router and the console are up, I can play without any disconnection.
 

Share this post


Link to post
Share on other sites
11 hours ago, Donovan said:

I installed the new DumaOS Development Milestone 1.3 on the R1 and since then the console disconnects from LAN while I play on my console.

After setting up my QoS, when I start to play online Street Fighter V Arcade Edition on my PS4 Pro, Playstation shows a message that it's disconnected from the LAN. The same message appears in loop until I reboot the NetDuma R1 and l restart the PS4 Pro/video game. Once the router and the console are up, I can play without any disconnection.
 

Hi Donovan - first thing to check is obviously your LAN cable. If you switch out that cable does it still occur? If you connect the PS4 to another router / modem using the same cable does it happen?

This is a common issue with the PS4 Pro and can happen regardless of what router you're using. I'd recommend looking it up. I assume this isn't happening over WiFi? Try using an MTU analyser to find the best MTU for you and set that in the PS4 settings.

Share this post


Link to post
Share on other sites
On 11/15/2018 at 10:35 AM, Netduma Jack said:

Hi Donovan - first thing to check is obviously your LAN cable. If you switch out that cable does it still occur? If you connect the PS4 to another router / modem using the same cable does it happen?

This is a common issue with the PS4 Pro and can happen regardless of what router you're using. I'd recommend looking it up. I assume this isn't happening over WiFi? Try using an MTU analyser to find the best MTU for you and set that in the PS4 settings.

Hello Jack,

I already tested with another LAN Cable, different Ethernet ports on the R1, 2 other routers/modem, and the best MTU (1500). The issue is coming from the new DumaOS Milestone 1.3 on the R1. Sometimes even if I reboot the R1 and PS4 Pro, I still get an error message of “LAN Cable Not Connected”.

Share this post


Link to post
Share on other sites
On 11/16/2018 at 6:43 PM, Netduma Fraser said:

Delete your device from the Geo-Filter completely and play without it, do you continue to get this message?

I deleted all my devices from the Geo-Filter and I still get the message "LAN Cable Not Connected".

Share this post


Link to post
Share on other sites
4 hours ago, Netduma Fraser said:

Out of interest, have you checked the port on the console itself? Sometimes the pins can misalign which causes the message.

Also give the PS4 a static IP address and forward the necessary ports for it

Yes, I checked the port on the PS4 with different Ethernet cables and routers / modem. I have setup with/without a static IP for the forwarding port for Street Fighter V Arcade Edition. The result is still the same with the message "LAN Cable Not Connected " in loop..

From what I remember, I never have this issue before I upgrade to the Milestone 1.3 last week. The first online match with the Milestone 1.3, I had immediately this message "LAN Cable Not Connected " during the first online match.

One thing I didn't try yet, it's to downgrade the firmware to dumaos-2.1.2.10 or R1-v-1-03-6j. Do you think I should try to downgrade to previous firmware?

Share this post


Link to post
Share on other sites
On 11/18/2018 at 12:47 PM, Netduma Fraser said:

Yes please try downgrading to the previous dumaos version, not the old firmware and see if it still happens please

I downgraded to dumaos-2.1.2.10 and I played couple hours without issue.

I upgrade back to dumaos-2.1.3.29, first match online, the message "LAN Cable Not Connected" appears. I do a factory reset, reconfigure all my settings and play couple games without any issue. I turn off my console and I close the window of the DumaOS.

Later I come back, I log on the DumaOS and set my Geo-Filter view before I start playing on Street Fighter V. Play my first online match the message "LAN Cable Not Connected" again. I decide to do another factory reset and I play without a disconnected from LAN. It seems something trigger after I log on the DumaOS and start a game. As long as I keep my DumaOS browser open after the factory reset it runs fine.

Share this post


Link to post
Share on other sites
3 hours ago, Netduma Admin said:

Hi Donovan - thanks for this information. A few questions:

  1. Are you using Filtering Mode?
  2. Is Ping Assist enabled (i.e. set to a higher value than 0ms)?
  3. Is Fast Search enabled?
  4. Are you using a VPN?

Thanks.

1. I tried with Filtering Mode but is not working for Street Fighter V Arcade Edition because the PlayStation server is outside of the range of 2000 Kilometers. It won't find any P2P Players without going through the PlayStation server first, so I have to set it up at Spectating Mode for PS4 Pro.

2. I tried from 0 to 100ms

3. I tried both Fast Seach enabled/disabled.

4. I do not use VPN.

Note: In the Geo-Filter Map, I also set the button Profiles with Unreal Engine or without any profile in the profile selector.

SFV PS4 LAN Cable Not Connected.jpg

Share this post


Link to post
Share on other sites

So previous DumaOS firmware, you only played a few hours. Would it have definitely appeared usually in that time or could it potentially take longer sometimes? Just want to clarify if it works correctly on that version. Keeping the browser open on the interface it works fine? Thats really odd. 

How many devices do you have connected to the router by chance? 

Share this post


Link to post
Share on other sites

On the previous DumaOS firmware ( dumaos-2.1.2.10 ) I can play couple hours without any issue.

On the new DumaOS Development Milestone 1.3 ( dumaos-2.1.3.29 ) everytime I log in the DumaOS interface with the browser (Firefox), mostly the first or two online match it will trigger the message LAN cable not connected between 4-10 minutes. If I don't reboot/factory reset the R1 and restart the PS4 Pro/Street Fighter V, the error message will come back.

I only have 3 devices connected on the Netduma R1 and the wifi is off.

Share this post


Link to post
Share on other sites
1 hour ago, Netduma Fraser said:

When the message occurs can you look at the log please and copy and paste here a block of log entries that happens around that time please

Tue Nov 20 21:49:45 2018 user.info com.netdumasoftware.neighwatch: DHCP lease change. Tue Nov 20 21:49:45 2018 user.info com.netdumasoftware.neighwatch: DHCP old event. Tue Nov 20 21:49:45 2018 daemon.info dnsmasq-dhcp[1249]: DHCPACK(br-lan) 192.168.88.135 bc:60:a7:bd:b4:a1 Tue Nov 20 21:49:45 2018 daemon.info dnsmasq-dhcp[1249]: DHCPREQUEST(br-lan) 192.168.88.135 bc:60:a7:bd:b4:a1 Tue Nov 20 21:49:45 2018 daemon.info dnsmasq-dhcp[1249]: DHCPOFFER(br-lan) 192.168.88.135 bc:60:a7:bd:b4:a1 Tue Nov 20 21:49:45 2018 daemon.info dnsmasq-dhcp[1249]: DHCPDISCOVER(br-lan) 192.168.88.135 bc:60:a7:bd:b4:a1 Tue Nov 20 21:49:38 2018 user.info com.netdumasoftware.neighwatch: DHCP lease change. Tue Nov 20 21:49:38 2018 user.info com.netdumasoftware.neighwatch: DHCP old event. Tue Nov 20 21:49:38 2018 daemon.info dnsmasq-dhcp[1249]: DHCPACK(br-lan) 192.168.88.135 bc:60:a7:bd:b4:a1 Tue Nov 20 21:49:38 2018 daemon.info dnsmasq-dhcp[1249]: DHCPREQUEST(br-lan) 192.168.88.135 bc:60:a7:bd:b4:a1 Tue Nov 20 21:49:38 2018 daemon.info dnsmasq-dhcp[1249]: DHCPOFFER(br-lan) 192.168.88.135 bc:60:a7:bd:b4:a1 Tue Nov 20 21:49:38 2018 daemon.info dnsmasq-dhcp[1249]: DHCPDISCOVER(br-lan) 192.168.88.135 bc:60:a7:bd:b4:a1 Tue Nov 20 21:49:37 2018 kern.info kernel: [90783.532000] recv: nf_ct_get failed Tue Nov 20 21:49:35 2018 user.info com.netdumasoftware.neighwatch: DHCP lease change. Tue Nov 20 21:49:35 2018 user.info com.netdumasoftware.neighwatch: DHCP old event. Tue Nov 20 21:49:35 2018 daemon.info dnsmasq-dhcp[1249]: DHCPACK(br-lan) 192.168.88.135 bc:60:a7:bd:b4:a1 Tue Nov 20 21:49:35 2018 daemon.info dnsmasq-dhcp[1249]: DHCPREQUEST(br-lan) 192.168.88.135 bc:60:a7:bd:b4:a1 Tue Nov 20 21:49:35 2018 daemon.info dnsmasq-dhcp[1249]: DHCPOFFER(br-lan) 192.168.88.135 bc:60:a7:bd:b4:a1 Tue Nov 20 21:49:35 2018 daemon.info dnsmasq-dhcp[1249]: DHCPDISCOVER(br-lan) 192.168.88.135 bc:60:a7:bd:b4:a1 Tue Nov 20 21:49:24 2018 kern.info kernel: [90770.296000] recv: nf_ct_get failed Tue Nov 20 21:49:24 2018 kern.info kernel: [90770.208000] send: nf_ct_get failed Tue Nov 20 21:49:24 2018 kern.info kernel: [90770.208000] recv: nf_ct_get failed Tue Nov 20 21:49:23 2018 user.info com.netdumasoftware.neighwatch: DHCP lease change. Tue Nov 20 21:49:23 2018 user.info com.netdumasoftware.neighwatch: DHCP old event. Tue Nov 20 21:49:23 2018 daemon.info dnsmasq-dhcp[1249]: DHCPACK(br-lan) 192.168.88.135 bc:60:a7:bd:b4:a1 Tue Nov 20 21:49:23 2018 daemon.info dnsmasq-dhcp[1249]: DHCPREQUEST(br-lan) 192.168.88.135 bc:60:a7:bd:b4:a1 Tue Nov 20 21:49:23 2018 daemon.info dnsmasq-dhcp[1249]: DHCPOFFER(br-lan) 192.168.88.135 bc:60:a7:bd:b4:a1 Tue Nov 20 21:49:23 2018 daemon.info dnsmasq-dhcp[1249]: DHCPDISCOVER(br-lan) 192.168.88.135 bc:60:a7:bd:b4:a1 Tue Nov 20 21:49:16 2018 kern.info kernel: [90762.864000] send: nf_ct_get failed Tue Nov 20 21:49:16 2018 kern.info kernel: [90762.864000] recv: nf_ct_get failed Tue Nov 20 21:49:01 2018 kern.info kernel: [90747.772000] recv: nf_ct_get failed Tue Nov 20 21:49:00 2018 kern.info dpiclass-daemon: Kill flow due to timeout Tue Nov 20 21:48:44 2018 kern.info kernel: [90730.920000] send: nf_ct_get failed Tue Nov 20 21:48:44 2018 kern.info kernel: [90730.920000] recv: nf_ct_get failed Tue Nov 20 21:48:30 2018 kern.info dpiclass-daemon: Kill flow due to timeout Tue Nov 20 21:48:30 2018 kern.info dpiclass-daemon: Kill flow due to timeout Tue Nov 20 21:48:30 2018 kern.info dpiclass-daemon: Kill flow due to timeout Tue Nov 20 21:48:30 2018 kern.info dpiclass-daemon: Kill flow due to timeout Tue Nov 20 21:48:30 2018 kern.info dpiclass-daemon: Kill flow due to timeout Tue Nov 20 21:48:30 2018 kern.info dpiclass-daemon: Kill flow due to timeout Tue Nov 20 21:48:30 2018 kern.info dpiclass-daemon: Kill flow due to timeout Tue Nov 20 21:48:30 2018 kern.info dpiclass-daemon: Kill flow due to timeout Tue Nov 20 21:48:29 2018 kern.info kernel: [90715.580000] recv: nf_ct_get failed Tue Nov 20 21:48:29 2018 kern.info kernel: [90715.112000] send: nf_ct_get failed Tue Nov 20 21:48:29 2018 kern.info kernel: [90715.108000] recv: nf_ct_get failed Tue Nov 20 21:48:13 2018 kern.info kernel: [90699.552000] send: nf_ct_get failed Tue Nov 20 21:48:13 2018 kern.info kernel: [90699.548000] recv: nf_ct_get failed Tue Nov 20 21:48:12 2018 kern.info kernel: [90698.976000] send: nf_ct_get failed Tue Nov 20 21:48:12 2018 kern.info kernel: [90698.976000] recv: nf_ct_get failed Tue Nov 20 21:48:05 2018 kern.info kernel: [90691.968000] recv: nf_ct_get failed Tue Nov 20 21:47:57 2018 kern.info kernel: [90683.992000] send: nf_ct_get failed Tue Nov 20 21:47:57 2018 kern.info kernel: [90683.988000] recv: nf_ct_get failed Tue Nov 20 21:47:54 2018 kern.info kernel: [90680.700000] recv: nf_ct_get failed Tue Nov 20 21:47:52 2018 kern.info kernel: [90678.120000] recv: nf_ct_get failed Tue Nov 20 21:47:42 2018 kern.info kernel: [90668.428000] send: nf_ct_get failed Tue Nov 20 21:47:42 2018 kern.info kernel: [90668.428000] recv: nf_ct_get failed Tue Nov 20 21:47:40 2018 kern.info kernel: [90667.032000] send: nf_ct_get failed Tue Nov 20 21:47:40 2018 kern.info kernel: [90667.032000] recv: nf_ct_get failed Tue Nov 20 21:47:26 2018 kern.info kernel: [90652.868000] send: nf_ct_get failed Tue Nov 20 21:47:26 2018 kern.info kernel: [90652.868000] recv: nf_ct_get failed Tue Nov 20 21:47:24 2018 kern.info kernel: [90650.960000] send: nf_ct_get failed Tue Nov 20 21:47:24 2018 kern.info kernel: [90650.960000] recv: nf_ct_get failed Tue Nov 20 21:47:18 2018 kern.info kernel: [90644.988000] send: nf_ct_get failed Tue Nov 20 21:47:18 2018 kern.info kernel: [90644.988000] recv: nf_ct_get failed Tue Nov 20 21:47:16 2018 kern.info kernel: [90642.824000] send: nf_ct_get failed Tue Nov 20 21:47:16 2018 kern.info kernel: [90642.824000] recv: nf_ct_get failed Tue Nov 20 21:47:14 2018 kern.info kernel: [90640.948000] send: nf_ct_get failed Tue Nov 20 21:47:14 2018 kern.info kernel: [90640.948000] recv: nf_ct_get failed Tue Nov 20 21:47:12 2018 kern.info kernel: [90638.828000] send: nf_ct_get failed Tue Nov 20 21:47:12 2018 kern.info kernel: [90638.828000] recv: nf_ct_get failed Tue Nov 20 21:47:12 2018 kern.info kernel: [90638.656000] send: nf_ct_get failed Tue Nov 20 21:47:12 2018 kern.info kernel: [90638.656000] recv: nf_ct_get failed Tue Nov 20 21:47:11 2018 kern.info kernel: [90637.668000] send: nf_ct_get failed Tue Nov 20 21:47:11 2018 kern.info kernel: [90637.668000] recv: nf_ct_get failed Tue Nov 20 21:47:10 2018 kern.info kernel: [90636.828000] send: nf_ct_get failed Tue Nov 20 21:47:10 2018 kern.info kernel: [90636.828000] recv: nf_ct_get failed Tue Nov 20 21:47:10 2018 kern.info kernel: [90636.544000] recv: nf_ct_get failed Tue Nov 20 21:47:10 2018 kern.info kernel: [90636.472000] send: nf_ct_get failed Tue Nov 20 21:47:10 2018 kern.info kernel: [90636.472000] recv: nf_ct_get failed Tue Nov 20 21:47:10 2018 kern.info kernel: [90636.308000] send: nf_ct_get failed Tue Nov 20 21:47:10 2018 kern.info kernel: [90636.308000] recv: nf_ct_get failed Tue Nov 20 21:47:09 2018 kern.info kernel: [90635.948000] send: nf_ct_get failed Tue Nov 20 21:47:09 2018 kern.info kernel: [90635.948000] recv: nf_ct_get failed Tue Nov 20 21:47:09 2018 kern.info kernel: [90635.668000] send: nf_ct_get failed Tue Nov 20 21:47:09 2018 kern.info kernel: [90635.668000] recv: nf_ct_get failed Tue Nov 20 21:47:09 2018 kern.info kernel: [90635.432000] send: nf_ct_get failed Tue Nov 20 21:47:09 2018 kern.info kernel: [90635.428000] recv: nf_ct_get failed Tue Nov 20 21:47:08 2018 kern.info kernel: [90634.816000] send: nf_ct_get failed Tue Nov 20 21:47:08 2018 kern.info kernel: [90634.816000] recv: nf_ct_get failed Tue Nov 20 21:47:07 2018 kern.info kernel: [90633.888000] send: nf_ct_get failed Tue Nov 20 21:47:07 2018 kern.info kernel: [90633.888000] recv: nf_ct_get failed Tue Nov 20 21:47:07 2018 kern.info kernel: [90633.324000] send: nf_ct_get failed Tue Nov 20 21:47:07 2018 kern.info kernel: [90633.324000] recv: nf_ct_get failed Tue Nov 20 21:47:06 2018 kern.info kernel: [90632.944000] send: nf_ct_get failed Tue Nov 20 21:47:06 2018 kern.info kernel: [90632.944000] recv: nf_ct_get failed Tue Nov 20 21:47:06 2018 kern.info kernel: [90632.652000] send: nf_ct_get failed Tue Nov 20 21:47:06 2018 kern.info kernel: [90632.652000] recv: nf_ct_get failed Tue Nov 20 21:47:02 2018 kern.info kernel: [90628.348000] recv: nf_ct_get failed Tue Nov 20 21:46:45 2018 kern.info kernel: [90611.860000] recv: nf_ct_get failed Tue Nov 20 21:46:30 2018 kern.info dpiclass-daemon: Kill flow due to timeout Tue Nov 20 21:46:10 2018 kern.info kernel: [90576.744000] recv: nf_ct_get failed Tue Nov 20 21:46:07 2018 kern.info kernel: [90573.944000] recv: nf_ct_get failed Tue Nov 20 21:46:00 2018 kern.info dpiclass-daemon: Kill flow due to timeout Tue Nov 20 21:46:00 2018 kern.info dpiclass-daemon: Kill flow due to timeout Tue Nov 20 21:46:00 2018 kern.info dpiclass-daemon: Kill flow due to timeout Tue Nov 20 21:46:00 2018 kern.info dpiclass-daemon: Kill flow due to timeout Tue Nov 20 21:46:00 2018 kern.info dpiclass-daemon: Kill flow due to timeout Tue Nov 20 21:46:00 2018 kern.info dpiclass-daemon: Kill flow due to timeout Tue Nov 20 21:46:00 2018 kern.info dpiclass-daemon: Kill flow due to timeout Tue Nov 20 21:46:00 2018 kern.info dpiclass-daemon: Kill flow due to timeout Tue Nov 20 21:46:00 2018 kern.info dpiclass-daemon: Kill flow due to timeout Tue Nov 20 21:46:00 2018 kern.info dpiclass-daemon: Kill flow due to timeout Tue Nov 20 21:46:00 2018 kern.info dpiclass-daemon: Kill flow due to timeout Tue Nov 20 21:45:42 2018 kern.info kernel: [90548.680000] send: nf_ct_get failed Tue Nov 20 21:45:42 2018 kern.info kernel: [90548.680000] recv: nf_ct_get failed Tue Nov 20 21:45:33 2018 kern.info kernel: [90539.748000] recv: nf_ct_get failed Tue Nov 20 21:45:15 2018 kern.info kernel: [90521.776000] recv: nf_ct_get failed Tue Nov 20 21:45:15 2018 kern.info kernel: [90521.772000] recv: nf_ct_get failed Tue Nov 20 21:45:07 2018 kern.info kernel: [90513.840000] recv: nf_ct_get failed Tue Nov 20 21:45:00 2018 kern.info kernel: [90506.448000] recv: nf_ct_get failed Tue Nov 20 21:45:00 2018 kern.info dpiclass-daemon: Kill flow due to timeout Tue Nov 20 21:44:45 2018 kern.info kernel: [90491.848000] recv: nf_ct_get failed Tue Nov 20 21:44:43 2018 kern.info kernel: [90489.396000] recv: nf_ct_get failed Tue Nov 20 21:44:42 2018 kern.info kernel: [90488.424000] recv: nf_ct_get failed Tue Nov 20 21:44:06 2018 kern.info kernel: [90452.876000] recv: nf_ct_get failed Tue Nov 20 21:43:55 2018 kern.info kernel: [90441.644000] recv: nf_ct_get failed Tue Nov 20 21:43:35 2018 kern.info kernel: [90421.876000] recv: nf_ct_get failed Tue Nov 20 21:43:28 2018 kern.info kernel: [90414.960000] recv: nf_ct_get failed Tue Nov 20 21:43:11 2018 daemon.warn odhcpd[877]: Failed to send to ff02::1%br-lan (Operation not permitted)

Share this post


Link to post
Share on other sites

Hello Fraser, could you please forward to the devs this longer log with a multiple notification of a LAN cable not connected.

Thank you,

 

Thu Nov 22 22:57:42 2018 kern.info kernel: [ 7288.428000] recv: nf_ct_get failed Thu Nov 22 22:57:14 2018 user.info com.netdumasoftware.neighwatch: DHCP lease change. Thu Nov 22 22:57:14 2018 user.info com.netdumasoftware.neighwatch: DHCP old event. Thu Nov 22 22:57:14 2018 daemon.info dnsmasq-dhcp[1323]: DHCPACK(br-lan) 192.168.88.135 bc:60:a7:bd:b4:a1 Thu Nov 22 22:57:14 2018 daemon.info dnsmasq-dhcp[1323]: DHCPREQUEST(br-lan) 192.168.88.135 bc:60:a7:bd:b4:a1 Thu Nov 22 22:57:14 2018 daemon.info dnsmasq-dhcp[1323]: DHCPOFFER(br-lan) 192.168.88.135 bc:60:a7:bd:b4:a1 Thu Nov 22 22:57:14 2018 daemon.info dnsmasq-dhcp[1323]: DHCPDISCOVER(br-lan) 192.168.88.135 bc:60:a7:bd:b4:a1 Thu Nov 22 22:57:10 2018 user.info com.netdumasoftware.neighwatch: DHCP lease change. Thu Nov 22 22:57:10 2018 user.info com.netdumasoftware.neighwatch: DHCP old event. Thu Nov 22 22:57:10 2018 daemon.info dnsmasq-dhcp[1323]: DHCPACK(br-lan) 192.168.88.135 bc:60:a7:bd:b4:a1 Thu Nov 22 22:57:10 2018 daemon.info dnsmasq-dhcp[1323]: DHCPREQUEST(br-lan) 192.168.88.135 bc:60:a7:bd:b4:a1 Thu Nov 22 22:57:10 2018 daemon.info dnsmasq-dhcp[1323]: DHCPOFFER(br-lan) 192.168.88.135 bc:60:a7:bd:b4:a1 Thu Nov 22 22:57:10 2018 daemon.info dnsmasq-dhcp[1323]: DHCPDISCOVER(br-lan) 192.168.88.135 bc:60:a7:bd:b4:a1 Thu Nov 22 22:57:04 2018 kern.info kernel: [ 7249.796000] recv: nf_ct_get failed Thu Nov 22 22:57:03 2018 kern.info kernel: [ 7249.044000] recv: nf_ct_get failed Thu Nov 22 22:57:02 2018 user.info com.netdumasoftware.neighwatch: DHCP lease change. Thu Nov 22 22:57:02 2018 user.info com.netdumasoftware.neighwatch: DHCP old event. Thu Nov 22 22:57:02 2018 daemon.info dnsmasq-dhcp[1323]: DHCPACK(br-lan) 192.168.88.135 bc:60:a7:bd:b4:a1 Thu Nov 22 22:57:02 2018 daemon.info dnsmasq-dhcp[1323]: DHCPREQUEST(br-lan) 192.168.88.135 bc:60:a7:bd:b4:a1 Thu Nov 22 22:57:02 2018 daemon.info dnsmasq-dhcp[1323]: DHCPOFFER(br-lan) 192.168.88.135 bc:60:a7:bd:b4:a1 Thu Nov 22 22:57:02 2018 daemon.info dnsmasq-dhcp[1323]: DHCPDISCOVER(br-lan) 192.168.88.135 bc:60:a7:bd:b4:a1 Thu Nov 22 22:56:58 2018 user.info com.netdumasoftware.neighwatch: DHCP lease change. Thu Nov 22 22:56:58 2018 user.info com.netdumasoftware.neighwatch: DHCP old event. Thu Nov 22 22:56:58 2018 daemon.info dnsmasq-dhcp[1323]: DHCPACK(br-lan) 192.168.88.135 bc:60:a7:bd:b4:a1 Thu Nov 22 22:56:58 2018 daemon.info dnsmasq-dhcp[1323]: DHCPREQUEST(br-lan) 192.168.88.135 bc:60:a7:bd:b4:a1 Thu Nov 22 22:56:58 2018 daemon.info dnsmasq-dhcp[1323]: DHCPOFFER(br-lan) 192.168.88.135 bc:60:a7:bd:b4:a1 Thu Nov 22 22:56:58 2018 daemon.info dnsmasq-dhcp[1323]: DHCPDISCOVER(br-lan) 192.168.88.135 bc:60:a7:bd:b4:a1 Thu Nov 22 22:56:55 2018 user.info com.netdumasoftware.neighwatch: DHCP lease change. Thu Nov 22 22:56:55 2018 user.info com.netdumasoftware.neighwatch: DHCP old event. Thu Nov 22 22:56:55 2018 daemon.info dnsmasq-dhcp[1323]: DHCPACK(br-lan) 192.168.88.135 bc:60:a7:bd:b4:a1 Thu Nov 22 22:56:55 2018 daemon.info dnsmasq-dhcp[1323]: DHCPREQUEST(br-lan) 192.168.88.135 bc:60:a7:bd:b4:a1 Thu Nov 22 22:56:55 2018 daemon.info dnsmasq-dhcp[1323]: DHCPOFFER(br-lan) 192.168.88.135 bc:60:a7:bd:b4:a1 Thu Nov 22 22:56:55 2018 daemon.info dnsmasq-dhcp[1323]: DHCPDISCOVER(br-lan) 192.168.88.135 bc:60:a7:bd:b4:a1 Thu Nov 22 22:56:48 2018 user.info com.netdumasoftware.neighwatch: DHCP lease change. Thu Nov 22 22:56:48 2018 user.info com.netdumasoftware.neighwatch: DHCP old event. Thu Nov 22 22:56:48 2018 daemon.info dnsmasq-dhcp[1323]: DHCPACK(br-lan) 192.168.88.135 bc:60:a7:bd:b4:a1 Thu Nov 22 22:56:48 2018 daemon.info dnsmasq-dhcp[1323]: DHCPREQUEST(br-lan) 192.168.88.135 bc:60:a7:bd:b4:a1 Thu Nov 22 22:56:48 2018 daemon.info dnsmasq-dhcp[1323]: DHCPOFFER(br-lan) 192.168.88.135 bc:60:a7:bd:b4:a1 Thu Nov 22 22:56:48 2018 daemon.info dnsmasq-dhcp[1323]: DHCPDISCOVER(br-lan) 192.168.88.135 bc:60:a7:bd:b4:a1 Thu Nov 22 22:56:41 2018 user.info com.netdumasoftware.neighwatch: DHCP lease change. Thu Nov 22 22:56:41 2018 user.info com.netdumasoftware.neighwatch: DHCP old event. Thu Nov 22 22:56:41 2018 daemon.info dnsmasq-dhcp[1323]: DHCPACK(br-lan) 192.168.88.135 bc:60:a7:bd:b4:a1 Thu Nov 22 22:56:41 2018 daemon.info dnsmasq-dhcp[1323]: DHCPREQUEST(br-lan) 192.168.88.135 bc:60:a7:bd:b4:a1 Thu Nov 22 22:56:41 2018 daemon.info dnsmasq-dhcp[1323]: DHCPOFFER(br-lan) 192.168.88.135 bc:60:a7:bd:b4:a1 Thu Nov 22 22:56:41 2018 daemon.info dnsmasq-dhcp[1323]: DHCPDISCOVER(br-lan) 192.168.88.135 bc:60:a7:bd:b4:a1 Thu Nov 22 22:56:34 2018 kern.info kernel: [ 7220.160000] recv: nf_ct_get failed Thu Nov 22 22:56:32 2018 user.info com.netdumasoftware.neighwatch: DHCP lease change. Thu Nov 22 22:56:32 2018 user.info com.netdumasoftware.neighwatch: DHCP old event. Thu Nov 22 22:56:32 2018 daemon.info dnsmasq-dhcp[1323]: DHCPACK(br-lan) 192.168.88.135 bc:60:a7:bd:b4:a1 Thu Nov 22 22:56:32 2018 daemon.info dnsmasq-dhcp[1323]: DHCPREQUEST(br-lan) 192.168.88.135 bc:60:a7:bd:b4:a1 Thu Nov 22 22:56:32 2018 daemon.info dnsmasq-dhcp[1323]: DHCPOFFER(br-lan) 192.168.88.135 bc:60:a7:bd:b4:a1 Thu Nov 22 22:56:32 2018 daemon.info dnsmasq-dhcp[1323]: DHCPDISCOVER(br-lan) 192.168.88.135 bc:60:a7:bd:b4:a1 Thu Nov 22 22:56:13 2018 kern.info dpiclass-daemon: Kill flow due to timeout Thu Nov 22 22:56:13 2018 kern.info dpiclass-daemon: Kill flow due to timeout Thu Nov 22 22:56:13 2018 kern.info dpiclass-daemon: Kill flow due to timeout Thu Nov 22 22:56:13 2018 kern.info dpiclass-daemon: Kill flow due to timeout Thu Nov 22 22:56:13 2018 kern.info dpiclass-daemon: Kill flow due to timeout Thu Nov 22 22:56:13 2018 kern.info dpiclass-daemon: Kill flow due to timeout Thu Nov 22 22:56:02 2018 kern.info kernel: [ 7187.620000] recv: nf_ct_get failed Thu Nov 22 22:55:43 2018 kern.info dpiclass-daemon: Kill flow due to timeout Thu Nov 22 22:55:43 2018 kern.info dpiclass-daemon: Kill flow due to timeout Thu Nov 22 22:55:43 2018 kern.info dpiclass-daemon: Kill flow due to timeout Thu Nov 22 22:55:39 2018 kern.info kernel: [ 7165.268000] recv: nf_ct_get failed Thu Nov 22 22:55:38 2018 kern.info kernel: [ 7163.988000] send: nf_ct_get failed Thu Nov 22 22:55:38 2018 kern.info kernel: [ 7163.988000] recv: nf_ct_get failed Thu Nov 22 22:55:22 2018 user.info com.netdumasoftware.neighwatch: DHCP lease change. Thu Nov 22 22:55:22 2018 user.info com.netdumasoftware.neighwatch: DHCP old event. Thu Nov 22 22:55:22 2018 daemon.info dnsmasq-dhcp[1323]: DHCPACK(br-lan) 192.168.88.135 bc:60:a7:bd:b4:a1 Thu Nov 22 22:55:22 2018 daemon.info dnsmasq-dhcp[1323]: DHCPREQUEST(br-lan) 192.168.88.135 bc:60:a7:bd:b4:a1 Thu Nov 22 22:55:22 2018 daemon.info dnsmasq-dhcp[1323]: DHCPOFFER(br-lan) 192.168.88.135 bc:60:a7:bd:b4:a1 Thu Nov 22 22:55:22 2018 daemon.info dnsmasq-dhcp[1323]: DHCPDISCOVER(br-lan) 192.168.88.135 bc:60:a7:bd:b4:a1 Thu Nov 22 22:55:16 2018 user.info com.netdumasoftware.neighwatch: DHCP lease change. Thu Nov 22 22:55:16 2018 user.info com.netdumasoftware.neighwatch: DHCP old event. Thu Nov 22 22:55:16 2018 daemon.info dnsmasq-dhcp[1323]: DHCPACK(br-lan) 192.168.88.135 bc:60:a7:bd:b4:a1 Thu Nov 22 22:55:16 2018 daemon.info dnsmasq-dhcp[1323]: DHCPREQUEST(br-lan) 192.168.88.135 bc:60:a7:bd:b4:a1 Thu Nov 22 22:55:16 2018 daemon.info dnsmasq-dhcp[1323]: DHCPOFFER(br-lan) 192.168.88.135 bc:60:a7:bd:b4:a1 Thu Nov 22 22:55:16 2018 daemon.info dnsmasq-dhcp[1323]: DHCPDISCOVER(br-lan) 192.168.88.135 bc:60:a7:bd:b4:a1 Thu Nov 22 22:54:54 2018 user.info com.netdumasoftware.neighwatch: DHCP lease change. Thu Nov 22 22:54:54 2018 user.info com.netdumasoftware.neighwatch: DHCP old event. Thu Nov 22 22:54:54 2018 daemon.info dnsmasq-dhcp[1323]: DHCPACK(br-lan) 192.168.88.135 bc:60:a7:bd:b4:a1 Thu Nov 22 22:54:54 2018 daemon.info dnsmasq-dhcp[1323]: DHCPREQUEST(br-lan) 192.168.88.135 bc:60:a7:bd:b4:a1 Thu Nov 22 22:54:54 2018 daemon.info dnsmasq-dhcp[1323]: DHCPOFFER(br-lan) 192.168.88.135 bc:60:a7:bd:b4:a1 Thu Nov 22 22:54:54 2018 daemon.info dnsmasq-dhcp[1323]: DHCPDISCOVER(br-lan) 192.168.88.135 bc:60:a7:bd:b4:a1 Thu Nov 22 22:54:48 2018 user.info com.netdumasoftware.neighwatch: DHCP lease change. Thu Nov 22 22:54:48 2018 user.info com.netdumasoftware.neighwatch: DHCP old event. Thu Nov 22 22:54:48 2018 daemon.info dnsmasq-dhcp[1323]: DHCPACK(br-lan) 192.168.88.135 bc:60:a7:bd:b4:a1 Thu Nov 22 22:54:48 2018 daemon.info dnsmasq-dhcp[1323]: DHCPREQUEST(br-lan) 192.168.88.135 bc:60:a7:bd:b4:a1 Thu Nov 22 22:54:48 2018 daemon.info dnsmasq-dhcp[1323]: DHCPOFFER(br-lan) 192.168.88.135 bc:60:a7:bd:b4:a1 Thu Nov 22 22:54:48 2018 daemon.info dnsmasq-dhcp[1323]: DHCPDISCOVER(br-lan) 192.168.88.135 bc:60:a7:bd:b4:a1 Thu Nov 22 22:54:44 2018 user.info com.netdumasoftware.neighwatch: DHCP lease change. Thu Nov 22 22:54:44 2018 user.info com.netdumasoftware.neighwatch: DHCP old event. Thu Nov 22 22:54:44 2018 daemon.info dnsmasq-dhcp[1323]: DHCPACK(br-lan) 192.168.88.135 bc:60:a7:bd:b4:a1 Thu Nov 22 22:54:44 2018 daemon.info dnsmasq-dhcp[1323]: DHCPREQUEST(br-lan) 192.168.88.135 bc:60:a7:bd:b4:a1 Thu Nov 22 22:54:44 2018 daemon.info dnsmasq-dhcp[1323]: DHCPOFFER(br-lan) 192.168.88.135 bc:60:a7:bd:b4:a1 Thu Nov 22 22:54:44 2018 daemon.info dnsmasq-dhcp[1323]: DHCPDISCOVER(br-lan) 192.168.88.135 bc:60:a7:bd:b4:a1 Thu Nov 22 22:54:43 2018 kern.info dpiclass-daemon: Kill flow due to timeout Thu Nov 22 22:54:43 2018 kern.info kernel: [ 7108.872000] recv: nf_ct_get failed Thu Nov 22 22:54:00 2018 kern.info kernel: [ 7065.892000] recv: nf_ct_get failed Thu Nov 22 22:52:42 2018 kern.info kernel: [ 6987.856000] recv: nf_ct_get failed Thu Nov 22 22:52:26 2018 kern.info kernel: [ 6971.676000] recv: nf_ct_get failed Thu Nov 22 22:51:58 2018 daemon.warn odhcpd[736]: Failed to send to ff02::1%br-lan (Operation not permitted) Thu Nov 22 22:51:43 2018 kern.info dpiclass-daemon: Kill flow due to timeout Thu Nov 22 22:51:43 2018 kern.info dpiclass-daemon: Kill flow due to timeout Thu Nov 22 22:51:43 2018 kern.info dpiclass-daemon: Kill flow due to timeout Thu Nov 22 22:51:13 2018 kern.info dpiclass-daemon: Kill flow due to timeout Thu Nov 22 22:51:13 2018 kern.info dpiclass-daemon: Kill flow due to timeout Thu Nov 22 22:51:13 2018 kern.info dpiclass-daemon: Kill flow due to timeout Thu Nov 22 22:51:13 2018 kern.info dpiclass-daemon: Kill flow due to timeout Thu Nov 22 22:51:13 2018 kern.info dpiclass-daemon: Kill flow due to timeout Thu Nov 22 22:51:13 2018 kern.info dpiclass-daemon: Kill flow due to timeout Thu Nov 22 22:51:13 2018 kern.info dpiclass-daemon: Kill flow due to timeout Thu Nov 22 22:51:13 2018 kern.info dpiclass-daemon: Kill flow due to timeout Thu Nov 22 22:51:13 2018 kern.info dpiclass-daemon: Kill flow due to timeout Thu Nov 22 22:51:11 2018 kern.info kernel: [ 6896.748000] recv: nf_ct_get failed Thu Nov 22 22:50:54 2018 kern.info kernel: [ 6880.244000] recv: nf_ct_get failed Thu Nov 22 22:50:43 2018 kern.info dpiclass-daemon: Kill flow due to timeout Thu Nov 22 22:50:43 2018 kern.info dpiclass-daemon: Kill flow due to timeout Thu Nov 22 22:50:38 2018 kern.info kernel: [ 6863.940000] send: nf_ct_get failed Thu Nov 22 22:50:38 2018 kern.info kernel: [ 6863.940000] recv: nf_ct_get failed Thu Nov 22 22:50:20 2018 kern.info kernel: [ 6846.372000] send: nf_ct_get failed Thu Nov 22 22:50:20 2018 kern.info kernel: [ 6846.372000] recv: nf_ct_get failed Thu Nov 22 22:48:30 2018 kern.info kernel: [ 6736.424000] recv: nf_ct_get failed Thu Nov 22 22:48:30 2018 kern.info kernel: [ 6735.864000] recv: nf_ct_get failed Thu Nov 22 22:48:28 2018 kern.info kernel: [ 6733.564000] recv: nf_ct_get failed Thu Nov 22 22:48:13 2018 kern.info dpiclass-daemon: Kill flow due to timeout Thu Nov 22 22:47:13 2018 kern.info dpiclass-daemon: Kill flow due to timeout Thu Nov 22 22:47:13 2018 kern.info dpiclass-daemon: Kill flow due to timeout Thu Nov 22 22:47:13 2018 kern.info dpiclass-daemon: Kill flow due to timeout Thu Nov 22 22:47:13 2018 kern.info dpiclass-daemon: Kill flow due to timeout Thu Nov 22 22:47:13 2018 kern.info dpiclass-daemon: Kill flow due to timeout Thu Nov 22 22:47:13 2018 kern.info dpiclass-daemon: Kill flow due to timeout Thu Nov 22 22:46:43 2018 kern.info dpiclass-daemon: Kill flow due to timeout Thu Nov 22 22:46:43 2018 kern.info dpiclass-daemon: Kill flow due to timeout Thu Nov 22 22:46:43 2018 kern.info dpiclass-daemon: Kill flow due to timeout Thu Nov 22 22:46:43 2018 kern.info dpiclass-daemon: Kill flow due to timeout Thu Nov 22 22:46:43 2018 kern.info dpiclass-daemon: Kill flow due to timeout Thu Nov 22 22:46:43 2018 kern.info dpiclass-daemon: Kill flow due to timeout Thu Nov 22 22:46:29 2018 kern.info kernel: [ 6615.180000] recv: nf_ct_get failed Thu Nov 22 22:46:21 2018 daemon.warn odhcpd[736]: Failed to send to ff02::1%br-lan (Operation not permitted) Thu Nov 22 22:46:13 2018 kern.info dpiclass-daemon: Kill flow due to timeout Thu Nov 22 22:46:13 2018 kern.info dpiclass-daemon: Kill flow due to timeout Thu Nov 22 22:45:43 2018 kern.info dpiclass-daemon: Kill flow due to timeout Thu Nov 22 22:45:38 2018 kern.info kernel: [ 6563.924000] send: nf_ct_get failed Thu Nov 22 22:45:38 2018 kern.info kernel: [ 6563.924000] recv: nf_ct_get failed Thu Nov 22 22:45:17 2018 kern.info kernel: [ 6542.792000] recv: nf_ct_get failed Thu Nov 22 22:45:13 2018 kern.info dpiclass-daemon: Kill flow due to timeout Thu Nov 22 22:44:45 2018 kern.info kernel: [ 6510.528000] send: nf_ct_get failed Thu Nov 22 22:44:45 2018 kern.info kernel: [ 6510.528000] recv: nf_ct_get failed Thu Nov 22 22:44:43 2018 kern.info dpiclass-daemon: Kill flow due to timeout Thu Nov 22 22:44:43 2018 kern.info dpiclass-daemon: Kill flow due to timeout Thu Nov 22 22:44:43 2018 kern.info dpiclass-daemon: Kill flow due to timeout Thu Nov 22 22:44:43 2018 kern.info dpiclass-daemon: Kill flow due to timeout Thu Nov 22 22:44:22 2018 kern.info kernel: [ 6488.176000] recv: nf_ct_get failed Thu Nov 22 22:44:20 2018 kern.info kernel: [ 6486.308000] recv: nf_ct_get failed Thu Nov 22 22:43:57 2018 user.info com.netdumasoftware.neighwatch: DHCP lease change. Thu Nov 22 22:43:57 2018 user.info com.netdumasoftware.neighwatch: DHCP old event. Thu Nov 22 22:43:57 2018 daemon.info dnsmasq-dhcp[1323]: DHCPACK(br-lan) 192.168.88.135 bc:60:a7:bd:b4:a1 Thu Nov 22 22:43:57 2018 daemon.info dnsmasq-dhcp[1323]: DHCPREQUEST(br-lan) 192.168.88.135 bc:60:a7:bd:b4:a1 Thu Nov 22 22:43:57 2018 daemon.info dnsmasq-dhcp[1323]: DHCPOFFER(br-lan) 192.168.88.135 bc:60:a7:bd:b4:a1 Thu Nov 22 22:43:57 2018 daemon.info dnsmasq-dhcp[1323]: DHCPDISCOVER(br-lan) 192.168.88.135 bc:60:a7:bd:b4:a1 Thu Nov 22 22:43:50 2018 user.info com.netdumasoftware.neighwatch: DHCP lease change. Thu Nov 22 22:43:50 2018 user.info com.netdumasoftware.neighwatch: DHCP old event. Thu Nov 22 22:43:50 2018 daemon.info dnsmasq-dhcp[1323]: DHCPACK(br-lan) 192.168.88.135 bc:60:a7:bd:b4:a1 Thu Nov 22 22:43:50 2018 daemon.info dnsmasq-dhcp[1323]: DHCPREQUEST(br-lan) 192.168.88.135 bc:60:a7:bd:b4:a1 Thu Nov 22 22:43:50 2018 daemon.info dnsmasq-dhcp[1323]: DHCPOFFER(br-lan) 192.168.88.135 bc:60:a7:bd:b4:a1 Thu Nov 22 22:43:50 2018 daemon.info dnsmasq-dhcp[1323]: DHCPDISCOVER(br-lan) 192.168.88.135 bc:60:a7:bd:b4:a1 Thu Nov 22 22:43:43 2018 kern.info dpiclass-daemon: Kill flow due to timeout Thu Nov 22 22:43:43 2018 kern.info dpiclass-daemon: Kill flow due to timeout Thu Nov 22 22:43:13 2018 kern.info dpiclass-daemon: Kill flow due to timeout Thu Nov 22 22:43:13 2018 kern.info dpiclass-daemon: Kill flow due to timeout Thu Nov 22 22:43:13 2018 kern.info dpiclass-daemon: Kill flow due to timeout Thu Nov 22 22:43:13 2018 kern.info dpiclass-daemon: Kill flow due to timeout Thu Nov 22 22:42:43 2018 kern.info dpiclass-daemon: Kill flow due to timeout Thu Nov 22 22:42:43 2018 kern.info dpiclass-daemon: Kill flow due to timeout Thu Nov 22 22:42:43 2018 kern.info dpiclass-daemon: Kill flow due to timeout Thu Nov 22 22:42:43 2018 kern.info dpiclass-daemon: Kill flow due to timeout Thu Nov 22 22:42:25 2018 kern.info kernel: [ 6370.504000] send: nf_ct_get failed Thu Nov 22 22:42:25 2018 kern.info kernel: [ 6370.504000] recv: nf_ct_get failed Thu Nov 22 22:42:13 2018 kern.info dpiclass-daemon: Kill flow due to timeout Thu Nov 22 22:41:55 2018 kern.info kernel: [ 6341.384000] recv: nf_ct_get failed Thu Nov 22 22:41:41 2018 kern.info kernel: [ 6326.888000] recv: nf_ct_get failed Thu Nov 22 22:41:37 2018 kern.info kernel: [ 6323.368000] send: nf_ct_get failed Thu Nov 22 22:41:37 2018 kern.info kernel: [ 6323.368000] recv: nf_ct_get failed Thu Nov 22 22:41:37 2018 kern.info kernel: [ 6323.360000] send: nf_ct_get failed Thu Nov 22 22:41:37 2018 kern.info kernel: [ 6323.360000] recv: nf_ct_get failed Thu Nov 22 22:41:35 2018 kern.info kernel: [ 6321.300000] send: nf_ct_get failed Thu Nov 22 22:41:35 2018 kern.info kernel: [ 6321.300000] recv: nf_ct_get failed Thu Nov 22 22:41:35 2018 user.info com.netdumasoftware.neighwatch: DHCP lease change. Thu Nov 22 22:41:35 2018 user.info com.netdumasoftware.neighwatch: DHCP old event. Thu Nov 22 22:41:35 2018 daemon.info dnsmasq-dhcp[1323]: DHCPACK(br-lan) 192.168.88.135 bc:60:a7:bd:b4:a1 Thu Nov 22 22:41:35 2018 daemon.info dnsmasq-dhcp[1323]: DHCPREQUEST(br-lan) 192.168.88.135 bc:60:a7:bd:b4:a1 Thu Nov 22 22:41:35 2018 daemon.info dnsmasq-dhcp[1323]: DHCPOFFER(br-lan) 192.168.88.135 bc:60:a7:bd:b4:a1 Thu Nov 22 22:41:35 2018 daemon.info dnsmasq-dhcp[1323]: DHCPDISCOVER(br-lan) 192.168.88.135 bc:60:a7:bd:b4:a1 Thu Nov 22 22:41:13 2018 kern.info dpiclass-daemon: Kill flow due to timeout Thu Nov 22 22:41:13 2018 kern.info kernel: [ 6298.864000] send: nf_ct_get failed Thu Nov 22 22:41:13 2018 kern.info kernel: [ 6298.864000] recv: nf_ct_get failed Thu Nov 22 22:40:40 2018 kern.info kernel: [ 6266.408000] send: nf_ct_get failed Thu Nov 22 22:40:40 2018 kern.info kernel: [ 6266.408000] recv: nf_ct_get failed Thu Nov 22 22:40:38 2018 kern.info kernel: [ 6263.916000] send: nf_ct_get failed Thu Nov 22 22:40:38 2018 kern.info kernel: [ 6263.916000] recv: nf_ct_get failed Thu Nov 22 22:40:09 2018 daemon.warn odhcpd[736]: Failed to send to ff02::1%br-lan (Operation not permitted) Thu Nov 22 22:40:08 2018 kern.info kernel: [ 6233.952000] send: nf_ct_get failed Thu Nov 22 22:40:08 2018 kern.info kernel: [ 6233.952000] recv: nf_ct_get failed Thu Nov 22 22:39:56 2018 kern.info kernel: [ 6221.760000] send: nf_ct_get failed Thu Nov 22 22:39:56 2018 kern.info kernel: [ 6221.760000] recv: nf_ct_get failed Thu Nov 22 22:39:40 2018 kern.info kernel: [ 6205.688000] send: nf_ct_get failed Thu Nov 22 22:39:40 2018 kern.info kernel: [ 6205.688000] recv: nf_ct_get failed Thu Nov 22 22:39:36 2018 kern.info kernel: [ 6201.496000] send: nf_ct_get failed Thu Nov 22 22:39:36 2018 kern.info kernel: [ 6201.496000] recv: nf_ct_get failed

 

SFV PS4 LAN Cable Not Connected 002.jpg

Share this post


Link to post
Share on other sites
On 11/22/2018 at 6:54 PM, Netduma Fraser said:

Thanks, I've let the devs know you've updated with new logs. Might be hard of them to read like that though, if you could download the log instead from the log menu and upload the file that'd probably be better

I got another log with the  LAN cable not connected and I downloaded the log file. It's also hard to read when you open the .txt but I upload the file in the attachment.

log-1543024462840.txt

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×