Hi!
I just want to let you know that I have solved my problem by means of
tcpdump.
I have an old attempt in my Xservers file. As my DNS server was cleaned
and I totally forget this attempt I was trying to reach a very old
machine which is not part of my network anymore.
Thanks.
Phil.
To U
> Original Message <<
On 1/19/01, 11:16:50 AM, Dominic Mitchell <[EMAIL PROTECTED]> wrote
regarding Re: ports:
> On Thu, Jan 18, 2001 at 10:02:23PM -0500, Christopher K Davis wrote:
> > W Gerald Hicks <[EMAIL PROTECTED]> writes:
> >
> > > This syndrome is often c
I've got a problem that, because of the nature of the problem and the
environment I can't give better details on.
When I cvsup'ed to -stable last week, (I was at 4.2 stable as of sometime
in December at that point) I rebooted after installing the new kernel and
when attempting to mount the filesy
I have a Dell PowerEdge server. Using FreeBSD-4.2
(recently built and updated), I can only force the
serial console IF I have a keyboard plugged in. It
doesn't matter what flags I use -P -D -h or just -h.
Is this a bug, or?
_F
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscri
:Short term, though, I liked the suggestion about stuffing an entry in
:/etc/hosts to work around the broken domains' DNS problems, and that does
:work for me for now. So at least I have an ugly workaround.. much less
:ugly than restarted named every few hours though. Next, I'm going to
:start c
At 11:48 AM 1/19/01 -0800, Matt Dillon wrote:
> Don't do that!
>
> If the broken hosts have at least one working name server, then you
> can use options in named.conf to make bind ignore the broken servers.
> The bind documentation has all the information you need to make this
>
:
:At 11:48 AM 1/19/01 -0800, Matt Dillon wrote:
:
:> Don't do that!
:>
:> If the broken hosts have at least one working name server, then you
:> can use options in named.conf to make bind ignore the broken servers.
:> The bind documentation has all the information you need to mak
The Intel PRO/1000F NIC does not seem to be fully supported by the wx
driver. I have directly connected two of these cards with a fiber patch
cable, link lights are on, and the driver tells me "wx0: gigabit link now
up".
However, pings across the link fail, because packets are simply swallowed:
F
Lars Eggert wrote:
> The Intel PRO/1000F NIC does not seem to be fully supported by the wx
> driver.
Sorry for not mentioning this in the original post: This card uses the
Intel 82543GC chip.
--
Lars Eggert <[EMAIL PROTECTED]> Information Sciences Institute
http://www.isi.edu/lar
Salvo Bartolotta <[EMAIL PROTECTED]> writes:
> You may wish to take a look at the cvsup FAQ found on
> http://www.polstra.com, and pay attention to the discussion in Q12,
> Q13.
[...]
> Both approaches (the tool and the correct synching procedure) have
> been discussed countless times on these li
Lars Eggert <[EMAIL PROTECTED]> probably said:
> Lars Eggert wrote:
> > The Intel PRO/1000F NIC does not seem to be fully supported by the wx
> > driver.
> Sorry for not mentioning this in the original post: This card uses the
> Intel 82543GC chip.
I realise this isn't very useful to you for gett
I'll look at it when I next spend a couple of days on this NIC (hopefully next
week).
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
Not sure if someone else has run into this, but with 4.2-STABLE circa
1/16/2000's sshd I get the following behavior:
othermachine% ssh -t 4.2stable-box ls
4.2stable-box%
That is, from any other machine (running ssh-1.2.27 or various versions of
openssh), trying to run a command via ssh while us
13 matches
Mail list logo
