Free Geek often has some of the older dual-band netgear routers for cheap.
Do some research on the model number, since most of them are very
compatible with openwrt.
Once you flash the router with openwrt, you can enable the features that
stock firmware doesn't provide. Several years ago I bought
Yes that is what g: is aimed at. But for some reason the program does not
see
it.
On Sun, Jun 10, 2018 at 11:20 PM, Larry Brigman
wrote:
> More likely to sdb.
>
> On Sun, Jun 10, 2018 at 9:01 PM Chuck Hast wrote:
>
> > On closer inspection I see that both of these are removed when the device
>
More likely to sdb.
On Sun, Jun 10, 2018 at 9:01 PM Chuck Hast wrote:
> On closer inspection I see that both of these are removed when the device
> is
> disconnected:
> Jun 9 23:18:50 kp4djt-t420 kernel: [ 1136.185219] sd 9:0:0:0: Attached
> scsi generic sg2 type 0
> Jun 9 23:18:50
Well, I looked at the listed dosdevices turns out g: is linked to sdb. BUT
it
complains that it cannot find the correct device driver. The program in
question
has no info on what it is aimed at. FYI it is the programming tool for a
radio
ConnectSystems CS800D.
I wonder if it is a permissions
Chee, I missed that one... Well now to give it a try, but I am getting too
sleepy,
so better wait until tomorrow.
On Sun, Jun 10, 2018 at 9:08 PM, Russell Senior
wrote:
> dmesg says /dev/sdb
>
> df or mount will only show it if it has been mounted.
>
> On Sun, Jun 10, 2018 at 6:20 PM, Chuck
It used to be a real problem on public networks, because the bit torrent
clients were pretty aggressive about congesting upstream links. There's a
name for the phenomenon: buffer bloat: basically, filling too-large queues
at a bandwidth choke point resulting in ugly latencies. For a number of
Not one someone else's network, they don't :)
-wes
On Sun, Jun 10, 2018 at 9:15 AM, Thomas Groman
wrote:
> On Sat, 9 Jun 2018 23:10:04 -0700
> Russell Senior wrote:
>
> > Our Personal Telco firmware (based on OpenWrt/LEDE) has a dumb
> > bittorrent blocker, and we include iftop and tcpdump as
dmesg says /dev/sdb
df or mount will only show it if it has been mounted.
On Sun, Jun 10, 2018 at 6:20 PM, Chuck Hast wrote:
> That was the second option after looking in /dev. I figured it would show
> up in
> one of those places but no joy.
> Here is what I see from the df command
>
>
That was the second option after looking in /dev. I figured it would show
up in
one of those places but no joy.
Here is what I see from the df command
Pre-USB connection:
kp4djt@kp4djt-t420:/dev$ df
Filesystem 1K-blocks Used Available Use% Mounted on
udev 3952548 0
The it will be a drive letter in dosdevices. Do a df and see where it is
mounted. In a Fedora Distribution, it should be mounted in
/run/media//.
Link that to a drive letter in dosdevices.
Ken
On Sun, Jun 10, 2018 at 11:18 AM Chuck Hast wrote:
> Ken,
> The first thing I did was look in /dev
Ken,
The first thing I did was look in /dev to see if it was there but no joy. I
see the
device appear on my desktop as a ST MicroSD Flash, but I cannot find where
to setup a link to the thing.
On Sun, Jun 10, 2018 at 11:02 AM, Ken Stephens
wrote:
> Chuck,
>
> You need to add a link to it in
On Sun, 10 Jun 2018, Rich Shepard wrote:
KLOGD_OPTIONS="-c 3 -x -m 0"
with the just added '-m 0'.
Well, syslog (on my 14.2 installation) does not accept the -m option when
I restart it. Interesting.
Rich
___
PLUG mailing list
PLUG@pdxlinux.org
On Sun, 10 Jun 2018, Bob Vinisky wrote:
I believe the option has changed since I last did this. In
/etc/rc.d/rc.syslog, near the top of the settings, isn option
SYSLOGD_OPTIONS=“-c “. By adding the syslog switch “-m 0” it should go
away (e.g. SYSLOGD_OPTIONS=“-c -m 0“). See man syslog.
Bob,
On Sat, 9 Jun 2018 23:10:04 -0700
Russell Senior wrote:
> Our Personal Telco firmware (based on OpenWrt/LEDE) has a dumb
> bittorrent blocker, and we include iftop and tcpdump as management
> tools. If you know someone is doing something they shouldn't be, it
> isn't very difficult to figure
Hi Rich,
> On Jun 10, 2018, at 8:04 AM, Rich Shepard wrote:
>
> When I view /var/log/messages I see an entry every half-hour when I'm
> logged into the system:
>
> Jun 10 05:47:56 salmo -- MARK --
> Jun 10 06:07:56 salmo -- MARK --
> Jun 10 06:27:56 salmo -- MARK --
> Jun 10 06:47:56 salmo --
On Sun, 10 Jun 2018, Paul Heinlein wrote:
In /etc/rsyslog.conf, you'll see an entry something like this:
$ModLoad immark
Just comment it out if your want the MARK entries to go away. It's
otherwise just a way to verify that your syslog log system is working even
when there isn't anything to
On Sun, 10 Jun 2018, Rich Shepard wrote:
When I view /var/log/messages I see an entry every half-hour when I'm
logged into the system:
Jun 10 05:47:56 salmo -- MARK --
Jun 10 06:07:56 salmo -- MARK --
Jun 10 06:27:56 salmo -- MARK --
Jun 10 06:47:56 salmo -- MARK --
Jun 10 07:07:56 salmo --
When I view /var/log/messages I see an entry every half-hour when I'm
logged into the system:
Jun 10 05:47:56 salmo -- MARK --
Jun 10 06:07:56 salmo -- MARK --
Jun 10 06:27:56 salmo -- MARK --
Jun 10 06:47:56 salmo -- MARK --
Jun 10 07:07:56 salmo -- MARK --
Jun 10 07:27:56 salmo -- MARK --
Our Personal Telco firmware (based on OpenWrt/LEDE) has a dumb bittorrent
blocker, and we include iftop and tcpdump as management tools. If you know
someone is doing something they shouldn't be, it isn't very difficult to
figure out which client is responsible, and then you can black-hole them
19 matches
Mail list logo
