cangw setup wrong

[nico0481]

cangw setup wrong

[marckleinebudde]

IC! That functionality was removed in a9985c7, as it's no longer needed with can-gw.

    candump: remove bridging functionality
    
    The tool 'candump' is used to dump CAN traffic to stdout or logfile.
    In early days where the in-kernel CAN gateway (can-gw) with the cangw tool was
    not yet implemented the bridging functionality allowed to send received (and
    filtered) CAN frames to another outgoing CAN interface.
    
    As we now have can-gw and sending CAN frames from a 'reading tool' seems wrong
    especially from the Unix philosophy "Write programs that do one thing and do
    it well." this patch removes the obsolete functionality from candump.
    
    Signed-off-by: Oliver Hartkopp <[email protected]>

[nico0481]

it works now, it was HW issue
Thanks

[marckleinebudde]

candump doesn't have a -B option. What should it do?

[nico0481]

Earlier candump has options:
-b
(bridge mode - send received frames to )

   -B <can>
          (bridge mode - like '-b' with disabled loopback)

See: https://manpages.ubuntu.com/manpages/focal/en/man1/candump.1.html

I used this option to bridge can0 to can1
But since few updates, option doesn't exist anymore.

[hartkopp]

I managed to use previously cangw on physical interfaces (can0&can1)with for instance:

        sudo modprobe can-gw
        sudo cangw -A -s can0 -d can1
        sudo cangw -A -s can1 -d can0

but can interfaces are not forwarded to each other. How can I set bridging between interfaces? What's wrong with my set up?

The setup is correct - but you likely do not see the outgoing traffic on your local machine as you did not enable the -e option to echo the sent traffic.

To have the -B can1 functionality invoke sudo cangw -A -s can0 -d can1 -e

Please also take a look what cangw -L tells you about the current can-gw routing jobs.

[hartkopp]

Thanks!