dwilson805
Premium
join:2005-07-22
Hanceville, AL
 ·RoadRunner Cable
| reply to viperm
Re: mikrotik and Verizon FIOS
said by viperm  :If thats the case then just put a 10/100 meg switch in between the ONT and your mikrotik see what that does? then reconfiguring another MK but its your call  crap. why didn't I think of that??????!!! so simple, and obvious, and readily available. I am so dumb sometimes! |
|
viperm
Carpe Diem
Premium
join:2002-07-09
Winchester, CA | reply to dwilson805
hahahah that's why we are all here to share ideas and thoughts. |
|
gunther_01
Premium
join:2004-03-29
Saybrook, IL
| reply to dwilson805
said by dwilson805 :said by gunther_01 :Try a crossover cable? Or normal if already using one? EDIT: just for kicks, I've seen wierd things with that before We'll try that, but I'm starting to think that the ethernet hardware in the FIOS ONT has a problem talking with gigabit adapters. The two units that connect successfully (the FIOS router and the linksys) both have 10/100 ports, whereas the mikrotik and the laptop both have 10/100/1000 ports, and have problems. And locking the mikrotik ethernet port at 100mb/full duplex didn't help either. One of my mikrotik's is 10/100 only, and I'm hopeful that will prove or disprove this theory. Would bet. It almost has to be a link issue of some kind. |
|
viperm
Carpe Diem
Premium
join:2002-07-09
Winchester, CA
| reply to dwilson805
Well??? whats the verdict I am really curious now its either the link issue or they have an ARP table on the Verizon side that needs to be flushed once you install the Mikrotik.
Like stated before we had the same issue when swapping out generic routers at a customer location running on a COX connection.
--
ComTrain Certified Tower Climber. American Tower Certified approved contractor. Wireless consultants. |
|
nevtxjustin
join:2006-04-18
Dallas, TX
1 edit | reply to dwilson805
said by dwilson805 :crap. why didn't I think of that??????!!! so simple, and obvious, and readily available. I am so dumb sometimes! That's funny...I was about to suggest a simple solution like that, but I thought I'd better look back to see if you found a solution.
Edited to mention...
I have a Verizon FIOS ONT that didn't play well with a Cisco switch. Putting a DLink commercial hub between them fixed it. |
|
dwilson805
Premium
join:2005-07-22
Hanceville, AL
·RoadRunner Cable
| reply to viperm
said by viperm :Well??? whats the verdict I am really curious now its either the link issue or they have an ARP table on the Verizon side that needs to be flushed once you install the Mikrotik. Like stated before we had the same issue when swapping out generic routers at a customer location running on a COX connection. I had some health issues this week that kept me from working on it, and my buddy had five kids down with swine flu, so nothing happened this week. We're hoping to try to swap it back in early next week, and I'll certainly post here what we find out. |
|
TomS_
debugger it
Premium,MVM
join:2002-07-19
Australia
1 edit | reply to dwilson805
If 100/full is successfully being negotiated, disabling negotiation is likely to only cause issues.
Hard coding to 100/full on your side will result in the default behaviour at the other end when autonegotiation fails, which is to come up as 100/half. Put a bit of traffic on a link with one end at 100/full and the other at 100/half and you'll just get buck loads of collisions and low throughput.
If your interfaces are able to negotiate 100/full, whether or not one device supports gigabit aswell technically should not matter. If it does, then whatever hardware is being used in one of the devices has issues. The whole point of autonegotiation is for devices to advertise their capabilities to the opposing end, and then decide on the best settings. |
|
TomS_
debugger it
Premium,MVM
join:2002-07-19
Australia
| reply to dwilson805
said by dwilson805 :It isn't stupid at all. We did put in the default (0.0.0.0/0) route, and in fact we see the ARP requests going out that interface, which they wouldn't if we didn't have a default route, no? You should still be able to ping the Verizon FIOS gateway IP from your MT without having a default route. The fact you cant suggests something is going wrong.
The IP that you assign to your MT WAN then makes that entire subnet a connected subnet, and as such does not require a manually configured routing table entry of any sort to be able to send data to hosts within that subnet - the router already knows how to reach that subnet because it is connected to it.
A default route is your last resort route. When no other route exists that more explicitly determines where traffic to a certian IP or subnet should go, the router uses the default route to move it somewhere, hopefully closer to its destination. Otherwise it is dropped as the destination is unreachable. |
|
dwilson805
Premium
join:2005-07-22
Hanceville, AL
·RoadRunner Cable
| reply to dwilson805
We got it working!
The problem appears to be that the ethernet port in the ONT is unable to auto-negotiate with certain ethernet chips. When we forced the mikrotik's ethernet port to 10mb half duplex, we synced right up and started passing traffic. At any other setting, no sync.
We also tried the linksys router again and found that it is intermittent. When my friend tried that a couple of weeks ago, he was at least able to ping out and pass traffic, but yesterday we had problems with that.
The fun started when we called Verizon tech support to try to get them to force the ONT's ethernet port to 100mb/full (since we are paying for 50mb/20mb service from VZ, setting the ethernet to 10/half kind of defeats the purpose?).
The first tech we talked to insisted that if we had 50/20 service, the ethernet between the ONT and our router had to run at those speeds also, and that the problem was our router because the Westell VZ supplied was quite capable of doing that! He was quite indignant that we wanted to adjust the speed without ordering (and paying for) higher-speed service! He also insisted that by setting the ethernet port to half-duplex, we had changed our router from a router to a bridge. At that point, I suggested to my friend that we hang up and call back and hope we got a different tech.
The second tech wasn't much help either, but he did recognize that we ought to be able to set the ethernet to 100/full. He did, however, try to insist that we could make the router sync up with the ONT at 100/full if we increased the MTU size on the router, because that would cause the router's sync frequency to more closely match the ONT's. He suggested we could move MTU all the way up to 20000 and that should help.
I'm not kidding.
So we'll call VZ back this morning and try again to get the ONT forced to 100/full. We've had much better luck with VZ's day-time staff's knowledge.
I'll post here again when it's up at 100/full, just to close this out (and to share any more funnies that come out of VZ's techs' mouths...)
Thanks for all your help!
Dan. |
|
viperm
Carpe Diem
Premium
join:2002-07-09
Winchester, CA | reply to dwilson805
Geez what apain I tell you tech support sucks nowdays.
Good that you figured it out though.. |
|
dwilson805
Premium
join:2005-07-22
Hanceville, AL
·RoadRunner Cable
| reply to dwilson805
It took a while, but we finally got a VZ tech who was willing to listen to what we were trying to do, and he got a network tech who reprogrammed the ONT's ethernet port to 100/full. We changed the mikrotik to match, and we are up and running!
So the moral of the story is, watch out for Verizon ONTs, because some of them appear to have dodgy ethernet chips. I haven't seen any other equipment with which mikrotik can't successfully autonegotiate, so I'm unwilling to blame mikrotik. We also hooked up the ONT last night directly to a 10/100 switch, and it couldn't autonegotiate with that, either. To me it is crystal clear that it is an ONT problem.
Thanks again for all the help!
Dan. |
|
Unreasonable
join:2007-10-15
Portland, OR
 ·Integra Telecom
·Comcast
| I appreciate you taking the time to post your resolution, remain calm, and not devolve into a rant.
I'm just learning the MT's, and they have a somewhat user-hostile documentation set, and support forums to match.
FWIW - I had an RB45G that was also having nway issues, and ultimately had to be rma'd. (Replacement unit had no issues using the config file from the failed unit.)
I did get some throughput by manually setting various speed/duplex combos.
|
|
