Forums

Resolved
0 votes
I am planning to install ClearOS on an old Shuttle box in order to protect our home network, which mostly runs on Fedora.

Can anyone make any recommendations for a PCI ADSL internal modem card available in UK? My 8-year old no-name router is about to give up the ghost and I would like to get everything in one box, as well as see what I can do with monitoring data throughput and QOS from ClearOS.

I know this question must get asked quite often, but as I am new to ClearOS (though not Linux) hopefully someone will take pity & answer...

Thanks,
Andrew
Saturday, October 27 2012, 11:46 PM
Share this post:
Responses (24)
  • Accepted Answer

    Sunday, July 19 2015, 09:21 PM - #Permalink
    Resolved
    0 votes
    Well my Danube ADSL card worked pretty well...until it gave up the ghost after about 18 months. This happened just before (as in a few hours) the motherboard on my 10+ year-old Shuttle box also expired...the M/b turned out to be some blown capacitors and after I replaced these it is fine again, but is it possible that the failing capacitors would have caused voltage surges that damaged the PCI card? There is no physical sign of damage, and while the "remote" (from the perspective of the card) Ethernet NIC still shows up, nothing on the card itself responds. I tried powering the card directly and using the RJ-45 connector (I had to hack a FDD power connector to fit the weird 5-pin connector on the card) but still nothing.

    Anyway, I need a new ADSL card and the Danube item still seems to be the only game in town. I looked at the Sangoma S518, as that seems to be the only native PCI ADSL line card and is available 2nd hand on eBay for around the same price as the Danube, but it doesn't support ADSL2/ADSL2+ (G.992.3/4/5) and can't be upgraded (I checked with Sangoma tech. support). There isn't any successor product that I can see, and the S518 dates back to about 2008 I think. I am surprised that no-one who makes the ADSL chipsets used in domestic gateway routers puts one directly on a PCI/PCIe card as they presumably use that interface internally, but there you are.

    Just wondered if anyone had any observations, or any other ideas.

    Andrew
    The reply is currently minimized Show
  • Accepted Answer

    Saturday, November 09 2013, 08:02 PM - #Permalink
    Resolved
    0 votes
    To display pics in-line they must be less than 800x800px - hover over the browse box by the img tag then look above the message box for more info.
    The reply is currently minimized Show
  • Accepted Answer

    Saturday, November 09 2013, 10:02 AM - #Permalink
    Resolved
    0 votes
    Hi Richard,

    I'm not entirely clear about your setup, and especially your use of the term "default gateway" - there can only be one of these, and on a firewall system it is probably best not to try and set this outside the ClearOS config. However I will go by your IP Settings screenshot from an earlier post.

    As I understand it, if you SSH into the ClearOS box you can ping 192.168.0.1, but not from a system on the 192.168.111.0 subnet, which is your internal LAN. In the latter case, is the error message to the effect "destination host unreachable", or is it "no reply from target"? If it says "no reply" that indicates that your ping packets have reached the Danube but the response doesn't know how to get back home.

    If you telnet into 192.168.0.1 from the ClearOS box (the BusyBox shell on the Danube doesn't offer SSH) and run the command route you should see output similar to the following if your earlier static route setup was successful:
    # route
    Kernel IP routing table
    Destination Gateway Genmask Flags Metric Ref Use Iface
    192.168.0.0 * 255.255.255.0 U 0 0 0 br0
    192.168.111.0 192.168.0.2 255.255.255.0 UG 0 0 0 br0

    If you don't see the second entry try adding a static route manually:
    route add -net 192.168.111.0 netmask 255.255.255.0 gw 192.168.0.2

    You should then be able to ping from the 192.168.111.0 subnet. The problem then is that static routes added this way don't survive reboots, and I don't know where in the Danube BusyBox file structure is the file that needs to be edited. However if this lets you ping from the 192.168.111.0 subnet you should also be able to open the web admin screen in a browser from there, and set the static route that way. The web admin takes care of making the static route permanent.

    To be clear, don't think this routing is required either to make the Danube ADSL work properly, or for ClearOS - it is only if you want to access the Danube for management purposes (as opposed to ADSL traffic throughput) from a system on the internal LAN subnet. You would be able to connect via web admin running directly on the box where the Danube is installed, but as ClearOS is nicely locked down you can't do that. One way round this without moving the card to another PC would be to boot the ClearOS box from something like a Fedora Live CD. I am working from memory here...my ClearOS box doesn't have a screen, keyboard or mouse connected any more and is buried under a pile of stuff (just like a firewall should be!) so I can't run through from scratch again.

    Let us know how you get on,
    Andrew

    PS: How did you get your screenshot graphic to display directly in-line your post?
    The reply is currently minimized Show
  • Accepted Answer

    Friday, November 08 2013, 09:56 AM - #Permalink
    Resolved
    0 votes
    Hi Andrew,

    I have changed my configuration slightly I know have the following:

    eth1: Default gateway for my existing PPPOE connection which is already setup

    eth4: New default gateway for the ADSL connection once setup

    ppp0: Existing PPPOE connection which is already in place

    ppp1: ADSL card which I have set to external with a connection type of PPPOE (this was originally showing up as eth2).

    This looks similar to you method although I am not using a bridge. You talk about setting up a dns entry for the Danube remote nic, I cannot see a way of doing this in clear os)?

    When I connect eth1 into a switch connected to my machine I still cannot access the web config page from the main network I am unable to ping 192.168.0.1 or 192.168.0.2 is there something I am missing?

    Kind Regards

    Richard
    The reply is currently minimized Show
  • Accepted Answer

    Friday, November 08 2013, 07:58 AM - #Permalink
    Resolved
    0 votes
    Hi Richard,

    I have a wired Ethernet NIC on the motherboard (eth0) and a USB wireless NIC (wlan0). These are bridged together (br0). The bridge is the interface to the LAN and has a static IP address.

    The ADSL card is set up as ppp0, following the ClearOS guidelines on the website. The ppp0 IP address is assigned by my ISP DHCP, though as I have a fixed IP address it is on a permanent lease. So although the external IP address is always the same, it is not actually a static address in my ClearOS setup.

    The "local" Ethernet NIC on the Danube ADSL card (eth1) also has a static IP address (192.168.0.2). I'm not sure why it doesn't appear in my IP Settings page, though I am quite pleased that it doesn't; it does appear in Bandwidth Viewer though, where it simply reproduces ppp0. eth1 doesn't feature in the firewall config, and is simply a management interface for ADSL config changes (very infrequent) and getting ADSL line stats (I would like to be able to automate data grabs for logging and analysis).

    Screenshot attached (with actual IP addresses redacted).
    [img size=400] http://www.clearfoundation.com/media/kunena/attachments/legacy/images/ClearOS_if.jpeg [/img]

    Regards,
    Andrew
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, November 07 2013, 07:39 PM - #Permalink
    Resolved
    0 votes
    Hi Andrew,

    The adsl card is showing up as eth2 in clear os do I assign the ip 192.168.0.2 to eth2 or do I have to apply the ip to another physical nic in the clear os box? Could you describe your IP setting in your clear os box please.

    KInd Regards

    Richard
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, November 07 2013, 06:00 PM - #Permalink
    Resolved
    0 votes
    Once I am able to connect to the configuration page I will install another NIC which will be for the gateway of the ADSL connection. So I will have one NIC for PPPOE, the ADSL card for the ADSL connection and two NIC's for the Gateways for the ADSL & PPPOE connections hope this makes ense.

    Kind Regards

    Richard
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, November 07 2013, 05:08 PM - #Permalink
    Resolved
    0 votes
    HI, I have plugged the card into a windows box and set a default route with the following:

    target wan: 192.168.111.0 subnet mask: 255.255.255.0 Gateway: 192.168.0.2.

    I have disabled DHCP.

    I have then moved the card to the clear OS box.

    I am a bit confused when you say set local NIC a static IP of 192.168.0.2.

    I currently have two NIC's installed in the box excluding the ADSL card, One card is for the LAN with an IP address of 192.168.111.246 and one NIC set to PPPOE for Internet with an external IP address.

    When the ADSL card is installed in Clear OS it shows up as eth2 do I need to set this to LAN with an IP of 192.168.0.2.

    Kind Regards

    Richard
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, November 07 2013, 01:58 PM - #Permalink
    Resolved
    0 votes
    I also got the Danube card from LinITX, as it seems to be pretty much the only PCI option available, and it works fine. I recall similar problems at first getting in to it. I found that it needs a routing entry on the ADSL card to make it accessible from another subnet.

    First of all, I put the card into a standalone Fedora box so that the local (from the point of view of the Fedora box) NIC gets an IP address from DHCP on the ADSL card; this will usually be 192.168.0.2. Then log in to the Danube web admin page and under Route Configuration - Static Routing set up a route to your "main" LAN subnet via gateway on 192.168.0.2. I then disabled DHCP on the Danube, moved the card into my ClearOS box and assigned the local NIC a static address of 192.168.0.2. I also set up a DNS entry for the Danube "remote" NIC (which I left as 192.168.0.1) and can access using both the web admin page and telnet from anywhere on our LAN.

    I found some very useful info on hacking the Danube card here: http://tjworld.net/wiki/Linux/Embedded/Infineon/Danube/ADSL2PCI. This card is basically a residential gateway ADSL router + a second Ethernet PCI NIC stuck together on a PCI card. The "local" NIC and the LAN-facing NIC on the router are connected physically on the card instead of by a Cat5 cable, but otherwise it is identical to operating an external ADSL modem in full bridge mode apart from the elimination of additional cables and power supplies...which is still a not-inconsiderable advantage. The "firmware" is basically a hacked Linux distro with what looks to be some GPL-violating binary blobs.

    The "ideal" scenario of a native ADSL chipset on a PCI card only seems to be available through options like the Sangoma cards mentioned previously, which seem to be (a) hugely expensive and (b) almost impossible to get hold of.

    Hope this helps,
    Andrew
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, November 07 2013, 01:18 PM - #Permalink
    Resolved
    0 votes
    This is kind of weird. I wonder what is in the routing table and firewall:
    ip route
    iptables -L -n -v
    iptables -t nat -L -n -v
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, November 07 2013, 12:04 AM - #Permalink
    Resolved
    0 votes
    Hi Nick,

    I can set the IP address to 192.168.0.2 (External & LAN) but I cannot ping it from the 192.168.111.0 network. If I SSH into the clear OS box I can ping 192.168.0.1 and 192.168.0.2.

    Kind Regards

    Richard
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, November 06 2013, 09:40 PM - #Permalink
    Resolved
    0 votes
    If 192.168.0.1 is in use can you set it to .2?
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, November 06 2013, 09:00 PM - #Permalink
    Resolved
    0 votes
    Hi Nick,

    When I try and set the IP to 192.168.0.1 it says the IP address is already in use. I didn't get any disks or drivers with the card just a piece of paper describing various jumper settings. When I delved into Linux it was using the 8139too driver you mentioned.

    Kind Regards

    Richard

    Ps Thanks for your continued assistance
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, November 06 2013, 08:48 PM - #Permalink
    Resolved
    0 votes
    Hmm. Guessing, but try giving it an external role with a fixed IP of 192.168.0.1 (it may work with a LAN role like this as well) and forget about the virtual interface.

    FWIW the LinITX ad says Linux source tree available. Have you got it and installed it? It may even come with a readme with instructions. Or it may just the the 8139too driver which is already in ClearOS.
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, November 06 2013, 08:32 PM - #Permalink
    Resolved
    0 votes
    Hi Nick,

    When I installed the card it was detected under the Ethernet section, I have set the interface to external and given it a bogus IP as I haven't connected the adsl line yet as it is currently used and I wanted to configure it all before switching it over as it is in a live environment. But I still am unable to connect to the management interface on 192.168.0.1. I installed the card in a windows box as a test and I was able to connect to the web interface on 192.168.0.1. The only instructions that came with the card talk about jumper settings for PCI mode etc not sure this is relevant though.

    Kind Regards

    Richard
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, November 06 2013, 06:19 PM - #Permalink
    Resolved
    0 votes
    Shouldn't the card be defined as external and not LAN?
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, November 06 2013, 02:03 PM - #Permalink
    Resolved
    0 votes
    Hi Nick,

    I have added the virtual Interface to eth2 and assigned it the IP as shown in the attached screenshot but I still cannot connect to the web configuration or telnet to 192.168.0.1. I can ping 192.168.0.2 but not 192.168.0.1 from the 192.168.11.0 network.

    Kind Regards

    Richard

    http://www.clearfoundation.com/media/kunena/attachments/legacy/images/screenshot-20131106.jpg
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, November 06 2013, 01:31 PM - #Permalink
    Resolved
    0 votes
    From memory the trick is to create a virtual interface on the ADSL connection in the same subnet - say 192.168.0.2 with a subnet mask of 255.255.255.0.
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, November 06 2013, 01:13 PM - #Permalink
    Resolved
    0 votes
    Hi Nick,

    My Subnet is 192.168.111.0/24

    I have one LAN connection already in the box set to 192.168.111.246/24 and one PPPOE connection for the internet. I want to add the ADSL card and a second LAN Card so I can run both a PPPOA & PPPOE connection and utilise the WAN Failover feature. So if the PPPOE fails I can failover to the ADSL connection.

    Kind Regards

    Richard
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, November 06 2013, 12:43 PM - #Permalink
    Resolved
    0 votes
    What is your ClearOS LAN subnet? Is it by any chance 192.168.0.0/24?
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, November 06 2013, 09:23 AM - #Permalink
    Resolved
    0 votes
    Hi Marco,

    I have just purchased this card but I am unable to connect to the management interface on 192.168.0.1 once the card is installed in the Linux clear OS box also I cannot telnet to 192.168.0.1. Clear OS picks up the card and I have the option to assign it as LAN, External etc. but nothing else. I am interested to find out how you managed to get this card working in Clear OS any help would be greatly appreciated.

    Kind Regards

    Richard
    The reply is currently minimized Show
  • Accepted Answer

    Marco
    Marco
    Offline
    Thursday, February 21 2013, 11:16 PM - #Permalink
    Resolved
    0 votes
    Hi Andrew,
    I currently use this pci adsl2+ card : http://linitx.com/product/12181
    I bought this modem one month ago and it's cuuently working very good.
    I hope that this information can help you
    Marco
    The reply is currently minimized Show
  • Accepted Answer

    Farzooma
    Farzooma
    Offline
    Saturday, February 09 2013, 11:42 PM - #Permalink
    Resolved
    0 votes
    You might try the Sangoma S518, its fully supported under Linux.


    Card details link
    http://www.sangoma.com/products/datacom_boards/adsl.html


    PDF file Link

    http://sangoma.com/assets/docs/datasheets/en/s518.pdf
    The reply is currently minimized Show
  • Accepted Answer

    Monday, October 29 2012, 03:08 PM - #Permalink
    Resolved
    0 votes
    Hi Andrew,
    From my experience, although I managed to get this kind of setup going, it would always give me problems in trying to get the right drivers loaded for that particular card. At times I wouldn't even be able to find the drivers. I have since resorted to buying an ADSL modem and configuring it in bridged mode. The ClearOS would then dial out through that modem and this has proved to work for me with little hustle over the years. Maybe you might want to try that.
    The reply is currently minimized Show
Your Reply