I don't need any switching/bridging functionality from the RB750. I
removed all of the settings for that so I could in effect have my Wan
port (ether1) and 4 separate subnets (ether2, ether3, ether4, ether5).
In this scenario, the RB at the clients house is directly connected to
the nanostation on ether2 - that nanostation is supposed to provide
internet access from the cable modem and rb750 to a grain elevator a few
miles away. Ether 3 is a different subnet hooked up into the client's
cisco AP so that he has internet access in his house.
The issue here seems to be that the RB750 is acting as if the
nanostation (and subsequently the devices behind it) does not exist.
It's as if when I plug in the NS to ether2, it locks the port up or
something, however even if I put another switch in between ether2 and
the nanostation, I still cannot access the nanostation from the RB750
and the devices behind the nanostation cannot communicate with the RB750
and subsequently can't get out to the internet. I can plug my laptop
directly into ether2 and access the internet, so it's not the port
itself - there is something else REALLY strange going on and I can't
figure it out.
If I plug my laptop into the nanostation at the client's house - I can
communicate with it and everything behind it just fine. In fact, right
now in order to at least get their internet access back up, I
reinstalled their old watchguard unit which is set up the same way as
the RB750 - I am having no issues whatsoever with that configuration.
Both the client's home subnet and the client's elevator subnet can
access the internet with the watchguard. Take the watchguard out and put
the RB750 back in place and the elevator subnet stops working.
On 4/30/2010 3:10 PM, Cameron Crum wrote:
If the ports are not bridged or in the same switch, they will not talk
on the same subnet. I would put them all in the same "switch" and then
assign the xxx.xxx.xxx.1 address to the master port (most likely
ether2). Then try pinging again. If you have a public IP on the 750,
I'd be happy to look at it remotely if you want.
Cameron
On 4/30/2010 2:57 PM, Rory McCann wrote:
I am completely at a loss with this issue. I performed additional
troubleshooting steps as followed with the same result each time -
unable to communicate with the NS units or anything behind them.
1) Tried a simple crossover cable
2) Tried placing a dumb switch in between the NS and RB750
3) Tried changing IP addresses
4) Tried manually adding an arp entry for the NS units
The RB750 shows the ethernet as linked and okay - checked out at 10
and 100 half/full. I did notice that on all the interfaces, the MTU
is 1500 but the L2 MTU is 1524. I changed that to 1500 and it did
nothing for me. Is there something else I could possibly be doing wrong?
On 4/30/2010 1:39 PM, Josh Luthman wrote:
Good point. The default config has ether2-5 hardware switched...
Though I am under the impression the rb750 worked with the Proxim link.
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 Fri, Apr 30, 2010 at 2:31 PM, Cameron Crum<cc...@dot11net.com>
wrote:
Are the ethernet ports on the 750 bridged?
Cameron
On 4/30/2010 1:03 PM, Josh Luthman wrote:
If you're not getting ARP that's very weird. It is showing 100M
FDX on
ether2 right?
Try removing/adding the IP address. Be certain that you put
192.168.1.1/24
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 Fri, Apr 30, 2010 at 1:57 PM, Rory
McCann<rmm.li...@gmail.com> wrote:
The NS is directly connected to port 2 on the RB750. IP, Netmask,
Gateway,
DNS is all 100% correct on all of the units. I can ping the NS
when I
plug
it directly into my laptop. I can also access the device when I
remove
the
RB750 from the picture and put their old Watchguard unit back in
place.
This was working fine before with the Proxim units, but the RB
just does
not seem to like the NS.
On 4/30/2010 12:52 PM, Robert Andrews wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Are you getting link lights on both connections? Have you
plugged the
ns2 directly into the RB? Have you pinged the NS2 directly
from your
pc? Have you tried the NS2 on a different port? double checked
everything... netmasks? Common in setup on the RB is to
forget the
netmask in the address and so you get a /32...
Robert
On 04/30/2010 10:47 AM, Rory McCann wrote:
RB is 192.168.1.1, NS local is 192.168.1.50, NS far end is
192.168.1.60
No arp, nothing. I can't figure out why it won't communicate
over the
ethernet cable. It doesn't seem likely to be cabling because I
can hook
the device into their old Watchguard unit and it passes traffic
just
fine and I can hook it into my laptop directly and get to the
unit.
On 4/30/2010 12:40 PM, Josh Luthman wrote:
Well if the RB can't ping a NS plugged right into it there is an
obvious
problem. What IPs are the port and NS? Are they getting ARP?
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 Fri, Apr 30, 2010 at 1:36 PM, Rory McCann<rmm.li...@gmail.com>
wrote:
The RB can't ping the NS connected to it or anything beyond
that. It
is
like there is no traffic being passed over the ethernet cable
at all.
On the far end you can get as far as the NS on the client's
house,
but can
not ping the RB that is attached to it's ethernet port.
These units are not configured for WDS.
On 4/30/2010 12:33 PM, Josh Luthman wrote:
So the RB can ping the AP, but can it ping the far Nanostation?
Can the laptop ping the far nanostation when plugged in to it?
Did you confirm they are setup for bridge mode and WDS?
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 Fri, Apr 30, 2010 at 1:29 PM, Rory
McCann<rmm.li...@gmail.com>
wrote:
Nope, and if you log into Winbox you cannot even ping the NS
directly
connected to it.
On 4/30/2010 12:25 PM, Josh Luthman wrote:
So you have rb750's port 2 to an NS which links to another
NS.
The
laptop
at the far NS can not get to the rb750?
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 Fri, Apr 30, 2010 at 1:23 PM, Rory
McCann<rmm.li...@gmail.com>
wrote:
Network map probably isn't necessary. In simple terms,
the AP end
is
attached to a house. The RB750 is in the basement hooked
up to a
cable
modem, a local access point and the Nanostation. The far
end is
at the
top
of an elevator. The cable goes down to the bottom into a
switch
and
into
the
rest of the elevator's network.
Port 1 is the cable modem, Port 2 is the nanostation,
Port 3 is
the
client's home network - all separate subnets.
Nano is set up as AP/Station.
On 4/30/2010 12:11 PM, Josh Luthman wrote:
Network map would surely help.
Are the Nanostations using WDS like a bridge? I'm not
sure what
the
Proxim
MP11 does - a true bridge or not.
What are the Nanostation's addresses and what port are
they on
the
RB750?
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 Fri, Apr 30, 2010 at 1:04 PM, Rory McCann<
rmm.li...@gmail.com>
wrote:
Hey everyone,
Using an RB750 as a router / vpn device for one of my
clients.
Port 1
is
the DHCP internet feed. Port 2 is assigned 192.168.1.1
and is
directly
connected to a wireless link that feeds the client's
business.
Port 3
is
another network that is private for the client's home.
Traffic
is
filtered
between the networks so that they can't communicate. VPN
clients talk
to
the
192.168.1.x network.
Originally there was a proxim MP11 link in place - that
link
failed
and
we
replaced it with a Nanostation link. From the far end (the
non-RB
end)
I
am
able to ping as far as the AP on the client's house
where the
internet
is,
however on the close end, I am not able to even ping the
nanostation
directly connected to the RB port. I can connect the cable
directly
to
the
laptop and access the Ubnt unit, but for whatever
reason I can
not
get
to
the unit when it's connected to the RB and it will not
pass any
traffic
through the ethernet interface. Pings result in "timed
out" or
"destination
host unreachable". I had thought maybe it was an ARP
issue, but
both
a
soft
and hard reboot later and it doesn't seem to make a
difference.
Any ideas on why I can not get the RB750 and
Nanostation to
talk
through
the ethernet cable and pass traffic like expected?
Thanks in advance!
-------------- next part --------------
An HTML attachment was scrubbed...
URL:<
http://www.butchevans.com/pipermail/mikrotik/attachments/20100430/dc6d4819/attachment.html
_______________________________________________
Mikrotik mailing list
Mikrotik@mail.butchevans.com
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/20100430/2b3f01ac/attachment.html
_______________________________________________
Mikrotik mailing list
Mikrotik@mail.butchevans.com
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/20100430/053f2295/attachment.html
_______________________________________________
Mikrotik mailing list
Mikrotik@mail.butchevans.com
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/20100430/1ec69136/attachment.html
_______________________________________________
Mikrotik mailing list
Mikrotik@mail.butchevans.com
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/20100430/f2c50d2d/attachment.html
_______________________________________________
Mikrotik mailing list
Mikrotik@mail.butchevans.com
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/20100430/37eef12b/attachment.html
_______________________________________________
Mikrotik mailing list
Mikrotik@mail.butchevans.com
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/20100430/b3bdfc80/attachment.html
_______________________________________________
Mikrotik mailing list
Mikrotik@mail.butchevans.com
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/20100430/51521137/attachment.html
_______________________________________________
Mikrotik mailing list
Mikrotik@mail.butchevans.com
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/20100430/1c61d2f8/attachment.html
_______________________________________________
Mikrotik mailing list
Mikrotik@mail.butchevans.com
http://www.butchevans.com/mailman/listinfo/mikrotik
Visit http://blog.butchevans.com/ for tutorials related to
Mikrotik
RouterOS
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJL2xjkAAoJEC+8HUjSuDOsPhUH/0u0pqQ9zETaEbsDBaCcSMM0
8jymax91mNlsKAWwjFtvViredssq4/TCKEJ77CSGHxf9UZj52dc6hm21carz61NB
6ywtd28Wj6VVenSUv40QHmqauKlQX8M4D0mmJiLGy5o7qJ29x1hVaBJepo59sTMm
OOrVX2kQCRKumP2QVTWXMd6EtfR0yR/9AtB6odqJIjAs1tmEh7ThiXOGBMRG1CYT
5OdIpdVeodZLt3LtQWr4casukAG4CHlfqpLjBf6ITyhS6WiIBJuddaw7AJbnGD5g
lDvD+c7AmrcWC8sy42FL3gC+2oVPOrCrhzUVij5CcpYYnXJji/kOAaZfLwaZ2e8=
=SgSE
-----END PGP SIGNATURE-----
_______________________________________________
Mikrotik mailing list
Mikrotik@mail.butchevans.com
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/20100430/4156d49f/attachment.html
_______________________________________________
Mikrotik mailing list
Mikrotik@mail.butchevans.com
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/20100430/26b75e11/attachment.html
_______________________________________________
Mikrotik mailing list
Mikrotik@mail.butchevans.com
http://www.butchevans.com/mailman/listinfo/mikrotik
Visit http://blog.butchevans.com/ for tutorials related to Mikrotik
RouterOS
_______________________________________________
Mikrotik mailing list
Mikrotik@mail.butchevans.com
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/20100430/db3db770/attachment.html>
_______________________________________________
Mikrotik mailing list
Mikrotik@mail.butchevans.com
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/20100430/2d96745e/attachment.html>
_______________________________________________
Mikrotik mailing list
Mikrotik@mail.butchevans.com
http://www.butchevans.com/mailman/listinfo/mikrotik
Visit http://blog.butchevans.com/ for tutorials related to Mikrotik
RouterOS
_______________________________________________
Mikrotik mailing list
Mikrotik@mail.butchevans.com
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/20100430/14caca31/attachment.html>
_______________________________________________
Mikrotik mailing list
Mikrotik@mail.butchevans.com
http://www.butchevans.com/mailman/listinfo/mikrotik
Visit http://blog.butchevans.com/ for tutorials related to Mikrotik RouterOS