BAY Ntwks (under House) Message Board

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Technology Stocks : BAY Ntwks (under House)

Public Reply Prvt Reply Mark as Last Read File

Previous 10 Next 10 Previous Next

To: rupert1 who wrote (4200)	2/12/1998 11:44:00 AM
From: Robert Sigle	Read Replies (2) of 6980

Let me try to clear this up. An Accelar running verion 1.1 of the agent will forward DHCP requests when the port is associated with IP (IP policy-based VLAN or IP router port). Explanation: A layer 2-only device (28200, 58000 BayStack350, Centillion) "bridges" all packets based on MAC addresses. A DHCP packet, like all other packets on a LAN, has a Destination and Source MAC address. Therefore a layer two device will forward a DHCP packet. An Accelar out of the box puts all ports in a default VLAN and acts as a layer-2 switch. Therefore DHCP will be forwarded with NO problem at layer 2 through an Accelar. However, if you put the port that the DHCP request enters the Accelar in an IP policy-based VLAN OR if you configure the port as a router port then the initial request will be dropped by the Accelar with version 1.0 of the agent. Version 1.1 of the agent supports a piece of code called a "relay agent" for DHCP/BootP. This "relay-agent" or some piece of software like it (i.e. Cisco's IP Helper) is necessary to forward DHCP/BootP requests whenever IP is configured on a port of a layer 3 device.

Report TOU Violation

Share This Post

Public Reply Prvt Reply Mark as Last Read File

Previous 10 Next 10 Previous Next