error handling in in_ifinit()

2002-03-22 Thread Backend Chan


In the newest 4-stable kernel whose source codes are synchronized by cvsup,
it would fail if trying to add an alias address whose network and netmask
are the same as the orignal one on that network interface:

# uname -a
FreeBSD intra.example.com 4.5-STABLE FreeBSD 4.5-STABLE #5: Fri Mar 22
13:45:41 CST 2002[EMAIL PROTECTED]:/usr/src/sys/compile/SERVER i386
# ifconfig xl0 inet 192.168.1.100 netmask 0xff00
# ifconfig xl0 inet 192.168.1.101 netmask 0xff00 alias
ifconfig: ioctl (SIOCDIFADDR): File exists

But it worked for 4.4-Release (I'd tested):

#uname -a
FreeBSD bsd.example.com 4.4-RELEASE FreeBSD 4.4-RELEASE # 17: Fri Mar 22
12:09:36 CST 2002[EMAIL PROTECTED]:/usr/src/sys/compile/SERVER i386
# ifconfig xl0 inet 192.168.1.100 netmask 0xff00
# ifconfig xl0 inet 192.168.1.101 netmask 0xff00 alias
# ifconfig xl0
xl0: flags=8843 mtu 1500
options=3
inet 192.168.1.100 netmask 0xff00 broadcast 192.168.1.255
inet6 fe80::201:2ff:fe80:2a8b%xl0 prefixlen 64 scopeid 0x2 
inet 192.168.1.101 netmask 0xff00 broadcast 255.255.255.0
ether 00:01:02:80:2a:8b 
media: Ethernet autoselect (100baseTX )
status: active


Below is a workground patch:

[root@www /sys/netinet]# diff -u in.c.orig in.c 
--- in.c.orig   Fri Mar 22 13:16:07 2002
+++ in.cFri Mar 22 13:16:41 2002
@@ -737,7 +737,8 @@
 * interface, because the bootp code wants to set a 0.0.0.0/0
 * address on all interfaces. Disable the check when bootp is used.
 */
-   if (error != 0 && ia->ia_dstaddr.sin_family == AF_INET) {
+   if (error != 0 && error != EEXIST &&
+   ia->ia_dstaddr.sin_family == AF_INET) {
ia->ia_addr = oldaddr;
return (error);
}

Should it be done so?

--- 
backend <[EMAIL PROTECTED]>

-- 

___
Sign-up for your own FREE Personalized E-mail at Mail.com
http://www.mail.com/?sr=signup

Win the Ultimate Hawaiian Experience from Travelocity.
http://ad.doubleclick.net/clk;4018363;6991039;n?http://svc.travelocity.com/promos/winhawaii/


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message



Re: error handling in in_ifinit()

2002-03-22 Thread Peter Pentchev

On Fri, Mar 22, 2002 at 09:50:53AM -0500, Backend Chan wrote:
> 
> In the newest 4-stable kernel whose source codes are synchronized by cvsup,
> it would fail if trying to add an alias address whose network and netmask
> are the same as the orignal one on that network interface:
> 
> # uname -a
> FreeBSD intra.example.com 4.5-STABLE FreeBSD 4.5-STABLE #5: Fri Mar 22
> 13:45:41 CST 2002[EMAIL PROTECTED]:/usr/src/sys/compile/SERVER i386
> # ifconfig xl0 inet 192.168.1.100 netmask 0xff00
> # ifconfig xl0 inet 192.168.1.101 netmask 0xff00 alias
> ifconfig: ioctl (SIOCDIFADDR): File exists
> 
> But it worked for 4.4-Release (I'd tested):
> 
> #uname -a
> FreeBSD bsd.example.com 4.4-RELEASE FreeBSD 4.4-RELEASE # 17: Fri Mar 22
> 12:09:36 CST 2002[EMAIL PROTECTED]:/usr/src/sys/compile/SERVER i386
> # ifconfig xl0 inet 192.168.1.100 netmask 0xff00
> # ifconfig xl0 inet 192.168.1.101 netmask 0xff00 alias
> # ifconfig xl0
> xl0: flags=8843 mtu 1500
[snip]
> inet 192.168.1.100 netmask 0xff00 broadcast 192.168.1.255
> inet6 fe80::201:2ff:fe80:2a8b%xl0 prefixlen 64 scopeid 0x2 
> inet 192.168.1.101 netmask 0xff00 broadcast 255.255.255.0
> 
> Below is a workground patch:
[snip patch]
> 
> Should it be done so?

Not really.

The ifconfig(8) manual page has documented this since.. well, for a LONG time:

  alias   Establish an additional network address for this interface.  This
  is sometimes useful when changing network numbers, and one wishes
  to accept packets addressed to the old interface.  If the address
  is on the same subnet as the first network address for this
  interface, a netmask of 0x has to be specified.

This is also covered in the FreeBSD FAQ, chapter 12 - "Networking",
question 12.2 - "How do I set up Ethernet aliases?".

The correct setup is to use a netmask of 0x (255.255.255.255)
for the alias.

G'luck,
Peter

-- 
Peter Pentchev  [EMAIL PROTECTED][EMAIL PROTECTED]
PGP key:http://people.FreeBSD.org/~roam/roam.key.asc
Key fingerprint FDBA FD79 C26F 3C51 C95E  DF9E ED18 B68D 1619 4553
This would easier understand fewer had omitted.



msg33046/pgp0.pgp
Description: PGP signature


Hifn 7751/PowerCrypt status? (or: Paging jlemon...)

2002-03-22 Thread Lee Cremeans

Has anyone heard from Jon Lemon about Hifn 7751 support? He mailed my boss a
few months ago (January), saying that support was working, but we haven't
heard from him since, and jkh suggested trying here.

-lee


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message



Re: Hifn 7751/PowerCrypt status? (or: Paging jlemon...)

2002-03-22 Thread Louis A. Mamakos

> Has anyone heard from Jon Lemon about Hifn 7751 support? He mailed my boss a
> few months ago (January), saying that support was working, but we haven't
> heard from him since, and jkh suggested trying here.
> 
> -lee
> 

On a related note, Sam Leffler just reported some success in
porting the OpenBSD crypto framework to FreeBSD 4-STABLE.  It's
apparently still a work-in-progress in that the KAME IPSEC stack
has not been modified to use it yet.

I've attached a message he sent to the soekris-tech mailing
list (for the net4501 small system that runs FreeBSD).

louie



--- Begin Message ---

I've put together a simple packaging environment for installing
PicoBSD/FreeBSD on net4501 systems.  There is an extensive (but unfinished)
set of instructions for working with the software and some sample
configurations that demonstrate how things work.  The tools let you
configure images for network booting and installation into compact flash.
There is a pxe-bootable installer image that walks you through installing an
image to compact flash.

Also included is a snapshot of my port of the openbsd crypto support that
hooks the Hifn 7951 to /dev/random and provides a /dev/crypto device.  This
will eventually include mods to the KAME IPsec code to use the 7951.

The package is available at http://www.errno.com/net4501/net4501.tgz.

MD5 (net4501-20020318.tgz) = 95fd358cbcf9451337a26d7878c7afb4

All work has been done on the -stable brunch of FreeBSD.  Please send
feedback directly to me.

Sam


_
Soekris Engineering, technical discussion mailing list
[un]subscribe: http://lists.soekris.com/mailman/listinfo/soekris-tech

--- End Message ---


Open bug reports with no action?

2002-03-22 Thread Ted Cabeen

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Content-Type: text/plain; charset=us-ascii

I submitted a bug report (PR# bin/31933) in November that's never been looked
at.  I even enclosed a patch that fixes the bug.  Is there anything that I can
do to get the bug looked at sooner rather than later?

- -- 
Ted Cabeen   http://www.pobox.com/~secabeen[EMAIL PROTECTED] 
Check Website or Keyserver for PGP/GPG Key BA0349D2 [EMAIL PROTECTED]
"I have taken all knowledge to be my province." -F. Bacon  [EMAIL PROTECTED]
"Human kind cannot bear very much reality."-T.S.Eliot[EMAIL PROTECTED]


-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (OpenBSD)
Comment: Exmh version 2.5 07/13/2001

iD8DBQE8m7c1oayJfLoDSdIRArYgAJ9R09lrKOvcO4D7JNYNwYsgemlaOgCdH7JO
RTfWVF0VgOEHEUK3OTolyk8=
=ueZ2
-END PGP SIGNATURE-


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message



Re: Open bug reports with no action?

2002-03-22 Thread Matthew Dillon

:Content-Type: text/plain; charset=us-ascii
:
:I submitted a bug report (PR# bin/31933) in November that's never been looked
:at.  I even enclosed a patch that fixes the bug.  Is there anything that I can
:do to get the bug looked at sooner rather than later?
:
:- -- 
:Ted Cabeen   http://www.pobox.com/~secabeen[EMAIL PROTECTED] 
:Check Website or Keyserver for PGP/GPG Key BA0349D2 [EMAIL PROTECTED]

Sure.  Hmm.  I'm not sure I like the idea of using -- instead of -n.
It led to some confusion when I was reading the patch.

What if we officially assigned an actual option letter like 'U' instead
of '-'?  Another alternative would be to have a global ExactUser global
that defaults to 0 and gets set to 1 if either -n or -u are explicitly
specified.


-Matt

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message



Canada; Subsidies, Grants, Loans, Financing

2002-03-22 Thread MG PUBLISHING


MG PUBLISHING
4865 HWY 138,R.R 1
ST-ANDREWS WEST
ONTARIO, KOC 2A0


PRESS RELEASE

CANADIAN SUBSIDY DIRECTORY YEAR 2002 EDITION
Legal Deposit-National Library of Canada
ISBN 2-922870-01-4 (2001)
ISBN 2-922870-02-2 (2002)

M.G. Publishing is offering to the public a revised edition of the Canadian
Subsidy Directory, a guide containing more than 2800 direct and indirect
financial subsidies, grants and loans offered by government departments and
agencies, foundations, associations and organizations.  In this new 2002
edition
all programs are well described.

The Canadian Subsidy Directory is the most comprehensive tool to start up a
business, improve existent activities, set up a business plan, or obtain
assistance from experts in fields such as: Industry, transport, agriculture,
communications, municipal infrastructure, education, import-export, labor,
construction and renovation, the service sector, hi-tech industries,
research
and development, joint ventures, arts, cinema, theatre, music and recording
industry, the self employed, contests, and new talents.
Assistance from and for foundations and associations, guidance to prepare a
business plan, market surveys, computers, and much more!

To obtain the Canadian Subsidy Directory call one of the following
resellers:

Fureteur: 450-465-5597 fax: 450-465-8144 (credit card orders only)
Canadian Business Ressource Center : 250-381-4822 (8am-4pm pacific time)

To remove your e-mail from our mailing list please reply at
[EMAIL PROTECTED] with the word remove in the subject window.



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message



apache13-ssl wiped out my Web pages

2002-03-22 Thread Mike Carr

I Have recently installed the Horde port to my machine.  I did not
have Apache+mod_ssl, PHP, or MySql installed on my system, just Apache
serving up my companies files.
The installation went fine up to the point when I went to check the
installation and found that the Apahe13-ssl port had wiped out my web
directories.  This definitely needs to change!
Here are some ideas
1) Show a warning prior to installing Apache, that the installation will
wipe out the users current web pages
2) Make a backup of the files prior to wiping them out
3) leave all the data in data.default directory alone
apache13-ssl/   pkg-plist

This is the problem area
@exec [ -d %D/www/data/ ] || ln -fs %B
%D/www/data
Line 131
-rw-r--r--    1 root  wheel  22804 Dec  2
15:17 pkg-plist
# New ports collection makefile for:    Apache +
mod_ssl
# Date created: Sat Aug
22 12:00:00 CDT 1998
#
Whom:
[EMAIL PROTECTED]
#
# $FreeBSD: ports/www/apache13-modssl/Makefile,v 1.94 2002/01/22 22:29:24
sf Exp $
#





apache13-ssl wiped out my Web pages

2002-03-22 Thread Mike Carr

I Have recently installed the Horde port to my machine.  I did not have 
Apache+mod_ssl, PHP, or MySql installed on my system, just Apache serving 
up my companies files.

The installation went fine up to the point when I went to check the 
installation and found that the Apahe13-ssl port had wiped out my web 
directories.  This definitely needs to change!

Here are some ideas
1) Show a warning prior to installing Apache, that the installation will 
wipe out the users current web pages
2) Make a backup of the files prior to wiping them out
3) leave all the data in data.default directory alone

apache13-ssl/   pkg-plist


This is the problem area

@exec [ -d %D/www/data/ ] || ln -fs %B %D/www/data
Line 131
-rw-r--r--1 root  wheel  22804 Dec  2 15:17 pkg-plist

# New ports collection makefile for:Apache + mod_ssl
# Date created: Sat Aug 22 12:00:00 CDT 1998
# Whom: [EMAIL PROTECTED]
#
# $FreeBSD: ports/www/apache13-modssl/Makefile,v 1.94 2002/01/22 22:29:24 
sf Exp $
#





To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message