This is supposedly fixed in PR/523902 which is resolved in 10.2R2 10.3R1
10.1R3 10.0R4 10.4R1. It includes two hidden commands which should allow the
forwarding of DHCP traffic on interfaces that are not configured for DHCP
(when using dhcp-relay or dhcp-local-server). I haven't had the time
On Thu, Aug 12, 2010 at 02:17:14AM -0700, Kaj Niemi wrote:
On 12/8/2010 12:01, sth...@nethelp.no sth...@nethelp.no wrote:
We have tested these two commands, both in daily build versions of
JunOS and in 10.0S7.1 where it is implemented. These commands seem to
do the job, even if they don't
On 12/8/2010 15:33, Chuck Anderson c...@wpi.edu wrote:
1. MX shouldn't require Option 82 (relay-agent-option) in order to
function as a stateless DHCP Relay Agent (BOOTP Helper), but it does.
2. MX shouldn't get confused and fail to function when the edge switch
has added it's own DHCP
On Thu, Aug 12, 2010 at 06:20:38AM -0700, Kaj Niemi wrote:
On 12/8/2010 15:33, Chuck Anderson c...@wpi.edu wrote:
1. MX shouldn't require Option 82 (relay-agent-option) in order to
function as a stateless DHCP Relay Agent (BOOTP Helper), but it does.
2. MX shouldn't get confused and
Hi,
This is supposedly fixed in PR/523902 which is resolved in 10.2R2 10.3R1
10.1R3 10.0R4 10.4R1. It includes two hidden commands which should allow the
forwarding of DHCP traffic on interfaces that are not configured for DHCP
(when using dhcp-relay or dhcp-local-server). I haven't had the time
I am trying to get DHCP relay working using either [forwarding-options
dhcp-relay] or [forwarding-options helpers bootp] on an M7i w/IQ2
ethernet running 9.6R1.13. I have several double-tagged and single
tagged vlans on interface ge-0/0/3 and am wanting to do relay on several
6 matches
Mail list logo
