for ATM NICs, please speak up so we can discuss a
different timeline.
The proposed big removal commit for NgATM is:
https://reviews.freebsd.org/D38879
ng_atmllc is removed in
https://reviews.freebsd.org/D38880
Deprecations and a few cleanups are linked in the stack of commits.
Thanks,
Brooks
ked for deletion prior to
FreeBSD 13.
Unless there is surprising outcry I plan to add (and MFC) deprecation
notices in about a week's time and remove the driver shortly thereafter.
-- Brooks
[0] I noticed today that part of the ndis 802.11 ioctl handler has been
broken since 2005.
signature.asc
Description: PGP signature
On Tue, Apr 07, 2020 at 07:32:37PM +0200, Hans Petter Selasky wrote:
> On 2020-04-07 19:26, Poul-Henning Kamp wrote:
> >
> > In message <20200407172151.gb72...@spindle.one-eyed-alien.net>, Brooks
> > Davis writes:
> >
> >> My question for t
latter I'll reduce my diffs locally.
-- Brooks
[0] To ensure use of the accessors in the kernel we don't define the
macros used to make ifr_ifru pseudo-transparent when _KERNEL is defined.
signature.asc
Description: PGP signature
On Tue, Oct 15, 2019 at 06:41:36AM +0800, Ben Woods wrote:
> On Sat, 12 Oct 2019 at 1:45 am, Brooks Davis wrote:
>
> > DHCP is one of the most exposed attack surfaces in existence. We expect
> > it to take input from explicitly untrustworthy networks and perform
> > ac
rm
actions as root. It might be OK to import this as a stopgap only
supporting IPv6, but without capsicum or privilege separation (as noted
elsewhere in the thread) it seems unlikely to be a good idea enable it
by default or replace the existing IPv4 dhclient.
-- Brooks
signature.asc
Description: PGP signature
eebsd/freebsd/pull/398
The FCP can be viewed at:
https://github.com/freebsd/fcp/blob/master/fcp-0101.md
-- Brooks
signature.asc
Description: PGP signature
On Fri, Feb 01, 2019 at 04:00:50AM -0800, Rodney W. Grimes wrote:
> > On Thu, Jan 31, 2019 at 11:43:44PM +, Brooks Davis wrote:
> > > We are currently planning to remove the following less-popular 10/100
> > > Ethernet drivers in the March/April timeframe:
> > &g
can not report them this way, please feel free to contact me
directly.
-- Brooks
[0] I've received a couple reports of ae(4) devices, but still not 5 of
them.
signature.asc
Description: PGP signature
members and fcp-editors explicit if that was desirable.
> We could add that once the document is submitted to core
> any change to it between submitting and vote by core requires
> core to be involved, even if it is simply an ack of a change
> has been made to what was submitted.
I agree. We'll need to think on how best to do this.
-- Brooks
signature.asc
Description: PGP signature
options=82808
> > > > > ether 00:40:d0:5e:26:38
> > > > > inet 192.168.91.65 netmask 0xff00 broadcast 192.168.91.255
> > > > > media: Ethernet autoselect (100baseTX
> > > )
> > > > > status: ac
; > )
> > > status: active
> > >
> > > Which currently runs 8.4-RELEASE & eg xrandr, but I'll upgrade soon
> > > when I also configure it to receive from a raspberry-pi TV VPN server.
> >
> > The above was a typo. vr is on the the ST
.91.255
> media: Ethernet autoselect (100baseTX
> )
> status: active
>
> Which currently runs 8.4-RELEASE & eg xrandr, but I'll upgrade soon
> when I also configure it to receive from a raspberry-pi TV VPN server.
The above was a typo. vr is on the the STAY list.
-- Brooks
signature.asc
Description: PGP signature
h a failure?
> If so, should it be better promoted or would it be pointless?
In theory it would provide valuable data, but in practice the website is
broken and unable to produce device data. I've asked multiple times for
it to be fixed. It would be great if it worked and we could use it.
-- Brooks
signature.asc
Description: PGP signature
irq 16 at device 0.0 on pci1
There are no plans to touch such drivers.
-- Brooks
signature.asc
Description: PGP signature
omeone to modernize the driver if
> needed.
It's definitly on the STAY list at this point. If you could help get it
update that would be great, especially if it's still shipping (a very
useful datapoint).
-- Brooks
signature.asc
Description: PGP signature
n and remove those notices
at and upto (or even after) removal from the tree.
In an effort to save some email, we will be moving rl(4) to the list of
drivers to STAY as it has proved itself to be popular. A few others
appear to be well on their way so keep the reports coming.
Thanks,
Brooks
P.S. A
list.
The full FCP-0101 is included below.
-- Brooks
---
authors: Brooks Davis
state: feedback
---
# FCP 101: Deprecation and removal of 10/100 Ethernet drivers
Deprecate most 10 and 10/100Mbps Ethernet drivers and remove them before
FreeBSD 13.
## Problem Statement
Each network driver create
ing each individual device isn't usually all that
high, but it's really frustrating to spend the majority of time on an
infrastructure change fixing issues in devices that shouldn't have
survived the last release branch (or the one before that). Devices or
technologies that failed in the market are the worst because they tend
to have drivers with cargo-cult copy-and-paste from the wrong example
that never gets fixed.
-- Brooks
signature.asc
Description: PGP signature
; Arcnet coming soon?
> and probably FDDI?
That's my plan. I started with token ring as it doesn't even have
drivers (Arcnet and FDDI have one driver each, but ISA and 32-bit PCI
respectively AFACT).
-- Brooks
signature.asc
Description: PGP signature
I have posted a revision which removes support for token-ring networking
from the tree. There have been no such devices for some time.
https://reviews.freebsd.org/D14875
-- Brooks
signature.asc
Description: PGP signature
any significant
> > users of this device and plan to remove it from FreeBSD-12 if not.
> >
> > -- Brooks
>
> Neterion has been acquired by exar.
> https://www.eetimes.com/document.asp?doc_id=1173009
>
> They have the datasheet for the Xframe-I here:
>
The nxge(4) driver for the Neterion Xframe-I and Xframe-II 10GbE
adapters has obvious bugs (by inspection) and it doesn't appear the
company exists any more. We'd like to see if there are any significant
users of this device and plan to remove it from FreeBSD-12 if not.
-- Brooks
sig
On Sun, Apr 30, 2017 at 12:47:51AM +0800, Julian Elischer wrote:
> On 28/4/17 2:00 am, Brooks Davis wrote:
> > As previous threatened, I've removed support for NATM (as well as a
> > remarkable number of remnants of the old ATM framework). One piece
> > that still rema
attach to physical interfaces and didn't depend on the NATM
interface code so I left them alone in the first cut. My question
is, are they useful without physical interfaces? If so, keeping them
doesn't appear to have a high support burden. If not, we should remove
them.
-- Brooks
signa
The fact that FreeBSD 11 has almost five years of support left is part
of what makes this a good time to remove support from 12. Updating 11
to support newer cards certainly makes sense.
-- Brooks
On Fri, Apr 07, 2017 at 06:30:05AM -0700, Kevin Bowling wrote:
> For consideration, stable/11 w
-- Brooks
signature.asc
Description: PGP signature
Thanks, I've forwarded a copy to the list, but given that there were zero
non-spam messages in 2016, only three legitimate messages (that no one
answered) in 2015, and zero in 2014, 2013, and 2012, I think it's safe
to say there are no users.
-- Brooks
On Sun, Feb 19, 2017 at 12:38:
e removing support for these NICs along with the
remaining ATM stack in FreeBSD 12. This will give any existing users
a supported OS until at least September 30, 2021 per our published EOL
date for FreeBSD 11.
Would removal on this schedule cause you realistic hardship? If so,
please let us know.
On Mon, Apr 04, 2016 at 10:37:48PM +, Brooks Davis wrote:
> On Mon, Apr 04, 2016 at 11:29:31AM +, Matt Churchyard via freebsd-net
> wrote:
> > From the little information I can find on the net it seems that valeX:Y is
> > the format for a port on a vale switch.
>
port names are
arbitrary strings, the only constraint being that the full name
must fit within 16 characters.
The manpage is confusing in that the name must be 15 characters plus the
NUL character. Given the other limits, it looks like bdg can be up to 8
characters in practice.
-
ns there.
>
> Great! Please feel free to ask if you need any help from my side.
I'm happy to review or help out as well. The only blocking issue I was
aware of was the local pfsync code not being updated to the netdissect API,
but I've done that.
-- Brooks
>
> Cheers,
>
t has been killed and restarted it can't
know it's on the same network, but in practice you want to try to get
the same lease again and fall back if it turns out you've moved or your dhcp
server is broken and lost state. I don't see how this would hurt anything.
-- Brooks
pgpjSgiUmYg8V.pgp
Description: PGP signature
On Fri, Jul 13, 2012 at 08:41:23AM -0400, John Baldwin wrote:
> [ Adding Brooks, IIRC, he imported the current dhclient ]
>
> On Friday, July 13, 2012 5:48:30 am Peter Jeremy wrote:
> > On 2012-Jul-12 13:41:39 -0700, Yuri wrote:
> > >I have the simplest possible DHCP s
will be run. Conversely,
> stop_if.em0 will also run when rc runs at shutdown.
On many cases you can simply use:
ifconfig_em0="DHCP mediaopt half-duplex"
While DHCP is not an actual ifconfig option we strip it from the list
(along with several other psuedo-arguments) and pass the remainder to
ifconfig. Not all option will work this way, but I believe mediaopt
does.
-- Brooks
pgpzAv7HRBImJ.pgp
Description: PGP signature
gnificant overhead?
I agree with the concern raised by Luigi about intra-branch
compatability. My prefered solution to that would be to MFC the adition
of the accessors pretty much instantly and to commit the changes to
individual drivers seperately to allow them to be merged as needed by
driver maintainers.
-- Brooks
pgpSv3ZgguMK4.pgp
Description: PGP signature
k at best to
be a good reason to disable it. I suspect support for PC-NFS or
something like that may be the reason, but if that's the case it really
doesn't make any sense.
-- Brooks
pgpiiC2vOSyrJ.pgp
Description: PGP signature
lse in practice). Updated patch:
This seems like the right thing to do. I might suggest merging the
userspace changes well before the kernel changes or the results may be
confusing.
-- Brooks
pgpKoueWtQGoS.pgp
Description: PGP signature
o chime in here, and please see
> about adding this to the base system.
Given that this would fix the problems many users see in the current
world order and that it's relativly unintrusive I think it's an ok thing
to add.
-- Brooks
pgpgXYfMAMLjs.pgp
Description: PGP signature
On Thu, Oct 29, 2009 at 11:17:27AM +0200, Artis Caune wrote:
> 2009/10/29 Brooks Davis :
> >> btw, wouldn't it be nice not to bother with loader.conf when using
> >> . syntax?
> >> This patch will load if_vlan automatically in this case:
> >
> > Sor
On Thu, Oct 29, 2009 at 12:31:49AM +0200, Artis Caune wrote:
> 2009/10/28 Brooks Davis :
> > On Wed, Oct 28, 2009 at 03:18:41PM +0100, Sebastian Hyrwall wrote:
> >> Hi
> >>
> >> Now that FreeBSD has support for writing ??, cloned_interfaces="em0.100"
-line in rc.conf for this?
>
> ifconfig_em0.100="" or ifconfig_em0_100="" does not work.
It should be ifconfig_em0_100.
-- Brooks
pgplfREukJbEH.pgp
Description: PGP signature
sense to do. This is mostly a feature for
appliance builders. If I were working on adding the ability to slim down
ifnet to the base system, I'd certainly make this an optional feature,
but there are much fatter targets at the moment.
-- Brooks
pgpHpnEpjLYXD.pgp
Description: PGP signature
301 Moved
> (http://svn.freebsd.org)
>
> Where to from here? Might there be an old-fashioned tarball?
Remove the "viewvc/" portion of the URL and it will work.
-- Brooks
pgpZ3U1NvCrEQ.pgp
Description: PGP signature
> > things be done automatically, but it is bad to remove the
> > ability to do things manually. ?This is UNIX, after all.
>
> Exactly. Both scenarios should probably be supported, but I guess we
> would need to ask brooks for some history on the depreciated warning
> for netwo
> > BMS
>
> Sorry for risking the whole community with a massive heart attack Bruce :)
> Yes, I am writing a driver and yes, it still has a bug or two I guess..
> About sharing it with the rest of the class, that's something I wanted
> to ask you guys: what's the proce
On Fri, Dec 19, 2008 at 05:33:17PM -0500, Jordy Dickinson wrote:
> On Fri, Dec 19, 2008 at 11:46 AM, Brooks Davis wrote:
>
> > On Fri, Dec 19, 2008 at 03:04:55PM +, Rui Paulo wrote:
> > >
> > > On 19 Dec 2008, at 14:19, Jordy Dickinson wrote:
> > >
>
_supplicant instead.
More specifically, setting "authmode wpa" with ifconfig will always be
wrong (unless perhaps someday someone adds a suplicant to the kernel).
If you want WPA to work, you must run wpa_supplicant.
-- Brooks
pgpevFNprr1AB.pgp
Description: PGP signature
ill
cause problems on some networks).
http://svn.freebsd.org/viewvc/base/stable/7/sbin/dhclient/bpf.c?revision=178675&view=markup
-- Brooks
pgpzRHe41QSfA.pgp
Description: PGP signature
Synopsis: [ndis] [patch] with wep enters kdb.enter.unknown, panics
Responsible-Changed-From-To: freebsd-net->thompsa
Responsible-Changed-By: brooks
Responsible-Changed-When: Fri Oct 17 14:17:37 UTC 2008
Responsible-Changed-Why:
thompsa seems to have insight into this problem to assign it to
that there's no entry for dhcp
> or bootp in /etc/inetd.conf
>
> Does someone had an idea about how to fix this problem and having my two
> vlans working with dhclient?
The current dhclinet scripts don't really support this case. In theory if you
removed support for default r
On Tue, Jul 22, 2008 at 07:16:24AM +, Jens Rehsack wrote:
> Brooks Davis wrote:
>> On Mon, Jul 21, 2008 at 10:36:34PM +, Jens Rehsack wrote:
>>> Brooks Davis wrote:
>>>> On Mon, Jul 21, 2008 at 09:30:39PM +0000, Jens Rehsack wrote:
>&g
On Mon, Jul 21, 2008 at 10:36:34PM +, Jens Rehsack wrote:
> Brooks Davis wrote:
>> On Mon, Jul 21, 2008 at 09:30:39PM +, Jens Rehsack wrote:
>>> Brooks Davis wrote:
>>>>> Hi,
>>>>>
>>>>> maybe this question is better asked in
On Mon, Jul 21, 2008 at 09:30:39PM +, Jens Rehsack wrote:
> Brooks Davis wrote:
>>> Hi,
>>>
>>> maybe this question is better asked in this list ...
>>>
>>> I was searching why ports/net/p5-Net-Interface was not working as
>>> expe
0 is shown twice
> and lo0 is not included.
> The same situation on another machine ..
The attachment didn't make it through.
-- Brooks
On Mon, Jul 21, 2008 at 08:39:29PM +, Jens Rehsack wrote:
>
> --- BEGIN ifconfig -a (waldorf)
> em0: flags=8843 metric 0 mtu 1500
>
?
No. It's a large and complex patch an a subsystem (ipsec) that must not
be broken. We're a bit shorthanded in this area, but people have been
working on this for quite some time and IIRC aren't fully comfortable
with the patch yet.
-- Brooks
pgpMrbDJxjxiL.pgp
Description: PGP signature
On Mon, Jun 16, 2008 at 09:22:32PM -0400, Steve Bertrand wrote:
> Steve Bertrand wrote:
>> Brooks Davis wrote:
>
>>> On Mon, Jun 16, 2008 at 08:27:47PM -0400, Steve Bertrand wrote:
>>>>> Is there any way to create, and assign addresses to a if_vlan
>>&g
g_em6.3="inet x.x.x.x netmask x.x.x.x"
>
> ...seems to be the job.
Almost. '.' isn't a valid character in a shell variable. We support '.' by
converting it into _ in shell variables so it should be:
cloned_interfaces="em6.3"
ifconfig_em6_3="inet x.x.x.x netmask x.x.x.x"
-- Brooks
pgpsNMN0pIVH5.pgp
Description: PGP signature
On Fri, Jun 13, 2008 at 01:02:07PM +0200, Kris Kennaway wrote:
> Brooks Davis wrote:
>> On Thu, Jun 12, 2008 at 06:30:05PM -0700, Peter Losher wrote:
>>> Randy Bush wrote:
>>>> this has been a cause of great pain for a lng time.
>>>>
>>>
hould strongly consider adding the rest of it to the base.
-- Brooks
pgpXKYHWCAe5F.pgp
Description: PGP signature
rface, why not add an appropriate
entry to /boot/loader.conf and be done with it?
-- Brooks
> P.S.: Because of the assumption for the interface name that
> ifmaybeload() does, this patch looks more like a hack and probably a
> better way could be found for handling this case. P.S2: If "
On Tue, Apr 22, 2008 at 10:38:31AM -0700, vijay singh wrote:
>
>
> - Original Message
> From: Robert Watson <[EMAIL PROTECTED]>
> To: Brooks Davis <[EMAIL PROTECTED]>
> Cc: vijay singh <[EMAIL PROTECTED]>; freebsd-net@freebsd.org
> Sent: Sunday,
value of the
global ifnet pointer which I'm not sure we can afford to lock. It
would be worth experimenting with rmlocks to see what the impact if of
locking would be.
I'm serious tempted to kill if_grow in favor of some sort of if_index_max
tunable.
-- Brooks
> if_alloc(u_char type)
&g
t did not find it in the ports tree.
> This suggests that perhaps there is a native solution after all, yet
> I can't seem to find it.
>
> Any suggestions?
Sam just comitted support to /etc/rc.d/wpa_supplicant in head to set the
driver to bsd or wired based on the device media
t's wrong, but filing a PR is
unlikely to cause it to change any time soon.
-- Brooks
pgpuuvP7xjChy.pgp
Description: PGP signature
he number of ports can potentially vary then the driver will need to
manage them internally. The unit number allocation framework can take care of
this for you. See alloc_unr(9).
-- Brooks
pgpHsJXaIL14i.pgp
Description: PGP signature
;
> cloned_interfaces="re0.10 re0.11"
> ifconfig_re0="media 100baseTX mediaopt full-duplex"
> ifconfig_re0.10="inet 192.168.60.1 netmask 255.255.255.0"
> ifconfig_re0.11="inet 192.168.100.1 netmask 255.255.255.0"
One small nit. The '.' isn't valid in variable names so the ifconfig_re0.xx
lines need to turn into ifconfig_re0_xx (we compress ./-+ to _).
-- Brooks
pgpNHC7VvZrW6.pgp
Description: PGP signature
On Mon, Feb 11, 2008 at 06:51:58PM +1100, Robert Jenssen wrote:
> Hi Brooks and all,
>
> On Mon, 11 Feb 2008 12:06:26 pm you wrote:
> > On Mon, Feb 11, 2008 at 11:37:21AM +1100, Robert Jenssen wrote:
> > > Hi,
> > > Every so often I have trouble connecting rt2560
> [pri
>
> It seems that devd has started two new dhclients and netif has started its
> own
> pair as well. 1916 is the process id of the bash shell I su'ed from to
> start /etc/rc.d/netif.
Does you still set four processes in the steady state? That shouldn't happen
since starting a second dhclient is supposed to kill the existing one.
There should be two processes per interface due to the privege seperation
model used by dhclient.
-- Brooks
pgpmIcYSRxecs.pgp
Description: PGP signature
e dhclient in /etc/devd.conf?
I wouldn't recommend it unless you never lose association since if you do and
you remove the lines in devd.conf you will end up without a dhclient.
-- Brooks
> Regards,
>
> Rob Jenssen
>
> PS:
>
> "uname -a" shows:
> FreeBSD
ut something to "trigger" them. Isn't there
> some kind of poll or interrupt sequence? I'm on 6.3 RC2 (will upgrade
> to 6.3-RELEASE imminently) but can't imagine this code changed? Does
> this work differently/better in 7.0?
It's known but not well understood and is a driver bug.
-- Brooks
pgpQG4FzFnBrd.pgp
Description: PGP signature
on; this will make my
> laptop that much more useful. ;)
devd already does a lot of this and is used to control dhclient
execution. ifstated from openbsd is also in ports.
-- Brooks
pgpLNkRuzWVxC.pgp
Description: PGP signature
rdinate their changes
with your changes, you need to be working in public. You should ideally
be working in perforce, but at a minimum regular posts discussing
details are required.
Non-public work (existent or not) will not be permitted to delay the
inclusion of desirable features that are
ries/FreeBSD-SA-07:03.ipv6.asc
-- Brooks
pgpI9Syhbp278.pgp
Description: PGP signature
w.vlakno.cz/~rdivacky/linux_socket.patch
>
> I have a report that it helps some java program. please review it so
> it can be commited
Looks fine at a glance.
-- Brooks
pgp8F7bBmyMmz.pgp
Description: PGP signature
uire as little configuraiton as possible. Ideally,
you could be able to get a connection if it's possible with nothing but
the IP address(es) of the friendly server and the IPoDNS zone.
Also, while it's less useful in the UDP case, the TCP case could be
extremely useful for setting up a
d ports to avoid
allocating. A more (over)engineered solution holds some attraction, but
I'm not yet convinced the fact that it could exist precludes the current
implementation.
-- Brooks
pgpaKGlHHOssb.pgp
Description: PGP signature
re@ soon so any feedback would be great.
Conceptually the patch seems right. A couple comments below (I saw the strlcpy
change).
-- Brooks
> Index: ifconfig.c
> ===
> RCS file: /home/ncvs/src/sbin/ifconfig/ifconfig.
correct. We really want dhclient to leave any
addresses other than ones it sets alone so always using alias directives
is probably correct.
-- Brooks
> Sean
>
> P.S. Please Cc me since I am not on this list.
> --
> [EMAIL PROTECTED]
Content-Description: dhclient-script patch
>
On Thu, Apr 05, 2007 at 06:46:44PM +0300, Mike Makonnen wrote:
> On Tue, Apr 03, 2007 at 06:14:23PM -0500, Brooks Davis wrote:
> > > - You can now do things like:
> > > # Start/Stop IPv6 on all interfaces
> > > /etc/rc.d/netif (start|stop) ip6
> > >
eedback on how stopping IPv6 on an interface
> should be handled. In rc.d/network_ipv6 it was handled at all.
> Currently, it goes through and deletes all
> IPv6 addresses on the interface.
I'd say if ipv6_enable=NO, attempting to configure IPv6 on an interface
should fail. If they turn it on, I'm not sure what the best approach
is. Not worrying about it may well be most appropriate.
-- Brooks
pgpK4bNqoXd4y.pgp
Description: PGP signature
e sense to use the sysctl
> net.link.generic.ifdata subtree. We have already IFDATA_DRIVERNAME there
> which returns a string. Could be IFDATA_DESCRIPTION (4). This would
> probably be more in line with the management nature of the data. Just a
> thought... Would be slightly ea
odule ABIs in current at any time and
there's no chance modules built on RELENG_6 will work on RELENG_7
trees anyway.
-- Brooks
pgpBjF7OcidMq.pgp
Description: PGP signature
t;
> scp(1) isn't really the best way to test this; the XBOX CPU cannot
> satisfy a 100mbit link using scp(1). FTP would be a much better idea,
> preferably with a large file.
Much better (unless you want to see the effect of disk I/O) would be
something like benchmarks/netpipe
D? I can use 6.1, 7.1, any version.
The feature you're looking for is divert(4) sockets. You use IPFW to
decide which packets to divert to userland and can reinject them as
needed.
-- Brooks
pgp8AsdXbAOTf.pgp
Description: PGP signature
On Sat, Nov 04, 2006 at 02:46:30AM +, MQ wrote:
> 2006/11/3, Brooks Davis <[EMAIL PROTECTED]>:
> >
> >On Fri, Nov 03, 2006 at 09:46:47AM +, MQ wrote:
> >> 2006/11/2, Brooks Davis <[EMAIL PROTECTED]>:
> >> >
> >> >O
Max Laier <[EMAIL PROTECTED]>:
> >
> >Hello "MQ",
> >
> >your email client is seriously mis-configured, could you please look into
> >this as it is a bit annoying.
> >
> >On Friday 03 November 2006 10:46, MQ wrote:
> >> 2006/11/2, Brooks D
On Fri, Nov 03, 2006 at 09:46:47AM +, MQ wrote:
> 2006/11/2, Brooks Davis <[EMAIL PROTECTED]>:
> >
> >On Thu, Nov 02, 2006 at 08:26:27AM +, . wrote:
> >> Hi,
> >>
> >> I am confused by the use of inet_ntoa function in the kernel.
>
ons
are ugly. What about extending log and printf to understand ip4v
addresses? That's 90% of the uses and the others appears to have
buffers already.
-- Brooks
pgpuUAXj3nhuM.pgp
Description: PGP signature
ripts and
dhclient-script to allow the local network to override the name if
desired while insuring that the system had a name at all times (required
for laptop use). I'd take patches to do this.
-- Brooks
P.S. hacking this into rc.local won't work longterm because addresses
will be assigned in a totally different context.
pgpyq5l04p644.pgp
Description: PGP signature
ould actually
work if the vlan module is loaded or compiled in.
-- Brooks
pgpvTPTZll7t3.pgp
Description: PGP signature
ght be a good
approach for this sort of thing. The current method of service matching
based on port and protocol could be augmented with the ability to
connect arbitrary "internal" services to arbitrary ports, perhaps via
arguments to the "internal" command. Then you could hook d
ter was temporarily broken and has been fixed.
-- Brooks
pgpHH01RLxHgJ.pgp
Description: PGP signature
denly require it.
It may be that the right thing to do with IPv6 interfaces is to require
that ipv6_ifconfig_ifn be set to something but that would be a change.
In many ways I think the best thing to do is remove plip from GENERIC
and be done with it.
-- Brooks
pgpexrB9hv1pT.pgp
Description: PGP signature
at
drivers will work with kernels older than they are. The only reason the
em code at the tip of 6-STABLE might not build with 6.0 sources is that
it uses some enhancements. If an individual maintainer wants to make
sure their driver will build with any sources they either need to not
use ne
us a "default" table since I find Robert's arguments
compelling, but have applications where a default is needed.
Alternativly ${varname-default_value} syntax could be implemented
alongside AFS semantics.
-- Brooks
P.S. The motivating application in my case is making /tmp a
Synopsis: [patch] ifconfig name does't rename netgraph node in network.subr
Responsible-Changed-From-To: freebsd-rc->freebsd-net
Responsible-Changed-By: brooks
Responsible-Changed-When: Mon Aug 28 12:49:02 UTC 2006
Responsible-Changed-Why:
While the proposed workaround is in network.su
On Fri, Aug 25, 2006 at 10:35:03AM +0900, JINMEI Tatuya / [EMAIL
PROTECTED]@C#:H wrote:
> >>>>> On Thu, 24 Aug 2006 13:42:29 -0500,
> >>>>> Brooks Davis <[EMAIL PROTECTED]> said:
>
> >> Um...I'm not sure if this is even possible. Let&#
ense. From that perspective the namespace really should
be xxx..local internally and xxx.local on the wire. Actually
doing that would probably cause all sorts of problems though. :(
-- Brooks
pgpsDSQS9EhMB.pgp
Description: PGP signature
On Fri, Aug 25, 2006 at 12:06:31AM +0200, Fredrik Lindberg wrote:
> Brooks Davis wrote:
> >
> >It just occured to me that the daemon could handle this without any
> >interaction with dhclient or the static interface configuration. In the
> >mode where you only want an
1 - 100 of 389 matches
Mail list logo
