I have configured my Juniper MX204 as a BNG IPOE with DHCP Relay and pointing an external DHCP server through forwarding options:
MX204 as BNG with DHCP relay configuration:
forwarding-options {
dhcp-relay {
access-profile Test;
server-group {
DHCP {
192.168.100.100;
}
}
active-server-group DHCP;
group all {
authentication {
username-include {
mac-address;
}
}
interface ge-0/0/0.0;
interface ge-0/0/2.0;
}
}
}
I have also configured an external RADIUS Server on Ubuntu and it authenticating and authorising by Access-Accept.
The issue is: My DHCP server received DHCP-DISCOVER request from BNG, it also offer IP to the BNG, However, the loopback interface of Juniper is not receiving it and clients are also not receiving any IPs from DHCP server. Some logs are here:
tail -f /var/log/syslog
Aug 2 12:09:33 DHCP dhcpd[45777]: DHCPDISCOVER from 50:02:00:31:00:01 (C-1) via 192.168.100.1
Aug 2 12:09:33 DHCP dhcpd[45777]: DHCPOFFER on 192.168.100.102 to 50:02:00:31:00:01 (C-1) via 192.168.100.1
Aug 2 12:09:42 DHCP dhcpd[45777]: DHCPDISCOVER from 50:02:00:31:00:01 (C-1) via 192.168.100.1
Aug 2 12:09:42 DHCP dhcpd[45777]: DHCPOFFER on 192.168.100.102 to 50:02:00:31:00:01 (C-1) via 192.168.100.1
Aug 2 12:09:47 DHCP dhcpd[45777]: DHCPDISCOVER from 50:02:00:31:00:01 (C-1) via 192.168.100.1
Aug 2 12:09:47 DHCP dhcpd[45777]: DHCPOFFER on 192.168.100.102 to 50:02:00:31:00:01 (C-1) via 192.168.100.1
Aug 2 12:09:48 DHCP dhcpd[45777]: DHCPDISCOVER from 50:02:00:31:00:01 (C-1) via 192.168.100.1
Aug 2 12:09:48 DHCP dhcpd[45777]: DHCPOFFER on 192.168.100.102 to 50:02:00:31:00:01 (C-1) via 192.168.100.1
Aug 2 12:09:48 DHCP dhcpd[45777]: DHCPDISCOVER from 50:02:00:31:00:01 (C-1) via 192.168.100.1
Aug 2 12:09:48 DHCP dhcpd[45777]: DHCPOFFER on 192.168.100.102 to 50:02:00:31:00:01 (C-1) via 192.168.100.1
DHCP Server cannot recognise BNG Loopback interface: (This is Wireshark packet capture)
Juniper is not receiving any IP from DHCP server: show log dhcplog | last 300
My Clients are not getting any IP:
Anyone has any solution for that please?
My dynamic profile configuration is as below:
dynamic-profiles {
DYP-IPOE-DHCP-INET {
predefined-variable-defaults {
input-filter default;
output-filter default;
output-ipv6-filter default-v6;
input-ipv6-filter default-v6;
}
routing-instances {
"$junos-routing-instance" {
interface "$junos-interface-name" {
any;
}
routing-options {
rib "$junos-ipv6-rib" {
access {
route $junos-framed-route-ipv6-address-prefix {
qualified-next-hop "$junos-interface-name";
metric "$junos-framed-route-ipv6-cost";
preference "$junos-framed-route-ipv6-distance";
tag "$junos-framed-route-ipv6-tag";
}
}
}
access {
route $junos-framed-route-ip-address-prefix {
next-hop "$junos-framed-route-nexthop";
metric "$junos-framed-route-cost";
preference "$junos-framed-route-distance";
tag "$junos-framed-route-tag";
}
}
}
}
}
interfaces {
demux0 {
unit "$junos-interface-unit" {
proxy-arp;
demux-options {
underlying-interface "$junos-underlying-interface";
}
family inet {
demux-source {
$junos-subscriber-ip-address;
}
filter {
input "$junos-input-filter";
output "$junos-output-filter";
}
unnumbered-address lo0.0;
}
family inet6 {
filter {
input "$junos-input-ipv6-filter";
output "$junos-output-ipv6-filter";
}
address $junos-ipv6-address;
demux-source {
"$junos-subscriber-ipv6-address";
}
unnumbered-address lo0.0;
}
}
}
}
protocols {
router-advertisement {
interface "$junos-interface-name" {
link-mtu;
prefix $junos-ipv6-ndra-prefix {
valid-lifetime 14400;
on-link;
preferred-lifetime 14400;
}
}
}
}
}
DYP-SVLAN-IPDEMUX {
interfaces {
demux0 {
unit "$junos-interface-unit" {
actual-transit-statistics;
demux-source [ inet inet6 ];
proxy-arp;
vlan-id "$junos-vlan-id";
demux-options {
underlying-interface "$junos-interface-ifd-name";
}
family inet {
unnumbered-address lo0.0 preferred-source-address 192.168.100.1;
}
family inet6 {
unnumbered-address lo0.0 preferred-source-address 2009:2007::1;
}
}
}
}
}
}
------------------------------
Nazmus Sakib
------------------------------