Apalis T30 Ethernet Slow To Connect

Technical Support
, , , ,
1

Hi,

I’m finding that when I connect the Apalis T30/Ixora to an ethernet switch using the wired ethernet port, it may take in excess of 10 seconds for the link light to appear on the switch port and it to allow PuTTY connections via SSH.

Could there be any reason for this?

Kind regards,
Kevin

2

That’s definitely not what we observe. What cabling, switch or accompanying network infrastructure are you using? How did you configure the network interface on the Apalis T30? Could you please post output of the connman services command on your Ethernet interface as indicated here.

3

Hi Marcel,

We’re using a Netgear GS105 switch. The network interface is set up for a static IP address on our local network. I will post back the output of connman on Monday.

Kind regards,
Kevin

4

Hi Marcel,

This is the output of the connmanctl services command:

connmanctl> services ethernet_00142d29613c_cable
/net/connman/service/ethernet_00142d29613c_cable
  Type = ethernet
  Security = [  ]
  State = ready
  Favorite = True
  Immutable = True
  AutoConnect = True
  Name = Wired
  Ethernet = [ Method=auto, Interface=enp3s0, Address=00:14:2D:29:61:3C, MTU=1500 ]
  IPv4 = [ Method=fixed, Address=192.168.0.250, Netmask=255.255.255.0, Gateway=192.168.0.5 ]
  IPv4.Configuration = [ Method=fixed, Address=192.168.0.250, Netmask=255.255.255.0, Gateway=192.168.0.5 ]
  IPv6 = [  ]
  IPv6.Configuration = [ Method=off ]
  Nameservers = [  ]
  Nameservers.Configuration = [  ]
  Timeservers = [ 192.168.0.5 ]
  Timeservers.Configuration = [  ]
  Domains = [  ]
  Domains.Configuration = [  ]
  Proxy = [ Method=direct ]
  Proxy.Configuration = [  ]
  Provider = [  ]

Kind regards,
Kevin

5

OK, so you are configuring it for static IP and it is not DHCP or anything the like causing the delay.

Could it be some kind of duplex mismatch during link negotiation? I assume you are using proper CAT5 cabling? What does ethtool enp3s0 show?

Another useful resource of more information to figure out what exactly is going on may be the full journalctl -f output during the whole plugging-in event.