From: Guy E. <gu...@tr...> - 2011-03-06 05:15:40
|
Hi Philip, Unfortunately auto-detecting PPP links as totally inpractical - you would have to send out an LCP request on every PVC! Based on your later emails, it looks like you should used bridged ethernet. See section 4 of the Geos Linux User Manual for tips. If your ISP uses DHCP then bring the interface up unnumbered ifconfig nas0 up Where is the user manual you ask? If you go to the Geos product page, there is a link for the Linux User Manual top RHS... http://www.traverse.com.au/productview.php?product_id=117 Cheers, - Guy. On 6/03/2011 9:59 AM, Philip Prindeville wrote: > There's no utility to auto-detect the configuration? > > What about using atmdump? > > -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 >>> |