Atlantis Land A02-RA(Atmos)_ME01 manual Config.h Ethernetdevicename s//edd

Page 77

config.h ETHERNET_DEVICE_NAME “s//edd”

If a default file is not defined, the name ether is not supported. However, it is still possible to define devices of type ether with an explicit filename.

The class IP-over-ATMincludes both SVC-based and PVC-based IP-over-ATM; the decision whether to use SVCs or PVCs is made at initialization, by testing the interface colors of the file if it supports the Indigo interface, then SVCs are used, and otherwise PVCs.

•<file> specifies the file name that will be opened to access the underlying device. The device can be any of the following:

•Ethernet •IP-over-ATM •PTP

• Loopback

The device must provide the colored interface appropriate for that type of device. For a loopback interface, <file> is not used, and can just be specified as “-” or omitted altogether.

Note that several different values of <type> specify the same class of interface; they differ in that each implies a different default value for <file>. As a result, for the most common interface configurations, <file> can be omitted, and one need only specify the appropriate value of <type>.

•<mtu> specifies the MTU (maximum transmission unit); that is, the size of the largest datagram (excluding media-specific headers) that IP will attempt to send through the interface. The value specified will be ignored if it is larger than the maximum supported by the interface class, which is currently 1500, unless the IP-over-ATM MTU value has been changed in the TCP/IP build-time configuration system file. Normally, there is no point in setting the MTU less than this, so the <mtu> option is of little use.

•<IP address> is the IP address that this system uses on the interface; if it is not specified, the interface will be disabled until an IP address is supplied with the ip enable command.

For a loopback interface, the address should be set to 127.0.0.1. (All addresses of the form 127.*.*.* will then be recognized as loopback addresses, as is normal practice.)

For non-loopback interfaces, the subnet mask for the local network will be assumed to be ff:ff:ff:00 (eg. a class C network); if the correct subnet mask is other than this then it will need to be set with the subnet command (see subnet on page 211).

If there is a DHCP client in the system, the address can be set to DHCP. This

Page 76 Page 78
Image 77
Page 76 Page 78
Contents Console Commands Reference Contents DHCP-client Console commands NAT Console commands Pptp Console commands Page Tftp Console commands Scope IntroductionTypographical conventions Text conventionsEquipment, including safety information Event … General notesRestart UptimeVersion Process, process commandExample Mymachine isfs versionSyntax Description History mechanismSpecial-purpose commands @ commandsIp device Ip @consoleEcho … ListTell process … Mymachine echo hello worldDebug Exit, exitCrlf, nocrlf Mymachine tell hswctrl portinfo a1Bind process, unbind Commands for the chips process 18 cpuExit Ip @ unbindInfo Help23 mem 24 rb, rh, rw, wb, wh, wwTell StealConsole tell command Device Remarks Source Device addSee also Device deleteDevice list Option Permitted Ethertype values EthertypeFilter Flush FilteragePortfilter InterfaceStatus SpanningVersion Command arguments Compile Time ConfigurationScope Build InclusionPortname Examples BuildList config ConfigShow device List devicesList ports List classesShow class List channels Show portSet port Set channel List all open channelsShow channel Reset port Bd3000 dhcpclient help Bd3000 dhcpclient configBd3000 dhcpclient pool PoolIp device DHCP-related IP process commandsTrace Bd3000 ip device Bd3000 ip device add ethernet ether //edd dhcpDHCP-server Console commands Bd3000 dhcpserver config Bd3000 dhcpserver pool ResetBd3000 dhcpserver help Bd3000 dhcpserver status Dhcp Server Lease Status Bd3000 dhcpserver resetBd3000 dhcpserver version Bd3000 dhcpserver traceNAT Console commands Event Event level Output InterfacesBd3000 nat event Bd3000 nat interfacesInbound Bd3000 nat inbound delete ProtocolStats SessionsBd3000 nat protocols Bd3000 nat sessions pppFragments DumpBd3000 nat version Bd3000 nat dump onBd3000 nat hashtable ethernet HashtableBd3000 nat fragments ether Console examples Console object typesIP dial-out over PPP IP dial-in server setupChannel clear Channel disableChannel discard Remote BridgingChannel echo every Channel echoChannel event Channel enableChannel hdlc Level DescriptionChannel info Channel lcpmaxconfigureChannel interface Channel lcpmaxfailureChannel llc Channel lcpmaxterminateChannel pvc Channel svc Channel qosChannel remoteip Channel theylogin 24 bcp Channel weloginChannel tunnel n tunnel protocol dial direction Interface n stats Interface n localipUser Pptp Console commandsDial-Out Console examplesTunnel connect BindTunnel disconnect Tunnel createTunnel delete Tunnel info Tunnel eventSummary 10.TCP/IP Console commandsDevice Command Shown by Help Saved in configurationAbort Symbol Description YesCommand Description Mymachine ip arp add ether 192.168.50.1 8020199AD9 10.3 arpAutoloop ArproutingMymachine ip ping Ip pingDevice Mymachine ip config saveClass Type Default file Config.h Ethernetdevicename s//edd Mymachine ip disable flane DisableMymachine ip device add loop loop Mymachine ip device delete flaneEtherfiles EnableErrors 10.11.3Example Files10.12.1Syntax 10.12.2Description10.14 get Ipatm arpserver Ipatm abortIpatm arp Ipatm files Ipatm lifetime Ipatm help10.22.1Syntax Ipatm pvc10.22.2Description 10.22.3Example10.24 nat IphostnamePing NoerrorsNorelay 10.27.2Description Portname10.27.3Example 10.28.1Syntax10.28.3Example Protocols10.29.1Syntax 10.29.2Description10.30.1Syntax Relay10.30.2Description 10.30.3ExampleRip allowed Rip acceptRip help Rip bootRip poison Rip hostroutesRip killrelay Rip relays Rip relayRip rxstatus Rip sendRoute Rip trigger10.44.3Example Snmp RouteflushRoutes 10.47.2Description 10.47.1Syntax10.48.1Syntax 10.48.2Description10.49.1Syntax Subnet10.49.2Description 10.49.3Example10.50.1Syntax Untrace10.50.2Description 10.50.3Example10.54 ? 10.54.2Description 11.2 get Connect11.6 put InitPut localfile remotefile Index Page Page Page Page Page Wh 31 ww

A02-RA(Atmos)_ME01 specifications

Atlantis Land A02-RA(Atmos)_ME01 represents a remarkable breakthrough in sustainable living and eco-friendly technology. Situated in a progressive ecological zone, this innovative habitat is designed to harmonize with its natural surroundings while providing modern amenities for its inhabitants.

One of the standout features of Atlantis Land A02-RA(Atmos)_ME01 is its integration of renewable energy sources. The habitat utilizes solar panels that are seamlessly incorporated into its structure, harnessing sunlight to power essential systems. Additionally, small wind turbines are strategically placed to capture wind energy, making the habitat largely self-sufficient and reducing reliance on non-renewable energy sources.

Another significant characteristic of this habitat is its advanced water management system. The A02-RA(Atmos)_ME01 employs rainwater harvesting technology, collecting and purifying rainwater for domestic use. This system not only conserves water but also helps reduce the overall ecological footprint of the habitat. Furthermore, graywater recycling ensures that water from sinks and showers is treated and repurposed for irrigation and other non-potable uses.

The architecture of Atlantis Land A02-RA(Atmos)_ME01 reflects its commitment to sustainability. Built with eco-friendly materials, the structure features large windows to optimize natural light and promote passive solar heating. The design also incorporates green roofs, which provide insulation, reduce stormwater runoff, and support local biodiversity by creating habitats for wildlife and plants.

For the comfort and convenience of its residents, the habitat is equipped with smart home technology. This system allows occupants to control lighting, heating, and water usage through a central device or mobile application, promoting energy efficiency and enhancing daily living. Additionally, the interior spaces are designed with versatility in mind, allowing for easy reconfiguration to accommodate various lifestyles and needs.

Lastly, community engagement is a central theme in the A02-RA(Atmos)_ME01 design. Shared spaces, such as gardens and recreation areas, encourage social interaction and foster a sense of belonging among residents. The emphasis on community promotes collaboration in sustainability initiatives, empowering individuals to take an active role in preserving their environment.

In summary, Atlantis Land A02-RA(Atmos)_ME01 stands as a model for future living, showcasing how innovative technology and thoughtful design can create a sustainable, comfortable, and community-oriented habitat. Its commitment to harnessing renewable resources, efficient water management, and smart home integration makes it an exemplary blueprint for eco-friendly living.
Top Page Image Contents