From: Philip P. <phi...@re...> - 2011-03-06 01:38:54
|
Couple of other things make me think that it's using RFC-2684. See: ftp://ftp.redfish-solutions.com/pub/westell.png And looking at the connection logs on the Westell that Frontier lent me: Jan 1 07:45:54 daemon.notice net_mgr[350]: Routes transitioning to Up state on nas1. ... Jan 1 07:45:50 local0.info udhcpc[2566]: Lease of 71.111.120.3 obtained,lease time 7200 Jan 1 07:45:49 local0.debug udhcpc[2566]: Sending select for 71.111.120.3... Jan 1 07:45:49 local0.debug udhcpc[2566]: Sending discover... Jan 1 07:45:46 local0.debug udhcpc[2566]: Sending discover... Ok, so cutting and pasting HTML tables blows... "nas1"? Hmm..... Also, how do I clone the MAC address of the Westell when using RFC-2684 mode? Thanks, -Philip On 3/5/11 2:18 PM, Guy Ellis wrote: > Hi Philip, > > Try PPPoA, VPI = 0, VCI = 35 and see if that works. > > I've got to go to the football this morning, so I'll put up the lastest user docs when I get back and post a link. > > Cheers, > > - Guy. > > > > > > On 6/03/2011 7:20 AM, Philip Prindeville wrote: >> I recently moved into Frontier Communications land, and it's been difficult getting support from them on non-Frontier issued equipment (including being told the settings were 'proprietary'... huh???). >> >> Anyway, I'm troubleshooting the DSL support on OpenWRT which is somewhat untested on my Geos (which has the Solos chipset built in). >> >> I'm using the config: >> >> config 'interface' 'wan' >> option 'proto' 'dhcp' >> option 'ifname' 'nas0' >> >> config 'atm-bridge' >> option 'unit' '0' >> option 'vpi' '0' >> option 'vci' '35' >> option 'atmdev' '0' >> option 'encaps' 'vc' >> option 'payload' 'routed' >> >> ("atmdev" just sets the unit # for the nasX interface, 'unit' sets the port # on a multiport card) >> >> But this isn't working and indeed I'm seeing: >> >> Mar 5 11:31:03 OpenWrt kern.warn kernel: solos 0000:00:0c.0: Received packet for unknown VPI.VCI 0.35 on port 0 >> >> Can someone walk me through troubleshooting this? >> >> Glancing at the driver code, it's not clear why I'd be seeing that message. I'm running 2.6.37. >> >> Thanks, >> >> -Philip |