Whinery: So, try unplugging the Asus, rebooting the ONT, and plugging in the Tomato.  The DHCP lease time is pretty low, so give it about an hour if it doesn't come up right away, and the leases for the port should clear.  If the Tomato router still doesn't get a DHCP address, I'd start thinking about the Tomato not supporting DHCP in a manner that interoperates with our DHCP.

qyiet: So.. the router side setup is just IPv4 DHCP on the appropiate ethernet port? 

No vlan tagging, no pppoe.. just DHCP?  That (in theory) makes life very easy. 

Does the same apply for customer with a static IP?  (I ask as someone who will be setting up a non-supported router)

BMarquis:

Whinery: So, try unplugging the Asus, rebooting the ONT, and plugging in the Tomato.  The DHCP lease time is pretty low, so give it about an hour if it doesn't come up right away, and the leases for the port should clear.  If the Tomato router still doesn't get a DHCP address, I'd start thinking about the Tomato not supporting DHCP in a manner that interoperates with our DHCP.

Just to correct this a little...
rebooting the ONT will not help, the lease is on your BNG.
We would actually prefer people do not restart the ONTs, as it is a piece of our network equipment.

I haven't heard of a problem yet where rebooting the ONT resolves an issue.

Coon: Anyone manage? 
MyRepublic uses dhcp instead of pppoe 
I keep getting "renewing" (lease) as opposed to "connected"

But with the Asus I can connect straight away 

Whinery:

BMarquis:

Whinery: So, try unplugging the Asus, rebooting the ONT, and plugging in the Tomato.  The DHCP lease time is pretty low, so give it about an hour if it doesn't come up right away, and the leases for the port should clear.  If the Tomato router still doesn't get a DHCP address, I'd start thinking about the Tomato not supporting DHCP in a manner that interoperates with our DHCP.

Just to correct this a little...
rebooting the ONT will not help, the lease is on your BNG.
We would actually prefer people do not restart the ONTs, as it is a piece of our network equipment.

I haven't heard of a problem yet where rebooting the ONT resolves an issue.

I've heard of people improperly plugging in switches, rather than routers to the ONT and hitting ONT MAC limits.  It was then recommended that an ONT can be rebooted to clear out MAC limits.  I'm not sure what that point is for us, and whether it differs amongst the LFCs, so I added in that step in case there was a MAC limit reached on the ONT (as I have no idea what was done prior to the point of this problem).  Or is it the OLT that enforces the MAC limit, and the reboot of an ONT won't help?

Your profile doesn't state your affiliation.  You speak as if you are representing an LFC, but I can't tell which one.  And the answers are sometimes different among the different LFCs. If you are representing a company, especially for those of us new here, can you state which one?

(apologies for the edit this post, the sig info on the profile page says sigs are disabled for the first 200 posts, and I just enabled it to test if it works, so I edited to delete the double-sig)

Regards,

linw: Interesting about not rebooting the ONT. I would hazard that many help desk pers have that on their crib sheet. Certainly, the Orcon help desk told me to reboot the ONT when I had an authentication  problem a couple of days ago. Pretty easy to see a normal LED pattern on the ONT and mine was certainly normal.

linw: Interesting - thanks.

Now you just have to get this info to the ISP help desk pers. Good luck with that!!