*To:* Ubiquiti Users Group ubnt_users@wispa.org
*Sent:* Sun, 31 Jul 2016 04:37:33 + (UTC)
*Subject:* Re: [Ubnt_users] upgrading edgemax from 1.7 to 1.8.5
OSPF stops working
Said differently, even though .13 is configured for it, the hello
packet doesn't appear to be refl
md5 key-id 0?
I've had issues with EdgeOS when it was configured for the correct md5 key, on
a different key-id. Usually in multi-vendor situations. Try setting up key-id
1 and 10.
On July 30, 2016 10:49:04 PM CDT, nath...@sswireless.net wrote:
>
>Good evening.
>
>
>
>We had this happen when
se.dup...@celeritycorp.net [mailto:jesse.dup...@celeritycorp.net]
To: Ubiquiti Users Group ubnt_users@wispa.org
Sent: Sun, 31 Jul 2016 04:37:33 + (UTC)
Subject: Re: [Ubnt_users] upgrading edgemax from 1.7 to 1.8.5 OSPF stops
working
Said differently, even though .13 is configured for it, the hello
+ (UTC)
Subject: Re: [Ubnt_users] upgrading edgemax from 1.7 to 1.8.5 OSPF stops
working
Said differently, even though .13 is configured for it, the hello packet
doesn't appear to be reflecting that config.
Get Outlook for Android
On Sat, Jul 30, 2016 at 10:27 PM -0600, "Nathan Ba
Said differently, even though .13 is configured for it, the hello packet
doesn't appear to be reflecting that config.
Get Outlook for Android
On Sat, Jul 30, 2016 at 10:27 PM -0600, "Nathan Babcock"
wrote:
13 adn 14 are set to
Well, in the packet details you provided, one if them says that auth type is
none so that's what made we say that. Maybe the upgrade wipes the key and need
to remove that part of the config and put it in again?
Get Outlook for Android
On Sat, Jul 30, 2016 at 10:27 PM -0600, "Nathan
13 adn 14 are set to MD5. Just reverified this.
On 7/30/2016 10:20 PM, Jesse Dupont wrote:
It looks like there is an Authentication Type mismatch. .13 is set to
none whereas .14 is set to MD5.
On Sat, Jul 30, 2016 at 9:49 PM, > wrote:
It looks like there is an Authentication Type mismatch. .13 is set to none
whereas .14 is set to MD5.
On Sat, Jul 30, 2016 at 9:49 PM, wrote:
> Good evening.
>
>
>
> We had this happen when we reloaded a router at an active site after a
> dhcp issue, and we are in the
Good evening.
We had this happen when we reloaded a router at an active site after a dhcp
issue, and we are in the process of bring up a new site and figured we would
try it on a fresh router without any risk of bringing a customer down.
We loaded the router with 1.7, as this is the