From: Michael Tremer <michael.tremer@ipfire.org>
To: sig-arm@lists.ipfire.org
Subject: Re: net-tools
Date: Fri, 22 Feb 2013 12:51:21 +0100 [thread overview]
Message-ID: <1361533881.28061.303.camel@rice-oxley.tremer.info> (raw)
In-Reply-To: <51273382.7010301@gmx.de>
[-- Attachment #1: Type: text/plain, Size: 5983 bytes --]
Hi Thomas,
yes I can see why this is happening. IPFire 2 mainly has IPv6 disabled
so there is no need to show those protocols.
In IPFire 3, we have ported a lot of additional patches from Fedora that
provide things like IPv6 support:
http://git.ipfire.org/?p=ipfire-3.x.git;a=tree;f=net-tools;h=415379b8e22ba68b1609c49c94040010273aceb2;hb=HEAD
What's the motivation behind this? Are you playing around with IPv6?
-Michael
On Fri, 2013-02-22 at 09:59 +0100, Thomas Ebert wrote:
> The netstat command under the arm-Platform is somehow buggy, because it
> doesn't implement a tcp6 output and therefore i didn't see all used ports.
>
> Here are the output of the original command from the original package:
> Proto Recv-Q Send-Q Local Address Foreign Address State
> PID/Program name
> tcp 0 0 0.0.0.0:42592 0.0.0.0:* LISTEN -
> tcp 0 0 0.0.0.0:993 0.0.0.0:* LISTEN
> 3411/master
> tcp 0 0 0.0.0.0:995 0.0.0.0:* LISTEN
> 3411/master
> tcp 0 0 127.0.0.1:3306 0.0.0.0:* LISTEN
> 3432/mysqld
> tcp 0 0 0.0.0.0:1194 0.0.0.0:* LISTEN
> 2946/openvpn
> tcp 0 0 192.168.11.5:139 0.0.0.0:* LISTEN 3462/smbd
> tcp 0 0 127.0.0.1:139 0.0.0.0:* LISTEN 3462/smbd
> tcp 0 0 0.0.0.0:110 0.0.0.0:* LISTEN
> 3411/master
> tcp 0 0 0.0.0.0:143 0.0.0.0:* LISTEN
> 3411/master
> tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN
> 3085/portmap
> tcp 0 0 0.0.0.0:43602 0.0.0.0:* LISTEN
> 3121/rpc.statd
> tcp 0 0 0.0.0.0:53 0.0.0.0:* LISTEN
> 2387/dnsmasq
> tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 3257/sshd
> tcp 0 0 0.0.0.0:631 0.0.0.0:* LISTEN 3140/cupsd
> tcp 0 0 0.0.0.0:45756 0.0.0.0:* LISTEN
> 3108/rpc.mountd
> tcp 0 0 192.168.11.5:445 0.0.0.0:* LISTEN 3462/smbd
> tcp 0 0 127.0.0.1:445 0.0.0.0:* LISTEN 3462/smbd
> tcp 0 0 192.168.11.5:705 192.168.11.3:2049 ESTABLISHED -
> tcp 0 148 192.168.11.5:22 192.168.11.13:57738
> ESTABLISHED 18509/0
>
> That is the output of the version i've self compiled:
> tcp 0 0 0.0.0.0:42592 0.0.0.0:* LISTEN -
> tcp 0 0 0.0.0.0:993 0.0.0.0:* LISTEN
> 3411/master
> tcp 0 0 0.0.0.0:995 0.0.0.0:* LISTEN
> 3411/master
> tcp 0 0 127.0.0.1:3306 0.0.0.0:* LISTEN
> 3432/mysqld
> tcp 0 0 0.0.0.0:1194 0.0.0.0:* LISTEN
> 2946/openvpn
> tcp 0 0 192.168.11.5:139 0.0.0.0:* LISTEN 3462/smbd
> tcp 0 0 127.0.0.1:139 0.0.0.0:* LISTEN 3462/smbd
> tcp 0 0 0.0.0.0:110 0.0.0.0:* LISTEN
> 3411/master
> tcp 0 0 0.0.0.0:143 0.0.0.0:* LISTEN
> 3411/master
> tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN
> 3085/portmap
> tcp 0 0 0.0.0.0:43602 0.0.0.0:* LISTEN
> 3121/rpc.statd
> tcp 0 0 0.0.0.0:53 0.0.0.0:* LISTEN
> 2387/dnsmasq
> tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 3257/sshd
> tcp 0 0 0.0.0.0:631 0.0.0.0:* LISTEN 3140/cupsd
> tcp 0 0 0.0.0.0:45756 0.0.0.0:* LISTEN
> 3108/rpc.mountd
> tcp 0 0 192.168.11.5:445 0.0.0.0:* LISTEN 3462/smbd
> tcp 0 0 127.0.0.1:445 0.0.0.0:* LISTEN 3462/smbd
> tcp 0 0 192.168.11.5:705 192.168.11.3:2049 ESTABLISHED -
> tcp 0 0 192.168.11.5:22 192.168.11.13:57738
> ESTABLISHED 18509/sshd: root(a)pt
> tcp6 0 0 :::993 :::* LISTEN 3411/master
> tcp6 0 0 :::995 :::* LISTEN 3411/master
> tcp6 0 0 :::1001 :::* LISTEN 7816/httpd
> tcp6 0 0 :::110 :::* LISTEN 3411/master
> tcp6 0 0 :::143 :::* LISTEN 3411/master
> tcp6 0 0 :::81 :::* LISTEN 7816/httpd
> tcp6 0 0 :::22 :::* LISTEN 3257/sshd
> tcp6 0 0 :::631 :::* LISTEN 3140/cupsd
> tcp6 0 0 :::444 :::* LISTEN 7816/httpd
>
> The Problem occurs under IPFire 2.11 and 2.13.
>
> Here is the output of a test installation IPFire 2.13 i586:
> Active Internet connections (servers and established)
> Proto Recv-Q Send-Q Local Address Foreign Address State
> PID/Program name
> tcp 0 0 0.0.0.0:81 0.0.0.0:* LISTEN 4108/httpd
> tcp 0 0 0.0.0.0:53 0.0.0.0:* LISTEN
> 3623/dnsmasq
> tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 4088/sshd
> tcp 0 0 0.0.0.0:444 0.0.0.0:* LISTEN 4108/httpd
> tcp 0 300 192.168.11.41:22 192.168.11.13:57750
> ESTABLISHED 10723/0
>
> You see that the process "httpd" doesn't show in the original netstat
> command of a default arm installation (kirkwood or dove).
>
> The sourcecode i've taken to test compile is taken from the gentoo git
> repository
> git://git.overlays.gentoo.org/proj/net-tools.git
>
> No more additional patches are made, i've taken the above code.
>
> Can anybody check this on his arm-Platform
> _______________________________________________
> SIG-ARM mailing list
> SIG-ARM(a)lists.ipfire.org
> http://lists.ipfire.org/mailman/listinfo/sig-arm
next prev parent reply other threads:[~2013-02-22 11:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-22 8:59 net-tools Thomas Ebert
2013-02-22 11:51 ` Michael Tremer [this message]
[not found] <512773E2.8000902@gmx.de>
2013-02-22 16:06 ` net-tools Michael Tremer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1361533881.28061.303.camel@rice-oxley.tremer.info \
--to=michael.tremer@ipfire.org \
--cc=sig-arm@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox