Did you try the Click-2.0 downloaded from the website? There was a bug while handling multiple interfaces. You may try git clone git://read.cs.ucla.edu/git/click DIR.
Jaeyong On Thu, Sep 22, 2011 at 11:30 PM, Kyungtae Kim <[email protected]>wrote: > Hello, > > > > I need some assistance. The following is the network configuration of my > test-bed. > > > > 192.168.2.100/24 (host1) -> (ath0) 192.168.2.1 (eth0) 10.0.0.2 (ROUTER) > -> (eth0)10.0.0.1 (host2) > > > > I want to send the packets from host1 to host2. With the ip_forward set > to 1, ROUTER is forwarding the packets between host1 and host2. No > problem. > > > > With running the click(version 2.0), the packets from host1 can be > reached to the ath0, not eth0 at ROUTER which was checked by tcpdump. > The packet is generated by iperf at host1. > > > > host1 and ROUTER is connected by wireless, where ROUTER is running > madwifi making ROUTER as an access point. > > > > The following is the click script. > > > > FromDevice(ath0) -> MarkIPHeader(14) -> Strip(14) -> EtherEncap(0x0800, > $SRC_ETHER, $DST_ETHER) -> Queue(100) -> ToDevice(eth0) ->IPPrint(OK); > > > > , where $SRC_ETHER is the mac address of eth0 at ROUTER, $DST_ETHER is > the mac address of HOST2. > > > > The output from the click prints out the following messages, which seems > ok. > > > > OK 192.168.2.100.36234 > 10.0.0.1.5001: udp 508 > > > > However, tcpdump at eth0/ROUTER and eth0/host2 doesn't show anything. > > > > I hope someone may be able to help me with this problem. > > > > Best regards, > > Kyungtae > > > > > > _______________________________________________ > click mailing list > [email protected] > https://amsterdam.lcs.mit.edu/mailman/listinfo/click > _______________________________________________ click mailing list [email protected] https://amsterdam.lcs.mit.edu/mailman/listinfo/click
