Discussion:
[OpenWrt-Users] conntrack-tools for 17.01 (MIPS24k)
Stefan Monnier
2018-04-22 15:44:45 UTC
Permalink
I'd like to delete some conntrack entries from a script, so I was
looking to install conntrack-tools. But I can't seem to find this
package.

https://openwrt.org/releases/17.01/changelog-17.01.0

says that conntrack-tools was updated to 1.4.4, which strongly suggests
that conntrack-tools is packaged for OpenWRT, yet "opkg list" on my
router doesn't show that package.

Any idea what's going on and where/how I could find&install it?

Alternatively, I could use `tcpkill` but this one does not seem to be
packaged for OpenWRT.


Stefan
Damiano Verzulli
2018-04-22 16:43:20 UTC
Permalink
Post by Stefan Monnier
I'd like to delete some conntrack entries from a script, so I was
looking to install conntrack-tools. But I can't seem to find this
package.
Even tough I'm using a "snapshot" release (so, a different release than
yours), I bet your problem is simply "naming": in my system your package is
"conntrack" and not "conntrack-tools":

=================================
***@WRT:/tmp# opkg update
[...]
***@WRT:/tmp# opkg info conntrack
Package: conntrack
Version: 2017-09-27-eefe649c-1
Depends: libc, libnetfilter-conntrack, libnetfilter-cttimeout,
libnetfilter-cthelper, libnetfilter-queue
Status: unknown ok not-installed
Section: net
Architecture: mips_24kc
Size: 18954
Filename: conntrack_2017-09-27-eefe649c-1_mips_24kc.ipk
Description: Conntrack is a userspace command line program targeted at system
administrators. It enables them to view and manage the in-kernel
connection tracking state table.
======================================

And inside the "conntrack" package that I downloaded [1] I found the binary
you're looking for:

-------------
-rwxr-xr-x 0/0 47264 2018-04-21 17:09 ./usr/sbin/conntrack
-------------

HTH.

Bye,
DV


[1] this:
http://downloads.lede-project.org/snapshots/packages/mips_24kc/base/conntrack_2017-09-27-eefe649c-1_mips_24kc.ipk
But please note that your package is in a DIFFERENT location as, again, I'm
under "snapshot".
--
Damiano Verzulli
e-mail: ***@verzulli.it
---
possible?ok:while(!possible){open_mindedness++}
---
"Technical people tend to fall into two categories: Specialists
and Generalists. The Specialist learns more and more about a
narrower and narrower field, until he eventually, in the limit,
knows everything about nothing. The Generalist learns less and
less about a wider and wider field, until eventually he knows
nothing about everything." - William Stucke - AfrISPA
http://elists.isoc.org/mailman/private/pubsoft/2007-December/001935.html
Stefan Monnier
2018-04-24 13:02:49 UTC
Permalink
Post by Damiano Verzulli
Post by Stefan Monnier
I'd like to delete some conntrack entries from a script, so I was
looking to install conntrack-tools. But I can't seem to find this
package.
Even tough I'm using a "snapshot" release (so, a different release than
yours), I bet your problem is simply "naming": in my system your package is
Hmm... no I don't have that either:

# opkg info conntrack
# opkg install conntrack
Unknown package 'conntrack'.
Collected errors:
* opkg_install_cmd: Cannot install package conntrack.
# opkg list | grep conntrack
iptables-mod-conntrack-extra - 1.4.21-3
kmod-ipt-conntrack - 4.4.92-1
kmod-ipt-conntrack-extra - 4.4.92-1
kmod-nf-conntrack - 4.4.92-1
kmod-nf-conntrack6 - 4.4.92-1
# cat /etc/opkg/distfeeds.conf
src/gz reboot_core http://downloads.lede-project.org/releases/17.01.4/targets/lantiq/xrx200/packages
src/gz reboot_base http://downloads.lede-project.org/releases/17.01.4/packages/mips_24kc/base
src/gz reboot_luci http://downloads.lede-project.org/releases/17.01.4/packages/mips_24kc/luci
src/gz reboot_packages http://downloads.lede-project.org/releases/17.01.4/packages/mips_24kc/packages
src/gz reboot_routing http://downloads.lede-project.org/releases/17.01.4/packages/mips_24kc/routing
src/gz reboot_telephony http://downloads.lede-project.org/releases/17.01.4/packages/mips_24kc/telephony
#

Do I need another `feed` for that?


Stefan
Milan P. Stanic
2018-04-24 15:09:48 UTC
Permalink
Post by Damiano Verzulli
Post by Damiano Verzulli
Post by Stefan Monnier
I'd like to delete some conntrack entries from a script, so I was
looking to install conntrack-tools. But I can't seem to find this
package.
Even tough I'm using a "snapshot" release (so, a different release than
yours), I bet your problem is simply "naming": in my system your package is
# opkg info conntrack
# opkg install conntrack
Unknown package 'conntrack'.
* opkg_install_cmd: Cannot install package conntrack.
# opkg list | grep conntrack
iptables-mod-conntrack-extra - 1.4.21-3
kmod-ipt-conntrack - 4.4.92-1
kmod-ipt-conntrack-extra - 4.4.92-1
kmod-nf-conntrack - 4.4.92-1
kmod-nf-conntrack6 - 4.4.92-1
# cat /etc/opkg/distfeeds.conf
src/gz reboot_core http://downloads.lede-project.org/releases/17.01.4/targets/lantiq/xrx200/packages
src/gz reboot_base http://downloads.lede-project.org/releases/17.01.4/packages/mips_24kc/base
src/gz reboot_luci http://downloads.lede-project.org/releases/17.01.4/packages/mips_24kc/luci
src/gz reboot_packages http://downloads.lede-project.org/releases/17.01.4/packages/mips_24kc/packages
src/gz reboot_routing http://downloads.lede-project.org/releases/17.01.4/packages/mips_24kc/routing
src/gz reboot_telephony http://downloads.lede-project.org/releases/17.01.4/packages/mips_24kc/telephony
#
Do I need another `feed` for that?
Try 'opkg update' first then 'opkg find conntrack'
Stefan Monnier
2018-04-24 22:22:47 UTC
Permalink
Post by Milan P. Stanic
Try 'opkg update' first then 'opkg find conntrack'
Duh!

Hmm... I had done that, tho a while ago. Was so sure I didn't need to
do it again. I know this data is flushed upon reboot, but is it also
flushed at other times (I could swear that I haven't rebooted since the
last time I had done "opkg update")?

In any case, thank you for stating the obvious that I had missed,


Stefan
Damiano Verzulli
2018-04-25 11:13:14 UTC
Permalink
Post by Stefan Monnier
Was so sure I didn't need to
do it again. I know this data is flushed upon reboot, but is it also
flushed at other times (I could swear that I haven't rebooted since the
last time I had done "opkg update")?
Three things come to my mind:

1 - I learnt that "uptime" is much more trustable than my mind, when
needing to take decisions based on "reboot-time" of my
little-devices-OpenWRT-based :-)

2 - I'm wondering --right now-- why "opkg update" is _NOT_
reboot-persistent. I mean:
- is having _OLD_ package indexes WORSE than not having them at all?";
- are package indexes kept in memory? Why aren't they flushed on the
file-system?

What am I missing, here?

3 - It would be nice --as a new feature of the "opkg" client tool-- to
raise an alert when package indexes is too-old or, worse, is completely
missing. I for myself, a couple of years ago, spent much time exactly
missing this requirement ("opkg update"). It was such a bad-feeling that
since then, _EVERY_ time I need to install something, I _ALWAYS_ prefix an
"opkg update" :-)

Cheers,
DV
Post by Stefan Monnier
Post by Milan P. Stanic
Try 'opkg update' first then 'opkg find conntrack'
In any case, thank you for stating the obvious that I had missed,
you're welcome :-)
--
Damiano Verzulli
e-mail: ***@verzulli.it
---
possible?ok:while(!possible){open_mindedness++}
---
"Technical people tend to fall into two categories: Specialists
and Generalists. The Specialist learns more and more about a
narrower and narrower field, until he eventually, in the limit,
knows everything about nothing. The Generalist learns less and
less about a wider and wider field, until eventually he knows
nothing about everything." - William Stucke - AfrISPA
http://elists.isoc.org/mailman/private/pubsoft/2007-December/001935.html
Milan P. Stanic
2018-04-25 12:04:46 UTC
Permalink
Post by Damiano Verzulli
Post by Stefan Monnier
Was so sure I didn't need to
do it again. I know this data is flushed upon reboot, but is it also
flushed at other times (I could swear that I haven't rebooted since the
last time I had done "opkg update")?
1 - I learnt that "uptime" is much more trustable than my mind, when
needing to take decisions based on "reboot-time" of my
little-devices-OpenWRT-based :-)
2 - I'm wondering --right now-- why "opkg update" is _NOT_
To save space on devices, which is usually scarce on the storage.
Post by Damiano Verzulli
- is having _OLD_ package indexes WORSE than not having them at all?";
- are package indexes kept in memory? Why aren't they flushed on the
file-system?
What am I missing, here?
3 - It would be nice --as a new feature of the "opkg" client tool-- to
raise an alert when package indexes is too-old or, worse, is completely
missing. I for myself, a couple of years ago, spent much time exactly
missing this requirement ("opkg update"). It was such a bad-feeling that
since then, _EVERY_ time I need to install something, I _ALWAYS_ prefix an
"opkg update" :-)
It could be set by editing /etc/opkg.conf and set some directive. I
forgot exact syntax, because some years passed when I did that, but I
think it could be 'lists_dir', to point to somewhere in the permanent
storage with enough free space.
By default it points to /var but the /var is symlink to /tmp which is
tmpfs.

Loading...