FreeBSD as router question

2004-11-22 Thread Dennis Moore
I'm trying to set up the following system.  Any help is appreciated.

* A switch with VLAN 2 and VLAN 3
* A FreeBSD server with interfaces VLANs 2 and 3
* X Number of clients on VLAN 3

* VLAN 2: 192.168.0.0/24
* VLAN 3: 172.0.0.0/24

Clients must be able to get an address from DHCP on the FreeBSD server.
Currently I am using NAT, but the system must be implementable with or
without it.

New clients must be on a probationary status where all their traffic is
redirected to the FreeBSD server. They will remain there until they perform
some action (i.e. submit a web page). Once they affirm on the web page,
they will be added to a semi-permanent list. Clients on this list will be
routed normally.

I am able to allow or block servers using their MAC address and Layer 2
ipfw2 rules. Is it possible to modify these rules so that the redirection
takes place instead of blocking (rule 30999)? 

# always allow ARP
00100 allow ip from any to any mac-type 0x0806
00105 skipto 3 ip from any to any MAC any any via vlan3
00110 skipto 31000 ip from any to any not layer2 via vlan3
# authorized client MAC
3 pipe 4 ip from any to any MAC 00:04:23:a6:40:d3 any out via vlan3
30001 pipe 40010 ip from any to any MAC any 00:04:23:a6:40:d3 in via vlan3
# deny all other macs; needs to change
30999 deny ip from any to any MAC any any via vlan3
# Broadcast traffic on port 67 of vlan3
31000 allow log logamount 1000 ip from any to 255.255.255.255 dst-port 67 via 
vlan3
# anti-spoofing
31010 deny ip from any to any not verrevpath in via vlan3
31020 allow ip from 172.0.0.0/24 to any in via vlan3
31030 allow ip from any to 172.0.0.0/24 out via vlan3
# NAT
61000 divert 8668 ip from any to any via em0
65000 allow ip from any to any
65535 deny ip from any to any

-- 
BLINK ;for (74,1970500640,1634627444,1751478816,1348825708,543711587,
1801810465){for($x=11^1;$x=11;$x--) {$q=hex ff,$r=oct($x=~s,\d,$*
10,e,$x),$x/=1/.1,$q=$r,$s.=chr (($_$q)$r),$t++}}while($= ||= !$|)
{$o=$o?$?:$/;$|=1;print $o?$s:$x$t if$;;print\bx$t;sleep 1} /BLINK
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Mozilla 1.2.1 and java

2003-01-22 Thread Dennis Moore
On Wed, Jan 22, 2003 at 08:41:47AM +, Aqua Daemon wrote:
 Hello,
  
 I just upgraded Mozilla (1.1 to 1.2.1). In the 1.1, I had all the plugins working 
(java, plugger, and Shockwave). After upgrading via portupgrade (WITH_GTK2=yes), all 
plugins except java loaded fine. The results are the same for both of my 4.7-STABLE 
and 5.0-RELEASE computers. I tried symlinking (ln -sf), then just copying (cp). Same 
results. I saw that other people were able to upgrade with no problems. What did I do 
wrong or what do I need to do?
  
 This is the text output of when I loaded the 1.2.1:
  
 ___
  
 www% mozilla
 No running window found.
 LoadPlugin: failed to initialize shared library 
/usr/local/jdk1.3.1/jre/plugin/i386/ns600/libjavaplugin_oji.so 
[/usr/local/jdk1.3.1/jre/plugin/i386/ns600/libjavaplugin_oji.so: Undefined symbol 
gdk_input_add]
 LoadPlugin: failed to initialize shared library 
/usr/X11R6/lib/mozilla/plugins/libjavaplugin_oji.so [Cannot open 
/usr/X11R6/lib/mozilla/plugins/libjavaplugin_oji.so]
 

just a guess..

/xfer/ports/www/mozilla cat pkg-message
###
A symlink has been created for the Java plugin.  However, in order for Java
to function, you must first install the java/jdk13 port.  If you do not
do this, you will see the following error when starting Mozilla:

LoadPlugin: failed to initialize shared library 
/usr/local/jdk1.3.1/jre/plugin/i386/ns600/libjavaplugin_oji.so [Cannot open 
/usr/local/jdk1.3.1/jre/plugin/i386/ns600/libjavaplugin_oji.so]

If you do not want Java support, you can safely ignore this message.
###

-- 
Dennis Moore jesus sewed my pants
Pro Bono Devil's Advocate  it's a love affair
archon@EFnet irc mainly jesus
http://forbidden.dough.net/  and my pants

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