Re: Solution for mail pseudo-users?

1999-07-31 Thread Jasper O'Malley

On Sat, 31 Jul 1999, Alex Povolotsky wrote:

 I'm going to implement a large mail-box, with several hundreds of mail-only
 users. They should never access anything besides their POP3 mailboxes and
 change password via (SSLed) web interface.
 
 So, I don't want to add all of them to /etc/passwd.

Use Cyrus :) The web pages at http://andrew2.andrew.cmu.edu/cyrus/ are
horribly out of date, but the project is still active, and there's recent
code in the FTP area.

Cheers,
Mick

The Reverend Jasper P. O'Malley  dotdot:[EMAIL PROTECTED]
Systems Administrator  ringring:asktheadmiral
Webnology, LLC   woowoo:http://www.webnology.com/~jooji



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



Re: Solution for mail pseudo-users?

1999-07-31 Thread Jasper O'Malley
On Sat, 31 Jul 1999, Alex Povolotsky wrote:

 I'm going to implement a large mail-box, with several hundreds of mail-only
 users. They should never access anything besides their POP3 mailboxes and
 change password via (SSLed) web interface.
 
 So, I don't want to add all of them to /etc/passwd.

Use Cyrus :) The web pages at http://andrew2.andrew.cmu.edu/cyrus/ are
horribly out of date, but the project is still active, and there's recent
code in the FTP area.

Cheers,
Mick

The Reverend Jasper P. O'Malley  dotdot:jo...@webnology.com
Systems Administrator  ringring:asktheadmiral
Webnology, LLC   woowoo:http://www.webnology.com/~jooji



To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body of the message



Final (maybe) ARP breakage plea

1999-07-14 Thread Jasper O'Malley


I realize it's not real high on the list of things to fix, but proxy ARP
is still broken in -STABLE. If anyone know the answers to any of these
questions, please drop me a line so I can try fixing it:

1) Can anyone explain the difference between "published" ARP table
   entries, and "published (proxy only)" ARP table entries?

2) What purpose does the sin_other parameter of the sockaddr_inarp
   structure serve (defined in /usr/include/netinet/if_ether.h, and set
   to SIN_PROXY for "proxy only" ARP entries)?

3) How about the significance of the RTF_HOST routing message flag (i.e.
   how does an IP "host" route functionally differ from a "net" route with
   a /32 netmask)? Or does this only have significance for non-IP routes?

4) What's the purpose of this snippet of code from rtmsg() in
   src/usr.sbin/arp/arp.c?

if (doing_proxy) {
if (export_only)
sin_m.sin_other = SIN_PROXY;
else {
rtm-rtm_addrs |= RTA_NETMASK;
rtm-rtm_flags = ~RTF_HOST;
}
}

Cheers,
Mick

The Reverend Jasper P. O'Malley  dotdot:[EMAIL PROTECTED]
Systems Administrator  ringring:asktheadmiral
Webnology, LLC   woowoo:http://www.webnology.com/~jooji





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



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



Final (maybe) ARP breakage plea

1999-07-14 Thread Jasper O'Malley

I realize it's not real high on the list of things to fix, but proxy ARP
is still broken in -STABLE. If anyone know the answers to any of these
questions, please drop me a line so I can try fixing it:

1) Can anyone explain the difference between published ARP table
   entries, and published (proxy only) ARP table entries?

2) What purpose does the sin_other parameter of the sockaddr_inarp
   structure serve (defined in /usr/include/netinet/if_ether.h, and set
   to SIN_PROXY for proxy only ARP entries)?

3) How about the significance of the RTF_HOST routing message flag (i.e.
   how does an IP host route functionally differ from a net route with
   a /32 netmask)? Or does this only have significance for non-IP routes?

4) What's the purpose of this snippet of code from rtmsg() in
   src/usr.sbin/arp/arp.c?

if (doing_proxy) {
if (export_only)
sin_m.sin_other = SIN_PROXY;
else {
rtm-rtm_addrs |= RTA_NETMASK;
rtm-rtm_flags = ~RTF_HOST;
}
}

Cheers,
Mick

The Reverend Jasper P. O'Malley  dotdot:jo...@webnology.com
Systems Administrator  ringring:asktheadmiral
Webnology, LLC   woowoo:http://www.webnology.com/~jooji





To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body of the message



To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body of the message



ARP questions

1999-07-11 Thread Jasper O'Malley


I'm going to take a crack at cleaning up arp(8), but I need hear some
specific answers from someone who's worked with the ARP subsystem:

1) What's the purpose of the sin_other field of a struct sockaddr_inarp
   (which is either set to 0 or SIN_PROXY)?

2) What's the difference between a "published" or "published (proxy only)"
   ARP table entry (as reported by arp(8))?

3) Should a proxy ARP entry be a host route (i.e. RTF_HOST is set) as I
   suspect, or a net route with a /32 netmask, as it strangely seemed to
   be for "published" entries before arp(8) broke in -STABLE? For either
   case, why?

4) If I want to perform proxy ARP on directly attached Ethernet network
   A for a host on directly attached Ethernet network B, do I actually
   need two ARP table entries--one "published (proxy only)" entry to allow
   for the proxying on network A, and another ordinary entry (which may
   in fact be automatically created through the normal ARP mechanism) to
   actually forward packets to the host on network B?

Cheers,
Mick

The Reverend Jasper P. O'Malley  dotdot:[EMAIL PROTECTED]
Systems Administrator  ringring:asktheadmiral
Webnology, LLC   woowoo:http://www.webnology.com/~jooji




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



ARP questions

1999-07-11 Thread Jasper O'Malley

I'm going to take a crack at cleaning up arp(8), but I need hear some
specific answers from someone who's worked with the ARP subsystem:

1) What's the purpose of the sin_other field of a struct sockaddr_inarp
   (which is either set to 0 or SIN_PROXY)?

2) What's the difference between a published or published (proxy only)
   ARP table entry (as reported by arp(8))?

3) Should a proxy ARP entry be a host route (i.e. RTF_HOST is set) as I
   suspect, or a net route with a /32 netmask, as it strangely seemed to
   be for published entries before arp(8) broke in -STABLE? For either
   case, why?

4) If I want to perform proxy ARP on directly attached Ethernet network
   A for a host on directly attached Ethernet network B, do I actually
   need two ARP table entries--one published (proxy only) entry to allow
   for the proxying on network A, and another ordinary entry (which may
   in fact be automatically created through the normal ARP mechanism) to
   actually forward packets to the host on network B?

Cheers,
Mick

The Reverend Jasper P. O'Malley  dotdot:jo...@webnology.com
Systems Administrator  ringring:asktheadmiral
Webnology, LLC   woowoo:http://www.webnology.com/~jooji




To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body of the message



ARP breakage

1999-07-07 Thread Jasper O'Malley


I haven't gotten much of a response in -stable, so I'll ask here. Any one
know what happened to proxy ARP in recent incarnations of 3.2-STABLE? See
problem report bin/12448, but in a nutshell:

# ifconfig ed1
ed1: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500
inet 192.168.54.1 netmask 0xff00 broadcast 192.168.54.255
ether 00:e0:29:32:21:ee

# arp -a
? (192.168.54.133) at 0:a0:c9:70:4c:1c [ethernet]
? (192.168.54.254) at 0:e0:1e:b9:7d:c1 [ethernet]

# netstat -nr
Routing tables

Internet:
DestinationGatewayFlags Refs Use Netif Expire
default192.168.54.254 UGSc20  ed1
127.0.0.1  127.0.0.1  UH  04  lo0
192.168.27 link#1 UC  00 fxp0
192.168.54 link#2 UC  00  ed1
192.168.54.133 0:a0:c9:70:4c:1c   UHLW1  128  ed1818
192.168.54.254 0:e0:1e:b9:7d:c1   UHLW10  ed1818

# arp -s 192.168.54.5 auto pub
using interface ed1 for proxy with address 0:e0:29:32:21:ee
arp: writing to routing socket: File exists
^^^

What broke?

Cheers,
Mick

The Reverend Jasper P. O'Malley  dotdot:[EMAIL PROTECTED]
Systems Administrator  ringring:asktheadmiral
Webnology, LLC   woowoo:http://www.webnology.com/~jooji



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



ARP breakage

1999-07-07 Thread Jasper O'Malley

I haven't gotten much of a response in -stable, so I'll ask here. Any one
know what happened to proxy ARP in recent incarnations of 3.2-STABLE? See
problem report bin/12448, but in a nutshell:

# ifconfig ed1
ed1: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500
inet 192.168.54.1 netmask 0xff00 broadcast 192.168.54.255
ether 00:e0:29:32:21:ee

# arp -a
? (192.168.54.133) at 0:a0:c9:70:4c:1c [ethernet]
? (192.168.54.254) at 0:e0:1e:b9:7d:c1 [ethernet]

# netstat -nr
Routing tables

Internet:
DestinationGatewayFlags Refs Use Netif Expire
default192.168.54.254 UGSc20  ed1
127.0.0.1  127.0.0.1  UH  04  lo0
192.168.27 link#1 UC  00 fxp0
192.168.54 link#2 UC  00  ed1
192.168.54.133 0:a0:c9:70:4c:1c   UHLW1  128  ed1818
192.168.54.254 0:e0:1e:b9:7d:c1   UHLW10  ed1818

# arp -s 192.168.54.5 auto pub
using interface ed1 for proxy with address 0:e0:29:32:21:ee
arp: writing to routing socket: File exists
^^^

What broke?

Cheers,
Mick

The Reverend Jasper P. O'Malley  dotdot:jo...@webnology.com
Systems Administrator  ringring:asktheadmiral
Webnology, LLC   woowoo:http://www.webnology.com/~jooji



To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body of the message



Re: ARP breakage

1999-07-07 Thread Jasper O'Malley
On Wed, 7 Jul 1999, Justin C. Walker wrote:

 Out of curiosity, what does 'arp -a' show after the 'arp -s'  
 command?

Same thing it shows before the arp -s attempt, as does netstat -nr :(
For the record, regular arp -s commands without the pub parameter
(i.e. static ARP cache entries, no proxying) work fine.

I have a couple of other related questions for anyone who knows the
answer, too:

1) Can anyone explain the difference between permanent published ARP
   table entries, and permanent published (proxy only) ARP table  
   entries?

2) What purpose does the RTF_ANNOUNCE (aka RTF_PROTO2) routing message
   flag serve? How about the sin_other parameter of the sockaddr_inarp
   structure (defined in /usr/include/netinet/if_ether.h)? How do they
   relate?

3) How about the significance of the RTF_HOST routing message flag (i.e.
   how does an IP host route functionally differ from a net route with
   a /32 netmask)? Or does this only have significance for non-IP routes?

4) What's the purpose of this snippet of code from rtmsg() in
   usr.sbin/arp/arp.c?

if (doing_proxy) {
if (export_only)
sin_m.sin_other = SIN_PROXY;
else {
rtm-rtm_addrs |= RTA_NETMASK;
rtm-rtm_flags = ~RTF_HOST;
}
}

   If I remove the last line of code (rtm-rtm_flags = ~RTF_HOST;) and
   recompile the arp command, it seems to insert the correct entry
   according to netstat -nr, but arp -a doesn't recognize it as
   published:

# newarp -s 192.168.54.5 auto pub
using interface ed1 for proxy with address 0:e0:29:32:21:ee

# newarp -a
? (192.168.54.5) at 0:e0:29:32:21:ee permanent [ethernet]
? (192.168.54.133) at 0:a0:c9:70:4c:1c [ethernet]
? (192.168.54.254) at 0:e0:1e:b9:7d:c1 [ethernet]

# netstat -nr
Routing tables

Internet:
DestinationGatewayFlags Refs Use Netif Expire
default192.168.54.254 UGSc20  ed1
127.0.0.1  127.0.0.1  UH  04  lo0
192.168.27 link#1 UC  00 fxp0
192.168.54 link#2 UC  00  ed1
192.168.54.5   0:e0:29:32:21:ee   UHLS2   00  ed1
192.168.54.133 0:a0:c9:70:4c:1c   UHLW1  322  ed1509
192.168.54.254 0:e0:1e:b9:7d:c1   UHLW10  ed1509


Note, however, that the code *with* the rtm-rtm_flags = ~RTF_HOST;
worked in earlier incarnations of 3.2-STABLE (it's in 3.2-RELEASE).

Cheers,
Mick

The Reverend Jasper P. O'Malley  dotdot:jo...@webnology.com
Systems Administrator  ringring:asktheadmiral
Webnology, LLC   woowoo:http://www.webnology.com/~jooji





To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body of the message