If the device has the MAC addy printed on the outside somewhere you can
take the arp list Tomas told you about, look it up in the list and you will
see
what IP addy maps to the MAC addy.
Here is what to look for:
pc01 (192.168.1.214) at 00:60:2F:3C:14:A5 [ether] on eth0
( ----- IP --------) |---------- MAC------|
So if you can find the mac on the device you should be in luck. From there
it is just looking at the arp table as Tomas showed you and finding the MAC
addy in question see what IP is mapped to it and try and ping the bugger.
Tomas gave you the rest of it quite well.
I had to do exactly this last night, I was trying to find my WiFi
thermostat, it
for some reason was not publishing its device name (first entry above) so I
got the MAC off of it pulled the arp table off of my DNS box and there it
was.
Here is what I got:
? (192.168.7.83) at 00:d0:2d:26:f7:3c [ether] on eth0
Notice there is a question mark where the device name goes, but I had the
MAC address, so no big deal.
I reset the thermostat after getting the data and a few minutes later I did
a
arp:
gateway26f73c.wchast.loc (192.168.7.83) at 00:d0:2d:26:f7:3c [ether] on eth0
| Device Name+url ---------|( ------ IP -------) |--------MAC-------|
Now I have a proper name, IP and MAC.
With your device plugged into the network if it takes a DHCP assignment it
may
give out a device name, that would help too, but the MAC is the key.
On Mon, Mar 20, 2017 at 8:32 PM, Tom <tomas.kuchta.li...@gmail.com> wrote:
> While I do not have direct experience with the device, I see a few
> misconceptions in what you describe.
>
> 1. I assume that you want to configure, setup, control and use the
> Lantronix device from a Linux PC.
> 2. You need to have working network which you can use to communicated
> with the Lantronix device
> 3. The normal and easiest way is to connect both Linux PC and Lantronix
> device to working network with DHCP address assignment.
> 4. In order to communicate to the Lantronix device you need to know its
> IP address.
> You can find it the IP by executing this on your Linux PC: arp -a
> This will list all devices known to your PC. Here is example output
> from my PC formatted to columns for readability:
> > /sbin/arp -a | column -t
> pc01 (192.168.1.214) at 00:60:2F:3C:14:A5 [ether] on eth0
> ? (192.168.1.10) at 00:60:2F:9E:B7:B4 [ether] on eth0
> gateway (192.168.1.1) at 00:60:2F:95:56:F9 [ether] on eth0
> srvr01 (192.168.1.11) at 00:60:2F:B7:24:D5 [ether] on eth0
> >
> One of the IPs (2nd column) will be your Lantronix device.
> You can see which one it is either by its name or try to connect to
> the suspects by telnet
> 5. Connecting by telnet from your PC is described in the PDF document
> bellow:
> Example: telnet 192.168.1.10:9999
> Then pres Enter within 5 seconds to configure the serial port part
> of the Lantronix device
> Save and exit the configuration - it should remember the configured
> values
> If you do not want to use DHCP network the next time you use the
> device - configure it
> with static IP of your choice, but do not forget the static IP.
> 6. Connect something to the serial port of the Lantronix device and
> communicate
> with it using telnet connection
>
> If you do not have working network with DHCP address assignment
> available - step 3 above
> you will need to create it. This can be done by number of ways the
> easiest one would be
> to use home router/gateway with multiple ethernet ports (use the LAN
> ports) to connect
> the PC to Lantronix device. You should not need to connect the
> router/gateway to the Internet.
>
> Alternatively, you could use your PCs ethernet port and setup simple
> DHCP server
> on your PC to assign IP to the Lantronix device. Please note that if
> you do this,
> you will need to disable the DHCP server before connecting the PC to
> any other network,
> otherwise you would most likely cause serious trouble for the connected
> devices.
> Google for: How to setup DHCP server on ubuntu/centos/....
>
> I hope this helps, Tomas
>
> On Mon, 2017-03-20 at 15:46 -0700, VY wrote:
> > I just tried to configure this Lantronix device but my experience
> > seems a
> > bit different than yours.
> > I am connecting to the device via a normal ethernet cable.
> >
> > I connected it and has the following messages showing in
> > /var/log/messages
> > (include below)
> > I then tried using "nmtui" to set an IP on the NIC where the device
> > is
> > connected. I am able to do so, activated the NIC and able to
> > ping the IP. I don't see how I can configure things like baud rate.
> > And
> > I believe "nmtui" is only configuring the NIC and not actually
> > writing the
> > IP onto the
> > Lantronix unit.
> >
> > When running "arp -a", I also don't see this device (or the NIC to
> > which
> > this is connected to) showing up.
> > I have not connected to my LAN yet since I do not have a router.
> > Even if I
> > do, I would have to login to router configuration to see what is it
> > new IP.
> > I am hoping I can configure this unit from a Linux box and nothing
> > else.
> >
> > I think I am missing something.
> > How do I actually configure it from my Linux host?
> >
> > Any help much appreciated.
> >
> >
> >
> > ------ /var/log/messages ------
> >
> > Mar 20 15:39:36 en12-beekeeper kernel: igb 0000:03:00.0 enp3s0: igb:
> > enp3s0
> > NIC Link is Up 10 Mbps Half Duplex, Flow Control: None
> > Mar 20 15:39:36 en12-beekeeper NetworkManager[875]: <info>
> > [1490049576.4918] device (enp3s0): link connected
> > Mar 20 15:39:36 en12-beekeeper NetworkManager[875]: <info>
> > [1490049576.4931] device (enp3s0): state change: unavailable ->
> > disconnected (reason 'carrier-changed') [20 30 40]
> > Mar 20 15:39:36 en12-beekeeper NetworkManager[875]: <info>
> > [1490049576.4951] policy: auto-activating connection 'enp3s0'
> > Mar 20 15:39:36 en12-beekeeper NetworkManager[875]: <info>
> > [1490049576.5043] device (enp3s0): Activation: starting connection
> > 'enp3s0'
> > (4db2432d-0792-46b8-b045-682a2cdddf4f)
> > Mar 20 15:39:36 en12-beekeeper NetworkManager[875]: <info>
> > [1490049576.5051] device (enp3s0): state change: disconnected ->
> > prepare
> > (reason 'none') [30 40 0]
> > Mar 20 15:39:36 en12-beekeeper NetworkManager[875]: <info>
> > [1490049576.5118] device (enp3s0): state change: prepare -> config
> > (reason
> > 'none') [40 50 0]
> > Mar 20 15:39:36 en12-beekeeper NetworkManager[875]: <info>
> > [1490049576.5278] device (enp3s0): state change: config -> ip-config
> > (reason 'none') [50 70 0]
> > Mar 20 15:39:36 en12-beekeeper avahi-daemon[761]: Joining mDNS
> > multicast
> > group on interface enp3s0.IPv4 with address 169.254.4.1.
> > Mar 20 15:39:36 en12-beekeeper avahi-daemon[761]: New relevant
> > interface
> > enp3s0.IPv4 for mDNS.
> > Mar 20 15:39:36 en12-beekeeper avahi-daemon[761]: Registering new
> > address
> > record for 169.254.4.1 on enp3s0.IPv4.
> > Mar 20 15:39:36 en12-beekeeper NetworkManager[875]: <info>
> > [1490049576.5357] device (enp3s0): state change: ip-config -> ip
> > -check
> > (reason 'none') [70 80 0]
> > Mar 20 15:39:36 en12-beekeeper NetworkManager[875]: <info>
> > [1490049576.5407] device (enp3s0): state change: ip-check ->
> > secondaries
> > (reason 'none') [80 90 0]
> > Mar 20 15:39:36 en12-beekeeper NetworkManager[875]: <info>
> > [1490049576.5409] device (enp3s0): state change: secondaries ->
> > activated
> > (reason 'none') [90 100 0]
> > Mar 20 15:39:36 en12-beekeeper NetworkManager[875]: <info>
> > [1490049576.5448] device (enp3s0): Activation: successful, device
> > activated.
> > Mar 20 15:39:36 en12-beekeeper dbus-daemon: dbus[764]: [system]
> > Activating
> > via systemd: service name='org.freedesktop.nm_dispatcher'
> > unit='dbus-org.freedesktop.nm-dispatcher.service'
> > Mar 20 15:39:36 en12-beekeeper dbus[764]: [system] Activating via
> > systemd:
> > service name='org.freedesktop.nm_dispatcher'
> > unit='dbus-org.freedesktop.nm-dispatcher.service'
> > Mar 20 15:39:36 en12-beekeeper systemd: Cannot add dependency job for
> > unit
> > microcode.service, ignoring: Unit is not loaded properly: Invalid
> > argument.
> > Mar 20 15:39:36 en12-beekeeper systemd: Starting Network Manager
> > Script
> > Dispatcher Service...
> > Mar 20 15:39:36 en12-beekeeper dbus-daemon: dbus[764]: [system]
> > Successfully activated service 'org.freedesktop.nm_dispatcher'
> > Mar 20 15:39:36 en12-beekeeper dbus[764]: [system] Successfully
> > activated
> > service 'org.freedesktop.nm_dispatcher'
> > Mar 20 15:39:36 en12-beekeeper systemd: Started Network Manager
> > Script
> > Dispatcher Service.
> > Mar 20 15:39:36 en12-beekeeper nm-dispatcher: req:1 'up' [enp3s0]:
> > new
> > request (5 scripts)
> > Mar 20 15:39:36 en12-beekeeper nm-dispatcher: req:1 'up' [enp3s0]:
> > start
> > running ordered scripts...
> > Mar 20 15:39:36 en12-beekeeper systemd: Unit iscsi.service cannot be
> > reloaded because it is inactive.
> > Mar 20 15:39:37 en12-beekeeper avahi-daemon[761]: Registering new
> > address
> > record for fe80::3190:e312:6a33:901e on enp3s0.*.
> > Mar 20 15:39:45 en12-beekeeper kernel: igb 0000:03:00.0 enp3s0: igb:
> > enp3s0
> > NIC Link is Down
> > Mar 20 15:39:46 en12-beekeeper kernel: igb 0000:03:00.0 enp3s0: igb:
> > enp3s0
> > NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX
> > Mar 20 15:39:46 en12-beekeeper NetworkManager[875]: <info>
> > [1490049586.9023] device (enp3s0): link connected
> >
> >
> > On Sat, Mar 18, 2017 at 9:50 PM, Mike C. <mconno...@gmail.com> wrote:
> >
> > > >
> > > > Hello All:
> > > >
> > > > I am looking for a mechanism from Linux to configure a device
> > > > that's a
> > > > small ethernet server:
> > > >
> > > >
> > > > https://www.lantronix.com/wp-content/uploads/pdf/XPort-AR_CR.pdf
> > > >
> > > > The initial steps involve configuring its BAUD rate, IP address
> > > > etc..
> > > > On Windows, per their instructions, folks are asked to use things
> > > > like
> > > > telnet and hyperterminal,
> > > > or other serial communication tools.
> > > >
> > > > On Linux, I have configured serial ports before, using things
> > > > like
> > > > minicom. But those devices would show up as /dev/TTY***. In
> > > > this
> > > > device, it is showing up in an ethernet port.
> > > >
> > > > what tools can I use to configure this device in such scenario
> > > > under
> > > Linux?
> > > > I know exactly which ethernet port it is connected to (e.g.
> > > > eth1)
> > > >
> > > > thanks in advanced for any tip.
> > > >
> > > >
> > > Are you connecting to the device via a serial port?
> > >
> > > Standard configuration for serial port communication is: 9600, 8,
> > > N, 1
> > >
> > > i.e.
> > > Bits per second (Baud Rate): 9600
> > > Data Bits: 8
> > > Parity: None
> > > Stop Bits: 1
> > > Flow Control: None
> > >
> > > This getting started document explains how to connect via the
> > > serial port.
> > > https://www.lantronix.com/wp-content/uploads/pdf/XPort-AR_QS.pdf
> > >
> > > The device also has DHCP enabled, so you could just plug into your
> > > LAN. You
> > > can run the command arp -a before plugging in it and then after.
> > > You should
> > > see the new mac & ip addr entry in your computer's arp table.
> > >
> > > Here's an example of an arp table entry on my computer:
> > >
> > > gateway (10.0.0.1) at 00:00:ca:11:22:33 [ether] on enp2s0
> > >
> > > The first 6 characters of any mac addr are reserved for the OUI,
> > > Organizationally Unique Identifier. In my example arp table entry,
> > > 00:00:ca
> > > is for Arris.
> > >
> > > Lantronix's OUI is: 00:80:A3
> > >
> > > HTH,
> > >
> > > Mike
> > > _______________________________________________
> > > PLUG mailing list
> > > PLUG@lists.pdxlinux.org
> > > http://lists.pdxlinux.org/mailman/listinfo/plug
> > >
> > _______________________________________________
> > PLUG mailing list
> > PLUG@lists.pdxlinux.org
> > http://lists.pdxlinux.org/mailman/listinfo/plug
> _______________________________________________
> PLUG mailing list
> PLUG@lists.pdxlinux.org
> http://lists.pdxlinux.org/mailman/listinfo/plug
>
--
Chuck Hast -- KP4DJT --
Glass, five thousand years of history and getting better.
The only container material that the USDA gives blanket approval on.
_______________________________________________
PLUG mailing list
PLUG@lists.pdxlinux.org
http://lists.pdxlinux.org/mailman/listinfo/plug
