Re: ADSL with pppoa (over ATM)
On Tue, Apr 11, 2006 at 08:18:34PM +0200, Luca Losio wrote: Can you explain how to handle the authentication? I missed this point The DLink does it. You put in your username and password that your ISP supplied into the DLink web interface. Put your external NIC to DHCP and that is the job done.
Re: ADSL with pppoa (over ATM)
The WAN allocated from the ISP's RADUIS server will be passed through the DLink, via DHCP, to your NIC. If you aren't convinced, put a windows box with a DHCP NIC behind the DLink while in bridge mode, and see it get a routable address. Try this: unplug the telephone wire, reboot the DLink, and your NIC will get a private address (on windows, do an ipconfig /renew). Plug in the telephone wire, and it will get a public one. Job done. Can you explain how to handle the authentication? I missed this point
Re: ADSL with pppoa (over ATM)
On Sat, Apr 01, 2006 at 01:05:50PM +0100, tony sarendal wrote: I'm afraid it is. Look at the third option in 4.4.2.10. (PPPoE LLC/SNAP) That is optional at the discretion of the ISP, default UK ADSL is VC-MUX and therefore PPPoA. It can't be both PPPoE and PPPoA. It is unusual for UK ISPs to use PPPoE for ADSL, some use it for (LLU) SDSL. You may want to check with your provider to ensure that you are using the correct protocol.
Re: ADSL with pppoa (over ATM)
On 04/04/06, Craig Skinner [EMAIL PROTECTED] wrote: On Sat, Apr 01, 2006 at 01:05:50PM +0100, tony sarendal wrote: I'm afraid it is. Look at the third option in 4.4.2.10. (PPPoE LLC/SNAP) That is optional at the discretion of the ISP Correct default UK ADSL is VC-MUX and therefore PPPoA. It can't be both PPPoE and PPPoA. Over a period it can, at the same time,no. It is unusual for UK ISPs to use PPPoE for ADSL, some use it for (LLU) SDSL. Maybe unusual in number of ISP's doing it, but not unusual counting number of subscribers doing it. You may want to check with your provider to ensure that you are using the correct protocol. Done that. /T Tony Sarendal - [EMAIL PROTECTED] IP/Unix -= The scorpion replied, I couldn't help it, it's my nature =-
Re: ADSL with pppoa (over ATM)
On 01/04/06, Craig Skinner [EMAIL PROTECTED] wrote: Set the MTU and MRU to 1453, not 1500. 1453 ? Explain please. -- Tony Sarendal - [EMAIL PROTECTED] IP/Unix -= The scorpion replied, I couldn't help it, it's my nature =-
Re: ADSL with pppoa (over ATM)
On Sat, Apr 01, 2006 at 09:16:33AM +0100, tony sarendal wrote: On 01/04/06, Craig Skinner [EMAIL PROTECTED] wrote: Set the MTU and MRU to 1453, not 1500. 1453 ? Explain please. Typo, should have been 1458: http://www.adslnation.com/support/knowledgebase/ht003.php http://www.adslguide.org.uk/guide/mtu.asp http://www.adslguide.org.uk/newsarchive.asp?item=899
Re: ADSL with pppoa (over ATM)
On 2006/04/01 08:36, Craig Skinner wrote: If you must do the PPP session in OpenBSD, try the Alcatel USB frog. Or ueagle(4). Better yet, buy a ZyXEL these work quite well IME, including on marginal lines (660H).
Re: ADSL with pppoa (over ATM)
On 01/04/06, Craig Skinner [EMAIL PROTECTED] wrote: On Sat, Apr 01, 2006 at 09:16:33AM +0100, tony sarendal wrote: On 01/04/06, Craig Skinner [EMAIL PROTECTED] wrote: Set the MTU and MRU to 1453, not 1500. 1453 ? Explain please. Typo, should have been 1458: http://www.adslnation.com/support/knowledgebase/ht003.php http://www.adslguide.org.uk/guide/mtu.asp http://www.adslguide.org.uk/newsarchive.asp?item=899 In my case (aslo on crappy UK broadband) 1454 is actually optimal. On the dsl part of the link my connection runs the Ethernet frames over ATM, so I get this nice pancake when crossing the pvc: ATM/AAL5/Ethernet/PPPoE/PPP/IP Unless the IP packet is smaller than 38 bytes I have 34 bytes of overhead before splitting up into ATM cells. If I were to use MTU 1458 that would make that 1458+34=1492 bytes. 1492 bytes will require 32 atm cells,32*53=1696 bytes. 1696/1458 = 16.3% overhead. Now if I would use MTU 1454. 1454+34=1488 1488 bytes require 31 atm cells=1643 bytes 1643/1488=10.4% overhead. Note that this is of course overhead on top of IP, not application. On a side note I modifed the traffic shaper in PF to understand the real overhead of my dsl link, so I can now set my shaper to 280kbps (ATM PVC 288kbps) and my QoS config works great no matter what the IP packet size is. Before I could get packet loss on the pvc even if I had the shaper set to 160kbps simply due to awesome overhead at smaller packet sizes. Example: TCP ACK=40 bytes IP That will require 2 ATM cells for me. 106/40 = a whopping 165% overhead on top of IP while crossing the ATM link. I think I'm going to add GFP (EoSDH) and a few others here. Enough ranting, time to feed the kids. -- Tony Sarendal - [EMAIL PROTECTED] IP/Unix -= The scorpion replied, I couldn't help it, it's my nature =-
Re: ADSL with pppoa (over ATM)
On Sat, Apr 01, 2006 at 10:39:26AM +0100, tony sarendal wrote: In my case (aslo on crappy UK broadband) You should try it in NZ, 128k upstream! 1454 is actually optimal. On the dsl part of the link my connection runs the Ethernet frames over ATM, so I get this nice pancake when crossing the pvc: ATM/AAL5/Ethernet/PPPoE/PPP/IP I doubt that there would be PPPoE in there, if your ISP resells std BT ADSL. You may want to see: http://www.sinet.bt.com/386v2p0.pdf Unless the IP packet is smaller than 38 bytes I have 34 bytes of overhead before splitting up into ATM cells. If I were to use MTU 1458 that would make that 1458+34=1492 bytes. 1492 bytes will require 32 atm cells,32*53=1696 bytes. 1696/1458 = 16.3% overhead. Now if I would use MTU 1454. 1454+34=1488 1488 bytes require 31 atm cells=1643 bytes 1643/1488=10.4% overhead. Cool stuff. Note that this is of course overhead on top of IP, not application. On a side note I modifed the traffic shaper in PF to understand the real overhead of my dsl link, so I can now set my shaper to 280kbps (ATM PVC 288kbps) and my QoS config works great no matter what the IP packet size is. Before I could get packet loss on the pvc even if I had the shaper set to 160kbps simply due to awesome overhead at smaller packet sizes. Example: TCP ACK=40 bytes IP That will require 2 ATM cells for me. 106/40 = a whopping 165% overhead on top of IP while crossing the ATM link. I think I'm going to add GFP (EoSDH) and a few others here. Enough ranting, time to feed the kids. To the labrador?
Re: ADSL with pppoa (over ATM)
On 01/04/06, Craig Skinner [EMAIL PROTECTED] wrote: On Sat, Apr 01, 2006 at 10:39:26AM +0100, tony sarendal wrote: In my case (aslo on crappy UK broadband) You should try it in NZ, 128k upstream! 1454 is actually optimal. On the dsl part of the link my connection runs the Ethernet frames over ATM, so I get this nice pancake when crossing the pvc: ATM/AAL5/Ethernet/PPPoE/PPP/IP I doubt that there would be PPPoE in there, if your ISP resells std BT ADSL. You may want to see: http://www.sinet.bt.com/386v2p0.pdf I'm afraid it is. Look at the third option in 4.4.2.10. (PPPoE LLC/SNAP) /T -- Tony Sarendal - [EMAIL PROTECTED] IP/Unix -= The scorpion replied, I couldn't help it, it's my nature =-
Re: ADSL with pppoa (over ATM)
Luca Losio wrote: My ADSL connection is PPPoA only, which is just PPPoE with ATM. They work at different layers so if you bridge your adsl modem and handle only the ATM part, then openbsd pppoe can do the rest. So this means your ADSL modem will have no public facing IP and reconnecting to it may be tricky once you have set it up. So be careful how you set it up. Can you please post your ppp configuration file? So on the Dlink modem all you just did was to set it on bridge mode. Why it shouldn't work with the 1-port version? I have this (300t) :-( but I upgraded the firmware Please review this as you have already been given the answer: http://archive.netbsd.se/?ml=openbsd-misca=2006-03m=1864140 This thread is closed. Here again for you: set your NIC to use DHCP, do not use pppoe. The WAN allocated from the ISP's RADUIS server will be passed through the DLink, via DHCP, to your NIC. If you aren't convinced, put a windows box with a DHCP NIC behind the DLink while in bridge mode, and see it get a routable address. Try this: unplug the telephone wire, reboot the DLink, and your NIC will get a private address (on windows, do an ipconfig /renew). Plug in the telephone wire, and it will get a public one. Job done. These routers are designed to be no brainers for windows users, yet there are no windows drivers, therefore it uses conventional networking. The router does PPPoA, this is a superior technology as the PPP session sits directly on top of the telco's ATM system. PPPoE is PPP over ethernet, over ATM: an extra layer that is not needed.
Re: ADSL with pppoa (over ATM)
On Fri, Mar 31, 2006 at 09:16:23AM +0200, Luca Losio wrote: My ADSL connection is PPPoA only, which is just PPPoE with ATM. They work at different layers so if you bridge your adsl modem and handle only the ATM part, then openbsd pppoe can do the rest. So this means your ADSL modem will have no public facing IP and reconnecting to it may be tricky once you have set it up. So be careful how you set it up. Can you please post your ppp configuration file? Assuming that you're wanting to user the kernel pppoe driver, which has been in OpenBSD since 3.7. Look at # man 4 pppoe for details, compare with man 8 pppoe which is the userland pppoe version and has been in OpenBSD since 2.8. The kernel pppoe network device only really become stable in 3.8. So on the Dlink modem all you just did was to set it on bridge mode. Why it shouldn't work with the 1-port version? I have this (300t) :-( but I upgraded the firmware I don't know for sure. I have the DSL-504T. Looking at the Setup, DSL Setup config of it, I have it setup as a Bridge with the approiate; Encapsulation, VPI, VCI, and QoS setting given by my ISP. On the WAN Setup they is no layer 3 setting, ie IP setting, since I want my OpenBSD box to do that bit. There's no point choosing DHCP since you still have to authenicate via PPP. If you don't have a bridge setup then DHCP looks like it'll work, although it's not needed. Obivously try it if you have no other option. Looking at the LAN setup I have disabled DHCP since I wanted to use dhcpd on my OpenBSD box. I have disabled the DNS relay function. Again I do that on another box since I maintain internal DNS for my RFC 1918 IPs, aka Private IPs 10/8, 172.16/12, 192.168/16. Then I changed the management IP to a different subnet, matching the IP of my ethernet card used by the pppoe network device. I have to use ssh port forwarding to access my D-link router, but then until today I hadn't connected to it since September 2005. And quite frankly I'd much prefer managing my adsl connection via my OpenBSD box than a web interface. So as for the OpenBSD box I have # cat /etc/hostname.pppoe0 pppoedev rl1 !/usr/sbin/spppcontrol \$if myauthproto=chap myauthname=username \ myauthkey=password !/sbin/ifconfig \$if inet 0.0.0.0 0.0.0.1 !/sbin/route add default 0.0.0.1 up Where username and password are set to what you ISP has given you for your PPPoA setting. # cat /etc/hostname.rl1 inet 192.168.10.100 255.255.255.0 In /etc/pf.conf I have scrub out on pppoe0 max-mss 1440 It's all in the man page, except I have given the physical network card an IP. If you were doing pure pppoe to your ISP, then you would do as the man page reads. You may also want to take note about setting the MTU as per the man page. If things are working nicely you'll see something like the following: # ifconfig pppoe0 pppoe0: flags=8851UP,POINTOPOINT,RUNNING,SIMPLEX,MULTICAST mtu 1492 dev: rl1 state: session sid: 0xcf8 PADI retries: 14 PADR retries: 0 time: 17d 15:03:41 groups: pppoe egress inet 10.10.10.10 -- 0.0.0.1 netmask 0xff00 inet6 fe80::260:8ff:dead:beef%pppoe0 - prefixlen 64 scopeid 0x9 Where 10.10.10.10 is the IP your ISP assigns you. I ususally find that on first booting the pppoe device takes a while to authenication but once up it's really stable. Seems better than most customer ADSL modems and also seems to cope with DSLAM reboots at the exchange very well. I've not had any complaints about it. As for the other side of my OpenBSD router I have quite a complicated setup which is probably overkill for most peoples needs. If you're just doing NAT on a single NIC then that should be pritty straight forward via /etc/pf.conf It was a pain to setup, but I'm glad of it now. Especially when there's DoS exploits in Netgear ADSL routers using IRC DCC commands when SPI is turned of. I'd much rather trust my OpenBSD than VxWorks or Linux based modem. Usually they're accessively slimed down and missing a lot of features OpenBSD has to offer. If you find this information useful I may be inclined to write some online docs for it. Since it'll possible help others if you didn't find much in Google. So let me know how you get one. Dan
Re: ADSL with pppoa (over ATM)
On Fri, Mar 31, 2006 at 11:52:27AM +0100, Craig Skinner wrote: Luca Losio wrote: My ADSL connection is PPPoA only, which is just PPPoE with ATM. They work at different layers so if you bridge your adsl modem and handle only the ATM part, then openbsd pppoe can do the rest. So this means your ADSL modem will have no public facing IP and reconnecting to it may be tricky once you have set it up. So be careful how you set it up. Can you please post your ppp configuration file? So on the Dlink modem all you just did was to set it on bridge mode. Why it shouldn't work with the 1-port version? I have this (300t) :-( but I upgraded the firmware Please review this as you have already been given the answer: http://archive.netbsd.se/?ml=openbsd-misca=2006-03m=1864140 This thread is closed. That depends on if Luca really wants to do that. Then again he may not. I think we should let him decide if this thread is closed. snip These routers are designed to be no brainers for windows users, yet there are no windows drivers, therefore it uses conventional networking. Personally I didn't want a point and drool interface, I wanted more control of my connection. The router does PPPoA, this is a superior technology as the PPP session sits directly on top of the telco's ATM system. PPPoE is PPP over ethernet, over ATM: an extra layer that is not needed. Read RFC 1661, RFC 2516 and RFC 2364 iirc. PPP, ethernet and ATM are all layer 2 of the OSI Seven Layer model. IP is in layer 3. ATM and ethernet are data links which tunnel the PPP data. PPP does the authenication and various other thing just like with dial up modems. It's not a case of tunneled PPP in ethernet in ATM. The ADSL modem deals with changing the wrapper to tunnel PPP from ethernet to ATM. ATM deal with getting the PPP data from my ADSL modem to the DSLAMs at the exchange. Ethernet deals with getting the PPP data from my OpenBSD box to my ADSL modem. I seriously doubt my exchange would understand me firing ethernet data at it or maybe I'm wasting bytes in my segments in unnecessary overheads. I'll admit this is not a normal setup but as far as I know OpenBSD doesn't have PPPoA support directly in the kernel, and I can't see why it would since most ADSL PCI cards are primaryly driven by software usually in the form of BLOBs. Maybe you fancy reverse engineering some of these cards and get them working in OpenBSD. Dan
Re: ADSL with pppoa (over ATM)
On Wed, Mar 29, 2006 at 03:16:38AM +0100, Daniel Walrond wrote: On Tue, Mar 21, 2006 at 08:21:40PM +0100, Luca Losio wrote: I read the faq searching for info about pppoa (http://www.openbsd.org/faq/faq6.html) : The main software interface to PPPoE/PPPoA on OpenBSD is pppoe(8), which is a userland implementation (in much the same way that we described ppp(8), above) but I can't figure out how to configure it for a ppp over ATM connection. Anyone can help? I don't want to have a double NAT, one from the adsl modem and one from the OpenBSD gateway... I have a Dlink 4-port ADSL modem, I forget the the product code. IIRC it won't work with the 1-port version. I use the pppoe kernel driver and my modem does the ATM part. It works very well, I've been running it since september 2005. My ADSL connection is PPPoA only, which is just PPPoE with ATM. That should have read ...PPP with ATM. If I have confused people. Dan
Re: ADSL with pppoa (over ATM)
On Fri, Mar 31, 2006 at 06:35:16PM +0100, Daniel Walrond wrote: These routers are designed to be no brainers for windows users, yet there are no windows drivers, therefore it uses conventional networking. Personally I didn't want a point and drool interface, I wanted more control of my connection. Absolutely, but it demonstrates just how easy it is to get a working connection, as the device was designed to be operated without PPP settings or drivers. or maybe I'm wasting bytes in my segments in unnecessary overheads. Set the MTU and MRU to 1453, not 1500. I'll admit this is not a normal setup but as far as I know OpenBSD doesn't have PPPoA support directly in the kernel, and I can't see why it would since most ADSL PCI cards are primaryly driven by software usually in the form of BLOBs. Maybe you fancy reverse engineering some of these cards and get them working in OpenBSD. I have a BeWAN one that works in Linux. I thought about sending it in as a hardware donation as I don't use Linux much anymore. The DLink 300T is not a PCI card, it is an ethernet connected router/modem, that operates in half bridge mode to pass it WAN IP to the client's NIC. ie: it is suitable for connecting one device only, you can not use a routeable LAN with it. The 300T does PPPoA, and operates a DHCP server, that passes it IP address to the connecting device's NIC. It really is that simple. If you must do the PPP session in OpenBSD, try the Alcatel USB frog. Better yet, buy a ZyXEL, these routers run a BSD, not uclibc Linux like the majority of routers do.
Re: ADSL with pppoa (over ATM)
My ADSL connection is PPPoA only, which is just PPPoE with ATM. They work at different layers so if you bridge your adsl modem and handle only the ATM part, then openbsd pppoe can do the rest. So this means your ADSL modem will have no public facing IP and reconnecting to it may be tricky once you have set it up. So be careful how you set it up. Can you please post your ppp configuration file? So on the Dlink modem all you just did was to set it on bridge mode. Why it shouldn't work with the 1-port version? I have this (300t) :-( but I upgraded the firmware
Re: ADSL with pppoa (over ATM)
Hello, On Tue, Mar 21, 2006 at 08:21:40PM +0100, Luca Losio wrote: I read the faq searching for info about pppoa (http://www.openbsd.org/faq/faq6.html) : The main software interface to PPPoE/PPPoA on OpenBSD is pppoe(8), which is a userland implementation (in much the same way that we described ppp(8), above) but I can't figure out how to configure it for a ppp over ATM connection. Anyone can help? I don't want to have a double NAT, one from the adsl modem and one from the OpenBSD gateway... I have a Dlink 4-port ADSL modem, I forget the the product code. IIRC it won't work with the 1-port version. I use the pppoe kernel driver and my modem does the ATM part. It works very well, I've been running it since september 2005. My ADSL connection is PPPoA only, which is just PPPoE with ATM. They work at different layers so if you bridge your adsl modem and handle only the ATM part, then openbsd pppoe can do the rest. So this means your ADSL modem will have no public facing IP and reconnecting to it may be tricky once you have set it up. So be careful how you set it up. Then you can setup your openbsd box to suit your needs removing a potentially buggy adsl modem firewall out of the loop. Now if you've got a block of IPs and your running them on red and dmz segments things can get very messy if you don't want to waste IPs. Running a bridge on the internal interfaces seems to do the job best, you can't include the pppoe device, and including the underlying ethernet card isn't going to work as one might expect. But the pppoe device and the bridge seem to interact fine. Enjoy :) Dan
Re: ADSL with pppoa (over ATM)
My understanding is that to operate in 'full bridge mode' requires pppoe support from the provider. Which is where this thread started. Donald J. Ankney wrote: Has anybody done this through a full bridge? My Actiontech isn't nearly as friendly with it's options... Simon Slaytor wrote: Half Bridge mode is your friend here. Not sure if the D-Link supports this mode however, Google is less than helpful. Essentially in half bridge mode the modem handles the PPPoA authentication with the ISP, as in NAT mode obtaining an IP address from the remote provider as normal. Unlike NAT mode however the modem then leases out this exact same IP address to the connected ethernet host, thereby presenting the external IP directly to your external ethernet port. Finally the modem begins to transparently bridge the ADSL/Ethernet connections. I can vouch for Zoom X3/4 and ADSL Nation X-Modems working in this mode without issue.
Re: ADSL with pppoa (over ATM)
On Tue, 21 Mar 2006 20:53:41 + Simon Slaytor [EMAIL PROTECTED] wrote: Half Bridge mode is your friend here. Not sure if the D-Link supports this mode however, Google is less than helpful. Essentially in half bridge mode the modem handles the PPPoA authentication with the ISP, as in NAT mode obtaining an IP address from the remote provider as normal. Unlike NAT mode however the modem then leases out this exact same IP address to the connected ethernet host, thereby presenting the external IP directly to your external ethernet port. Finally the modem begins to transparently bridge the ADSL/Ethernet connections. I can vouch for Zoom X3/4 and ADSL Nation X-Modems working in this mode without issue. My Aethra Starbridge-EU works fine in half-bridge, although I had to set VCI=0 in the modem, whatever that is. I would much rather have my ext_if assigned the routable ip, and do all of the nat and rdr from pf :) Mike
Re: ADSL with pppoa (over ATM)
On Wed, Mar 22, 2006 at 04:29:56AM -0600, mike wrote: My Aethra Starbridge-EU works fine in half-bridge, although I had to set VCI=0 in the modem, whatever that is. You need to set the VPI VCI, encapsulation modulation. It is different for many countries depending on how the telcos deceide to run their network. See: http://www.patton.com/support/faqs_detail.asp?id=142 http://www.adslguide.org.uk/qanda.asp?faq=DSLHardware I would much rather have my ext_if assigned the routable ip, and do all of the nat and rdr from pf :) As you seem to have a static IP on the router's WAN, your ISP will probably be able to provide a /30 routeable LAN for the asking! eg: I have 84.19.247.29/32 on the WAN of the router, and 84.19.247.232/29 as a routeable LAN.
Re: ADSL with pppoa (over ATM)
On 3/22/06, Simon Slaytor [EMAIL PROTECTED] wrote: My understanding is that to operate in 'full bridge mode' requires pppoe support from the provider. Which is where this thread started. Not pppoe, but pppoa
Re: ADSL with pppoa (over ATM)
I used to have one of these. On your external NIC, use DHCP, and that is it. The DLink does the PPPoA stuff and issues the WAN IP address to your DHCP card. You can still telnet to the DLink on 192.168.0.1 at the same time as your link being up. mmm...I tried switching off dhcp server on the modem, issued a dhcpclient xl1 but I can't get a dhcp response
Re: ADSL with pppoa (over ATM)
On Wed, Mar 22, 2006 at 07:14:23PM +0100, Luca Losio wrote: I used to have one of these. On your external NIC, use DHCP, and that is it. The DLink does the PPPoA stuff and issues the WAN IP address to your DHCP card. You can still telnet to the DLink on 192.168.0.1 at the same time as your link being up. mmm...I tried switching off dhcp server on the modem, issued a dhcpclient xl1 but I can't get a dhcp response Leave the DHCP server enabled on the DLink, and enable your NIC via DHCP. Job done. Unplug the phone line and reboot the router, your NIC will get a 192.168.0.2 address, plug the phone line in and it will get issued the public WAN IP from the router. The router was designed for Windoze users, and they wouldn't mess about with static setups. I now use a ZyXEL and have my ISP allocate a routeable LAN, which is better, but not doable with the DLink model that you have.
Re: ADSL with pppoa (over ATM)
On Wed, 22 Mar 2006 11:14:07 + Craig Skinner [EMAIL PROTECTED] wrote: On Wed, Mar 22, 2006 at 04:29:56AM -0600, mike wrote: My Aethra Starbridge-EU works fine in half-bridge, although I had to set VCI=0 in the modem, whatever that is. You need to set the VPI VCI, encapsulation modulation. It is different for many countries depending on how the telcos deceide to run their network. See: http://www.patton.com/support/faqs_detail.asp?id=142 http://www.adslguide.org.uk/qanda.asp?faq=DSLHardware I was mistaken, my VPI=0, VCI=35 per my ISP. Note that this is in Wisconsin, USA, so the above link's table is not quite correct, as it lists the USA's VPI as 8, which also was the modem's default. I would much rather have my ext_if assigned the routable ip, and do all of the nat and rdr from pf :) As you seem to have a static IP on the router's WAN, your ISP will probably be able to provide a /30 routeable LAN for the asking! eg: I have 84.19.247.29/32 on the WAN of the router, and 84.19.247.232/29 as a routeable LAN. A /30 would be nice, but I have no complaints with a dynamic /32, dyndns, and then rdr'ing ssh smtp via pf.
Re: ADSL with pppoa (over ATM)
mike wrote: http://www.patton.com/support/faqs_detail.asp?id=142 http://www.adslguide.org.uk/qanda.asp?faq=DSLHardware I was mistaken, my VPI=0, VCI=35 per my ISP. Note that this is in Wisconsin, USA, so the above link's table is not quite correct, as it lists the USA's VPI as 8, which also was the modem's default. VPI/VCI numbers vary all over the US, so that table is about worthless. Here in Colorado, on Qwest, I believe we are 0,32. -- Chris 'Xenon' Hanson | Xenon @ 3D Nature | http://www.3DNature.com/ I set the wheels in motion, turn up all the machines, activate the programs, and run behind the scenes. I set the clouds in motion, turn up light and sound, activate the window, and watch the world go 'round. -Prime Mover, Rush.
ADSL with pppoa (over ATM)
Hi, I read the faq searching for info about pppoa (http://www.openbsd.org/faq/faq6.html) : The main software interface to PPPoE/PPPoA on OpenBSD is pppoe(8), which is a userland implementation (in much the same way that we described ppp(8), above) but I can't figure out how to configure it for a ppp over ATM connection. Anyone can help? I don't want to have a double NAT, one from the adsl modem and one from the OpenBSD gateway... thanks
Re: ADSL with pppoa (over ATM)
Luca Losio wrote: Hi, I read the faq searching for info about pppoa (http://www.openbsd.org/faq/faq6.html) : The main software interface to PPPoE/PPPoA on OpenBSD is pppoe(8), which is a userland implementation (in much the same way that we described ppp(8), above) but I can't figure out how to configure it for a ppp over ATM connection. Anyone can help? I don't want to have a double NAT, one from the adsl modem and one from the OpenBSD gateway... First, what kind of ADSL modem do you have? thanks -- Chris 'Xenon' Hanson | Xenon @ 3D Nature | http://www.3DNature.com/ I set the wheels in motion, turn up all the machines, activate the programs, and run behind the scenes. I set the clouds in motion, turn up light and sound, activate the window, and watch the world go 'round. -Prime Mover, Rush.
Re: ADSL with pppoa (over ATM)
D-link 300T that now it's doing NAT and working with a DHCP server for the internal network
Re: ADSL with pppoa (over ATM)
Half Bridge mode is your friend here. Not sure if the D-Link supports this mode however, Google is less than helpful. Essentially in half bridge mode the modem handles the PPPoA authentication with the ISP, as in NAT mode obtaining an IP address from the remote provider as normal. Unlike NAT mode however the modem then leases out this exact same IP address to the connected ethernet host, thereby presenting the external IP directly to your external ethernet port. Finally the modem begins to transparently bridge the ADSL/Ethernet connections. I can vouch for Zoom X3/4 and ADSL Nation X-Modems working in this mode without issue.
Re: ADSL with pppoa (over ATM)
Has anybody done this through a full bridge? My Actiontech isn't nearly as friendly with it's options... Simon Slaytor wrote: Half Bridge mode is your friend here. Not sure if the D-Link supports this mode however, Google is less than helpful. Essentially in half bridge mode the modem handles the PPPoA authentication with the ISP, as in NAT mode obtaining an IP address from the remote provider as normal. Unlike NAT mode however the modem then leases out this exact same IP address to the connected ethernet host, thereby presenting the external IP directly to your external ethernet port. Finally the modem begins to transparently bridge the ADSL/Ethernet connections. I can vouch for Zoom X3/4 and ADSL Nation X-Modems working in this mode without issue.
Re: ADSL with pppoa (over ATM)
On Tue, Mar 21, 2006 at 08:29:19PM +0100, Luca Losio wrote: D-link 300T that now it's doing NAT and working with a DHCP server for the internal network I used to have one of these. On your external NIC, use DHCP, and that is it. The DLink does the PPPoA stuff and issues the WAN IP address to your DHCP card. You can still telnet to the DLink on 192.168.0.1 at the same time as your link being up.
