On Mon, 15 Sep 2003, Kip Macy wrote:
We have FreeBSD machines connected to EMC 8830 working fine!
Leal
what FC hardware are you using/recommend? btw, is this an i86?
thanks,
danny
Date: Mon, 15 Sep 2003 08:48:46 -0700 (PDT)
From: Kip Macy [EMAIL PROTECTED]
To: Danny
Barry Bouwsma wrote:
Would anyone care to explain why the following simple patch could be
enough to wedge my machine solid? (My original hack-patches without
any console printf() debuggery did the same thing within seconds, as
well...) All it does is notify the console whenever a serial port
On Tue, Sep 16, 2003 at 04:16:31AM +0800, maillist bsd wrote:
I am just testing jail on my FreeBSD4.8-stable box, i found i can not ssh to the
jail environment, but i can telnet to jail environment, the sshd is running both
inside and outside jail. What's the problem.
This is [EMAIL
--On Tuesday, September 16, 2003 09:07:15 +0100 Matthew Seaman
[EMAIL PROTECTED] wrote:
On Tue, Sep 16, 2003 at 04:16:31AM +0800, maillist bsd wrote:
I am just testing jail on my FreeBSD4.8-stable box, i found i can not
ssh to the jail environment, but i can telnet to jail environment, the
sshd
Hi,There is a problem when PCMCIA related stuff
is used as module, ATA CF is not recognized.
This is because PCMCIA atachment is not compiled
when pccard(4) is not compiled in.
To fix it, we have to supply PCMCIA attachment
in any form.
One way is to make a kernel module that contains only
On Wed, 17 Sep 2003 00:43:19 +0900
Takanori Watanabe [EMAIL PROTECTED] wrote:
Hi,There is a problem when PCMCIA related stuff
is used as module, ATA CF is not recognized.
This is because PCMCIA atachment is not compiled
when pccard(4) is not compiled in.
To fix it, we have to supply PCMCIA
It seems Takanori Watanabe wrote:
Hi,There is a problem when PCMCIA related stuff
is used as module, ATA CF is not recognized.
This is because PCMCIA atachment is not compiled
when pccard(4) is not compiled in.
To fix it, we have to supply PCMCIA attachment
in any form.
One way is to
Hello,
I read documents on Vinum for FreeBSD. But, some points exculed.. I want to
find some points on Vinum..
If I have identical 2 disks (Samsung SP6300 Series),suppose, I want to
install the
FreeBSD on one of them 60 Gb. After installing the FreeBSD , I want to run
vinum with mirroring with
On Tue, Sep 16, 2003 at 07:08:13PM +0300, Murat USTUNTAS wrote:
Hello,
I read documents on Vinum for FreeBSD. But, some points exculed.. I want to
find some points on Vinum..
If I have identical 2 disks (Samsung SP6300 Series),suppose, I want to
install the
FreeBSD on one of them 60 Gb.
* William Michael Grim [EMAIL PROTECTED] [030916 14:46]:
What the hell are you talking about? Thanks for not giving us any info
about your problem.
I suspect he means:
http://www.securityfocus.com/archive/1/337662/2003-09-13/2003-09-19/0
--Mike
From: Josh Brooks [mailto:[EMAIL PROTECTED]
1. What is the workaround for this issue ? Be creative. Not
everyone can
update their userland in a normal fashion - and no, I won't
sit here and
justify that statement. Think embedded systems.
2. Is there really an exploit in the wild ?
On Tue, 16 Sep 2003, William Michael Grim wrote:
What the hell are you talking about? Thanks for not giving us any info
about your problem.
He appears to have made a basic assumption that the readers of -hackers
would subscribe to security-advisories as well.
FreeBSD Security Advisory
Do you use any klds? What does kldstat say?
No klds loaded.
Well, it looks like the dc net driver is causing the panic. After some
testing, I got this backtrace:
---
#0 dumpsys () at ../../kern/kern_shutdown.c:487
#1 0xc0168237 in boot (howto=256) at ../../kern/kern_shutdown.c:316
#2
Hi,
#0 dumpsys () at ../../kern/kern_shutdown.c:487
#1 0xc0168237 in boot (howto=256) at ../../kern/kern_shutdown.c:316
#2 0xc0168675 in panic (fmt=0xc02db260 m_copydata, offset size of mbuf
chain) at ../../kern/kern_shutdown.c:595
#3 0xc018576e in m_copydata (m=0xc1560d00, off=6144,
Hi,
#0 dumpsys () at ../../kern/kern_shutdown.c:487
#1 0xc0168237 in boot (howto=256) at ../../kern/kern_shutdown.c:316
#2 0xc0168675 in panic (fmt=0xc02db260 m_copydata, offset size of
mbuf
chain) at ../../kern/kern_shutdown.c:595
#3 0xc018576e in m_copydata (m=0xc1560d00, off=6144,
Hi,
#!/bin/bash
while :; do
ping -f -s 65467 ip_addr
done
So probably mbuf exhaustion.
Here's the NIC info:
[EMAIL PROTECTED]:9:0: class=0x02 card=0x00ed16ec chip=0x12161113 rev=0x11
hdr=0x00
vendor = 'Accton Technology Corporation'
device = 'EN5251-Based Fast
From: David Rhodus [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: Martin Blapp [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: Re: 4.8-stable kernel panic
Yes, I don't think this email will make it to hackers@ because all the
email from
my office gets drop because freebsd.org''s
For those who don't know what I'm talking about, try executing host
thisdomainhasneverexistedandneverwill.com, or any other domain you'd
care to make up in .com or .net. Verisign has abused the trust placed
in them to operate a root name server, by creating wildcard A records
directly under
On 16 Sep 2003 at 10:23, Clifton Royston wrote:
In the meantime I'm trying to figure out if there's some simple hack
to disregard these wildcard A records, short of requesting zone
transfers of the root nameservers (e.g. via peering with
f.root-servers.net) and purging those records out of
At 10:23 AM -1000 9/16/03, Clifton Royston wrote:
In the meantime I'm trying to figure out if there's some
simple hack to disregard these wildcard A records, short of
requesting zone transfers of the root nameservers (e.g. via
peering with f.root-servers.net) and purging those records
out of the
On Tue, 16 Sep 2003, Clifton Royston wrote:
In the meantime I'm trying to figure out if there's some simple hack
to disregard these wildcard A records, short of requesting zone
transfers of the root nameservers (e.g. via peering with
f.root-servers.net) and purging those records out of the
* Dan Langille [EMAIL PROTECTED] [030916 16:46]:
On 16 Sep 2003 at 10:23, Clifton Royston wrote:
In the meantime I'm trying to figure out if there's some simple hack
to disregard these wildcard A records, short of requesting zone
transfers of the root nameservers (e.g. via peering with
On 16-Sep-2003 Dan Langille wrote:
On 16 Sep 2003 at 10:23, Clifton Royston wrote:
In the meantime I'm trying to figure out if there's some simple hack
to disregard these wildcard A records, short of requesting zone
transfers of the root nameservers (e.g. via peering with
On Fri, 12 Sep 2003, Aaron Wohl wrote:
We have two systems with this motherboard. Id recommend looking for a
different motherboard. If you find one in the same class let me know
what you find Im looking too for our next set of servers.
Aaron, I just ordered a supermicro X5DP8 board (and
On 2003-Sep-14 18:54:40 +, Zane Long Quentine [EMAIL PROTECTED] wrote:
the version of FreeBSD is 4.8
use the dmesg, I found some related information about my usb strorage
--begin here
umass0: Digital , Inc. TGE UFD MP3 Player., rev 1.10/0.01, addr 2
umass0: Get Max Lun not supported (IOERROR)
I'm trying to implement a serial protocol that is timing sensitive.
I'm noticing things like drains and reads and blocking until the
next kernel tick. I believe this is due to the lbolt sleeps
in the tty.c code.
It looks like I can avoid these sleeps if isbackground() returns
false, however I
In message: [EMAIL PROTECTED]
Soeren Straarup [EMAIL PROTECTED] writes:
: Can there be more than one 'vendor SOMETHING 0x0001 Desc' with different
: SOMETHING and Desc in src/sys/dev/usb/usbdevs ?
Of course. That's the whole point of having a vendor space that's
assigned by a central
OpenSSH_3.6.1p1 FreeBSD-20030916, SSH protocols 1.5/2.0, OpenSSL 0x0090701f
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Rhosts Authentication disabled, originating port will not be trusted.
debug1: Connecting to 10.10.1.23 [10.10.1.23] port 22.
debug1: Connection established
In message: [EMAIL PROTECTED]
Takanori Watanabe [EMAIL PROTECTED] writes:
: Hi,There is a problem when PCMCIA related stuff
: is used as module, ATA CF is not recognized.
:
: This is because PCMCIA atachment is not compiled
: when pccard(4) is not compiled in.
:
: To fix it, we have
I think we should put a filter for this nonsense into the base
system. Hack the resolve to filter out the adddress, and hack bind to
filter it out too. that way we can leverage our position in the name
servers in the world to do something about this BS.
Warner
On 16-Sep-2003 M. Warner Losh wrote:
I think we should put a filter for this nonsense into the base
system. Hack the resolve to filter out the adddress, and hack bind to
filter it out too. that way we can leverage our position in the name
servers in the world to do something about this BS.
In message: [EMAIL PROTECTED]
John Polstra [EMAIL PROTECTED] writes:
: On 16-Sep-2003 M. Warner Losh wrote:
: I think we should put a filter for this nonsense into the base
: system. Hack the resolve to filter out the adddress, and hack bind to
: filter it out too. that way we can
* M. Warner Losh [EMAIL PROTECTED] [030916 20:12]:
I think we should put a filter for this nonsense into the base
system. Hack the resolve to filter out the adddress, and hack bind to
filter it out too. that way we can leverage our position in the name
servers in the world to do something
* John Polstra [EMAIL PROTECTED] [030916 20:14]:
On 16-Sep-2003 M. Warner Losh wrote:
I think we should put a filter for this nonsense into the base
system. Hack the resolve to filter out the adddress, and hack bind to
filter it out too. that way we can leverage our position in the name
. It's just that
it was a noise-level problem until it affected .com and .net)
The ISC has announced it expects to have a patch by Wednesday.
That's better than I'd hoped. Thanks for all the feedback I've got,
BTW.
http://apnews.excite.com/article/20030916/D7TJOF3G0.html
-- Clifton
position in the name
servers in the world to do something about this BS.
ISC claims they'll have a patch ready for the stock BIND sometime in the
next few days for this. All we need to do is import it :)
In particular, see:
http://apnews.excite.com/article/20030916/D7TJOF3G0.html
Though
I've had preliminary success with this patch. More testing needs
to be done, but in the meantime, I would appreciate reviews and
comments. The patched code is available from
http://beta.freebsddiary.org/tmp/uthread_write.c and the patch
appears below.
In short, the logic has been changed to
On Tue, Sep 16, 2003 at 06:04:17PM -0600, M. Warner Losh wrote:
Agreed. but it wouldn't be too hard to determine at boot/hourly doing
a bogus query to find the address of the moment. Even they would be
hard pressed to change things more than hourly.
In the document VeriSign distributes on
On Tue, 16 Sep 2003, Dan Langille wrote:
I've had preliminary success with this patch. More testing needs
to be done, but in the meantime, I would appreciate reviews and
comments. The patched code is available from
http://beta.freebsddiary.org/tmp/uthread_write.c and the patch
appears
M. Warner Losh wrote:
In message: [EMAIL PROTECTED]
John Polstra [EMAIL PROTECTED] writes:
: On 16-Sep-2003 M. Warner Losh wrote:
: I think we should put a filter for this nonsense into the base
: system. Hack the resolve to filter out the adddress, and hack bind to
: filter it out
On Tue, Sep 16, 2003 at 01:45:42PM -0500, William Michael Grim wrote:
What the hell are you talking about? Thanks for not giving us any info
about your problem.
I think he was assuming that we were all aware of the OpenSSH exploit
that was just announced. Mr. Brooks would do well to read
* Clifton Royston [EMAIL PROTECTED] [030916 20:22]:
I found most of the discussion seems to be going on on NANOG.
(Apparently they're not the first, BTW; some CC TLDs have been doing it
for a while, as have some of the new TLDs like .museum. It's just that
it was a noise-level problem
On 17-Sep-2003 M. Warner Losh wrote:
In message: [EMAIL PROTECTED]
John Polstra [EMAIL PROTECTED] writes:
: On 16-Sep-2003 M. Warner Losh wrote:
: I think we should put a filter for this nonsense into the base
: system. Hack the resolve to filter out the adddress, and hack bind to
Hi all
I've got a pppoe gateway with freebsd 5.1-release and two nics : a lan nic
(RFC 1918) and a pppoe nic.
(the same thing append with a 4.7-release...and older versions of nmap)
When I launch nmap to test a machine on the inside : fine !
But when I launch nmap to test a machine on the
* John Polstra [EMAIL PROTECTED] [030916 21:27]:
True, we could probably do it. I guess we'd have to generate a few
random and unlikely queries, try them, and see if all/most of them
resolve to the same address. Or maybe the to the same small set of
addresses, depending on how determined
On 17-Sep-2003 Michael Edenfield wrote:
* John Polstra [EMAIL PROTECTED] [030916 21:27]:
True, we could probably do it. I guess we'd have to generate a few
random and unlikely queries, try them, and see if all/most of them
resolve to the same address. Or maybe the to the same small set of
46 matches
Mail list logo
