Business Community > Gateways > ER7212PC v2.0 SFP stick access problem
< Gateways

ER7212PC v2.0 SFP stick access problem

ER7212PC v2.0 SFP stick access problem

ER7212PC v2.0 SFP stick access problem
ER7212PC v2.0 SFP stick access problem
2025-10-23 18:17:05
Model: ER7212PC  
Hardware Version: V2
Firmware Version: 2.1.3 20250922 Release 85334

Hello everyone! I'm facing a serious problem with my new ER7212PC v2.0: I simply can't access my ODI DFP-34X-2C2 STP stick at all. The default access IP for the ODI DFP-34X-2C2 is 192.168.1.1, which gives access to a web interface with a series of settings such as LOID, LOID Password, PLOAM Format, PLOAM Password, GPON SN, Vendor ID, software version 1, software version 2, Product class, HW version, Device serial number, MAC, MACKEY, etc. This is essential for the user to be able to clone some information from the ISP's HGU and receive authentication.

I have normal access to this web interface via Media Converter TP-Link MC220L v5.0. However, when I connect the ODI DFP-34X-2C2 stick to SFP port 1 or 2, I can no longer access the stick's web interface, although the ping (ping -t 192.168.1.1) responds normally. On the ER7212PC v2.0 I tried to set a dynamic IP and was unable to access, so I followed the logic that should work correctly by setting the static IP 192.168.1.2 and subnet mask 255.255.255.0, and in the same way I cannot access the web interface via IP 192.168.1.1, although the ping responds normally.

I see several reports of ER7212PC v1.0 users normally accessing this same ODI DFP-34X-2C2 stick by setting the static IP 192.168.1.2 and subnet mask 255.255.255.0 to an SFP port of the ER7212PC v1.0, so there was some change in the ER7212PC v2.0 update compared to version 1.0. I figured it might be a firmware-related bug, so I installed the latest beta version ER7212PC_v2_V2.1.3 pre-release (https://community.tp-link.com/en/business/forum/topic/843040), but the problem remains: I still can't access the stick's web interface via IP 192.168.1.1.


In addition to the stock firmware for the ODI DFP-34X-2C2 stick, I also tried different custom firmwares, such as those from developer Tripleoxygen: M110_V1.1.8-240408, M114_V1.7.1-231021, M114_V1.7.1-231022 and V1.9.1-240202.


How can I regain access to this stick's web interface when connected to the ER7212PC v2.0 SFP ports?

Thank you in advance.

  0      
 
  0      
 
#1
Options
2 Reply
Re:ER7212PC v2.0 SFP stick access problem
2025-10-27 11:44:33

Hi  @Leatg 

 

Thanks for posting here.

To understand the situation better, please let us know more details:

1. When you plug the stick into the SFP ports, will the corresponding port LED light up? What's the status? solid on or flashing？

2. What devices are you trying to use to manage the stick? A PC? Where do you plug it into? An Ethernet port of the ER7212PC?

3. If ping the stick's IP address, will it reply? Please share with us the screenshot of the ping result. 

How to use the Ping command

 

4. What's the error message when failed to access the page? Please share with a screenshot.

5. What's the LAN IP of the ER7212PC?

6. Do you have any other SFP devices, such as a switch that can run a comparison test?

 

Wish you a happy life and smooth network usage!  >Omada US Enterprise Beta Program Launch< >Get the Latest Omada SDN Controller Releases Here< >Experience the Latest Omada EAP Firmware<
  0  
  0  
#2
Options
Re:ER7212PC v2.0 SFP stick access problem
2025-11-06 23:34:07

@Leatg I had a similar issue where I could ping 192.168.1.1 but when trying to access via browser, it was not working.

 

The solution was quite simple, I just had to make sure to use http://192.168.1.1 (explicitly stating http and not https here), otherwise my browser would try going through HTTPS first and ODI's web page would be stuck loading.

 

Hope this solves it. If not, try making sure the router's subnet is different from ODI's, or try another static IP like 192.168.1.254, subnet mask 255.255.255.0, gateway 192.168.1.1. As a last resort, check for firewall rules or try creating a static route to it (usually shouldn't be needed). Also if you're using PPPoE, you can add a secondary connection on the WAN page and assign an internal IP like 192.168.1.254 too, this has the advantage of both the management interface and Internet being available simulteneosly. For Dynamic IP WAN though, a secondary connection is not possible, so you need to make your first connection using static IP and after configuring the stick you can change the WAN port to Dynamic IP to fetch the ISP's DHCP server.

  0  
  0  
#3
Options

Information

Helpful: 0

Views: 962

Replies: 2

About Us
Press
Copyright © TP-Link Systems Inc. All rights reserved.