From owner-freebsd-net@FreeBSD.ORG Tue Aug 19 07:02:13 2014 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 74BD2325 for ; Tue, 19 Aug 2014 07:02:13 +0000 (UTC) Received: from mx0.pp.com.pl (sol.pp.com.pl [195.20.3.30]) by mx1.freebsd.org (Postfix) with ESMTP id E595837EA for ; Tue, 19 Aug 2014 07:02:12 +0000 (UTC) Received: from [192.168.3.17] (lan.pp.com.pl [195.20.3.242]) by mx0.pp.com.pl (Postfix) with ESMTPSA id 539C564003F for ; Tue, 19 Aug 2014 09:09:13 +0200 (CEST) Message-ID: <53F2F669.1030101@pp.com.pl> Date: Tue, 19 Aug 2014 09:02:01 +0200 From: Piotr Kubaj User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Icedove/24.6.0 MIME-Version: 1.0 To: freebsd-net@freebsd.org Subject: Re: Sending data via MAC address References: <53F26851.2020309@pp.com.pl> In-Reply-To: <53F26851.2020309@pp.com.pl> X-Forwarded-Message-Id: <53F26851.2020309@pp.com.pl> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Aug 2014 07:02:13 -0000 On 08/18/2014 22:39, Nikolay Denev wrote: > On Mon, Aug 18, 2014 at 8:05 PM, Ryan Stone wrote: >> On Mon, Aug 18, 2014 at 8:58 AM, Piotr Kubaj wrote: >>> Hi. Please see >>> http://forums.freebsd.org/viewtopic.php?f=15&t=45303#p264204 and >>> http://forums.freebsd.org/viewtopic.php?f=15&t=45303#p264249 . >>> I know I can use web interface or ssh but WinBox is required. In short, >>> using Linux and Wine, I can connect to my routers via MAC, provided they >>> are in the same network. With FreeBSD it's not possible (I've checked >>> various Wine versions, so it's not its fault). Right now I have Debian >>> running on my PC and have tested FreeBSD in VM with bridged NIC. When I >>> run Winbox in Linux, I can connect to RB, with FreeBSD in VM it works >>> only with IP (provided both PC and the router are in the same network). >>> Is it possible in any way to connect using only MAC addresses or when PC >>> and the router are in different networks (no network aliases, as there >>> are times when it's not known what network the router is in). Thanks for >>> answers. >>> _______________________________________________ >>> freebsd-net@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-net >>> To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" >> So the problem, if I'm understanding you correctly, is that you have a >> router with an unknown IP address (but a known MAC address). You're >> unable to set the IP on the router and you want to use it to forward >> your traffic? >> >> You could do something like this (assuming your NIC is on the >> 192.168.1.0/24 subnet: >> >> route add default 192.168.1.1 >> >> The IP address that you use here is arbitrary. Pick an unused address >> on your subnet. If you only want to route certain subnets through >> this router, replace "default" with the subnet that you want to route. >> >> arp -s 192.168.1.1 xx:xx:xx:xx:xx:xx pub >> >> This will create a static arp entry for 192.168.1.1. Now when you try >> to route traffic to 192.168.1.1 it will use the static MAC and things >> should just work. >> >> Note that you probably won't be able to do this to access the router >> at all (e.g. ping 192.168.1.1). The router's IP stack won't respond >> to packets that aren't addressed to the router's IP address. >> _______________________________________________ >> freebsd-net@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-net >> To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > I think the OP is talking about MikroTik RouterOS based devices that > are usually configured > via WinBox (a proprietary windows based GUI tool) that can > auto-discover and setup such devices either based on IP, > or via some proprietary protocol using on L2 if they are on the same > ethernet segment, even if they don't have IP configured. > > For what is worth I was able to run WinBox in Wine under OS X and > configure such devices, so > I'm not sure what could be the problem on FreeBSD preventing that communication. > I think some packet traces might show what's going on. > > --Nikolay Yes, I may have worded it poorly, but that's what I meant. I'll try Ryan's solution tomorrow, but it seems that FreeBSD is missing something and that's why some extra-configuration is needed. WinBox on Linux works OOTB just like in OSX, but it's not like that on FreeBSD. I'll also try to get packet traces.