Community discussions

MikroTik App
 
craigmyster
newbie
Topic Author
Posts: 35
Joined: Thu Dec 15, 2005 2:26 pm

750GL Issue

Tue Sep 13, 2011 10:41 am

Hi;
I purchased 10 750GLs from the first batch and wondered if anybody else was having issues. I have the following even after updating to 5.6

1) remote SYSLOG does not work. I have a catch all !debug send to remote action. And the remote action is a standard syslog entry
2) ethernet link. I have a lot of issues with Autonegotiation with cards like RTL 8139 etc.....
3) Winbox reboot does not work all the time

I have contacted mt support but they do not seem to respond to my emails.

Thanks,
 
User avatar
normis
MikroTik Support
MikroTik Support
Posts: 26379
Joined: Fri May 28, 2004 11:04 am
Location: Riga, Latvia

Re: 750GL Issue

Tue Sep 13, 2011 10:52 am

they do not seem to respond to my emails
if you included supout.rif file and described the problem clearly, standard response time is up to 3 business days
 
fuzzbawl
just joined
Posts: 22
Joined: Tue Dec 21, 2010 8:41 pm

Re: 750GL Issue

Tue Sep 13, 2011 7:16 pm

I have found that upgrading the Routerboard firmware (The routerboot file) to 2.36 seems to fix this issue. I'm not sure if that is really the fix or not, but we haven't seen the Ethernet negotiation issues after upgrading. So far they seem fine.
 
craigmyster
newbie
Topic Author
Posts: 35
Joined: Thu Dec 15, 2005 2:26 pm

Re: 750GL Issue

Wed Sep 14, 2011 3:57 pm

thank you. I just upgraded the boot loader. I will observe for a few more days.
 
craigmyster
newbie
Topic Author
Posts: 35
Joined: Thu Dec 15, 2005 2:26 pm

Re: 750GL Issue [SYSLOG]

Tue Jan 17, 2012 3:46 pm

Still having absolute 0 luck on the remote syslog working on the 750GL devices. I installed 5.X x86 version on another machine bug cannot reproduce the issue. It happens on all of my 750GL's though. Anybody else have this issue?

PS auto neg is working good now
 
User avatar
janisk
MikroTik Support
MikroTik Support
Posts: 6263
Joined: Tue Feb 14, 2006 9:46 am
Location: Riga, Latvia

Re: 750GL Issue

Wed Jan 18, 2012 8:32 am

to test remote logging, you can add prefix and log those messages locally, and then when remote logging action is set up - change to that.

When changed to that, you can see with torch or packet sniffer that UDP packets are leaving the router. Remeber to receive the log packets you have to have remote server that will accept these UDP packets.
 
craigmyster
newbie
Topic Author
Posts: 35
Joined: Thu Dec 15, 2005 2:26 pm

Re: 750GL Issue

Sat Jan 21, 2012 6:04 am

to test remote logging, you can add prefix and log those messages locally, and then when remote logging action is set up - change to that.

When changed to that, you can see with torch or packet sniffer that UDP packets are leaving the router. Remeber to receive the log packets you have to have remote server that will accept these UDP packets.
I found the issue only happens when you leave out the src-address. I leave the default 192.168.88.1 address in all my routers. If I put anything (fake/real) into the src-address even just 1.1.1.1 or 123.123.123.123 the logging works but if I put 192.168.88.1 it does not work. This only happens on the GL's it looks like. But I am very happy to have a solution.

Also, I notice that the snmp info that appears to be more toward debut information is showing up as not debut

Jan 21 12:58:32 myiprev snmp rt-01: packet from: 123.123.123.123 version: 0
Jan 21 12:58:32 myiprev snmp rt-01: community: xxx

but I just ignored snmp for now that was an easy work around.

Who is online

Users browsing this forum: Extrems and 39 guests