Issue with an ERL behind a CradlePoint MBR1400
-
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?
-
Ok, never mind. No WAN port. Looked it up.
-
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 -
@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.
-
@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.
-
Never mind. I just did the math. The .52/30 is the network address. .53 and .54 would fall inside that subnet.
-
Have you tried hard setting the duplex & speeds and also maybe try a cross-over cable between them.
-
@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.
-
@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.
-
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.
-
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.
