[PLUG] serial communication over ethernet (VY)

[VY]

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. <mconnors1 at 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 at lists.pdxlinux.org
> http://lists.pdxlinux.org/mailman/listinfo/plug
>