Charles Sprickman wrote
in <4df9970d.5000...@bway.net>:
sp> -Edit rc.conf to include your IPv6 IP(s) and default route, specify
sp> which interfaces will run IPv6, and enable IPv6:
sp>
sp> ipv6_enable="YES"
sp> ipv6_network_interfaces="lo0 bce1"
sp> ipv6_defaultrouter="2001:xxx:::1"
sp> ipv
Just wanted to summarize after I was able to watch all this on another
host. I ran tcpdump on the host that I was adding to the IPv6 network
as well as on another host that would see all the broad^H^H^H multicast
traffic for neighbor discovery.
First I'll just lay out what appears to be the corre
"Bjoern A. Zeeb" wrote
in <6fe95ac6-ccb2-45b0-8347-ab31283ee...@lists.zabbadoz.net>:
bz> I am not entirely sure I like "slaac" or "dhcp4". I wonder if progname
bz> would be sufficient in call cases either (I could well see a "dhclient"
bz> or another "fooapp" that can handle both v4 and v6) bu
Hi,
> On Wed, 15 Jun 2011 20:21:15 +
> "Bjoern A. Zeeb" said:
bzeeb> having helped some friends running penguin OS in the past I have been
bzeeb> confronted with what OpenSuse does. Apart from a completely over
bzeeb> engineered framework they have the ability to sort entries by ifn
Hi,
On Wed, 15 Jun 2011 20:21:15 +
"Bjoern A. Zeeb" wrote:
> On Jun 15, 2011, at 4:53 PM, Hiroki Sato wrote:
>
> Hi,
> > ...
> > My proposal is adding a string representing the information source
> > to the interface id which is used for resolvconf(8). Specifically,
> > I would like to pro
> Pawel wrote:
>> I had notices some GSOC project in maybe 2008
>> on MPLS. There doesn't seem to be much current
>> talk of this. So I am unsure, excluding the GSOC,
>> of the overall picture of MPLS in FreeBSD.
>> Is there any current work? Or directions planned?
>> Overall interest / demand?
>
On Jun 15, 2011, at 4:53 PM, Hiroki Sato wrote:
Hi,
> ...
> My proposal is adding a string representing the information source to
> the interface id which is used for resolvconf(8). Specifically, I
> would like to propose to use the following syntax throughout
> utilities that update /etc/resolv.
LRO is not ON by default so there's no need to disable it :)
I've just realized that I need to add HWTSO to the igb driver so VLAN's get
use it, I will do that
shortly.
In the data you displayed earlier you had two different driver revisions on
each end of your link,
I suggest you get the latest
Hi,
I would like your comments about the following issue and proposal.
The background is as follows. The resolvconf(8) utility has been
imported some time before to handle update of /etc/resolv.conf by
using multiple RDNSS (recursive DNS server) information sources. The
possible sources ar
IIRC it needs to be in sysctl.conf, so try that.
- Original Message -
From: "Mario Spinthiras"
To:
Cc: "Jack Vogel"
Sent: Wednesday, June 15, 2011 9:56 AM
Subject: Re: strange igb interface performance problems
Hi,
To disable LRO I tried ifconfig igb1 -lro and I also tried adding
Hi,
To disable LRO I tried ifconfig igb1 -lro and I also tried adding the
sysctl params in loader.conf. Both did not result in any change.
I'm going to have to find a way to use the new igb driver I guess, hoping
that would fix it maybe.
Regards,
Mario
11 matches
Mail list logo