On 1/30/2025 12:02 PM, Gleb Smirnoff wrote:
On Sun, Jan 26, 2025 at 04:58:57PM +0100, Alexander Leidinger wrote:
A> something has changed in the output of "netstat -rn" between
A> 2024-11-23-195545 and 2025-01-22-151306. The default route is not listed as
A> "default&quo
On Sun, Jan 26, 2025 at 04:58:57PM +0100, Alexander Leidinger wrote:
A> something has changed in the output of "netstat -rn" between
A> 2024-11-23-195545 and 2025-01-22-151306. The default route is not listed as
A> "default" anymore, but with "0.0.0.0" resp.
ionales in favor
of "-nn".
Bye,
Alexander.
-Max
On Tue, Jan 28, 2025, 5:46 PM Gleb Smirnoff
wrote: On Sun, Jan 26, 2025 at 04:58:57PM +0100, Alexander Leidinger
wrote:
A> something has changed in the output of "netstat -rn" between
A> 2024-11-23-195545 and 2025-
tionales in favor of
> "-nn".
>
> Bye,
> Alexander.
>
>
> -Max
>
> On Tue, Jan 28, 2025, 5:46 PM Gleb Smirnoff wrote:
>
> On Sun, Jan 26, 2025 at 04:58:57PM +0100, Alexander Leidinger wrote:
> A> something has changed in the output of "netstat -rn&q
On Tue, Jan 28, 2025 at 08:46:04AM -0800, Gleb Smirnoff wrote:
> On Sun, Jan 26, 2025 at 04:58:57PM +0100, Alexander Leidinger wrote:
> A> something has changed in the output of "netstat -rn" between
> A> 2024-11-23-195545 and 2025-01-22-151306. The default route is no
dinger wrote:
A> something has changed in the output of "netstat -rn" between
A> 2024-11-23-195545 and 2025-01-22-151306. The default route is not
listed as
A> "default" anymore, but with "0.0.0.0" resp. "::/0". This breaks
some tools
A> (e
while why is it 0.0.0.0 and not 0.0.0.0/0, 0/0 or 0?
why is it ::/0 not ::, 0:0:0:0:0:0:0:0, 0:0:0:0:0:0:0:0/0,
::::::: or
:::::::/0?
realistically we need automated interfaces too. parsing everything out of human
ui is very error
On Sun, Jan 26, 2025 at 04:58:57PM +0100, Alexander Leidinger wrote:
A> something has changed in the output of "netstat -rn" between
A> 2024-11-23-195545 and 2025-01-22-151306. The default route is not listed as
A> "default" anymore, but with "0.0.0.0" resp.
W dniu 27.01.2025 o 21:07, Michael Gmelin pisze:
On Sun, 26 Jan 2025 16:58:57 +0100
Alexander Leidinger wrote:
Hi,
something has changed in the output of "netstat -rn" between
2024-11-23-195545 and 2025-01-22-151306. The default route is not
listed as "default" anymor
On Sun, 26 Jan 2025 16:58:57 +0100
Alexander Leidinger wrote:
> Hi,
>
> something has changed in the output of "netstat -rn" between
> 2024-11-23-195545 and 2025-01-22-151306. The default route is not
> listed as "default" anymore, but with "0.0.0.0
Am 2025-01-26 16:58, schrieb Alexander Leidinger:
Hi,
something has changed in the output of "netstat -rn" between
2024-11-23-195545 and 2025-01-22-151306. The default route is not
listed as "default" anymore, but with "0.0.0.0" resp. "::/0". This
brea
:
> Hi,
>
> something has changed in the output of "netstat -rn" between
> 2024-11-23-195545 and 2025-01-22-151306. The default route is not listed
> as "default" anymore, but with "0.0.0.0" resp. "::/0". This breaks some
> tools (e.g. iocage)
Hi,
something has changed in the output of "netstat -rn" between
2024-11-23-195545 and 2025-01-22-151306. The default route is not listed
as "default" anymore, but with "0.0.0.0" resp. "::/0". This breaks some
tools (e.g. iocage). Iocage uses python,
master 3459 13 tcp4 *:25 *:*
root@db21:~ # netstat -nl -p tcp
Active Internet connections
Proto Recv-Q Send-Q Local Address
Foreign Address (state)
tcp4 0 0 172.17.2.33.4567
172.17.1.33.0 ESTABLISHED
+++ b/libxo/libxo.c
@@ -8104,6 +8104,8 @@ xo_parse_args (int argc, char **argv)
cp = strrchr(xo_program, '/');
if (cp)
xo_program = ++cp;
+else
+ cp = argv[0]; /* Reset to front of string */
/* GNU tools add an annoying ".test" as the program extension;
On 7 Nov 2019, at 11:03, Arnaud Ysmal wrote:
> Looks cleaner than the unconst.
I've spun a new release (1.3.1) and am importing it now. Building...
Thanks,
Phil
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinf
My bad. Will role a fix asap.
Thanks,
Phil
On 7 Nov 2019, at 10:08, Arnaud Ysmal wrote:
Hi,
I just got the same issue, it happens when argv[0] does not contain a
/ (calling uptime segfault but calling /usr/bin/uptime works).
In xo_parse_args there is no check whether cp is NULL before c
Looks cleaner than the unconst.
Le 7 novembre 2019 16:40:04 GMT+01:00, Phil Shafer a écrit :
>+++ b/libxo/libxo.c
>@@ -8104,6 +8104,8 @@ xo_parse_args (int argc, char **argv)
> cp = strrchr(xo_program, '/');
> if (cp)
> xo_program = ++cp;
>+else
>+ cp = argv[0];
On Thu, Nov 07, 2019 at 04:08:28PM +0100, Arnaud Ysmal wrote:
> Hi,
>
> I just got the same issue, it happens when argv[0] does not contain a /
> (calling uptime segfault but calling /usr/bin/uptime works).
>
> In xo_parse_args there is no check whether cp is NULL before calling
> xo_streq.
>
Hi,
I just got the same issue, it happens when argv[0] does not contain a /
(calling uptime segfault but calling /usr/bin/uptime works).
In xo_parse_args there is no check whether cp is NULL before calling
xo_streq.
I fixed it by changing this line:
- cp = &cp[len + 1 - sizeof(gnu_ext
bj/usr/src/amd64.amd64/sys/CANARY amd64
g1-49(13.0-C)[2] which netstat
/usr/bin/netstat
g1-49(13.0-C)[3] ls -lT `!!`
ls -lT `which netstat`
-r-xr-sr-x 1 root kmem 160192 Nov 7 04:17:46 2019 /usr/bin/netstat
g1-49(13.0-C)[4] netstat -nr
Segmentation fault
g1-49(13.0-C)[5] sudo netstat -nr
Segmentatio
On 5 Apr 2019, at 15:03, Cy Schubert wrote:
> Add arp(8) broken by the libxo import. It's broken at line 603 of
> libxo.c as well. A NULL pointer deref.
Apologies. I have a fix in hand. Will commit shortly.
Thanks,
Phil
___
freebsd-current@freebsd.or
In message <8a6173f2-b6a5-48e6-9ec0-063698c0c...@gmail.com>, Enji
Cooper writes
:
>
> > On Apr 5, 2019, at 5:19 AM, Michael Butler wro
> te:
> >
> > Something changed in libxo that causes 'netstat -i' to segfault as below:
> >
> > imb@toshi
> On Apr 5, 2019, at 5:19 AM, Michael Butler
> wrote:
>
> Something changed in libxo that causes 'netstat -i' to segfault as below:
>
> imb@toshi:/usr/src/usr.bin/netstat> lldb
> /usr/obj/usr/src/amd64.amd64/usr.bin/netstat/netstat
> (lldb) target create
Something changed in libxo that causes 'netstat -i' to segfault as below:
imb@toshi:/usr/src/usr.bin/netstat> lldb
/usr/obj/usr/src/amd64.amd64/usr.bin/netstat/netstat
(lldb) target create "/usr/obj/usr/src/amd64.amd64/usr.bin/netstat/netstat"
Current executable set to
On 10/1/18, Konstantin Belousov wrote:
> On Mon, Oct 01, 2018 at 09:15:46AM +0300, Yuri Pankov wrote:
>> Hi,
>>
>> I've noticed the following rebooting after a panic:
>>
>> pid 41246 (vmstat), uid 0: exited on signal 11 (core dumped)
>> pid 47091 (ne
On Mon, Oct 01, 2018 at 09:15:46AM +0300, Yuri Pankov wrote:
> Hi,
>
> I've noticed the following rebooting after a panic:
>
> pid 41246 (vmstat), uid 0: exited on signal 11 (core dumped)
> pid 47091 (netstat), uid 0: exited on signal 11
>
> And indeed, trying
Hi,
I've noticed the following rebooting after a panic:
pid 41246 (vmstat), uid 0: exited on signal 11 (core dumped)
pid 47091 (netstat), uid 0: exited on signal 11
And indeed, trying to manually run those on the resulting vmcore makes
them crash:
# vmstat -m -M /var/crash/vmc
> Author: brooks
> Date: Thu Jul 5 17:02:10 2018
> New Revision: 336002
> URL:
> https://svnweb.freebsd.org/changeset/base/336002
>
>
> Log:
> Work around lame warnings in ancient gcc on 32-bit platforms.
>
> Fixes r335979.
[The below are the gcc 4.2.1 based 32-bit architectures.]
htt
he jail 192.168.0.103.
> > SSHD is started within the jail, root IS allowed login.
> > But any attempt to ssh to 192.168.0.103 from the host,
> > returns:
> > ssh_exchange_identification: Connection closed by remote host.
> >
> > SSHD id NOT running on the host.
> >
> >
exchange_identification: Connection closed by remote host.
>
> SSHD id NOT running on the host.
>
> inetd_flags="-wW -a 192.168.0.100" and syslogd_flags="-ss"
> is set on the host via rc.conf
>
> second issue; loging into the jail, via jexex. If I perf
So DHCP
> >> assigns it 192.168.0.100. I assigned the jail 192.168.0.103.
> >> SSHD is started within the jail, root IS allowed login.
> >> But any attempt to ssh to 192.168.0.103 from the host,
> >> returns:
> >> ssh_exchange_identification: Connection closed by
S allowed login.
>> But any attempt to ssh to 192.168.0.103 from the host,
>> returns:
>> ssh_exchange_identification: Connection closed by remote host.
>>
>> SSHD id NOT running on the host.
>>
>> inetd_flags="-wW -a 192.168.0.100" and syslogd_flags=
nning on the host.
inetd_flags="-wW -a 192.168.0.100" and syslogd_flags="-ss"
is set on the host via rc.conf
what does netstat -aAn show (on the main host).
second issue; loging into the jail, via jexex. If I perform:
netstat -nr
The following is returned:
netstat: kvm not available:
a 192.168.0.100" and syslogd_flags="-ss"
is set on the host via rc.conf
second issue; loging into the jail, via jexex. If I perform:
netstat -nr
The following is returned:
netstat: kvm not available: /dev/mem: No such file or directory
Routing tables
rt_table
Hiroki Sato wrote:
> ia> Hiroki Sato wrote:
> ia> > Hm, how about the attached one?
> ia> >
> ia> > I think the cause is just a race when length of the sysctl's output
> ia> > is changed in kernel after the buffer allocation in userspace, not
> ia> > memory shortage. Size of the routing table
Ian FREISLICH wrote
in :
ia> Hiroki Sato wrote:
ia> > Hm, how about the attached one?
ia> >
ia> > I think the cause is just a race when length of the sysctl's output
ia> > is changed in kernel after the buffer allocation in userspace, not
ia> > memory shortage. Size of the routing table ca
rrect. It's growing at about 9000 entries per second (I
wish it were faster).
This is what the output looks like now. I guess I'm not the average
case.
[firewall1.jnb1] ~ # netstat -rn |wc -l
netstat: Routing table grew, retrying
netstat: Routing table grew, retrying
netstat: Routin
Ian FREISLICH wrote
in :
ia> Hiroki Sato wrote:
ia> > ia> While recieving my routing table I used to be able to check how far
ia> > ia> it got by counting the output netstat -rn. It takes about 2 seconds
ia> > ia> to recieve the routes from my route-server,
On 21 Feb, Ian FREISLICH wrote:
> Hiroki Sato wrote:
>> ia> While recieving my routing table I used to be able to check how far
>> ia> it got by counting the output netstat -rn. It takes about 2 seconds
>> ia> to recieve the routes from my route-server, but over
Hiroki Sato wrote:
> ia> While recieving my routing table I used to be able to check how far
> ia> it got by counting the output netstat -rn. It takes about 2 seconds
> ia> to recieve the routes from my route-server, but over a minute to
> ia> update the kernel routing ta
"Ian FREISLICH" wrote
in :
ia> Hi
ia>
ia> While recieving my routing table I used to be able to check how far
ia> it got by counting the output netstat -rn. It takes about 2 seconds
ia> to recieve the routes from my route-server, but over a minute to
ia> update
Hi
While recieving my routing table I used to be able to check how far
it got by counting the output netstat -rn. It takes about 2 seconds
to recieve the routes from my route-server, but over a minute to
update the kernel routing table.
I'm now getting this error until zebra completes
On Jul 16, 2012, at 12:30 AM, Anton Shterenlikht wrote:
> On ia64 netstat -r broke some time
> between 8.1-release, and r237134.
Can you file a PR so that it's being tracked.
Thanks,
--
Marcel Moolenaar
mar...@xcllnt.net
___
free
On ia64 netstat -r broke some time
between 8.1-release, and r237134.
mech-as221# uname -a
FreeBSD mech-as221.men.bris.ac.uk 8.1-RELEASE FreeBSD 8.1-RELEASE #0: Sun Jul 18
18:31:37 UTC 2010 r...@pluto1.freebsd.org:/usr/obj/usr/src/sys/GENERIC ia6
4
mech-as221# netstat -r
Routing tables
On Mon, May 21, 2012 at 06:51:21AM +, Hartmut Brandt wrote:
> Hi,
>
> I'm running a kernel+world compiled with clang (everything fresh from two
> days ago). Kernel and world are in sync. When I run netstat -rn I get a
> 'no namelist'.
>
> I tried to track
Hi,
I'm running a kernel+world compiled with clang (everything fresh from two
days ago). Kernel and world are in sync. When I run netstat -rn I get a
'no namelist'.
I tried to track that down and it looks like this is an issue with the symbol
dumptid defined in kern_shutdown.
On both r233779 and r234515 on my 10-CURRENT amd64 home box netstat returns: no
namelist
This is a Q9550 system and I rebuilt both world and kernel using clang with -j8
The last revision netstat was functioning for me was r230839.
I went from r230839 to r233779 so no other updates went in between
Rui Paulo schrieb am 2010-03-26:
> On 26 Mar 2010, at 17:24, Alexander Best wrote:
> > hi there,
> > `netstat -i` reports:
> > NameMtu Network Address Ipkts Ierrs Idrop
> > Opkts
> > Oerrs Coll
> > ath0 2290 00:0f:b5:82
On 26 Mar 2010, at 17:24, Alexander Best wrote:
> hi there,
>
> `netstat -i` reports:
>
> NameMtu Network Address Ipkts Ierrs IdropOpkts
> Oerrs Coll
> ath0 2290 00:0f:b5:82:07:c8 6046435 691159 0 654080
&g
On Fri, Mar 26, 2010 at 12:24 PM, Alexander Best wrote:
> hi there,
>
> `netstat -i` reports:
>
> Name Mtu Network Address Ipkts Ierrs Idrop Opkts
> Oerrs Coll
> ath0 2290 00:0f:b5:82:07:c8 6046435 691159 0 654080
&g
hi there,
`netstat -i` reports:
NameMtu Network Address Ipkts Ierrs IdropOpkts
Oerrs Coll
ath0 2290 00:0f:b5:82:07:c8 6046435 691159 0 654080
0 0
lo0 16384 1280796 0 0 1280796
0 0
lo0 16384 your-net
On Monday 01 December 2003 05:25 pm, Leo Bicknell wrote:
> In an effort to cut down on Sam's load...
>
> This is a known issue. Evidently there are some low level radio
> counters that are incorrectly being reported as input errors.
> Basically they should be ignored until the driver can be change
Hi Leo.
Thanks for the information, but do you know if is some thing to do
to fix this? or simply I need wait for another driver version, because
the driver looks so much better than a couple a week ago, the only bad
thing is this problem and when happen kill all the wireless network
Thanks
Hi there.
I running an script every 4 sec. on my Freebsd Atheros Access Point to
log the netstat errors and I can confirm every time I have more than 3
Ierrs per sec or Oerrs per sec.. my ping to the clients box start to
be very high and the connection work very slow until the error go down
In an effort to cut down on Sam's load...
This is a known issue. Evidently there are some low level radio
counters that are incorrectly being reported as input errors.
Basically they should be ignored until the driver can be changed
to not report them.
--
Leo Bicknell - [EMAIL PROTECTE
Hi there.
I running an script every 4 sec. on my Freebsd Atheros Access Point to
log the netstat errors and I can confirm every time I have more than 3
Ierrs per sec or Oerrs per sec.. my ping to the clients box start to be
very high and the connection work very slow until the error go down
On Tue, 1 Jul 2003, 22:45+1200, Andrew Thompson wrote:
> Hi,
>
>
> Is there any reason that the interface name in netstat is truncated at 5
> chars? I have a box with ~100 vlans so the interface name gets chopped
> after vlan9.
>
> Here is a patch to increase it to 7 char
Hi,
Is there any reason that the interface name in netstat is truncated at 5
chars? I have a box with ~100 vlans so the interface name gets chopped
after vlan9.
Here is a patch to increase it to 7 chars. Any probs?
thanks,
Andy
--- usr.bin/netstat/if.c.orig Tue Jul 1 22:37:14 2003
* De: "Scott R." <[EMAIL PROTECTED]> [ Data: 2003-01-30 ]
[ Subjecte: Re: Is netstat b?rked? ]
> On Thu, Jan 30, 2003 at 12:30:44AM -0800, Juli Mallett wrote:
> > * De: Ruslan Ermilov <[EMAIL PROTECTED]> [ Data: 2003-01-30 ]
> > [ Subjecte: Re: Is n
On Thu, Jan 30, 2003 at 12:30:44AM -0800, Juli Mallett wrote:
> * De: Ruslan Ermilov <[EMAIL PROTECTED]> [ Data: 2003-01-30 ]
> [ Subjecte: Re: Is netstat b?rked? ]
> > On Wed, Jan 29, 2003 at 02:07:50PM -0800, Juli Mallett wrote:
> > > ref5% ne
* De: Ruslan Ermilov <[EMAIL PROTECTED]> [ Data: 2003-01-30 ]
[ Subjecte: Re: Is netstat b?rked? ]
> On Wed, Jan 29, 2003 at 02:07:50PM -0800, Juli Mallett wrote:
> > ref5% netstat -na -p tcp
> > ref5%
> >
> > dalek# netstat -an -p tcp
> > dalek#
On Wed, Jan 29, 2003 at 02:07:50PM -0800, Juli Mallett wrote:
> ref5% netstat -na -p tcp
> ref5%
>
> dalek# netstat -an -p tcp
> dalek#
>
Both beast and ref5 are from Jan 4 and exhibit this problem;
builder, which is from Jan 28, doesn't.
Perhaps, someone updated t
Works here.
largo# netstat -an -p tcp
Active Internet connections (including servers)
Proto Recv-Q Send-Q Local Address Foreign Address(state)
tcp4 0 0 *.22 *.*LISTEN
tcp6 0 0 *.22
ref5% netstat -na -p tcp
ref5%
dalek# netstat -an -p tcp
dalek#
Both times logged in via ssh, etc.
--
Juli Mallett <[EMAIL PROTECTED]>
AIM: BSDFlata -- IRC: juli on EFnet
OpenDarwin, Mono, FreeBSD Developer
ircd-hybrid Developer, EFnet addict
FreeBSD on MIPS-Anything on FreeB
Built and installed a new kernel, problem went away.
tnx
-kim
--
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
fe80:4::204:5aff:0 -0 - -
Note all interface addresses are 192.58.161.22
netstat -r works as expected.
Any help here is greatly appreciated.
-kim
--
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-curren
In article <[EMAIL PROTECTED]>,
zhang jack <[EMAIL PROTECTED]> wrote:
> Hi,
> When I using netperf to test Intel Pro/1000 performance,
> I got strange netstat output:
>
> #./netperf -H 10.0.0.2
> TCP STREAM TEST to 10.0.0.2
>
> on 10.0.0.2, I start n
Hi,
When I using netperf to test Intel Pro/1000 performance,
I got strange netstat output:
#./netperf -H 10.0.0.2
TCP STREAM TEST to 10.0.0.2
on 10.0.0.2, I start netstat -w 1 , but got strange output:
it seems the link is dowm and up ceaselessly.
input(Total
I have submitted the following PR (bin/36400) against netstat.
After I havestarted xdm and X11 (XFree86 4.2) on my machine
I can no longer get information on LOCAL (i.e. UNIX) domain sockets because
netstat seg faults. I have built a version with debugging and traced this
down to
the printf
On Mon, 24 Dec 2001, Martin Blapp wrote:
> As we just have noted, there is no output anymore for netstat -f inet.
> Has the support been dropped ?
>
> Also there are only unix domain sockets in the normal netstat output. I
> cannot see any tpc4 connections anymore.
>
>
> Works fine.
Hi,
I guess the world is not 100% up to date. I seems that I just got
this after running a cvsup 2 hours later after the initial one.
Shit happens.
Thanks for the answer and sorry.
Martin
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in t
On Mon, Dec 24, 2001 at 08:06:06AM -0500, [EMAIL PROTECTED] wrote:
> On Mon, Dec 24, 2001 at 02:01:19PM +0100, Wilko Bulte wrote:
> > On Mon, Dec 24, 2001 at 02:02:00PM +0100, Martin Blapp wrote:
> > >
> > > Hi All,
> > >
> > > As we just have noted,
On Mon, Dec 24, 2001 at 02:01:19PM +0100, Wilko Bulte wrote:
> On Mon, Dec 24, 2001 at 02:02:00PM +0100, Martin Blapp wrote:
> >
> > Hi All,
> >
> > As we just have noted, there is no output anymore for
> > netstat -f inet. Has the support been dropped ?
On Mon, Dec 24, 2001 at 02:02:00PM +0100, Martin Blapp wrote:
> Hi All,
>
> As we just have noted, there is no output anymore for
> netstat -f inet. Has the support been dropped ?
Incorrect.
> Also there are only unix domain sockets in the normal
> netstat output. I c
On Mon, Dec 24, 2001 at 02:02:00PM +0100, Martin Blapp wrote:
>
> Hi All,
>
> As we just have noted, there is no output anymore for
> netstat -f inet. Has the support been dropped ?
I also don't get any output.
> Also there are only unix domain sockets in the normal
>
Hi All,
As we just have noted, there is no output anymore for
netstat -f inet. Has the support been dropped ?
Also there are only unix domain sockets in the normal
netstat output. I cannot see any tpc4 connections anymore.
I noted this in 4.5 PRERELEASE too. It used to work in
4.3 RELEASE and
switched to a virtual terminal and
endered "#>netstat -a -f inet" from a root prompt. The lines "Panic: too many
open files, syncing, automatic reboot in 15 seconds" appeared, followed by a
reboot.
I am new to this, indeed this is the first panic I have experienced. I
could fin
On Mon, 16 Jul 2001, Wilko Bulte wrote:
> On Mon, Jul 16, 2001 at 02:30:47PM -0700, Matthew Jacob wrote:
> > > I've seen this panic many times on my alpha SMP testbox. It seems that the vm
> > > object returned by vm_map_lookup via the fs.first_object variable is actually
> > > NULL, resulting
On Mon, Jul 16, 2001 at 02:30:47PM -0700, Matthew Jacob wrote:
> > I've seen this panic many times on my alpha SMP testbox. It seems that the vm
> > object returned by vm_map_lookup via the fs.first_object variable is actually
> > NULL, resulting in a NULL pointer deref when calling vm_object_pip
On Mon, Jul 16, 2001 at 02:39:17PM -0700, Matthew Jacob wrote:
>
> On Mon, 16 Jul 2001, Wilko Bulte wrote:
>
> > On Mon, Jul 16, 2001 at 02:30:47PM -0700, Matthew Jacob wrote:
> > > > I've seen this panic many times on my alpha SMP testbox. It seems that the vm
> > > > object returned by vm_map
> I've seen this panic many times on my alpha SMP testbox. It seems that the vm
> object returned by vm_map_lookup via the fs.first_object variable is actually
> NULL, resulting in a NULL pointer deref when calling vm_object_pip_add() (note
> object=0x0). I haven't seen this on UP or x86 before,
Thus spake John Baldwin ([EMAIL PROTECTED]):
> > tf_eip = -1070822146, tf_cs = 8, tf_eflags = 66118,
> > tf_esp = -1069680480, tf_ss = 1}) at /usr/src/sys/i386/i386/trap.c:405
> >#11 0xc02c8cfe in vm_object_pip_add (object=0x0, i=1)
>
> I've seen this panic many times on my alpha SM
gment = base 0x0, limit 0xf, type 0x1b
> = DPL 0, pres 1, def32 1, gran 1
> processor eflags = interrupt enabled, resume, IOPL = 0
> current process = 595 (netstat)
> panic: from debugger
> panic: from debugger
> Uptime: 2m41s
Hello, when running netstat or using an app, that uses it
(such as linux-navigator), my machine panics:
Script started on Sat Jul 14 12:52:06 2001
(kgdb) mobile# gdb -k /usr/obj/usr/src/sys/MOBILE/kernel.debug vmcore.1
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered
Immediate problem is fixed by including machine/param.h in netstat/if.c.
ifmcstat, rip6query, rtadvd/dump.c, i4b/isdnd/rc_config.c too...
Those appear to be all.
I don't know the "canonical" solution;
maybe including machine/param.h in if_var.h? (or was removing it
for &q
On Sun, Apr 23, 2000 at 06:44:51PM -0400, Will Andrews wrote:
> If Mark or Garrett could fix this ASAP that would be nice. :)
Never mind, this was an oversight on my part.
--
Will Andrews <[EMAIL PROTECTED]>
GCS/E/S @d- s+:+>+:- a--->+++ C++ UB P+ L- E--- W+++ !N !o ?K w---
?O M+ V-- PS+ PE
Buildworld on 5.0-CURRENT is breaking here:
===> usr.bin/netstat
cc -O -pipe -Wall -DINET6 -DIPSEC -I/usr/obj/usr/src/i386/usr/include -c
/usr/src/usr.bin/netstat/if.c
cc -O -pipe -Wall -DINET6 -DIPSEC -I/usr/obj/usr/src/i386/usr/include -c
/usr/src/usr.bin/netstat/inet.c
cc -O -pipe -W
> > And sorry, it is not added to netstat man yet.
>
> I see you've just commited a change there, but I think it needs adding to
> the usage message as well:
>
> ben@platinum:~$ netstat -\?
> netstat: illegal option -- ?
> usage: netstat [-Aan] [-f addr
Yoshinobu Inoue wrote:
> Please add "-l" flag.
ah.. thanks.
> And sorry, it is not added to netstat man yet.
I see you've just commited a change there, but I think it needs adding to
the usage message as well:
ben@platinum:~$ netstat -\?
netstat: illegal option -- ?
usag
Hi,
>>>>> On Sat, 11 Mar 2000 12:44:57 +
>>>>> Ben Smithurst <[EMAIL PROTECTED]> said:
ben> Is there any way to see the full IPv6 address with netstat? I just see:
Try do with -l option.
ume@peace:263# netstat -anl -f inet6
Active Internet connection
> Is there any way to see the full IPv6 address with netstat? I just see:
>
> ben@strontium:~$ netstat -an -f inet6
> Active Internet connections (including servers)
> Proto Recv-Q Send-Q Local Address Foreign Address(state)
> tcp6 0 0 2002:d4e4
Is there any way to see the full IPv6 address with netstat? I just see:
ben@strontium:~$ netstat -an -f inet6
Active Internet connections (including servers)
Proto Recv-Q Send-Q Local Address Foreign Address(state)
tcp6 0 0 2002:d4e4:e0d:0:.989 2002:d4e4:e0d:0:.22
s display mode, when, e.g.
>
> netstat -s -I bar0 -f inet6
>
>is specified. (though this is inet6 only now.)
I see where you are going now. The syntax of netstat, already complex,
is becoming even more complex. More detail in the man page will be
necessary soon. Also, the "ifla
> Hmm, I've just noticed some small misalignment of column headings in the
> default output. I'll fix that too.
>
> Stephen.
I also noticed that my another IPv6 related change is one of
main cause of the misalignment.
So I also tried to make patches for it, including
&quo
I think my last description was poor.
> Could this be left with adding sflag check?
> Because now there is interface statistics display mode, when, e.g.
Maybe improved one is,
Because now there is a mode where protocol specific statistics
over each interface is displayed.
Yoshinobu Inoue
> Recently that changed, and "netstat -f inet -i" in particular changed to
> give the -f flag priority over the -i flag. This makes no sense to me,
> so I intend to commit this patch:
Could this be left with adding sflag check?
Because now there is interface statistics disp
I've got very used to an alias ns='netstat -f inet' which lets me do all
the things I like to do without annoying me with stuff I don't want to
see. All the options that don't care about the address family just ignore
that option. Or, used to.
Recently that changed, an
Hi, it looks GREAT !
X clive@cartier ~> netstat -a -f inet -L
Current listen queue sizes (qlen/incqlen/maxqlen)
Listen Local Address
0/0/5 *.1029
0/0/5 *.1028
0/0/5 *.1027
0/0/5 *.1
< said:
> I'd like to have a review on the following patch:
> http://www.freebsd.org/~guido/netstat.diff
> It adds support to netstat to show listen queue lengths.
> Manual page diffs are in the working.
Looks good to me.
-GAWollman
To Unsubscribe: send mail to [E
1 - 100 of 110 matches
Mail list logo
