Hello

This is a field implementation and attempting to ping machines. First, I have read the manual. I think I may need a real Gateway, difficult in this application.

Here is the simple scenario.....

I have RB112 with RouterOS 2.9.51.

One Ethernet Interface, One WLan Interface.
I am making a vehicle-to-vehicle network to connect two computers.
Computer A (10.52.1.101/24) connects by ether1 (10.52.1.200/24)
Computer B (10.52.1.102/24) connects by wlan1 (10.52.1.220/24)
A bridge1 is used (10.52.1.240)
A DHCP Server setup on bridge1. This works.
IP Route is default setup.

I can ping ether1, wlan1, bridge1 from either computer.
I can not ping Computer A <---> Computer B.

I did set the Gateway to 10.52.1.1 . However there is NO gateway server in the system. There is no DNS server. This is not a traditional network - it is just connecting two machines together through the router. I am using Mikrotik because it has NStreme, dynamic Ack timing, and facility to host Ubiquiti mini-PCI cards for a long distance application.

What am I doing wrong? Must I have a Gateway? Would Hotspot Gateway cover this and can I effectively do it without auhentication (walled garden)?

The question supercedes my previous questions as I explore why I cannot ping. The manual is good, but always gives examples where a gateway device is present. No fair.

Hi,


no gateway needed.

You have to put IP in ether1 and put ether1 and wlan in a bridge. Then you can ping the other side. You can use APbridge in one side and station in other side, or you can use WDS. See the wiki.

No IP needed in wlan or bridge.



Martín.

If I am understanding correctly (and partly based on an forum thread I found this morning...)

I set the 'gateway' IP to the ethernet port.
I really dont even care about giving wlan and/or bridge their own ip addresses.

Is that a correct reading?

Thank-you for your response.

gateway isn't necessary if you only need to ping machines.. if only have ips and a bridge you can ping each other.

Martín

One Ethernet Interface, One WLan Interface.
I am making a vehicle-to-vehicle network to connect two computers.
Computer A (10.52.1.101/24) connects by ether1 (10.52.1.200/24)
Computer B (10.52.1.102/24) connects by wlan1 (10.52.1.220/24)
A bridge1 is used (10.52.1.240)
A DHCP Server setup on bridge1. This works.
IP Route is default setup.

I can ping ether1, wlan1, bridge1 from either computer.
I can not ping Computer A <---> Computer B.

Hi ;
i have some comments to you i hope they will help you .
first : you are connecting two pc's to a RB one by wlan and the second by the ether port .
you do not need to assign ip to NIC , you just need to make a bridge and add the wlan and ether1 to the bridge after that assign ip to the bridge like 10.52.1.1/24 " i thing it will be enough for you to use subnetmask /29 " , and in this way you will be sure that the two pc's will be connected together .
second : if you need to give ip automaticaly to the two pc's you could configure the DHCP server with the the interface bridge1 .
third : here is the important one to you , you have to disable the firewall in both pc's so you could ping each other .
if the firewall is enabled in one of them you will not be able to ping it .
with best regards to you .

Thank-you..

heh,, when you mention it, the firewall issue may be the culprit..
Was not thinking of that; one of those simple things.

I'll see how the more direct setup works out.

Thanks.

Some followup... Firewall was the issue... yeah, something that stupid. We are likely static routing in the end. Thanks for all the help!

Some followup... Firewall was the issue... yeah, something that stupid. We are likely static routing in the end. Thanks for all the help!

Hi again ;
did you disable the firewall in the pc and you start ping other side as i told you ?
what do you mean by " we are likely static routing in the end "
with best regards .

What I meant was, yes I disabled the firewall. I'll want to be careful with that during testing since it opens my laptops up. Might be able to configure some allowed routes.

On Static - I mean I will specifically mark the paths I want the network to take.