Customizing the Gateway

Article
06/30/2006

After you create the platform, you can customize it. When you are finished customizing, you must configure the registry.

Adding Environment Variables

Depending on your hardware, you may need to set some environment variables to enable support for your device. To create a gateway, set the following environment variables to match the hardware and features that your device supports.

Setting type	Environment variable
Required settings	BSP_ENABLE_FSREGHIVE=1 BSP_ICS=1 BSP_NOSHAREETH=1
Hardware specific examples	BSP_DISPLAY_MEDIAGX=1 BSP_NIC_RTL8139=1 BSP_NIC_RTL81392=1 BSP_PCMCIA_I82365=1
Optional settings examples	BSP_NOAUDIO=1 BSP_NOUSBSER=1 BSP_USB_OHCI=1 BSP_USB_UHCI=1

Required settings

BSP_ENABLE_FSREGHIVE=1

BSP_ICS=1

BSP_NOSHAREETH=1

Hardware specific examples

BSP_DISPLAY_MEDIAGX=1

BSP_NIC_RTL8139=1

BSP_NIC_RTL81392=1

BSP_PCMCIA_I82365=1

Optional settings examples

BSP_NOAUDIO=1

BSP_NOUSBSER=1

BSP_USB_OHCI=1

BSP_USB_UHCI=1

Changing IP Firewall Rules

The IP Firewall is enabled by default when you create a Gateway by using the New Platform Wizard. This firewall uses rules to determine whether to block, allow, or log inbound or outbound traffic. For information about the default rules, see Default IP Firewall Rules. You can change these default settings through the registry. For more information, see IP Firewall Registry Settings.

Adding IPv6 Support

For security reasons, IPv6 is not enabled by default when it is added to the image. You can enable IPv6 with the sample network admin ISAPI only if the device supports a persistent registry. Most sample CEPC images, for example, do not support a persistent registry.

Note Unlike IPv4, IPv6 does not use the network address translation (NAT) functionality to connect to the external network. To avoid exposing internal devices directly on the external public network, you must configure the IP firewall on the gateway. For information about configuring the IP firewall to properly manage traffic destined for the internal network, see IP Firewall Reference.

Make sure that you understand the security consequences of enabling IPv6 routing on the device by reviewing the IPv6 documentation. For information about changing the default behavior so that IPv6 is enabled by default during the build, see TCP/IP Security.

Using the Template Gateway User Interface

You can configure the Web Server to make the template gateway user interface, Admin2.dll, the default page for the Gateway. For more information, see Setting the Default Page and Using the Template Gateway User Interface.

Using the ICS Web-Based Configuration Utility

In addition to the template gateway user interface, you can also use a more comprehensive sample network configuration utility, Natadmin.dll. This sample allows you to verify and configure your network environment during the development of the Gateway platform. You can also modify the sample to suit your needs.

To add Natadmin to your platform, set the SYSGEN_REMOTEADMIN variable.

For more information, see Using the Network Administration Utility.

Implementing the Internet Gateway Device Schema

You can include a sample implementation of Internet Gateway Device (IGD) schema. However, the sample may require further customization to expose the full capability of your device. For more information see Implementing the Internet Gateway Device Schema and NAT Traversal in Internet Gateways.

Adding Support for Wireless Access Point

You can customize your gateway to function as a wireless access point by adding the Wireless Access Point (802.11) Support feature from the catalog. You can also add the feature by setting the SYSGEN_WIFI_APP variable.

Share via