nickkaranatsios

<nav class="navbar navbar-inverse">
  <div class="container-fluid">
    <div class="navbar-header">
      <button type="button" class="navbar-toggle" data-toggle="collapse" data-target="#myNavbar">
        <span class="icon-bar"></span>
        <span class="icon-bar"></span>
        <span class="icon-bar"></span>
      </button>
      <a class="navbar-brand" href="#">Logo</a>
    </div>

nickkaranatsios

Currently trema-switch configuration looks like the following:

trema_switch( "lsw" ) {
  datapath_id "0xabc"
  ports "trema0-0,trema1-0"
}

vhost ("host1") {
  ip "192.168.0.1"
 netmask "255.255.0.0"

nickkaranatsios

The new encodeded table_features reply. The phantom 82 number at flexible actions should be fixed soon.

#<Trema::Messages::TableFeaturesMultipartReply:0x9b3f2b4 @length=1712, @table_id=109, @name="table109", @metadata_match=18446744073709551615, @metadata_write=18446744073709551615, @config=0, @max_entries=255, 
@properties={

:instructions=>[Trema::Instructions::ApplyAction, Trema::Instructions::ClearAction, Trema::Instructions::WriteAction, Trema::Instructions::WriteMetadata, Trema::Instructions::GotoTable], 

:instructions_miss=>[Trema::Instructions::ApplyAction, Trema::Instructions::ClearAction, Trema::Instructions::WriteAction, Trema::Instructions::WriteMetadata, Trema::Instructions::GotoTable], 

nickkaranatsios

lldp packet on my envirnoment at home

To be able to transmit lldp packets using a particular management address you need to specifiy the interface that holds the management ip address.

packets captured using veth0 and management address set 192.168.1.12 which is the veth1 address.

Process started as follows

/usr/sbin/lldpd -I veth0 -m 192.168.1.12

veth1 configuration

nickkaranatsios

# What's this

This is a routing switch application with slicing and packet filter capabilities.
The slicing function allows us to create multiple Layer 2 domains (similar to port and MAC-based VLAN
Look at packet information to choose path and cache paths to minimize connection setup latency.
We are interesting in inter-domain routing policy for full end-to-end paths.
A host that wishes to be reachable by senders installs an entry in a lookup service.
The sliceable routing switch supports redirection of unauthorized users to a specified port? page.
A slice of a resource users extends this to describe resource provisioning.