Difference between revisions of "Network Connections"
Kyoungmeyer (talk | contribs) (Page created) |
|||
| (7 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
| − | {{todo| | + | {{todo|SEOKWREV (11.26.13-10:49->KY+);(11.26.13-21:50->MD+);(12.20.13-11:09->MW+);(03.04.14-15:25->BS-);(03.14.14-16:10->BS+)|Klint Youngmeyer|project=oe 4,oe 5,ky,SEOKWREV,md,mw,bs}} |
| + | {{#seo: | ||
| + | |title=Network Connections | ||
| + | |titlemode=append | ||
| + | |keywords=Network Connections,Local Area Network,Direct connection | ||
| + | |description=Process of establishing a basic network connection with EMAC boards. | ||
| + | }} | ||
== Network Connections == | == Network Connections == | ||
This section describes the process of establishing a basic network connection with the board. Once a network connection is established, the system may be accessed through the servers on the board, including SSH, HTTP, FTP, and Telnet. | This section describes the process of establishing a basic network connection with the board. Once a network connection is established, the system may be accessed through the servers on the board, including SSH, HTTP, FTP, and Telnet. | ||
| Line 52: | Line 58: | ||
| − | {{mbox | type = notice | text = Note that most newer networking devices include support for Auto | + | {{mbox | type = notice | text = Note that most newer networking devices include support for Auto MDI/MDIX, which allows them to detect if the network cable requires a crossover and automatically matches the correct configuration. Auto MDI/MDIX only needs to be supported on one end of the link for this to work. If you are certain that your workstation or target board supports Auto MDI/MDIX, a standard Ethernet patch cable may be used for a direct connection rather than a crossover cable.}} |
| Line 91: | Line 97: | ||
After you have established a connection with your device running EMAC OE Linux, you will need to [[System_Log_In | log into the system.]] | After you have established a connection with your device running EMAC OE Linux, you will need to [[System_Log_In | log into the system.]] | ||
| + | <!-- | ||
[[Category:Linux]] | [[Category:Linux]] | ||
[[Category:OpenEmbedded]] | [[Category:OpenEmbedded]] | ||
| + | --> | ||
Latest revision as of 14:12, 17 March 2014
Network Connections
This section describes the process of establishing a basic network connection with the board. Once a network connection is established, the system may be accessed through the servers on the board, including SSH, HTTP, FTP, and Telnet.
Local Area Network
To make a connection to a local area network (LAN), simply connect a standard Ethernet patch cable to the primary Ethernet port on the board. This may be done before or after power has been applied, as the system is set up to allow hot-plugging of the network interface and should automatically re-configure the network settings when a link is detected.
EMAC OE Linux devices are set to attempt a DHCP network configuration by default. If a DHCP server is available on the network that the system is connected to, it will contact the server to secure an IP address lease. If an address has been obtained by DHCP, there are several ways of determining what address has been leased. The easiest way to access this information is to connect to the board through another method (i.e. serial terminal or graphical interface) and run the ifconfig command to determine the address that has been obtained on the eth0 interface. Alternatively, network tools such as packet sniffers can be used to determine what IP address has been leased. The local network administration can determine and provide this information as well by querying the DHCP server tables. The listing below illustrates usage of the ifconfig command to determine the IP address.
root@emac-oe:~# ifconfig
eth0 Link encap:Ethernet HWaddr 00:50:C2:E6:60:F4
inet addr:10.0.2.100 Bcast:10.0.255.255 Mask:255.255.0.0
inet6 addr: fe80::5054:ff:feb1:f83e/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1825 errors:0 dropped:0 overruns:0 frame:0
TX packets:553 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:139124 (135.8 KiB) TX bytes:50603 (49.4 KiB)
Interrupt:25 Base address:0xc000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
If the board fails to obtain a lease from a DHCP server, it will fall back to a static networking configuration. The default settings are detailed in Table 2 below.
| Table 2: Default Static IP Settings | |
|---|---|
| IP Address | 10.0.2.41 |
| Subnetwork Mask | 255.255.255.0 |
| Default Gateway | 10.0.2.1 |
| Broadcast Address | 10.0.2.255 |
Direct Connection
If a LAN connection is not available or desirable, you may make a direct connection to the board. Use an Ethernet crossover cable to connect directly between the workstation and the target board. Apply power to the board once the physical connections have been made.
 | Note that most newer networking devices include support for Auto MDI/MDIX, which allows them to detect if the network cable requires a crossover and automatically matches the correct configuration. Auto MDI/MDIX only needs to be supported on one end of the link for this to work. If you are certain that your workstation or target board supports Auto MDI/MDIX, a standard Ethernet patch cable may be used for a direct connection rather than a crossover cable. |
If a direct connection has been made to the board and a DHCP server is not running on the workstation, DHCP will fail and the system will fall back to the default IP settings in Table 2 above. The network interface on the workstation will then need to be configured to use the same subnetwork mask and broadcast address as the target board with a different IP address that falls in the same subnetwork. See Table 3 below for suggested static network settings if the board is still configured with the default static fall back settings. If the configuration has been changed, adjust these values to match the new settings.
| Table 3: Static Network Settings for Direct Connection | |
|---|---|
| IP Address | 10.0.2.1 |
| Subnetwork Mask | 255.255.255.0 |
| Default Gateway | Blank or 10.0.2.41 |
| Broadcast Address | 10.0.2.255 |
To verify that the connection is working properly, use the ping utility to test that the board responds at the address 10.0.2.41 (assuming default network configuration). The listing below shows an example of a successful ping (Ctrl-c was pressed after five packets).
developer@ldc:~$ ping 10.0.2.41
PING 10.0.2.41 (10.0.2.41) 56(84) bytes of data.
64 bytes from 10.0.2.41: icmp_req=1 ttl=64 time=0.447 ms
64 bytes from 10.0.2.41: icmp_req=2 ttl=64 time=0.213 ms
64 bytes from 10.0.2.41: icmp_req=3 ttl=64 time=0.308 ms
64 bytes from 10.0.2.41: icmp_req=4 ttl=64 time=0.318 ms
64 bytes from 10.0.2.41: icmp_req=5 ttl=64 time=0.251 ms
^C
--- 10.0.2.41 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 3996ms
rtt min/avg/max/mdev = 0.213/0.307/0.447/0.081 ms
Next Steps
After you have established a connection with your device running EMAC OE Linux, you will need to log into the system.
