The Graveyard - Products No Longer Supported > EBR-2310
DHCP Out the WAN Port
soundman87:
I have an issue with the ebr-2310 router. It is Hardware Revision C1 with Firmware Version: 3.00
If I disable the DHCP server, it starts issuing DHCP addresses to devices connected to the WAN port. As soon as turn the DHCP server back on it no longer issues addresses out the wan port.
I have an address range of 192.168.5.0 in the office with a DHCP server on the file server. I then have this router connected up with the wan port connected to the office network. The lan ports are connected to a couple of devices that are on a 192.168.1.0 address range that I can not change. I then have port forwardings setup so that I can access the 192.168.1.0 devices from my office desk through the router.
Devices on the office network are getting DHCP addresses from the router. It even shows up in the system logs on the ebr-2310 router. How can a fix this.
FurryNutz:
Are you trying to use this as an actual router or do you have the file server acting as a DHCP server?
Can you draw us a diagram of what your network looks like?
Example:ISP Modem>Router<>any swtiches><Wired devices
jyakimic:
Bump:
I've just had the exact same issue with the same revision and firmware number! It was sending DHCP OUT of the WAN port! I've just updated to firmware 3.01 and will update with whether the issue is corrected with the firmware upgrade.
DHCP OUT the WAN port! Crazy.
FurryNutz:
Hmmm, that seems odd behavior.
Keep us posted on results.
--- Quote from: jyakimic on June 26, 2013, 12:00:03 PM ---Bump:
I've just had the exact same issue with the same revision and firmware number! It was sending DHCP OUT of the WAN port! I've just updated to firmware 3.01 and will update with whether the issue is corrected with the firmware upgrade.
DHCP OUT the WAN port! Crazy.
--- End quote ---
jyakimic:
Extremely odd. Updating to firmware 3.01 fixed the issue. I used 2 separate brand new routers of this model/revision on 3.00 for testing (I have dozens of them sitting here for a project- glad the firmware update solved the issue). Never heard of anything like it.
Navigation
[0] Message Index
[#] Next page
Go to full version