Wifi - logging brief connection

Jul 18, 2020 32 Replies

You are wrong, it does

The log screen shows the following information:? Date and time. The date and time the log entry was recorded.? Source IP. The IP address of the initiating device for this log entry.? Target address. The name or IP address of the website or news group visited or to which access was attempted.? Action. Whether the access was blocked or allowed.To refresh the log screen, click the Refresh button.To clear the log entries, click the Clear Log button.To email the log immediately, click the Send Log button.

It finally went into the ferment vessel at 19:33 yesterday evening, after I at last saw it had produced data on the website.

It is normal for the SG to initially rise gradually up some way during the first day, before the fermentation proper gets under way. The line becomes jagged as I shake the vessel up, as happened at 21:14.

BT Infinity Smart Hubs are pretty well black box.

As does any running linux box you have root access to.

With it's NIC in promiscuous mode it just needs to be on the same subnet.

Is it a freemium service and that's the kicker to get you to pay?

Piece of piss then :-)

SSH onto the router, decide which interface to monitor (either your DSL interface [maybe pppoe-WAN1] or the bridge interface between your wired and wifi segments [br-lan])

Presumably you know where the widget is configured to send its data? if so, lookup that destination ip, otherwise use the widget's source ip addr

tcpdump -i INTERFACE host SRC-OR-DEST-IP

e.g.

tcpdump -i br-lan host 50.23.124.68

check with a ping that the packet filter is working, then wait for the widget to do its stuff ...

Andy Burns expressed precisely :

Yes, not worth paying for a service I rarely make use of..

Not that easy for wifi, and with switches rather than hubs, not that easy on wired unless you can configure a mirror port, or as Dave says some other form of ethernet tap ...

That was my thought, but some WiFi adaptors don't work in promiscuous mode and only show packets that match the machine's IP address.

With it working perhaps now's the time to now check and setup the right filter to see just the packets from the gadget.

Another approach would be to set the DHCP lease to a very short value such as 5 minutes in the router. Then look at the DHCP table which you almost certainly have access to and see if it appears regularly. That will at least show that the device is talking to the network.

John

What log screen? How do you get to it?

Join the Discussion

Have something to add? Share your thoughts — no account required.

Didn't find your answer?

Ask the community — no account required