ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Issue with an ERL behind a CradlePoint MBR1400

    IT Discussion
    edgemax cradlepoint ubiquiti
    5
    15
    3.4k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • JaredBuschJ
      JaredBusch
      last edited by

      I am having the damnedest time getting an ERL to work correctly behind a CradlePoint MBR1400.

      The CradlePoint is in IP Passthrough mode and the ERL is getting the correct IP address.

      I posted the details over on the UBNT forums, but wanted a different set of eyes to poke on it too.

      http://community.ubnt.com/t5/EdgeMAX/Issue-with-a-ERL-behind-a-Cradlepoint-MBR1400/m-p/1231383

      1 Reply Last reply Reply Quote 0
      • thanksajdotcomT
        thanksajdotcom
        last edited by

        Silly question, but I've seen the term ERL used a lot on ML lately. What is an ERL?

        coliverC 1 Reply Last reply Reply Quote 1
        • coliverC
          coliver @thanksajdotcom
          last edited by

          @thanksajdotcom From the context it looks like it stands for Edge Router Lite.

          1 Reply Last reply Reply Quote 0
          • scottalanmillerS
            scottalanmiller
            last edited by

            Yup, The Edge Router Lite the former entry point into the enterprise firewall and routing space from Ubiquiti.

            1 Reply Last reply Reply Quote 1
            • thanksajdotcomT
              thanksajdotcom
              last edited by

              Remove the static route. I assume that's there to force all traffic out via eth0, right? I assume the ERL has a WAN port, right?

              1 Reply Last reply Reply Quote 0
              • thanksajdotcomT
                thanksajdotcom
                last edited by

                Ok, never mind. No WAN port. Looked it up.

                1 Reply Last reply Reply Quote 0
                • thanksajdotcomT
                  thanksajdotcom
                  last edited by

                  Not sure if I'm misunderstanding something, but I noticed a discrepancy in your post on Ubiquiti's site. In the interface list in the GUI, eth0's IP ends in .52 but at the CLI it shows it as ending in .53. Is this how it's supposed to be?

                  ubnt@ubnt:~$ show dhcp client leases 
                  interface  : eth0
                  ip address : 166.130.116.53     [Active]
                  subnet mask: 255.255.255.252
                  domain name: local.tld  [overridden by domain-name set using CLI]
                  router     : 166.130.116.54
                  name server: 166.216.138.41 166.216.138.42
                  dhcp server: 166.130.116.54
                  lease time : 43200
                  last update: Fri Apr 17 15:12:07 UTC 2015
                  expiry     : Sat Apr 18 03:12:00 UTC 2015
                  reason     : BOUND
                  
                  ? 1 Reply Last reply Reply Quote 0
                  • ?
                    A Former User @thanksajdotcom
                    last edited by A Former User

                    @thanksajdotcom said:

                    Not sure if I'm misunderstanding something, but I noticed a discrepancy in your post on Ubiquiti's site. In the interface list in the GUI, eth0's IP ends in .52 but at the CLI it shows it as ending in .53. Is this how it's supposed to be?

                    eth0 is DHCP assigned from his configuration.

                    thanksajdotcomT 1 Reply Last reply Reply Quote 0
                    • thanksajdotcomT
                      thanksajdotcom @A Former User
                      last edited by

                      @thecreativeone91 said:

                      @thanksajdotcom said:

                      Not sure if I'm misunderstanding something, but I noticed a discrepancy in your post on Ubiquiti's site. In the interface list in the GUI, eth0's IP ends in .52 but at the CLI it shows it as ending in .53. Is this how it's supposed to be?

                      eth0 is DHCP assigned from his configuration.

                      That's why I'm wondering where the discrepancy comes from.

                      1 Reply Last reply Reply Quote 0
                      • thanksajdotcomT
                        thanksajdotcom
                        last edited by

                        Never mind. I just did the math. The .52/30 is the network address. .53 and .54 would fall inside that subnet.

                        1 Reply Last reply Reply Quote 0
                        • ?
                          A Former User
                          last edited by

                          Have you tried hard setting the duplex & speeds and also maybe try a cross-over cable between them.

                          thanksajdotcomT 1 Reply Last reply Reply Quote 0
                          • thanksajdotcomT
                            thanksajdotcom @A Former User
                            last edited by

                            @thecreativeone91 said:

                            Have you tried hard setting the duplex & speeds and also maybe try a cross-over cable between them.

                            Most modern networking devices don't care about the pattern of the wires, as long as it's consistent. They can make almost anything work.

                            ? 1 Reply Last reply Reply Quote -1
                            • ?
                              A Former User @thanksajdotcom
                              last edited by

                              @thanksajdotcom said:

                              Most modern networking devices don't care about the pattern of the wires, as long as it's consistent. They can make almost anything work.

                              Auto MDI-X and Auto negotiation doesn't always work which is where you can see odd problems like this.

                              1 Reply Last reply Reply Quote 1
                              • JaredBuschJ
                                JaredBusch
                                last edited by

                                Picked this back up tonight. new information in the UBNT forum, but looking at MTU issues now.

                                Trying one more setting then calling it a night.

                                1 Reply Last reply Reply Quote 0
                                • ?
                                  A Former User
                                  last edited by A Former User

                                  I have to change my mtu to 1350 I think on 3G. I've seen TCP Window scaling cause similar issues as well (and along with) MTU issues, But I would hope never devices would have issues with it as they both seem to be new enough.

                                  1 Reply Last reply Reply Quote 0
                                  • 1 / 1
                                  • First post
                                    Last post