Does anyone know why DHCP discover packets are not relayed through an MX
from my client to en external DHCP server that resides on the same network
as one on the interfaces on MX (I can ping this DHCP server from the MX).
I don't see any mention of which *interface* to run the DHCP helper on
Hi,
From Cisco I remember that when an IP packet is labeled, the IP precedence
value is copied into MPLS experimental bits.
Is Juniper behaving the same way?
If so, why, for a identical bit pattern (e.g. 101) both MPLS EXP and IP
Precedence do not point to the same alias (e.g. ef)?
[EMAIL PROTECTED] schrieb:
I don't see any mention of which *interface* to run the DHCP helper on
under your forwarding-options. I believe you need that.
No, that's not required here.
--
Accelerated IT Services GmbH
Schubertstrasse 10D-67251 Freinsheim
[EMAIL
Still no luck. This is what I have. Also there is no firewall in this
network.
forwarding-options {
helpers {
bootp {
server 10.0.0.100;
relay-agent-option;
}
}
}
interfaces { ---client side
ge-0/0/0 {
unit 0 {
What you get when you do show helper statistics
You can also use some packet capturing applications like ethereal on DHCP
server; just to check the packets are being forward to DHCP server or not.
If you need include the maximum-hop-count statement, deault value is 4 hops.
set the routing
This counter is incrementing:
Due to no valid local address: 1 - when I run 'show helper
statisctics'
[EMAIL PROTECTED] run show helper statistics
bootps:
Received packets: 1
Forwarded packets: 0
Dropped packets: 1
Due to no interface in fud database: 0
Due to no
6 matches
Mail list logo
