On 11/23/11 19:05, Brian Seklecki (Mobile) wrote:
Send us:
grep ifconfig /etc/rc.conf
ifconfig -a
ifconfig -m
netstat -i
netstat -rn
netstat -i
arp -an
For both the working and non-working cards to compare.
Sorry for the noise...
I accidentally removed the "media" option from rc.conf and the
On 11/23/11 19:05, Brian Seklecki (Mobile) wrote:
Send us:
grep ifconfig /etc/rc.conf
ifconfig -a
ifconfig -m
netstat -i
netstat -rn
netstat -i
arp -an
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ne
Send us:
grep ifconfig /etc/rc.conf
ifconfig -a
ifconfig -m
netstat -i
netstat -rn
netstat -i
arp -an
For both the working and non-working cards to compare.
Thx,
~BAS
On Wed, 23 Nov 2011, Andrea Venturoli wrote:
Hello.
Just to say today I upgraded from 8.1 to 8.2 and xl0 stopped wo
On 11/23/2011 3:53 PM, Marko Zec wrote:
On Wednesday 23 November 2011 14:17:11 Nikos Vassiliadis wrote:
On 11/23/2011 1:22 PM, Gleb Smirnoff wrote:
I'd suspect VIMAGE. Can you please try w/o it and if it appears to be
VIMAGE-related, then please file a PR.
It seems VIMAGE related. I'll ask at
Hello.
Just to say today I upgraded from 8.1 to 8.2 and xl0 stopped working.
It is detected:
xl0: <3Com 3c900B-COMBO Etherlink XL> port 0xd800-0xd87f mem
0xfdefe000-0xfdefe07f irq 17 at device 7.0 on pci1
xl0: selecting 10baseT transceiver, half duplex
xl0: Ethernet address: 00:50:04:22:a9:c0
x
On Wednesday 23 November 2011 14:17:11 Nikos Vassiliadis wrote:
> On 11/23/2011 1:22 PM, Gleb Smirnoff wrote:
> > I'd suspect VIMAGE. Can you please try w/o it and if it appears to be
> > VIMAGE-related, then please file a PR.
>
> It seems VIMAGE related. I'll ask at virtualization@.
From the back
On 11/23/2011 1:22 PM, Gleb Smirnoff wrote:
I'd suspect VIMAGE. Can you please try w/o it and if it appears to be
VIMAGE-related,
then please file a PR.
It seems VIMAGE related. I'll ask at virtualization@.
Thanks, Nikos
___
freebsd-net@freebsd.org
On Nov 23, 2011, at 9:30 AM, Nikolay Denev wrote:
> I'm seeing exactly the same problem with Quagga.
> Quagga's bgpd also seem to always set the TCP_MD5 socket option, and newer
> freebsd 8.2 machines
> don't seem to be able to establish bgp sessions, probably due to the recent
> TCP_MD5 fixes
On Nov 21, 2011, at 3:29 PM, Borja Marcos wrote:
>
> (Sent to freebsd-bugs as well, copied here for discussion, if needed)
>
>
>
>
>
> Sorry for the brief report and the scarce details. The fing form insists
> on rejecting the captcha after one hour writing a report.
>
> So, in
On Wed, Nov 23, 2011 at 01:09:34PM +0200, Nikos Vassiliadis wrote:
N> On 11/22/2011 9:48 PM, Gleb Smirnoff wrote:
N> > Can't reproduce this on head. May be some additional measures are needed?
Traffic?
N>
N> Just noticed that the panic does not happen using GENERIC.
N> Here is my kernel configura
On 11/22/2011 9:48 PM, Gleb Smirnoff wrote:
Can't reproduce this on head. May be some additional measures are needed?
Traffic?
Just noticed that the panic does not happen using GENERIC.
Here is my kernel configuration, if you want to dig deeper.
include GENERIC
ident LAB
options VIMA
On Nov 23, 2011, at 9:30 AM, Nikolay Denev wrote:
> the RFC states :
>
> Upon receiving a signed segment, the receiver must validate it by
> calculating its own digest from the same data (using its own key) and
> comparing the two digest. A failing comparison must result in the
> segmen
12 matches
Mail list logo
