Re: [WISPA] Mikrotik routing/queing problem
AMEN to THAT use Intel wherever possible On May 27, 2010, at 7:00 PM, Josh Luthman wrote: > I would definitely replace those. IME Broadcom is the worst *nix NIC. > > Josh Luthman > Office: 937-552-2340 > Direct: 937-552-2343 > 1100 Wayne St > Suite 1337 > Troy, OH 45373 > > “Success is not final, failure is not fatal: it is the courage to > continue that counts.” > --- Winston Churchill > > > > On Thu, May 27, 2010 at 7:51 PM, Kevin Sullivan > wrote: >> Broadcom, not sure which. I'll check. >> >> Kevin >> - Original Message - >> From: "Josh Luthman" >> To: "WISPA General List" >> Sent: Thursday, May 27, 2010 4:30 PM >> Subject: Re: [WISPA] Mikrotik routing/queing problem >> >> >> What NICs are your Linux routers? >> >> On 5/27/10, Kevin Sullivan wrote: >>> Can you lock down gig? Most of the time I've tried to do that it >>> seemed >>> problematic. >>> >>> Kevin >>> - Original Message - >>> From: "Leon D. Zetekoff" >>> To: >>> Sent: Thursday, May 27, 2010 7:09 AM >>> Subject: Re: [WISPA] Mikrotik routing/queing problem >>> >>> >>>> On 5/27/2010 10:04 AM, RickG wrote: >>>>> Auto neg can cause problems. >>>>> >>>>> On Thu, May 27, 2010 at 1:51 AM, Kevin Sullivan >>>>> wrote: >>>>> >>>>>> No, it's a gig link, set to auto neg. >>>>>> >>>> >>>> >>>> auto-neg definitely the problem especially if non gig on other >>>> side. >>>> Lock both sides down >>>> >>>> Leon >>> >>> >>> >>> >>> >>> >>> No virus found in this outgoing message. >>> Checked by AVG - www.avg.com >>> Version: 9.0.819 / Virus Database: 271.1.1/2897 - Release Date: >>> 05/26/10 >>> 02:25:00 >>> >>> >>> >>> >>> >>> >>>> >>>> >>>> >>>> WISPA Wants You! Join today! >>>> http://signup.wispa.org/ >>>> >>>> >>>> WISPA Wireless List: wireless@wispa.org >>>> >>>> Subscribe/Unsubscribe: >>>> http://lists.wispa.org/mailman/listinfo/wireless >>>> >>>> Archives: http://lists.wispa.org/pipermail/wireless/ >>> >>> >>> >>> >>> WISPA Wants You! Join today! >>> http://signup.wispa.org/ >>> >>> >>> WISPA Wireless List: wireless@wispa.org >>> >>> Subscribe/Unsubscribe: >>> http://lists.wispa.org/mailman/listinfo/wireless >>> >>> Archives: http://lists.wispa.org/pipermail/wireless/ >>> >> >> >> -- >> Josh Luthman >> Office: 937-552-2340 >> Direct: 937-552-2343 >> 1100 Wayne St >> Suite 1337 >> Troy, OH 45373 >> >> “Success is not final, failure is not fatal: it is the courage to >> continue that counts.” >> --- Winston Churchill >> >> >> >> WISPA Wants You! Join today! >> http://signup.wispa.org/ >> >> >> WISPA Wireless List: wireless@wispa.org >> >> Subscribe/Unsubscribe: >> http://lists.wispa.org/mailman/listinfo/wireless >> >> Archives: http://lists.wispa.org/pipermail/wireless/ >> >> >> >> >> WISPA Wants You! Join today! >> http://signup.wispa.org/ >> >> >> WISPA Wireless List: wireless@wispa.org >> >> Subscribe/Unsubscribe: >> http://lists.wispa.org/mailman/listinfo/wireless >> >> Archives: http://lists.wispa.org/pipermail/wireless/ >> > > > > WISPA Wants You! Join today! > http://signup.wispa.org/ > > > WISPA Wireless List: wireless@wispa.org > > Subscribe/Unsubscribe: > http://lists.wispa.org/mailman/listinfo/wireless > > Archives: http://lists.wispa.org/pipermail/wireless/ WISPA Wants You! Join today! http://signup.wispa.org/ WISPA Wireless List: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/
Re: [WISPA] Mikrotik routing/queing problem
I would definitely replace those. IME Broadcom is the worst *nix NIC. Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 “Success is not final, failure is not fatal: it is the courage to continue that counts.” --- Winston Churchill On Thu, May 27, 2010 at 7:51 PM, Kevin Sullivan wrote: > Broadcom, not sure which. I'll check. > > Kevin > - Original Message - > From: "Josh Luthman" > To: "WISPA General List" > Sent: Thursday, May 27, 2010 4:30 PM > Subject: Re: [WISPA] Mikrotik routing/queing problem > > > What NICs are your Linux routers? > > On 5/27/10, Kevin Sullivan wrote: >> Can you lock down gig? Most of the time I've tried to do that it seemed >> problematic. >> >> Kevin >> - Original Message - >> From: "Leon D. Zetekoff" >> To: >> Sent: Thursday, May 27, 2010 7:09 AM >> Subject: Re: [WISPA] Mikrotik routing/queing problem >> >> >>> On 5/27/2010 10:04 AM, RickG wrote: >>>> Auto neg can cause problems. >>>> >>>> On Thu, May 27, 2010 at 1:51 AM, Kevin Sullivan >>>> wrote: >>>> >>>>> No, it's a gig link, set to auto neg. >>>>> >>> >>> >>> auto-neg definitely the problem especially if non gig on other side. >>> Lock both sides down >>> >>> Leon >> >> >> >> >> >> >> No virus found in this outgoing message. >> Checked by AVG - www.avg.com >> Version: 9.0.819 / Virus Database: 271.1.1/2897 - Release Date: 05/26/10 >> 02:25:00 >> >> >> >> >> >> >>> >>> >>> >>> WISPA Wants You! Join today! >>> http://signup.wispa.org/ >>> >>> >>> WISPA Wireless List: wireless@wispa.org >>> >>> Subscribe/Unsubscribe: >>> http://lists.wispa.org/mailman/listinfo/wireless >>> >>> Archives: http://lists.wispa.org/pipermail/wireless/ >> >> >> >> >> WISPA Wants You! Join today! >> http://signup.wispa.org/ >> >> >> WISPA Wireless List: wireless@wispa.org >> >> Subscribe/Unsubscribe: >> http://lists.wispa.org/mailman/listinfo/wireless >> >> Archives: http://lists.wispa.org/pipermail/wireless/ >> > > > -- > Josh Luthman > Office: 937-552-2340 > Direct: 937-552-2343 > 1100 Wayne St > Suite 1337 > Troy, OH 45373 > > “Success is not final, failure is not fatal: it is the courage to > continue that counts.” > --- Winston Churchill > > > > WISPA Wants You! Join today! > http://signup.wispa.org/ > > > WISPA Wireless List: wireless@wispa.org > > Subscribe/Unsubscribe: > http://lists.wispa.org/mailman/listinfo/wireless > > Archives: http://lists.wispa.org/pipermail/wireless/ > > > > > WISPA Wants You! Join today! > http://signup.wispa.org/ > > > WISPA Wireless List: wireless@wispa.org > > Subscribe/Unsubscribe: > http://lists.wispa.org/mailman/listinfo/wireless > > Archives: http://lists.wispa.org/pipermail/wireless/ > WISPA Wants You! Join today! http://signup.wispa.org/ WISPA Wireless List: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/
Re: [WISPA] Mikrotik routing/queing problem
Broadcom, not sure which. I'll check. Kevin - Original Message - From: "Josh Luthman" To: "WISPA General List" Sent: Thursday, May 27, 2010 4:30 PM Subject: Re: [WISPA] Mikrotik routing/queing problem What NICs are your Linux routers? On 5/27/10, Kevin Sullivan wrote: > Can you lock down gig? Most of the time I've tried to do that it seemed > problematic. > > Kevin > - Original Message - > From: "Leon D. Zetekoff" > To: > Sent: Thursday, May 27, 2010 7:09 AM > Subject: Re: [WISPA] Mikrotik routing/queing problem > > >> On 5/27/2010 10:04 AM, RickG wrote: >>> Auto neg can cause problems. >>> >>> On Thu, May 27, 2010 at 1:51 AM, Kevin Sullivan >>> wrote: >>> >>>> No, it's a gig link, set to auto neg. >>>> >> >> >> auto-neg definitely the problem especially if non gig on other side. >> Lock both sides down >> >> Leon > > > > > > > No virus found in this outgoing message. > Checked by AVG - www.avg.com > Version: 9.0.819 / Virus Database: 271.1.1/2897 - Release Date: 05/26/10 > 02:25:00 > > > > > > >> >> >> >> WISPA Wants You! Join today! >> http://signup.wispa.org/ >> >> >> WISPA Wireless List: wireless@wispa.org >> >> Subscribe/Unsubscribe: >> http://lists.wispa.org/mailman/listinfo/wireless >> >> Archives: http://lists.wispa.org/pipermail/wireless/ > > > > > WISPA Wants You! Join today! > http://signup.wispa.org/ > > > WISPA Wireless List: wireless@wispa.org > > Subscribe/Unsubscribe: > http://lists.wispa.org/mailman/listinfo/wireless > > Archives: http://lists.wispa.org/pipermail/wireless/ > -- Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 “Success is not final, failure is not fatal: it is the courage to continue that counts.” --- Winston Churchill WISPA Wants You! Join today! http://signup.wispa.org/ WISPA Wireless List: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/ WISPA Wants You! Join today! http://signup.wispa.org/ WISPA Wireless List: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/
Re: [WISPA] Mikrotik routing/queing problem
What NICs are your Linux routers? On 5/27/10, Kevin Sullivan wrote: > Can you lock down gig? Most of the time I've tried to do that it seemed > problematic. > > Kevin > - Original Message - > From: "Leon D. Zetekoff" > To: > Sent: Thursday, May 27, 2010 7:09 AM > Subject: Re: [WISPA] Mikrotik routing/queing problem > > >> On 5/27/2010 10:04 AM, RickG wrote: >>> Auto neg can cause problems. >>> >>> On Thu, May 27, 2010 at 1:51 AM, Kevin Sullivan >>> wrote: >>> >>>> No, it's a gig link, set to auto neg. >>>> >> >> >> auto-neg definitely the problem especially if non gig on other side. >> Lock both sides down >> >> Leon > > > > > > > No virus found in this outgoing message. > Checked by AVG - www.avg.com > Version: 9.0.819 / Virus Database: 271.1.1/2897 - Release Date: 05/26/10 > 02:25:00 > > > > > > >> >> >> >> WISPA Wants You! Join today! >> http://signup.wispa.org/ >> >> >> WISPA Wireless List: wireless@wispa.org >> >> Subscribe/Unsubscribe: >> http://lists.wispa.org/mailman/listinfo/wireless >> >> Archives: http://lists.wispa.org/pipermail/wireless/ > > > > > WISPA Wants You! Join today! > http://signup.wispa.org/ > > > WISPA Wireless List: wireless@wispa.org > > Subscribe/Unsubscribe: > http://lists.wispa.org/mailman/listinfo/wireless > > Archives: http://lists.wispa.org/pipermail/wireless/ > -- Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 “Success is not final, failure is not fatal: it is the courage to continue that counts.” --- Winston Churchill WISPA Wants You! Join today! http://signup.wispa.org/ WISPA Wireless List: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/
Re: [WISPA] Mikrotik routing/queing problem
Can you lock down gig? Most of the time I've tried to do that it seemed problematic. Kevin - Original Message - From: "Leon D. Zetekoff" To: Sent: Thursday, May 27, 2010 7:09 AM Subject: Re: [WISPA] Mikrotik routing/queing problem > On 5/27/2010 10:04 AM, RickG wrote: >> Auto neg can cause problems. >> >> On Thu, May 27, 2010 at 1:51 AM, Kevin Sullivan >> wrote: >> >>> No, it's a gig link, set to auto neg. >>> > > > auto-neg definitely the problem especially if non gig on other side. > Lock both sides down > > Leon No virus found in this outgoing message. Checked by AVG - www.avg.com Version: 9.0.819 / Virus Database: 271.1.1/2897 - Release Date: 05/26/10 02:25:00 > > > > WISPA Wants You! Join today! > http://signup.wispa.org/ > > > WISPA Wireless List: wireless@wispa.org > > Subscribe/Unsubscribe: > http://lists.wispa.org/mailman/listinfo/wireless > > Archives: http://lists.wispa.org/pipermail/wireless/ WISPA Wants You! Join today! http://signup.wispa.org/ WISPA Wireless List: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/
Re: [WISPA] Mikrotik routing/queing problem
On 5/27/2010 10:04 AM, RickG wrote: Auto neg can cause problems. On Thu, May 27, 2010 at 1:51 AM, Kevin Sullivan wrote: No, it's a gig link, set to auto neg. auto-neg definitely the problem especially if non gig on other side. Lock both sides down Leon No virus found in this outgoing message. Checked by AVG - www.avg.com Version: 9.0.819 / Virus Database: 271.1.1/2897 - Release Date: 05/26/10 02:25:00 WISPA Wants You! Join today! http://signup.wispa.org/ WISPA Wireless List: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/
Re: [WISPA] Mikrotik routing/queing problem
Auto neg can cause problems. On Thu, May 27, 2010 at 1:51 AM, Kevin Sullivan wrote: > No, it's a gig link, set to auto neg. > > Kevin > - Original Message - > From: "RickG" > To: "WISPA General List" > Sent: Wednesday, May 26, 2010 6:55 PM > Subject: Re: [WISPA] Mikrotik routing/queing problem > > > I havent seen that on my RB1000. Do you have the ports locked down to > a set rate? > > On Wed, May 26, 2010 at 1:16 PM, Kevin Sullivan > wrote: >> I think I have found a legitimate bug. I'm running an RB1000 that >> we put in service about 2 weeks ago (it replaced another RB1000 that was >> having similar problems). Here is what is going on: >> >> Linux router "A" <-> [ether1] RB1000 [ether3] <---> Linux >> router "B" >> >> >> The RB1000 above is connected to the two hosts shown. >> Each link A < > RB1000 < > B has latency ~1ms. We are not using any >> Mikrotik wireless. >> >> A and B both know that they can reach each other through the RB1000 >> (thanks >> to OSPF). >> >> A and B are Linux routers. When I ping B from A (traffic going through the >> RB1000), I get no response. When I log into B and tcpdump traffic, I can >> see icmp echo request packets coming in from A, and echo reply packets >> going >> out to A. Fine. I then log into the RB1000 and packet sniff ether1 and >> ether3. >> >> ether1 packet sniff shows icmp request packets coming in. ether3 shows >> icmp >> request packets going out, and icmp reply packets coming in. However, the >> replies are not going out ether1. >> >> BUT after several minutes, A starts seeing replies. >> >> 64 bytes from x.x.x.x: icmp_seq=1049 ttl=63 time=671216 ms >> 64 bytes from x.x.x.x: icmp_seq=1095 ttl=63 time=628217 ms >> 64 bytes from x.x.x.x: icmp_seq=1142 ttl=63 time=584217 ms >> 64 bytes from x.x.x.x: icmp_seq=1188 ttl=63 time=541218 ms >> 64 bytes from x.x.x.x: icmp_seq=1235 ttl=63 time=497234 ms >> >> the RB1000 has been queuing my ICMP packets for ~500 seconds!! >> >> I STOP pinging from A and packet sniff ether1 on the RB1000 again. It is >> STILL sending out queued ICMP replies from A, even though I am >> not sending requests anymore. >> >> Several minutes after I stop pinging from A, the RB1000 stops sending >> replies on ether1. >> >> Clients have been complaining for months about slow speeds passing traffic >> through this router. I've also noticed high CPU utilization, even when >> normal CPU hungry tasks were turned off (one mangle rule, no queues, no >> proxy, no DNS, etc). During the day, we see 70-80% CPU utilization. The >> previous router (same config) went to 100% utilization, which is why we >> replaced it. >> >> Regards, >> >> Kevin >> >> >> >> >> >> >> >> >> WISPA Wants You! Join today! >> http://signup.wispa.org/ >> >> >> WISPA Wireless List: wireless@wispa.org >> >> Subscribe/Unsubscribe: >> http://lists.wispa.org/mailman/listinfo/wireless >> >> Archives: http://lists.wispa.org/pipermail/wireless/ >> > > > > WISPA Wants You! Join today! > http://signup.wispa.org/ > > > WISPA Wireless List: wireless@wispa.org > > Subscribe/Unsubscribe: > http://lists.wispa.org/mailman/listinfo/wireless > > Archives: http://lists.wispa.org/pipermail/wireless/ > > > > > WISPA Wants You! Join today! > http://signup.wispa.org/ > > > WISPA Wireless List: wireless@wispa.org > > Subscribe/Unsubscribe: > http://lists.wispa.org/mailman/listinfo/wireless > > Archives: http://lists.wispa.org/pipermail/wireless/ > WISPA Wants You! Join today! http://signup.wispa.org/ WISPA Wireless List: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/
Re: [WISPA] Mikrotik routing/queing problem
Did you upgrade to 4.9 Did you run an earlier version with this router with this same configuration? Have you tried regressing to an earlier version? Did you post this issue to the MT forum? Greg On May 27, 2010, at 1:19 AM, Kevin Sullivan wrote: > 4.9 > - Original Message - > From: "Josh Luthman" > To: "WISPA General List" > Sent: Wednesday, May 26, 2010 12:18 PM > Subject: Re: [WISPA] Mikrotik routing/queing problem > > > Also what firmware (sys routerboar pr)? > > Josh Luthman > Office: 937-552-2340 > Direct: 937-552-2343 > 1100 Wayne St > Suite 1337 > Troy, OH 45373 > > “Success is not final, failure is not fatal: it is the courage to continue > that counts.” > --- Winston Churchill > > > On Wed, May 26, 2010 at 3:15 PM, Greg Ihnen wrote: > >> What version of RouterOS are you running? >> >> Greg >> >> On May 26, 2010, at 12:46 PM, Kevin Sullivan wrote: >> >>> I think I have found a legitimate bug. I'm running an RB1000 that >>> we put in service about 2 weeks ago (it replaced another RB1000 that was >>> having similar problems). Here is what is going on: >>> >>> Linux router "A" <-> [ether1] RB1000 [ether3] <---> >> Linux router "B" >>> >>> >>> The RB1000 above is connected to the two hosts shown. >>> Each link A < > RB1000 < > B has latency ~1ms. We are not using any >>> Mikrotik wireless. >>> >>> A and B both know that they can reach each other through the RB1000 >> (thanks >>> to OSPF). >>> >>> A and B are Linux routers. When I ping B from A (traffic going through >> the >>> RB1000), I get no response. When I log into B and tcpdump traffic, I >>> can >>> see icmp echo request packets coming in from A, and echo reply packets >> going >>> out to A. Fine. I then log into the RB1000 and packet sniff ether1 and >>> ether3. >>> >>> ether1 packet sniff shows icmp request packets coming in. ether3 shows >> icmp >>> request packets going out, and icmp reply packets coming in. However, >> the >>> replies are not going out ether1. >>> >>> BUT after several minutes, A starts seeing replies. >>> >>> 64 bytes from x.x.x.x: icmp_seq=1049 ttl=63 time=671216 ms >>> 64 bytes from x.x.x.x: icmp_seq=1095 ttl=63 time=628217 ms >>> 64 bytes from x.x.x.x: icmp_seq=1142 ttl=63 time=584217 ms >>> 64 bytes from x.x.x.x: icmp_seq=1188 ttl=63 time=541218 ms >>> 64 bytes from x.x.x.x: icmp_seq=1235 ttl=63 time=497234 ms >>> >>> the RB1000 has been queuing my ICMP packets for ~500 seconds!! >>> >>> I STOP pinging from A and packet sniff ether1 on the RB1000 again. It >>> is >>> STILL sending out queued ICMP replies from A, even though I am >>> not sending requests anymore. >>> >>> Several minutes after I stop pinging from A, the RB1000 stops sending >>> replies on ether1. >>> >>> Clients have been complaining for months about slow speeds passing >> traffic >>> through this router. I've also noticed high CPU utilization, even when >>> normal CPU hungry tasks were turned off (one mangle rule, no queues, no >>> proxy, no DNS, etc). During the day, we see 70-80% CPU utilization. >> The >>> previous router (same config) went to 100% utilization, which is why we >>> replaced it. >>> >>> Regards, >>> >>> Kevin >>> >>> >>> >>> >>> >>> >>> >>> >> >>> WISPA Wants You! Join today! >>> http://signup.wispa.org/ >>> >> >>> >>> WISPA Wireless List: wireless@wispa.org >>> >>> Subscribe/Unsubscribe: >>> http://lists.wispa.org/mailman/listinfo/wireless >>> >>> Archives: http://lists.wispa.org/pipermail/wireless/ >> >> >> >> >> >> WISPA Wants You! Join today! >> http://signup.wispa.org/ >> >> >> >> WISPA Wireless List: wireless@wispa.org >> >> Subscr
Re: [WISPA] Mikrotik routing/queing problem
Check that again... [jluth...@jmlhomerouter] > sys resour pr uptime: 1w6d11h14m7s version: "4.9" free-memory: 15668kB total-memory: 29944kB cpu: "MIPS 24K V7.4" cpu-count: 1 cpu-frequency: 400MHz cpu-load: 7 free-hdd-space: 30796kB total-hdd-space: 61440kB write-sect-since-reboot: 2201993 write-sect-total: 2298678 bad-blocks: 0 architecture-name: "mipsbe" board-name: "RB750" platform: "MikroTik" [jluth...@jmlhomerouter] > sys routerb pr routerboard: yes model: "750" serial-number: "qqpewpew" current-firmware: "2.22" upgrade-firmware: "2.26" Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 “Success is not final, failure is not fatal: it is the courage to continue that counts.” --- Winston Churchill On Thu, May 27, 2010 at 1:49 AM, Kevin Sullivan wrote: > 4.9 > - Original Message - > From: "Josh Luthman" > To: "WISPA General List" > Sent: Wednesday, May 26, 2010 12:18 PM > Subject: Re: [WISPA] Mikrotik routing/queing problem > > > Also what firmware (sys routerboar pr)? > > Josh Luthman > Office: 937-552-2340 > Direct: 937-552-2343 > 1100 Wayne St > Suite 1337 > Troy, OH 45373 > > “Success is not final, failure is not fatal: it is the courage to continue > that counts.” > --- Winston Churchill > > > On Wed, May 26, 2010 at 3:15 PM, Greg Ihnen wrote: > >> What version of RouterOS are you running? >> >> Greg >> >> On May 26, 2010, at 12:46 PM, Kevin Sullivan wrote: >> >> > I think I have found a legitimate bug. I'm running an RB1000 that >> > we put in service about 2 weeks ago (it replaced another RB1000 that was >> > having similar problems). Here is what is going on: >> > >> > Linux router "A" <-> [ether1] RB1000 [ether3] <---> >> Linux router "B" >> > >> > >> > The RB1000 above is connected to the two hosts shown. >> > Each link A < > RB1000 < > B has latency ~1ms. We are not using any >> > Mikrotik wireless. >> > >> > A and B both know that they can reach each other through the RB1000 >> (thanks >> > to OSPF). >> > >> > A and B are Linux routers. When I ping B from A (traffic going through >> the >> > RB1000), I get no response. When I log into B and tcpdump traffic, I >> > can >> > see icmp echo request packets coming in from A, and echo reply packets >> going >> > out to A. Fine. I then log into the RB1000 and packet sniff ether1 and >> > ether3. >> > >> > ether1 packet sniff shows icmp request packets coming in. ether3 shows >> icmp >> > request packets going out, and icmp reply packets coming in. However, >> the >> > replies are not going out ether1. >> > >> > BUT after several minutes, A starts seeing replies. >> > >> > 64 bytes from x.x.x.x: icmp_seq=1049 ttl=63 time=671216 ms >> > 64 bytes from x.x.x.x: icmp_seq=1095 ttl=63 time=628217 ms >> > 64 bytes from x.x.x.x: icmp_seq=1142 ttl=63 time=584217 ms >> > 64 bytes from x.x.x.x: icmp_seq=1188 ttl=63 time=541218 ms >> > 64 bytes from x.x.x.x: icmp_seq=1235 ttl=63 time=497234 ms >> > >> > the RB1000 has been queuing my ICMP packets for ~500 seconds!! >> > >> > I STOP pinging from A and packet sniff ether1 on the RB1000 again. It >> > is >> > STILL sending out queued ICMP replies from A, even though I am >> > not sending requests anymore. >> > >> > Several minutes after I stop pinging from A, the RB1000 stops sending >> > replies on ether1. >> > >> > Clients have been complaining for months about slow speeds passing >> traffic >> > through this router. I've also noticed high CPU utilization, even when >> > normal CPU hungry tasks were turned off (one mangle rule, no queues, no >> > proxy, no DNS, etc). During the day, we see 70-80% CPU utilization. >> The >> > previous router (same config) went to 100% utilization, which is why we >> > replaced it. >> > >> > Regards, >> > >> > Kevin >> > >> > >> > >> > >> > >> > >> > >
Re: [WISPA] Mikrotik routing/queing problem
No, it's a gig link, set to auto neg. Kevin - Original Message - From: "RickG" To: "WISPA General List" Sent: Wednesday, May 26, 2010 6:55 PM Subject: Re: [WISPA] Mikrotik routing/queing problem I havent seen that on my RB1000. Do you have the ports locked down to a set rate? On Wed, May 26, 2010 at 1:16 PM, Kevin Sullivan wrote: > I think I have found a legitimate bug. I'm running an RB1000 that > we put in service about 2 weeks ago (it replaced another RB1000 that was > having similar problems). Here is what is going on: > > Linux router "A" <-> [ether1] RB1000 [ether3] <---> Linux > router "B" > > > The RB1000 above is connected to the two hosts shown. > Each link A < > RB1000 < > B has latency ~1ms. We are not using any > Mikrotik wireless. > > A and B both know that they can reach each other through the RB1000 > (thanks > to OSPF). > > A and B are Linux routers. When I ping B from A (traffic going through the > RB1000), I get no response. When I log into B and tcpdump traffic, I can > see icmp echo request packets coming in from A, and echo reply packets > going > out to A. Fine. I then log into the RB1000 and packet sniff ether1 and > ether3. > > ether1 packet sniff shows icmp request packets coming in. ether3 shows > icmp > request packets going out, and icmp reply packets coming in. However, the > replies are not going out ether1. > > BUT after several minutes, A starts seeing replies. > > 64 bytes from x.x.x.x: icmp_seq=1049 ttl=63 time=671216 ms > 64 bytes from x.x.x.x: icmp_seq=1095 ttl=63 time=628217 ms > 64 bytes from x.x.x.x: icmp_seq=1142 ttl=63 time=584217 ms > 64 bytes from x.x.x.x: icmp_seq=1188 ttl=63 time=541218 ms > 64 bytes from x.x.x.x: icmp_seq=1235 ttl=63 time=497234 ms > > the RB1000 has been queuing my ICMP packets for ~500 seconds!! > > I STOP pinging from A and packet sniff ether1 on the RB1000 again. It is > STILL sending out queued ICMP replies from A, even though I am > not sending requests anymore. > > Several minutes after I stop pinging from A, the RB1000 stops sending > replies on ether1. > > Clients have been complaining for months about slow speeds passing traffic > through this router. I've also noticed high CPU utilization, even when > normal CPU hungry tasks were turned off (one mangle rule, no queues, no > proxy, no DNS, etc). During the day, we see 70-80% CPU utilization. The > previous router (same config) went to 100% utilization, which is why we > replaced it. > > Regards, > > Kevin > > > > > > > > > WISPA Wants You! Join today! > http://signup.wispa.org/ > > > WISPA Wireless List: wireless@wispa.org > > Subscribe/Unsubscribe: > http://lists.wispa.org/mailman/listinfo/wireless > > Archives: http://lists.wispa.org/pipermail/wireless/ > WISPA Wants You! Join today! http://signup.wispa.org/ WISPA Wireless List: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/ WISPA Wants You! Join today! http://signup.wispa.org/ WISPA Wireless List: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/
Re: [WISPA] Mikrotik routing/queing problem
4.9 - Original Message - From: "Josh Luthman" To: "WISPA General List" Sent: Wednesday, May 26, 2010 12:18 PM Subject: Re: [WISPA] Mikrotik routing/queing problem Also what firmware (sys routerboar pr)? Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 “Success is not final, failure is not fatal: it is the courage to continue that counts.” --- Winston Churchill On Wed, May 26, 2010 at 3:15 PM, Greg Ihnen wrote: > What version of RouterOS are you running? > > Greg > > On May 26, 2010, at 12:46 PM, Kevin Sullivan wrote: > > > I think I have found a legitimate bug. I'm running an RB1000 that > > we put in service about 2 weeks ago (it replaced another RB1000 that was > > having similar problems). Here is what is going on: > > > > Linux router "A" <-> [ether1] RB1000 [ether3] <---> > Linux router "B" > > > > > > The RB1000 above is connected to the two hosts shown. > > Each link A < > RB1000 < > B has latency ~1ms. We are not using any > > Mikrotik wireless. > > > > A and B both know that they can reach each other through the RB1000 > (thanks > > to OSPF). > > > > A and B are Linux routers. When I ping B from A (traffic going through > the > > RB1000), I get no response. When I log into B and tcpdump traffic, I > > can > > see icmp echo request packets coming in from A, and echo reply packets > going > > out to A. Fine. I then log into the RB1000 and packet sniff ether1 and > > ether3. > > > > ether1 packet sniff shows icmp request packets coming in. ether3 shows > icmp > > request packets going out, and icmp reply packets coming in. However, > the > > replies are not going out ether1. > > > > BUT after several minutes, A starts seeing replies. > > > > 64 bytes from x.x.x.x: icmp_seq=1049 ttl=63 time=671216 ms > > 64 bytes from x.x.x.x: icmp_seq=1095 ttl=63 time=628217 ms > > 64 bytes from x.x.x.x: icmp_seq=1142 ttl=63 time=584217 ms > > 64 bytes from x.x.x.x: icmp_seq=1188 ttl=63 time=541218 ms > > 64 bytes from x.x.x.x: icmp_seq=1235 ttl=63 time=497234 ms > > > > the RB1000 has been queuing my ICMP packets for ~500 seconds!! > > > > I STOP pinging from A and packet sniff ether1 on the RB1000 again. It > > is > > STILL sending out queued ICMP replies from A, even though I am > > not sending requests anymore. > > > > Several minutes after I stop pinging from A, the RB1000 stops sending > > replies on ether1. > > > > Clients have been complaining for months about slow speeds passing > traffic > > through this router. I've also noticed high CPU utilization, even when > > normal CPU hungry tasks were turned off (one mangle rule, no queues, no > > proxy, no DNS, etc). During the day, we see 70-80% CPU utilization. > The > > previous router (same config) went to 100% utilization, which is why we > > replaced it. > > > > Regards, > > > > Kevin > > > > > > > > > > > > > > > > > > > WISPA Wants You! Join today! > > http://signup.wispa.org/ > > > > > > > WISPA Wireless List: wireless@wispa.org > > > > Subscribe/Unsubscribe: > > http://lists.wispa.org/mailman/listinfo/wireless > > > > Archives: http://lists.wispa.org/pipermail/wireless/ > > > > > > WISPA Wants You! Join today! > http://signup.wispa.org/ > > > > WISPA Wireless List: wireless@wispa.org > > Subscribe/Unsubscribe: > http://lists.wispa.org/mailman/listinfo/wireless > > Archives: http://lists.wispa.org/pipermail/wireless/ > WISPA Wants You! Join today! http://signup.wispa.org/ WISPA Wireless List: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/ WISPA Wants You! Join today! http://signup.wispa.org/ WISPA Wireless List: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/
Re: [WISPA] Mikrotik routing/queing problem
I havent seen that on my RB1000. Do you have the ports locked down to a set rate? On Wed, May 26, 2010 at 1:16 PM, Kevin Sullivan wrote: > I think I have found a legitimate bug. I'm running an RB1000 that > we put in service about 2 weeks ago (it replaced another RB1000 that was > having similar problems). Here is what is going on: > > Linux router "A" <-> [ether1] RB1000 [ether3] <---> Linux > router "B" > > > The RB1000 above is connected to the two hosts shown. > Each link A < > RB1000 < > B has latency ~1ms. We are not using any > Mikrotik wireless. > > A and B both know that they can reach each other through the RB1000 (thanks > to OSPF). > > A and B are Linux routers. When I ping B from A (traffic going through the > RB1000), I get no response. When I log into B and tcpdump traffic, I can > see icmp echo request packets coming in from A, and echo reply packets going > out to A. Fine. I then log into the RB1000 and packet sniff ether1 and > ether3. > > ether1 packet sniff shows icmp request packets coming in. ether3 shows icmp > request packets going out, and icmp reply packets coming in. However, the > replies are not going out ether1. > > BUT after several minutes, A starts seeing replies. > > 64 bytes from x.x.x.x: icmp_seq=1049 ttl=63 time=671216 ms > 64 bytes from x.x.x.x: icmp_seq=1095 ttl=63 time=628217 ms > 64 bytes from x.x.x.x: icmp_seq=1142 ttl=63 time=584217 ms > 64 bytes from x.x.x.x: icmp_seq=1188 ttl=63 time=541218 ms > 64 bytes from x.x.x.x: icmp_seq=1235 ttl=63 time=497234 ms > > the RB1000 has been queuing my ICMP packets for ~500 seconds!! > > I STOP pinging from A and packet sniff ether1 on the RB1000 again. It is > STILL sending out queued ICMP replies from A, even though I am > not sending requests anymore. > > Several minutes after I stop pinging from A, the RB1000 stops sending > replies on ether1. > > Clients have been complaining for months about slow speeds passing traffic > through this router. I've also noticed high CPU utilization, even when > normal CPU hungry tasks were turned off (one mangle rule, no queues, no > proxy, no DNS, etc). During the day, we see 70-80% CPU utilization. The > previous router (same config) went to 100% utilization, which is why we > replaced it. > > Regards, > > Kevin > > > > > > > > > WISPA Wants You! Join today! > http://signup.wispa.org/ > > > WISPA Wireless List: wireless@wispa.org > > Subscribe/Unsubscribe: > http://lists.wispa.org/mailman/listinfo/wireless > > Archives: http://lists.wispa.org/pipermail/wireless/ > WISPA Wants You! Join today! http://signup.wispa.org/ WISPA Wireless List: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/
Re: [WISPA] Mikrotik routing/queing problem
Also what firmware (sys routerboar pr)? Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 “Success is not final, failure is not fatal: it is the courage to continue that counts.” --- Winston Churchill On Wed, May 26, 2010 at 3:15 PM, Greg Ihnen wrote: > What version of RouterOS are you running? > > Greg > > On May 26, 2010, at 12:46 PM, Kevin Sullivan wrote: > > > I think I have found a legitimate bug. I'm running an RB1000 that > > we put in service about 2 weeks ago (it replaced another RB1000 that was > > having similar problems). Here is what is going on: > > > > Linux router "A" <-> [ether1] RB1000 [ether3] <---> > Linux router "B" > > > > > > The RB1000 above is connected to the two hosts shown. > > Each link A < > RB1000 < > B has latency ~1ms. We are not using any > > Mikrotik wireless. > > > > A and B both know that they can reach each other through the RB1000 > (thanks > > to OSPF). > > > > A and B are Linux routers. When I ping B from A (traffic going through > the > > RB1000), I get no response. When I log into B and tcpdump traffic, I can > > see icmp echo request packets coming in from A, and echo reply packets > going > > out to A. Fine. I then log into the RB1000 and packet sniff ether1 and > > ether3. > > > > ether1 packet sniff shows icmp request packets coming in. ether3 shows > icmp > > request packets going out, and icmp reply packets coming in. However, > the > > replies are not going out ether1. > > > > BUT after several minutes, A starts seeing replies. > > > > 64 bytes from x.x.x.x: icmp_seq=1049 ttl=63 time=671216 ms > > 64 bytes from x.x.x.x: icmp_seq=1095 ttl=63 time=628217 ms > > 64 bytes from x.x.x.x: icmp_seq=1142 ttl=63 time=584217 ms > > 64 bytes from x.x.x.x: icmp_seq=1188 ttl=63 time=541218 ms > > 64 bytes from x.x.x.x: icmp_seq=1235 ttl=63 time=497234 ms > > > > the RB1000 has been queuing my ICMP packets for ~500 seconds!! > > > > I STOP pinging from A and packet sniff ether1 on the RB1000 again. It is > > STILL sending out queued ICMP replies from A, even though I am > > not sending requests anymore. > > > > Several minutes after I stop pinging from A, the RB1000 stops sending > > replies on ether1. > > > > Clients have been complaining for months about slow speeds passing > traffic > > through this router. I've also noticed high CPU utilization, even when > > normal CPU hungry tasks were turned off (one mangle rule, no queues, no > > proxy, no DNS, etc). During the day, we see 70-80% CPU utilization. > The > > previous router (same config) went to 100% utilization, which is why we > > replaced it. > > > > Regards, > > > > Kevin > > > > > > > > > > > > > > > > > > > WISPA Wants You! Join today! > > http://signup.wispa.org/ > > > > > > > WISPA Wireless List: wireless@wispa.org > > > > Subscribe/Unsubscribe: > > http://lists.wispa.org/mailman/listinfo/wireless > > > > Archives: http://lists.wispa.org/pipermail/wireless/ > > > > > > WISPA Wants You! Join today! > http://signup.wispa.org/ > > > > WISPA Wireless List: wireless@wispa.org > > Subscribe/Unsubscribe: > http://lists.wispa.org/mailman/listinfo/wireless > > Archives: http://lists.wispa.org/pipermail/wireless/ > WISPA Wants You! Join today! http://signup.wispa.org/ WISPA Wireless List: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/
Re: [WISPA] Mikrotik routing/queing problem
What version of RouterOS are you running? Greg On May 26, 2010, at 12:46 PM, Kevin Sullivan wrote: > I think I have found a legitimate bug. I'm running an RB1000 that > we put in service about 2 weeks ago (it replaced another RB1000 that was > having similar problems). Here is what is going on: > > Linux router "A" <-> [ether1] RB1000 [ether3] <---> Linux > router "B" > > > The RB1000 above is connected to the two hosts shown. > Each link A < > RB1000 < > B has latency ~1ms. We are not using any > Mikrotik wireless. > > A and B both know that they can reach each other through the RB1000 (thanks > to OSPF). > > A and B are Linux routers. When I ping B from A (traffic going through the > RB1000), I get no response. When I log into B and tcpdump traffic, I can > see icmp echo request packets coming in from A, and echo reply packets going > out to A. Fine. I then log into the RB1000 and packet sniff ether1 and > ether3. > > ether1 packet sniff shows icmp request packets coming in. ether3 shows icmp > request packets going out, and icmp reply packets coming in. However, the > replies are not going out ether1. > > BUT after several minutes, A starts seeing replies. > > 64 bytes from x.x.x.x: icmp_seq=1049 ttl=63 time=671216 ms > 64 bytes from x.x.x.x: icmp_seq=1095 ttl=63 time=628217 ms > 64 bytes from x.x.x.x: icmp_seq=1142 ttl=63 time=584217 ms > 64 bytes from x.x.x.x: icmp_seq=1188 ttl=63 time=541218 ms > 64 bytes from x.x.x.x: icmp_seq=1235 ttl=63 time=497234 ms > > the RB1000 has been queuing my ICMP packets for ~500 seconds!! > > I STOP pinging from A and packet sniff ether1 on the RB1000 again. It is > STILL sending out queued ICMP replies from A, even though I am > not sending requests anymore. > > Several minutes after I stop pinging from A, the RB1000 stops sending > replies on ether1. > > Clients have been complaining for months about slow speeds passing traffic > through this router. I've also noticed high CPU utilization, even when > normal CPU hungry tasks were turned off (one mangle rule, no queues, no > proxy, no DNS, etc). During the day, we see 70-80% CPU utilization. The > previous router (same config) went to 100% utilization, which is why we > replaced it. > > Regards, > > Kevin > > > > > > > > > WISPA Wants You! Join today! > http://signup.wispa.org/ > > > WISPA Wireless List: wireless@wispa.org > > Subscribe/Unsubscribe: > http://lists.wispa.org/mailman/listinfo/wireless > > Archives: http://lists.wispa.org/pipermail/wireless/ WISPA Wants You! Join today! http://signup.wispa.org/ WISPA Wireless List: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/
[WISPA] Mikrotik routing/queing problem
I think I have found a legitimate bug. I'm running an RB1000 that we put in service about 2 weeks ago (it replaced another RB1000 that was having similar problems). Here is what is going on: Linux router "A" <-> [ether1] RB1000 [ether3] <---> Linux router "B" The RB1000 above is connected to the two hosts shown. Each link A < > RB1000 < > B has latency ~1ms. We are not using any Mikrotik wireless. A and B both know that they can reach each other through the RB1000 (thanks to OSPF). A and B are Linux routers. When I ping B from A (traffic going through the RB1000), I get no response. When I log into B and tcpdump traffic, I can see icmp echo request packets coming in from A, and echo reply packets going out to A. Fine. I then log into the RB1000 and packet sniff ether1 and ether3. ether1 packet sniff shows icmp request packets coming in. ether3 shows icmp request packets going out, and icmp reply packets coming in. However, the replies are not going out ether1. BUT after several minutes, A starts seeing replies. 64 bytes from x.x.x.x: icmp_seq=1049 ttl=63 time=671216 ms 64 bytes from x.x.x.x: icmp_seq=1095 ttl=63 time=628217 ms 64 bytes from x.x.x.x: icmp_seq=1142 ttl=63 time=584217 ms 64 bytes from x.x.x.x: icmp_seq=1188 ttl=63 time=541218 ms 64 bytes from x.x.x.x: icmp_seq=1235 ttl=63 time=497234 ms the RB1000 has been queuing my ICMP packets for ~500 seconds!! I STOP pinging from A and packet sniff ether1 on the RB1000 again. It is STILL sending out queued ICMP replies from A, even though I am not sending requests anymore. Several minutes after I stop pinging from A, the RB1000 stops sending replies on ether1. Clients have been complaining for months about slow speeds passing traffic through this router. I've also noticed high CPU utilization, even when normal CPU hungry tasks were turned off (one mangle rule, no queues, no proxy, no DNS, etc). During the day, we see 70-80% CPU utilization. The previous router (same config) went to 100% utilization, which is why we replaced it. Regards, Kevin WISPA Wants You! Join today! http://signup.wispa.org/ WISPA Wireless List: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/
