search for: br2684ctl

...have a router, which does routing functionality between nasx interfaces and eth0. >From user space, setting up a bridge connection is quite simple. First, the linking an ATM VC with an interface should be done followed by configuring this interface. The syntax of the command is the following: br2684ctl [-c n -e 0|1 -b 0|1 -s buf_size -a [itf].vpi.vci ]+ -a [itf].vpi.vci : ATM PVC number, VPI and VCI. Mandatory -c n : BR2684 interface number such as nas0, nas1,... Mandatory -e 0|1 : Encapsulation method. 0=LLC, 1=VC mux. default is 0, LL...

Hello all, Does anyone know of a methodology to build a route based on the inbound and outbound interfaces as opposed to ip addresses? We are essentially trying to forward packets from one interface to another without looking at the ip address. Bridging (brctl, br2684ctl) will not work in this case as the interfaces use different layer 2 encapsulation (e.g., atm0<=>eth0, or ppp0<=>eth0). We could build a rule to match the incoming interface, then point to a routing table with a default route set to the outbound interface. The problem, with this approac...

...t` cd module && make clean make[1]: Entering directory `/home/paulo/amedyn/module` rm -f *.o .*.flags *.ko *.mod.* .*.o.cmd .*.ko.cmd make[1]: Leaving directory `/home/paulo/amedyn/module` cd bridged && make clean make[1]: Entering directory `/home/paulo/amedyn/bridged` rm -f br2684ctl make[1]: Leaving directory `/home/paulo/amedyn/bridged` cd init && make && make install make[1]: Entering directory `/home/paulo/amedyn/init` gcc -O2 -Wstrict-prototypes -fomit-frame-pointer -pipe -march=i686 -Wall -DLINUX -Wsign-compare -I../include -lusb amload.c -o amload am...