Metal 5SHPn firmware 6.12 is current (addendum)
Note also: What's new in 6.11 (2014-Mar-20 09:16): *) ... *) ovpn - make bridge mode work with big packets (do not leave extraneous padding); Is this related to the "change-mss" firewall mangling rules in our own setup?
Dean, I'll answer both your emails in this one. RE the first email concerning route cache with l2tp tunnels. We saw that and have tested it on Bart's and I's uplink modems and it has not fixed the route cache issue for non-l2tp tunnels, this is confirmed by the forum ports. The mangle rules are not related to ovpn. The issue is that the uplinks have connections (public ISPs) that limit to an MTU of 1500, and the ipip tunnel with ipsec takes up some of that for the headers, so packets must be mangled to be smaller than that to pass through the uplink nodes to and from the internet correctly. Nigel K7NVH On May 3, 2014, at 10:04 PM, Dean Gibson AE7Q <hamwan@ae7q.com> wrote:
Note also:
What's new in 6.11 (2014-Mar-20 09:16):
*) ... *) ovpn - make bridge mode work with big packets (do not leave extraneous padding);
Is this related to the "change-mss" firewall mangling rules in our own setup?
_______________________________________________ PSDR mailing list PSDR@hamwan.org http://mail.hamwan.org/mailman/listinfo/psdr_hamwan.org
Where "correctly" means "without fragmentation". The network will fragment larger packets and still pass them OK, it's just less efficient. TCP can be hinted to use smaller packets which don't require fragmentation, and that's what the MSS settings are about. --Bart On 5/3/2014 10:46 PM, Nigel Vander Houwen wrote:
Dean,
I'll answer both your emails in this one. RE the first email concerning route cache with l2tp tunnels. We saw that and have tested it on Bart's and I's uplink modems and it has not fixed the route cache issue for non-l2tp tunnels, this is confirmed by the forum ports.
The mangle rules are not related to ovpn. The issue is that the uplinks have connections (public ISPs) that limit to an MTU of 1500, and the ipip tunnel with ipsec takes up some of that for the headers, so packets must be mangled to be smaller than that to pass through the uplink nodes to and from the internet correctly.
Nigel K7NVH
On May 3, 2014, at 10:04 PM, Dean Gibson AE7Q <hamwan@ae7q.com> wrote:
Note also:
What's new in 6.11 (2014-Mar-20 09:16):
*) ... *) ovpn - make bridge mode work with big packets (do not leave extraneous padding);
Is this related to the "change-mss" firewall mangling rules in our own setup?
_______________________________________________ PSDR mailing list PSDR@hamwan.org http://mail.hamwan.org/mailman/listinfo/psdr_hamwan.org
_______________________________________________ PSDR mailing list PSDR@hamwan.org http://mail.hamwan.org/mailman/listinfo/psdr_hamwan.org
Well, this did not end well. As you can see from Nigel's SNMP data for my site, right after I installed firmware v6.12 at 9pm, my wireless signal strength dropped by about 10dB. In other respects, everything seems to work, and I at first I thought perhaps it was the rain. However, we've had rain on and off all day, and as you can see from Nigel's site, the signal strength was fairly uniform until the very sudden drop at 9pm. Reboots did not solve the problem, so I reverted to v6.10 using the "downgrade" command line option. That did not improve the signal strength, so I upgraded back to v6.12. I checked all the configuration settings, and everything looked normal. Data transfer through the radio worked fine. So, I decided to reset the configuration (using the command line) to make sure nothing had changed. I'd done that a couple times a month ago, with no ill effects. However, this time it appears to have "bricked" the radio. It draws about 160ma (about the value from a week ago, when I first measured it). There is no light on the side of the unit, and the Ethernet port is dead. I'm going to bed. Sunday morning I will go out onto the roof and attempt to reset the unit via the pinhole. I hope this is not indicative of MikroTik quality. I'm glad the thing is not up on a tower ...
Hehe, congrats on your adventures! Can you elaborate on the ethernet port being "dead"? Do link lights not come up after power-on? If you don't wanna work the reset button in future events like this, there is an option to tell the modem to try PXE booting first, and only after that fails, consult the flash (called "nand" in the config). However, the boot loader would be operating the ethernet port for this to work. If the ethernet port truly does not ever bring up a link after power-on, then that's a weirder problem. Hope the reset helps! --Bart On 5/4/2014 1:44 AM, Dean Gibson AE7Q wrote:
Well, this did not end well.
As you can see from Nigel's SNMP data for my site, right after I installed firmware v6.12 at 9pm, my wireless signal strength dropped by about 10dB. In other respects, everything seems to work, and I at first I thought perhaps it was the rain. However, we've had rain on and off all day, and as you can see from Nigel's site, the signal strength was fairly uniform until the very sudden drop at 9pm.
Reboots did not solve the problem, so I reverted to v6.10 using the "downgrade" command line option. That did not improve the signal strength, so I upgraded back to v6.12. I checked all the configuration settings, and everything looked normal. Data transfer through the radio worked fine.
So, I decided to reset the configuration (using the command line) to make sure nothing had changed. I'd done that a couple times a month ago, with no ill effects.
However, this time it appears to have "bricked" the radio.
It draws about 160ma (about the value from a week ago, when I first measured it). There is no light on the side of the unit, and the Ethernet port is dead.
I'm going to bed. Sunday morning I will go out onto the roof and attempt to reset the unit via the pinhole.
I hope this is not indicative of MikroTik quality. I'm glad the thing is not up on a tower ...
_______________________________________________ PSDR mailing list PSDR@hamwan.org http://mail.hamwan.org/mailman/listinfo/psdr_hamwan.org
Can't find the cheat sheet; however I also thought that I bricked my unit. Was able to connect to it and re-flash.; if memory serves me correctly it was with software that scanned for a Mac address and connected via Layer 2. Hopefully someone here remembers how to do this, or better yet can point you to instructions on the manufacturer's website. Mike WA9QHP -----Original Message----- From: PSDR [mailto:psdr-bounces@hamwan.org] On Behalf Of Dean Gibson AE7Q Sent: Sunday, May 4, 2014 1:44 AM To: Puget Sound Data Ring Subject: Re: [HamWAN PSDR] Metal 5SHPn firmware 6.12 is current (addendum) Well, this did not end well. As you can see from Nigel's SNMP data for my site, right after I installed firmware v6.12 at 9pm, my wireless signal strength dropped by about 10dB. In other respects, everything seems to work, and I at first I thought perhaps it was the rain. However, we've had rain on and off all day, and as you can see from Nigel's site, the signal strength was fairly uniform until the very sudden drop at 9pm. Reboots did not solve the problem, so I reverted to v6.10 using the "downgrade" command line option. That did not improve the signal strength, so I upgraded back to v6.12. I checked all the configuration settings, and everything looked normal. Data transfer through the radio worked fine. So, I decided to reset the configuration (using the command line) to make sure nothing had changed. I'd done that a couple times a month ago, with no ill effects. However, this time it appears to have "bricked" the radio. It draws about 160ma (about the value from a week ago, when I first measured it). There is no light on the side of the unit, and the Ethernet port is dead. I'm going to bed. Sunday morning I will go out onto the roof and attempt to reset the unit via the pinhole. I hope this is not indicative of MikroTik quality. I'm glad the thing is not up on a tower ... _______________________________________________ PSDR mailing list PSDR@hamwan.org http://mail.hamwan.org/mailman/listinfo/psdr_hamwan.org
The Winbox application allows the Layer2 connection.... On Sun, May 4, 2014 at 8:46 AM, Mike Culver <mculver@extencia.com> wrote:
Can't find the cheat sheet; however I also thought that I bricked my unit. Was able to connect to it and re-flash.; if memory serves me correctly it was with software that scanned for a Mac address and connected via Layer 2.
Hopefully someone here remembers how to do this, or better yet can point you to instructions on the manufacturer's website.
Mike WA9QHP
-----Original Message----- From: PSDR [mailto:psdr-bounces@hamwan.org] On Behalf Of Dean Gibson AE7Q Sent: Sunday, May 4, 2014 1:44 AM To: Puget Sound Data Ring Subject: Re: [HamWAN PSDR] Metal 5SHPn firmware 6.12 is current (addendum)
Well, this did not end well.
As you can see from Nigel's SNMP data for my site, right after I installed firmware v6.12 at 9pm, my wireless signal strength dropped by about 10dB. In other respects, everything seems to work, and I at first I thought perhaps it was the rain. However, we've had rain on and off all day, and as you can see from Nigel's site, the signal strength was fairly uniform until the very sudden drop at 9pm.
Reboots did not solve the problem, so I reverted to v6.10 using the "downgrade" command line option. That did not improve the signal strength, so I upgraded back to v6.12. I checked all the configuration settings, and everything looked normal. Data transfer through the radio worked fine.
So, I decided to reset the configuration (using the command line) to make sure nothing had changed. I'd done that a couple times a month ago, with no ill effects.
However, this time it appears to have "bricked" the radio.
It draws about 160ma (about the value from a week ago, when I first measured it). There is no light on the side of the unit, and the Ethernet port is dead.
I'm going to bed. Sunday morning I will go out onto the roof and attempt to reset the unit via the pinhole.
I hope this is not indicative of MikroTik quality. I'm glad the thing is not up on a tower ...
_______________________________________________ PSDR mailing list PSDR@hamwan.org http://mail.hamwan.org/mailman/listinfo/psdr_hamwan.org
_______________________________________________ PSDR mailing list PSDR@hamwan.org http://mail.hamwan.org/mailman/listinfo/psdr_hamwan.org
There's some confusion here, so allow me to clear it up. What Mike's talking about is a utility called Netinstall (http://wiki.mikrotik.com/wiki/Manual:Netinstall) that allows recovery of truly crashed devices. "Truly crashed" means that RouterOS is not booting. It doesn't scan for devices, it just serves as a PXE server, and it's up to the devices to request a PXE boot. The code that controls PXE booting is in a different part of flash than the RouterOS itself, and does not depend on RouterOS. Winbox can indeed use a layer 2 protocol (called mac-winbox), and it can also use IP (layer 3). Which protocol it uses depends on the address (MAC vs IP) you tell it to connect to. However, it doesn't provide the PXE flashing capability. If RouterOS is truly crashed, Winbox won't work. Another layer 2 protocol is mac-telnet. This is configured as a separate service from mac-winbox on RouterOS. Recently we had a case where mac-telnet was inaccessible (was not configured to listen on any interfaces) but mac-winbox was set to its default of listening on all interfaces. We were able to regain control of the router by using the alternative layer 2 protocol. In Dean's case, we don't know what he means by "dead". It could be that the ethernet link is up and IP just stopped working. He can try the 2 MAC protocols. If those fail, he can try the Netinstall recovery. --Bart On 5/4/2014 9:40 AM, Kenny Richards wrote:
The Winbox application allows the Layer2 connection....
On Sun, May 4, 2014 at 8:46 AM, Mike Culver <mculver@extencia.com <mailto:mculver@extencia.com>> wrote:
Can't find the cheat sheet; however I also thought that I bricked my unit. Was able to connect to it and re-flash.; if memory serves me correctly it was with software that scanned for a Mac address and connected via Layer 2.
Hopefully someone here remembers how to do this, or better yet can point you to instructions on the manufacturer's website.
Mike WA9QHP
-----Original Message----- From: PSDR [mailto:psdr-bounces@hamwan.org <mailto:psdr-bounces@hamwan.org>] On Behalf Of Dean Gibson AE7Q Sent: Sunday, May 4, 2014 1:44 AM To: Puget Sound Data Ring Subject: Re: [HamWAN PSDR] Metal 5SHPn firmware 6.12 is current (addendum)
Well, this did not end well.
As you can see from Nigel's SNMP data for my site, right after I installed firmware v6.12 at 9pm, my wireless signal strength dropped by about 10dB. In other respects, everything seems to work, and I at first I thought perhaps it was the rain. However, we've had rain on and off all day, and as you can see from Nigel's site, the signal strength was fairly uniform until the very sudden drop at 9pm.
Reboots did not solve the problem, so I reverted to v6.10 using the "downgrade" command line option. That did not improve the signal strength, so I upgraded back to v6.12. I checked all the configuration settings, and everything looked normal. Data transfer through the radio worked fine.
So, I decided to reset the configuration (using the command line) to make sure nothing had changed. I'd done that a couple times a month ago, with no ill effects.
However, this time it appears to have "bricked" the radio.
It draws about 160ma (about the value from a week ago, when I first measured it). There is no light on the side of the unit, and the Ethernet port is dead.
I'm going to bed. Sunday morning I will go out onto the roof and attempt to reset the unit via the pinhole.
I hope this is not indicative of MikroTik quality. I'm glad the thing is not up on a tower ...
_______________________________________________ PSDR mailing list PSDR@hamwan.org <mailto:PSDR@hamwan.org> http://mail.hamwan.org/mailman/listinfo/psdr_hamwan.org
_______________________________________________ PSDR mailing list PSDR@hamwan.org <mailto:PSDR@hamwan.org> http://mail.hamwan.org/mailman/listinfo/psdr_hamwan.org
_______________________________________________ PSDR mailing list PSDR@hamwan.org http://mail.hamwan.org/mailman/listinfo/psdr_hamwan.org
On May 4, 2014 10:15 AM, "Bart Kus" <me@bartk.us> wrote:
There's some confusion here, so allow me to clear it up.
What Mike's talking about is a utility called Netinstall ( http://wiki.mikrotik.com/wiki/Manual:Netinstall) that allows recovery of truly crashed devices. "Truly crashed" means that RouterOS is not booting. It doesn't scan for devices, it just serves as a PXE server, and it's up to the devices to request a PXE boot. The code that controls PXE booting is in a different part of flash than the RouterOS itself, and does not depend on RouterOS.
Winbox can indeed use a layer 2 protocol (called mac-winbox), and it can also use IP (layer 3). Which protocol it uses depends on the address (MAC vs IP) you tell it to connect to. However, it doesn't provide the PXE flashing capability. If RouterOS is truly crashed, Winbox won't work.
Another layer 2 protocol is mac-telnet. This is configured as a separate service from mac-winbox on RouterOS. Recently we had a case where mac-telnet was inaccessible (was not configured to listen on any interfaces) but mac-winbox was set to its default of listening on all interfaces. We were able to regain control of the router by using the alternative layer 2 protocol.
In Dean's case, we don't know what he means by "dead". It could be that the ethernet link is up and IP just stopped working. He can try the 2 MAC protocols. If those fail, he can try the Netinstall recovery.
--Bart
On 5/4/2014 9:40 AM, Kenny Richards wrote:
The Winbox application allows the Layer2 connection....
On Sun, May 4, 2014 at 8:46 AM, Mike Culver <mculver@extencia.com> wrote:
Can't find the cheat sheet; however I also thought that I bricked my unit. Was able to connect to it and re-flash.; if memory serves me correctly it was with software that scanned for a Mac address and connected via Layer 2.
Hopefully someone here remembers how to do this, or better yet can point you to instructions on the manufacturer's website.
Mike WA9QHP
-----Original Message----- From: PSDR [mailto:psdr-bounces@hamwan.org] On Behalf Of Dean Gibson AE7Q Sent: Sunday, May 4, 2014 1:44 AM To: Puget Sound Data Ring Subject: Re: [HamWAN PSDR] Metal 5SHPn firmware 6.12 is current (addendum)
Well, this did not end well.
As you can see from Nigel's SNMP data for my site, right after I installed firmware v6.12 at 9pm, my wireless signal strength dropped by about 10dB. In other respects, everything seems to work, and I at first I thought perhaps it was the rain. However, we've had rain on and off all day, and as you can see from Nigel's site, the signal strength was fairly uniform until the very sudden drop at 9pm.
Reboots did not solve the problem, so I reverted to v6.10 using the "downgrade" command line option. That did not improve the signal strength, so I upgraded back to v6.12. I checked all the configuration settings, and everything looked normal. Data transfer through the radio worked fine.
So, I decided to reset the configuration (using the command line) to make sure nothing had changed. I'd done that a couple times a month ago, with no ill effects.
However, this time it appears to have "bricked" the radio.
It draws about 160ma (about the value from a week ago, when I first measured it). There is no light on the side of the unit, and the Ethernet port is dead.
I'm going to bed. Sunday morning I will go out onto the roof and attempt to reset the unit via the pinhole.
I hope this is not indicative of MikroTik quality. I'm glad the thing is not up on a tower ...
_______________________________________________ PSDR mailing list PSDR@hamwan.org http://mail.hamwan.org/mailman/listinfo/psdr_hamwan.org
_______________________________________________ PSDR mailing list PSDR@hamwan.org http://mail.hamwan.org/mailman/listinfo/psdr_hamwan.org
_______________________________________________ PSDR mailing listPSDR@hamwan.orghttp://mail.hamwan.org/mailman/listinfo/psdr_hamwan.org
_______________________________________________ PSDR mailing list PSDR@hamwan.org http://mail.hamwan.org/mailman/listinfo/psdr_hamwan.org
OK, everything is back working, and I have my dBm back!! Not a comedy of errors, but two factors intertwined to create this problem: 1. Since configuring the radio after a configuration reset requires the use of WinBox (until you get IP addresses set up), I moved the network connection from the radio to its normal router on the DMZ, and connected it to a router on my LAN via an extension Ethernet cable and a "dual-RJ-45-jack adapter". The port light on the router associated with the radio connection was off. This morning when I went to disconnect the cables, I saw the port light on the router flash momentarily. Junked the dual-RJ-45 adapter and used another one (I had previously tried a different cable), and I had WinBox access to the radio! Everything worked except for the LEDs ... 2. *After much more screwing around*, I found out that for version 6.12,*the LEDs are not configured by default* !!! Remember, I had done a "reset-configuration" ... So, for others that update to v6.12, here are the relevant lines in the setup: */system leds add type=interface-status interface=ether1-local leds=user-led /system leds add type=wireless-signal-strength interface=wlan1-gateway leds=led1,led2,led3,led4,led5* Now that I know I can configure the LEDs with other options, I'll try some. On the IBM PC, I wrote a program for the keyboard LEDs called "Motel" ... I have no clue as to why my dBm dropped, and why I now have my prior values back ... -- Dean -----Original Message----- From: PSDR [mailto:psdr-bounces@hamwan.org <mailto:psdr-bounces@hamwan.org>] On Behalf Of Dean Gibson AE7Q Sent: Sunday, May 4, 2014 1:44 AM To: Puget Sound Data Ring Subject: Re: [HamWAN PSDR] Metal 5SHPn firmware 6.12 is current (addendum) Well, this did not end well. ... I decided to reset the configuration (using the command line) ... it appears to have "bricked" the radio. It draws about 160ma (about the value from a week ago, when I first measured it). There is no light on the side of the unit, and the Ethernet port is dead.
participants (6)
-
Bart Kus -
Bill Vodall -
Dean Gibson AE7Q -
Kenny Richards -
Mike Culver -
Nigel Vander Houwen