Question

persistent "Destination Host Unreachable" for new IP block

  • 2 May 2020
  • 1 reply
  • 79 views

We recently upgraded to a whole cabinet for colocation, with the upgrade we are planning on adding more servers. When we first moved into the new space, we were given a /29 IP block - 130.250.76.144/29. We are trying to move forward with some testing and asked for our service provider for a /27 block - 130.250.68.32/27. We have a single switch that runs Cumulus Linux 2.5.12.
Our /29 block works perfectly, we are currently struggling with routing the /27 - we were given the next hop. Everything we have tried as responded back with "Destination Host Unreachable".

The information we were provided for the /29 is:

    130.250.76.144/29 (Directly Connected)
    130.250.76.145 - GTW
    130.250.76.146 - CAS1.MN01 ge-0/0/6 USED BY Datacenter
    130.250.76.147 - CAS2.MN01 ge-0/0/6 USED BY Datacenter
    130.250.76.148 - 130.250.76.150 - AVAILABLE FOR CUSTOMER TO USE
    130.250.76.151 - BROADCAST

The information we were provided for the /27 is:

    130.250.68.32 / 27 (Statically Connected) Next hop used is 130.250.76.148
    130.250.68.33 - 130.250.68.62 - AVAILABLE FOR CUSTOMER TO USE
    130.250.68.63 – BROADCAST

Our /etc/network/interfaces is as follows:

    # The loopback network interface
    auto lo
    iface lo inet loopback
    
    # The primary network interface
    auto eth0
    iface eth0 inet static
        address 130.250.76.150
        broadcast 130.250.76.151
        gateway    130.250.76.145
        netmask 255.255.255.0
    
    auto swp1
    iface swp1
        address 130.250.76.144/29
        post-up ip route add 130.250.76.144/29 via 130.250.76.145
        post-up ip route add 130.250.68.32/27 nexthop via 130.250.76.148
        link-autoneg off
        link-speed 100
        link-duplex full
    
    auto swp2
    iface swp2
        address 130.250.76.144/29
        post-up ip route add 130.250.76.144/29 via 130.250.76.145
        post-up ip route add 130.250.68.32/27 nexthop via 130.250.76.148
        link-autoneg off
        link-speed 100
        link-duplex full
    
    auto swp3
    iface swp3
    
    auto swp4
    iface swp4    
    
    auto bridge-untagged
    iface bridge-untagged
        address 130.250.68.34/27
        post-up ip route add 130.250.68.32/27 via 130.250.76.148
        bridge-stp on
      bridge-ports \
          swp1 swp2 swp3 swp4 swp5 \
          swp6 swp7 swp8 swp9 swp10 \
          swp11 swp12 swp13 swp14 swp15 \
          swp16 swp17 swp18 swp19 swp20 \
          swp21 swp22 swp23 swp24 swp25 \
          swp26 swp27 swp28 swp29 swp30 \
          swp31 swp32 swp33 swp34 swp35 \
          swp36 swp37 swp38 swp39 swp40 \
          swp41 swp42 swp43 swp44 swp45 \
          swp46 swp47 swp48 swp49 swp50 \
          swp51 swp52


1 reply

Userlevel 5

There are a lot of things which are unclear here about what you’re trying to do. 

  1. Firstly, why is the traditional bridge being used?
  1. Why is a route pointing to yourself being added through an external party
        auto swp2
        iface swp2
            address 130.250.76.144/29
            post-up ip route add 130.250.76.144/29 via 130.250.76.145
  2. It is unclear what the addresses are that were provided above without some good labels from your service provider.

Because there is such a lack of clarity here I would recommend reaching out to your sales team as they can have someone sit down with you to understand your requirements and help craft a configuration which will meet your needs. If you need a hand getting connected, let me know!

Reply