Matthew N. Dodd wrote:
On Thu, 25 Apr 2002, Peter Wemm wrote:
This is well known. If we recieve an ARP frame before we sent one, then
we print this. eg: a broadcast ARP packet will trigger it. dhclient
etc use bpf etc so ARP isn't initialized at this point.
We could just put this
On 25-Apr-2002 Jan Stocker wrote:
My -current system gives me a
swi_net: unregistered isr number: 18.
too. I cant find any reply to this old subject. May anyone know where it
comes from?
It seems to trigger whenever there is traffic while the IP is 0.0.0.0,
even for non-DHCP stuff.
John Baldwin wrote:
On 25-Apr-2002 Jan Stocker wrote:
My -current system gives me a
swi_net: unregistered isr number: 18.
too. I cant find any reply to this old subject. May anyone know where it
comes from?
It seems to trigger whenever there is traffic while the IP is
John Baldwin wrote:
On 25-Apr-2002 Jan Stocker wrote:
My -current system gives me a
swi_net: unregistered isr number: 18.
too. I cant find any reply to this old subject. May anyone know where it
comes from?
It seems to trigger whenever there is traffic while the IP is 0.0.0.0,
On Thu, 25 Apr 2002, Peter Wemm wrote:
This is well known. If we recieve an ARP frame before we sent one, then
we print this. eg: a broadcast ARP packet will trigger it. dhclient
etc use bpf etc so ARP isn't initialized at this point.
We could just put this block of code from
If this might be of interest:
kernel built 07.feb
at boot time...
| Doing initial network setup: hostname.
* swi_net: unregistered isr number: 18.
| xl0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500
| options=3rxcsum,txcsum
[...]
This is (probably) the dhclient being run at
If this might be of interest:
kernel built 07.feb
at boot time...
| Doing initial network setup: hostname.
* swi_net: unregistered isr number: 18.
| xl0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500
| options=3rxcsum,txcsum
[...]
This is (probably) the dhclient being run at
