Re: Verizon DSL FreeBSD?

[C J Michaels]

Some time in the recent past John E. Martin scribbled:


 Anyone know if you can get Verizon DSL working with
 FreeBSD?

 No problem at all.

 Verizon DSL uses straight DHCP. No PPPoE involved at all. At least,
 here in West Los Angeles that is the case.

This is not entirely true.  If you are in a former BellAtlantic region
(east coast) Verizon DSL uses PPPoE.  On that note, the ppp client that
comes with FreeBSD works perfectly fine.  I've had one setup for a family
member for a couple years now w/o any problems.



 Peace,
 -John



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

Re: port redirect with ipfw NOT NAT (not NAT)

[C J Michaels]

Some time in the recent past Lowell Gilbert scribbled:
 Josh Brooks [EMAIL PROTECTED] writes:

  Have you tried something like:
 
  add 01000 fwd 10.10.10.10,5050 tcp from any to 10.10.10.10 50


 When I do this, I get:

 ipfw: getsockopt(IP_FW_ADD): Invalid argumentipfw:
 getsockopt(IP_FW_ADD): Invalid argument


 Any ideas ?   Is there any reason why port forwarding with ipfw is
 special and annoying ?  Or is there really something qualitatively
 different about this action that warrants this behavior ?

I don't see anything wrong with your syntax on that command and I use a
similar command to foward to my transparent proxy.

The only thing *I* can think of is that you didn't compile your kernel with:
options IPFIREWALL_FORWARD

--
Chris



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

OT: QMail, Procmail, Root privs.

[C J Michaels]

I am running qmail(mbox)+procmail.  I have a script that is run from
/usr/local/etc/procmailrc.  For reasons I can't fathom it seems to have
dropped root privs before the script specifies it (DROPPRIV).

It's a very simple script, it sets some env variables, runs 'test' and
'grep' and delivers mail based on the results.  Problem is the files
aren't readable but everyone and test and grep need to run as root.

Has anyone run into this or have any ideas on how I can troubleshoot? 
Verbost logging does say anything about dropping privs.

Thanks

-- 
Chris



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

Re: How to chmod on FAT32 partition?

[C J Michaels]

Some time in the recent past David Gerard scribbled:

 OK, got disk up. (Problem was I didn't know its make. ad3s1 eventually
 worked.)

 Now it seems I can't make it writable by anyone but root:

 diva# ls -l viv.html
 -rwxr-xr-x  1 root  wheel  1987 Jul  4 05:21 viv.html
 diva# chmod g+w viv.html
 diva# ls -l viv.html
 -rwxr-xr-x  1 root  wheel  1987 Jul  4 05:21 viv.html
 diva# chmod a+w viv.html
 diva# ls -l viv.html
 -rwxr-xr-x  1 root  wheel  1987 Jul  4 05:21 viv.html

 Same for any files. Is this some sort of FAT32 limitation? Is this
 documented anywhere?

I know it's documented somewhere but I'm too lazy to look right now.  I
know for a fact if you search the archives you'll find more detail.

The short answer is that FAT32 has no concept of permissions there's not
way to 'change them' on a per file/dir basis.  When you mount a FAT{32}
partition it'll inherrit the permissions of the mount point.  So
chown/chmod that directory and re-mount.


 - d.


-- 
Chris



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