Find the answer to your Linux question:
Results 1 to 3 of 3
I have this 3 machines with this setup: Computer1----Computer with Ubuntu 12.04-----Computer2 Computer1 have IP 192.168.10.1 and Computer2 have 192.168.10.10. My computer with Ubuntu have 2 ethernet interfaces. I want ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined!
    Join Date
    Feb 2014
    Posts
    2

    Exclamation Strange bridge behaviour, need sugestions


    I have this 3 machines with this setup:
    Computer1----Computer with Ubuntu 12.04-----Computer2

    Computer1 have IP 192.168.10.1 and Computer2 have 192.168.10.10.
    My computer with Ubuntu have 2 ethernet interfaces. I want to create a bridge in Ubuntu so Computer1 and Computer2 can talk to each other.

    I have created a bridge in Ubuntu with

    Code:
    sudo ifconfig eth0 0.0.0.0 down
    sudo ifconfig eth1 0.0.0.0 down
    sudo brctl addbr br0
    sudo brctl addif br0 eth0
    sudo brctl addif br0 eth1
    sudo ifconfig br0 up
    sudo ifconfig eth0 promisc up
    sudo ifconfig eth1 promisc up
    The command "brctl showstp br0" shows me that the state of eth0 and eth1 is forwarding.

    Then I start tshark in bridge with

    Code:
    sudo tshark -i br0
    If in Computer2 I try to ping Computer1 I get

    Code:
    ARP 60 Who has 192.168.10.1? Tell 192.168.10.10
    In the bridge I get the ARP Request from Computer2 but I don't see ARP Reply from Computer1

    When I run the tshark at Computer1 gets this

    Code:
    ARP 60 Who has 192.168.10.1? Tell 192.168.10.10
    ARP 42 192.168.10.1 is at XX:XX:XX:XX:XX:XX (mac hidden)
    With this I see that ARP gets passed through the brige, Computer1 receives the ARP and sends the reply but that reply don't go through the bridge.

    Any ideas???

    Thanks

  2. #2
    Linux Guru Rubberman's Avatar
    Join Date
    Apr 2009
    Location
    I can be found either 40 miles west of Chicago, in Chicago, or in a galaxy far, far away.
    Posts
    11,692
    Assuming you have a router on 192.168.10.x then I have to ask why are they not able to connect? If you don't have a router for this subnet, then you need to set your route tables.
    Sometimes, real fast is almost as good as real time.
    Just remember, Semper Gumbi - always be flexible!

  3. #3
    Just Joined!
    Join Date
    Feb 2014
    Posts
    2
    Quote Originally Posted by Rubberman View Post
    Assuming you have a router on 192.168.10.x then I have to ask why are they not able to connect? If you don't have a router for this subnet, then you need to set your route tables.
    The problem was in the route tables.

    Thanks

  4. $spacer_open
    $spacer_close

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •