Yes.  The traffic is definitely 2-way right up to the key exchange.

bp


On 6/23/2010 5:11 PM, Terri Kelley wrote:
Sounds like that pretty much. Can see traffic coming back from their server 
though.

Terri Kelley
Network Engineer
254-697-6710
Farm to Market Broadband
www.farm-market.net



On Jun 23, 2010, at 7:01 PM, Bill Prince wrote:

We ran traces on it, and it stopped before that in our observation.

When the femtocell first starts up it does a few dozen NTP calls to at least 4 
different NTP servers, then starts handshaking with the server via SSL.  
Finally, when it gets around to key exchange, the femtocell sends a couple of 
fragmented packets, and the server does not respond.

We ran at least 4 or 5 different traces, and that was pretty much the sequence 
each time.


bp


On 6/23/2010 4:52 PM, Terri Kelley wrote:
In ours, AP is bridged and the cpe is routed with NAT. Seems it stops at the 
CPE on the way back to the customers microcell.

Terri Kelley
Network Engineer
254-697-6710
Farm to Market Broadband
www.farm-market.net



On Jun 23, 2010, at 6:38 PM, Chuck Hogg wrote:


It's working on our network without any special config.  We're
completely routed.

Regards,
Chuck Hogg
Shelby Broadband
502-722-9292
[email protected]
http://www.shelbybb.com


-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Terri Kelley
Sent: Wednesday, June 23, 2010 5:54 PM
To: Mikrotik discussions
Subject: [Mikrotik] 4500 traffic

I have a customer wanting to use an AT&T microcell on his connection but
can't seem to get it to work.
His CPE is a 411AH on 2.4, only firewall are input rules on the 411 and
there is NAT.
Ethernet side of the 411 is connected directly to the microcell unit.
I see it in the arp table and can watch via torch, traffic going out. It
is using UDP 4500 trying to build the tunnel.
I can watch on the tower and see the response on 4500 coming back.
I see the traffic reach the wan interface of the cpe, port 4500.
But it looks like it is failing to pass through that cpe.

Any ideas why this is the case?
I would like to try to solve the mystery rather than just bridge the
unit.

Thanks,

Terri Kelley
Network Engineer
254-697-6710
Farm to Market Broadband
www.farm-market.net



-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://www.butchevans.com/pipermail/mikrotik/attachments/20100623/2e3ef
5d0/attachment.html>
_______________________________________________
Mikrotik mailing list
[email protected]
http://www.butchevans.com/mailman/listinfo/mikrotik

Visit http://blog.butchevans.com/ for tutorials related to Mikrotik
RouterOS
_______________________________________________
Mikrotik mailing list
[email protected]
http://www.butchevans.com/mailman/listinfo/mikrotik

Visit http://blog.butchevans.com/ for tutorials related to Mikrotik RouterOS

-------------- next part --------------
An HTML attachment was scrubbed...
URL:<http://www.butchevans.com/pipermail/mikrotik/attachments/20100623/aa5ceb7d/attachment.html>
_______________________________________________
Mikrotik mailing list
[email protected]
http://www.butchevans.com/mailman/listinfo/mikrotik

Visit http://blog.butchevans.com/ for tutorials related to Mikrotik RouterOS


_______________________________________________
Mikrotik mailing list
[email protected]
http://www.butchevans.com/mailman/listinfo/mikrotik

Visit http://blog.butchevans.com/ for tutorials related to Mikrotik RouterOS
-------------- next part --------------
An HTML attachment was scrubbed...
URL:<http://www.butchevans.com/pipermail/mikrotik/attachments/20100623/17402829/attachment.html>
_______________________________________________
Mikrotik mailing list
[email protected]
http://www.butchevans.com/mailman/listinfo/mikrotik

Visit http://blog.butchevans.com/ for tutorials related to Mikrotik RouterOS

_______________________________________________
Mikrotik mailing list
[email protected]
http://www.butchevans.com/mailman/listinfo/mikrotik

Visit http://blog.butchevans.com/ for tutorials related to Mikrotik RouterOS

Reply via email to