Hello!
I have Compaq DL360G2 with Broadcom BCM5701 Gigabit Ethernet and
FreeBSD 5.1R installed. There are no problems if I use bge as usual
network card, but when I try to use 802.1Q vlans, I can't receive (only
receive, sending is ok) packets more then 1456 bytes! What is the
problem? BGE dr
Terry Lambert wrote:
Hello!
Boris Kovalenko wrote:
I have Compaq DL360G2 with Broadcom BCM5701 Gigabit Ethernet and
FreeBSD 5.1R installed. There are no problems if I use bge as usual
network card, but when I try to use 802.1Q vlans, I can't receive (only
receive, sending is ok) packets
Hello!
What is the problem if I see arp: unknown hardware address format
(0x4d6f) messages with bge driver on 5.1R?
Yours truly,
Boris Kovalenko
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To
implementation?
Thanks in advance,
Boris Kovalenko
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
512 Oct 9 08:55 gcov
drwxr-xr-x 2 root wheel 512 Oct 9 08:55 protoize
drwxr-xr-x 2 root wheel 512 Oct 9 08:55 tradcpp0
What is wrong? Current system is 5.1-RELEASE-p8
Yours truly,
Boris Kovalenko
___
[EMAIL PROTECTED] mailing list
http
Hello!
I know about -r and -f options. They don't help.
Proc wrote:
man rm
Note -r and -f.
Boris Kovalenko wrote:
Hello!
Can not remove directory /usr/obj/usr/src/gnu/usr.bin/cc/cc1
rm: /usr/obj/usr/src/gnu/usr.bin/cc/cc1: Directory not empty
bash-2.05b# pwd; ls -la
/usr/obj/usr/sr
Hello!
Seems You are right:
BAD INODE NUMBER FOR '.' I=353381 OWNER=root MODE=40755
SIZE=512 MTIME=Oct 9 08:54 2003
DIR=/obj/usr/src/gnu/usr.bin/cc/cc1
UNEXPECTED SOFT UPDATE INCONSISTENCY
FIX? no
Will reboot and run fsck manually. Thanks for advance!
Yours truly,
Boris Kov
parameter, so if a have dowloaded 4.5G (for example) what
number will send to radius?
Regards,
Boris
Barney Wolff wrote:
On Wed, Nov 19, 2003 at 09:00:01AM +0500, Boris Kovalenko wrote:
I found a serious bug in RADIUS accounting code. The problem is that
OctetsIn and OctetsOut are defined
Hello!
Standard PPP does not support UPDATE packets, and of course (as my
RADIUS knowledge) the counters should not be resetted, because RADIUS
updates the same record.
Regards,
Boris
Michael Bretterklieber wrote:
Hi,
On Wed, 19 Nov 2003, Boris Kovalenko wrote:
Hello!
Yes
The RFC says:
5.4. Acct-Output-Octets
blabla
can only be
present in Accounting-Request records where the Acct-Status-Type
is set to Stop.
It looks like, that these counters must not present in accounting updates.
You are right, but your words - "but a patch could be written :-)".
A
Hello!
So sending interim update packets won't help.
Like I said :)
looking for someone who supervises my patch and commit it if no problems
will be founded.
this can be a problem :-)
This is the problem now :) I'm wondering if I only one useing ppp with
RADIUS accounting with FreeBSD.
R
Hello!
I found a serious bug in RADIUS accounting code. The problem is that
OctetsIn and OctetsOut are defined as unsingned long long, but the
RADIUS supports only INT32 values, so, when
we're doing rad_put_int(r->cx.rad, RAD_ACCT_OUTPUT_OCTETS,
stats->OctetsOut) in radius.c for OctetsOut (an
12 matches
Mail list logo