> On Wed, 29 Sep 2004 11:40:23 +0300 (EEST),
> Pekka Savola <[EMAIL PROTECTED]> said:
>> >> Okay. Now I think I figure out the problem. Those host routes were
>> >> created not deliberately, so the kernel will eventually need a fix to
>> >> this.
>> >>
>> >> But if you are in a hurry a
Kalin Hristov wrote:
It would be very nice
As they say about the MPLS "The feature of the Internet"
Did they change the acronym from "Mostly Pointless Lamp Switching"?
Pete
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/fr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
It would be very nice
As they say about the MPLS "The feature of the Internet"
-BEGIN PGP SIGNATURE-
Version: PGP 6.5.8
iQA/AwUBQVsHc2cb2v9P9sWHEQJxQgCglXvPzlF6R9Ev7pKzM+p7QW35SIgAnAmV
uJxBcDZODDPamn2C6230+cO8
=jyFP
-END PGP SIGNATUR
On Tue, 28 Sep 2004, Raphael H. Becker wrote:
> Hmm. if_bge buggy?
> But, same machine on a FE-Switich worked perfectly (with 100MBit).
>
> By default ifconfig says:
>
> bge0: flags=8843 mtu 1500
> options=1a
> inet 10.101.240.56 netmask 0xff00 broadcast 10.101.240.255
>
On Wednesday 29 September 2004 04:50, dima wrote:
> Would you bother reading cisco tech documentation regarding 802.1x?
I have. Would you bother dropping invalid assumptions?
> http://cisco.com/en/US/products/hw/switches/ps628/products_configuration_gu
>ide_chapter09186a008022995b.html It states
Hi folks,
I've cleaned-up the bfe driver's locking. I've also fixed it up so
it doesn't need a recursive mute anymore. I'm running it locally and it's
working with mpsafenet=1. Please test it on your bfe nics and let me know
how it goes. I would also like to here from the networking folks as to th
> guass# ipfw -a list
> 10 0 deny ip from any to 203.222.55.37 via rl0
> 65535 1287 499525 allow ip from any to any
>
> guass# ping 203.222.55.37
> PING 203.222.55.37 (203.222.55.37): 56 data bytes
> 64 bytes from 203.222.55.37: icmp_seq=0 ttl=255 time=0.281 ms
> 64 bytes from 203.22
Would you bother reading cisco tech documentation regarding 802.1x?
http://cisco.com/en/US/products/hw/switches/ps628/products_configuration_guide_chapter09186a008022995b.html
It states you can configure guest vlan for non-authentified users; you
can also temporarily disable infected users' account
On Wed, 29 Sep 2004, JINMEI Tatuya / [ISO-2022-JP] [EMAIL PROTECTED]@C#:H(B wrote:
> >> Okay. Now I think I figure out the problem. Those host routes were
> >> created not deliberately, so the kernel will eventually need a fix to
> >> this.
> >>
> >> But if you are in a hurry and/or cannot repl
> On Wed, 29 Sep 2004 10:59:32 +0300 (EEST),
> Pekka Savola <[EMAIL PROTECTED]> said:
>> Okay. Now I think I figure out the problem. Those host routes were
>> created not deliberately, so the kernel will eventually need a fix to
>> this.
>>
>> But if you are in a hurry and/or cannot re
> On Wed, 29 Sep 2004 10:59:32 +0300 (EEST),
> Pekka Savola <[EMAIL PROTECTED]> said:
>> Okay. Now I think I figure out the problem. Those host routes were
>> created not deliberately, so the kernel will eventually need a fix to
>> this.
>>
>> But if you are in a hurry and/or cannot re
On Tue, 28 Sep 2004, JINMEI Tatuya / [ISO-2022-JP] [EMAIL PROTECTED]@C#:H(B wrote:
> Okay. Now I think I figure out the problem. Those host routes were
> created not deliberately, so the kernel will eventually need a fix to
> this.
>
> But if you are in a hurry and/or cannot replace the kernel
12 matches
Mail list logo
