On Thu, Aug 23, 2001 at 04:53:26PM -0400, Barney Wolff wrote:
>
> As another heavy nmap user, I'd vote just the other way. It's useful
> to differentiate between a reset coming back from the destination host
> and an unreachable from a firewall/router-acl. Ordinary apps probably
> don't care all
Ian Dowse writes:
> In message <[EMAIL PROTECTED]>, Warner Losh writes:
> >
> >I think that might be due to a bug in the shared interrupt code that
> >Ian Dowse sent me about earlier today.
>
> Just to add a few details - there is a bug in the update_masks()
> function in i386/isa/intr_mac
As another heavy nmap user, I'd vote just the other way. It's useful
to differentiate between a reset coming back from the destination host
and an unreachable from a firewall/router-acl. Ordinary apps probably
don't care all that much about why a connection could not be established,
and just rep
>thank you for writing!
>My problem is that, when trying a tunnel between a Linux box to the
>FreeBSD box, in the Linux routing table, the nexthop address
>is fe80::8007:54. (here 8007:54 is in hexadecimal the IPv4 address of the
>FreeBSD box -or sit1 for Linux (endpoint of the tunnel).
>This i
In message <[EMAIL PROTECTED]>, Warner Losh writes:
>
>I think that might be due to a bug in the shared interrupt code that
>Ian Dowse sent me about earlier today.
Just to add a few details - there is a bug in the update_masks()
function in i386/isa/intr_machdep.c that can cause some interrupts
t
On 23 Aug, Bill Paul wrote:
> Ok, I think I found the bug. There was a problem with the way I was
> loading the hash table for the multicast filter. The chip actually
> uses 4 16-bit registers, not two 32-bit ones. Please apply the patch
> at:
>
> http://www.freebsd.org/~wpaul/Sundance/ste.diff
>
On 23 Aug, Bill Paul wrote:
> > IPv6 autoconfiguration with -STABLE and Dlink DFE-550TX network adapters is
> > not working as it should.
>
> I need you do "pciconf -l | grep ste"
All cards have the same behavior. Here you go:
ste0@pci0:15:0: class=0x02 card=0x10021186 chip=0x10021186 rev=0
Ok, I think I found the bug. There was a problem with the way I was
loading the hash table for the multicast filter. The chip actually
uses 4 16-bit registers, not two 32-bit ones. Please apply the patch
at:
http://www.freebsd.org/~wpaul/Sundance/ste.diff
# cd /tmp
# fetch http://www.freebsd.org
Hi,
Are you sure that all your nodes are running 10 Mbit or 100 Mbit ?
Will the hub get confused by a mixture of 10 and 100 Mbit cards? I have recently
seen a case like this (on NetBSD 1.5 sending NS).
Try using a cross-over cable between your router and each of your hosts - one at
a time. This w
> Hi,
>
> IPv6 autoconfiguration with -STABLE and Dlink DFE-550TX network adapters is
> not working as it should.
>
> My network topology is simple : 3 machines on the same ethernet segment,
> connected by a 10/100 hub. They are running 4.4-RC as of today and use the
> same NIC, a Dlink DFE-550T
Hello Peter,
Now I used the tftp-hpa-0.21 client with a tftp server (SuSE 6.4,
where a tftpd runs in whose binary code I found:
tftp-hpa $Id: tftd.c,v 1.4 1999/09/26 07:12:54 hpa Exp).
I inserted in tftp/tftp.c after line
285 if (dp->th_block == block) {
following lines:
if (block == 1) {
>> I hope this time (the second attempt) somebody can help me, because I know
>>other users have the solution.
>>What do I need to do with my kernel or configuration files or whatsoever
>>in order to be able to see a Link Address
>>
>>fe80::8007:544%gif0 link#...
>>
>>8007:544 is derived from
> I hope this time (the second attempt) somebody can help me, because I know
>other users have the solution.
>What do I need to do with my kernel or configuration files or whatsoever
>in order to be able to see a Link Address
>
>fe80::8007:544%gif0 link#...
>
>8007:544 is derived from the IPv4
Hello all,
I hope this time (the second attempt) somebody can help me, because I know
other users have the solution.
What do I need to do with my kernel or configuration files or whatsoever
in order to be able to see a Link Address
fe80::8007:544%gif0 link#...
8007:544 is derived from the
On 23 Aug, [EMAIL PROTECTED] wrote:
>
> >IPv6 autoconfiguration with -STABLE and Dlink DFE-550TX network adapters is
> >not working as it should.
>
> my guess is that either of the machines (the router, or the end node)
> have a broken multicast packet filter on the card, or the driv
>IPv6 autoconfiguration with -STABLE and Dlink DFE-550TX network adapters is
>not working as it should.
my guess is that either of the machines (the router, or the end node)
have a broken multicast packet filter on the card, or the driver is
broken in terms of multicast p
Hi,
When a link address enters the stale state you have added a nd6_gctimer ( garbage
collection timer) so that the entry is removed after the address time expires in the
stale state.
I found that the value of this is one day. Is this the default value. Or this value
can changed by the system
Hi,
I found that in the rtadvd daemon code there is a function which is called to join to
the all router multicast address( ff02::02).
My doubt is if rtadvd is disabled for a router then whether it will join the all
routers multicast list?
one reason i find for such a implementation is that jo
Hi,
IPv6 autoconfiguration with -STABLE and Dlink DFE-550TX network adapters is
not working as it should.
My network topology is simple : 3 machines on the same ethernet segment,
connected by a 10/100 hub. They are running 4.4-RC as of today and use the
same NIC, a Dlink DFE-550TX (ste driver).
19 matches
Mail list logo
