Re: 8.0-BETA4 not responding to ARP for published entries

2009-09-14 Thread Hiroharu Tamaru
.0.11 is-at 00:16:d3:xx:xx:xx > > As you can see from the above, > 'arp -s 192.168.0.12 auto pub' on 8.0-current host > seems not to be producing proxy arp's. > > What am I missing? > > Thanks. > -- > Hiroharu Tamaru ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

Re: 8.0-BETA4 not responding to ARP for published entries

2009-09-15 Thread Hiroharu Tamaru
902/amd64 as expected. Thanks! Could it be considered important enough to make it into 8.0-RELEASE at this final stage? Hope it will, but if not, please consider to point it out in the release note. Hiroharu Tamaru > -Original Message- > From: owner-freebsd-...@freebsd.org on behal

Re: 8.0-BETA4 not responding to ARP for published entries

2009-09-15 Thread Hiroharu Tamaru
Hi, At Tue, 15 Sep 2009 17:05:46 -0700, Li, Qing wrote: > Hi, > > I have committed the code into -CURRENT and it's now merged into 8 > Release > branch. So RC1 should contain the fix. > > -- Qing Excellent! I'll try RC1 when it comes out. Thanks. Hiroharu Ta

Can ASPM be disabled on 82573 to allow Jumbo Frames with em(4)?

2009-02-19 Thread Hiroharu Tamaru
Hi I am not sure if I am understanding things right, but is it possible to forcibly disable ASPM in em(4) for 82573 devices? What I wanted to do is to use Jumbo Frames for these NICs and I saw in sys/dev/e1000/if_em.c that says: | static int | em_ioctl(struct ifnet *ifp, u_long command, caddr_t

proxy arp on 8.0-current?

2009-04-23 Thread Hiroharu Tamaru
7; on 8.0-current host seems not to be producing proxy arp's. What am I missing? Thanks. -- Hiroharu Tamaru ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

Re: PCCard Problem (Telecom Device SuperSocket HPC100)

2001-10-13 Thread Hiroharu Tamaru
:04:09 +0900 From: Hiroharu Tamaru <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Message-ID: <[EMAIL PROTECTED]> Warner and I concluded it to be very likely an "ed" driver problem that became visible after Warner's MFC of Cardbus bridge PCI interrupt routing code, but since