• Mike Hibler's avatar
    Initial steps toward a hardware-assisted (switch VLAN) firewall implementation. · 0527441a
    Mike Hibler authored
    This checkin adds the necessary NS and client-side changes.
    
    You get such a firewall by creating a firewall object and doing:
    
    	$fw set-type ipfw2-vlan
    
    In addition to the usual firewall setup, it sets the firewall node command
    line to boot "/kernel.fw" which is an IPFW2-enabled kernel with a custom
    bridge hack.
    
    The client-side setup for firewalled nodes is easy: do nothing.
    
    The client-side setup for the firewall is more involved, using vlan devices
    and bridging and all sorts of geeky magic.
    
    Note finally that I don't yet have a decent set of default rules for anything
    other than a completely open firewall.  The rules might be slightly different
    than for the "software" firewall since they are applied at layer2 (and we want
    them just to be applied at layer2 and not multiple times)
    0527441a
Name
Last commit
Last update
..
GNUmakefile.in Loading commit data...
README Loading commit data...
event.tcl Loading commit data...
firewall.tcl Loading commit data...
lanlink.tcl Loading commit data...
node.tcl Loading commit data...
nsenode.tcl Loading commit data...
nsobject.tcl Loading commit data...
nstb_compat.tcl Loading commit data...
null.tcl Loading commit data...
parse-ns.in Loading commit data...
parse.proxy.in Loading commit data...
parse.tcl.in Loading commit data...
program.tcl Loading commit data...
sim.tcl.in Loading commit data...
tb_compat.tcl.in Loading commit data...
traffic.tcl Loading commit data...
vtype.tcl Loading commit data...