ifconfig eth0 uppon dsl-providerWord of caution: before you make any changes to these files, make a copy/backup of them in case you need to restore them. After you make any changes, remember to restart networking.

Anyone know if that COAX connection is important to VZ? I was on with a tech last night for an hour trying to fix my connection and he didn't give me a definitive answer.

The coax on the router afaik is used to provide channel/guide data and video on demand back to your set-top-box. Verizon has a few different ways of setting up the TV services and connections, so I can only speculate on your specific setup.

FIOS TV is delivered to your STB via coax directly from the ONT. It (most likely) also has a second coax connection coming from the router where it gets/downloads the guide data. If you are making use of the guide data feature, then you would need to keep the coax from the router to the stb in place.

if you move the VZ router behind the LMCE core, you should disable the wan routing features of the VZ router, and run it as a simple lan switch (4 ports built in). As long as your lan is properly set up, the STB will be able to download the guide data through the VZ router (now switch).

255.255.255.255 for the external net mask looks odd to me. That mask would result in a subnet of 0 IP addresses. That might have something to do with what's going on here. Is that subnet mask being provided through DHCP from your ISP or has it been configured manually? Also the gateway address of 0.0.0.0 is invalid. It should be the IP address of your internal network's DHCP server IP.

Are you sure your lan clients/nodes are getting the correct network info via DHCP from the core?Can you post the ifconfig (linux) or ipconfig -a (windows) info from a lan node that will not connect to internet?

Can you also post the routing table from the core?type "route" in a terminal.

For the record, I just tore down my entire network and rebuilt/set everything from scratch again.I am using the core as the wan gateway with dhcp enabled. I have three internal switches and one wireless AP.

EXTERNAL_IFACE ppp0EXTERNAL_MAC EXTERNAL_IP inet addr:72.85.xxx.xxx P-t-P:10.9.69.1 Mask:255.255.255.255EXTERNAL_NETMASK 255.255.255.255EXTERNAL_DHCP 0INTERNAL_IFACE eth1INTERNAL_MAC 00:02:E3:11:B3:95INTERNAL_IP 192.168.15.2INTERNAL_NETMASK 255.255.255.0GATEWAY 0.0.0.0DNS1 71.243.0.12DNS2 71.250.0.12As you can see my Mask and Gateway are the same as yours... This is normal for VZ PPPOE.

PPP and IP operate on different "layers" of the OSI model. (google that for some great bedtime reading - it'll put you right to sleep) IP operates on the logical layer while PPP works on the actual physical layer. MAC addressing VS. IP addressing.

I'm thinking you have either a DNS or default route mis-configured somewhere.can you try using static ips and setting DNS and default gateway manually on a pc that cannot connect and see if it will connect that way?

In addition to the if/ipconfig and route info, can you include your /etc/dhcp3/dhcpd.conf info? It would be very helpful.

meaning it is looking for DNS info from the core, but the core is not acting as the DNS server.when your client nodes ask for DNS servers from dhcp, the core is giving them 192.168.80.1 which is what is found in the line "option domain-name-servers 192.168.80.1;"

Changing that line in the dhcpd.conf file to reflect you ISP assigned DNS server IPs should do the trick.Good Luck!!