Really, really odd problem with RouterOS 2.9.40

thermant · Sat Apr 21, 2007 6:32 am

Heya guys,

A newbie with a strange problem here.

I've just recently installed RouterOS 2.9.40 on my router, and I have this weird problem with a LAN Card suddenly disconnecting (usually) once a day.

I'm using the onboard LAN Card (Local) and a 3Com 3c905B-TX (Public)on the router, and the one that keeps disconnecting is the 3Com. It just, well, died for no apparent reason. I have to get into winbox and disable the 3Com, then enables it again, and then it would connect just fine.

Most of the time it would just do this once a day, but on certain occasion it would do it twice a day.

Oh, by the way, RouterOS detects the 3Com as 3Com 3c59x PCI, and I'm using a Lv 1 (demo) license. Is this some sort of limitation of the Lv 1 license?

Sure, it's usually only once a day, but this disconnect thing really annoys my customers...

Anyone can help?

Thanks much.

thermant · Sun Apr 22, 2007 5:46 am

No one can help me with this?

Well, the only fiewall rule I use is the one for the NAT:

chain=srcnat out-interface=PUBLIC action=masquerade

Just like in the quick start, and nothing else.

Does this help anyone answer my question somewhat?

Whenever this problem happens, I look in the "Packages" section that "Routing" is disabled. Is this why the problem happens? And is it possible that someone from the outside somehow disables it (I have a 30+ char password)?

I have now enabled the firewall through the web interface (I checked everything "Protect Router", "Protect Customer", and "NAT"). Is it possible that the same problem will happen in the future?

Anyone shedding light on this matter is greatly appreciated.

Thanks much.

mneumark · Sun Apr 22, 2007 8:48 am

Thermant,

First recommend is to upgrade to 2.9.42. Second as long as you got routing-test or routing enable then yes you should be able to route traffic.

Matt

thermant · Mon May 07, 2007 5:22 am

mneumark:
Like you suggested, I upgraded to .42. Also added some firewall rules through the winbox web interface (enabled both protect router and protect customer). I also changed the Public interface to use the DLink card.

Things were fine for a few days.

Now the same problem is back, although slightly changed. The router would still disconnects (usually) once a day, but sometimes it would reconnect on its own. Other times it requires me to disconnect then reconnect the lan cable that's used for Public...

Oh, by the way, now the Package List (/system/package) shows the correct services and didn't change on its own like before. So what should be enabled stays enabled, and what should be disabled (routing-test, wireless-legacy, and webproxy-test) stay disabled.

Suggestions, anyone?

jerryroy1 · Mon May 07, 2007 6:53 am

mneumark:
Like you suggested, I upgraded to .42. Also added some firewall rules through the winbox web interface (enabled both protect router and protect customer). I also changed the Public interface to use the DLink card.

Things were fine for a few days.

Now the same problem is back, although slightly changed. The router would still disconnects (usually) once a day, but sometimes it would reconnect on its own. Other times it requires me to disconnect then reconnect the lan cable that's used for Public...

Oh, by the way, now the Package List (/system/package) shows the correct services and didn't change on its own like before. So what should be enabled stays enabled, and what should be disabled (routing-test, wireless-legacy, and webproxy-test) stay disabled.

Suggestions, anyone?

What board is it? I am having a constant disconnect when using winbox and packet loss. I am directly connected poe and have static IP's on RB and Notebook. see my post for details

http://forum.mikrotik.com/viewtopic.php?t=15622

thermant · Mon May 07, 2007 7:05 am

board? Oh, you mean routerboard? No, I'm using a PC.

Sorry I forgot to mention that in my post.

savage · Mon May 07, 2007 2:41 pm

I know this sounds silly, but it's solved many issues before...

- Replace the cable,
- Replace the 3Com NIC...

--
C

thermant · Tue May 08, 2007 5:36 pm

Actually, it's not silly at all.

I've heard that 3Com boards are more picky about the quality of cable, connector, and so on. That's why I changed to the DLink, which is more, well, lenient on such items.

Like I said, the first few days are fine. But now it's back to the old trouble again... The only thing I haven't tried is replacing the cable... Will try that tomorrow. I'm out of connectors.

Thanks for the suggestion.

dvisbal · Tue May 08, 2007 11:59 pm

Thermant,

with your winbox, under the interface menu on each ethernet check their parameters " auto-negotiation, speed, 10/100 mbps " you need to hace a perfect syncronization between each equipment.

SO make sure each interface gets syncronized with the equipment they are connected to, and you should see a green light means that your link is ok and its running.

I know this is basic stuff, but it is very important to review this.

Regards,

Dan

planedriver · Wed May 09, 2007 1:22 pm

I will second what Dan said. I've seen lots of issues where ethernet NICs appear to "fail" and lock up. My routine now is to set everything to 100 full-duplex MANUALLY on all devices. I only use 3Com and Intel where possible, but have no control on the NIC hardware of other vendor's equipment.

Manual settings are much, much more reliable.

HTH

dvisbal · Wed May 09, 2007 4:31 pm

agree 100 %

Manually configuration is what i alway configure.

Really, really odd problem with RouterOS 2.9.40

Really, really odd problem with RouterOS 2.9.40

it's still there

Re: it's still there

board?

Did that

Who is online