Re: [Soekris] New Soekris?
Atom? 2009/1/28 Lars Noodén l...@umich.edu: Sargun Dhillon wrote: ...They aren't going to release any new Geode processors. Does Soekris have a roadmap for new devices over the next 3 years? ... ARM ? -Lars ___ Soekris-tech mailing list Soekris-tech@lists.soekris.com http://lists.soekris.com/mailman/listinfo/soekris-tech -- Adam Retter ___ Soekris-tech mailing list Soekris-tech@lists.soekris.com http://lists.soekris.com/mailman/listinfo/soekris-tech
Re: [Soekris] Traverse Technologies Viking PCI ADSL2+ Card
I had a Traverse Pulsar ADSL PCI card in a net4801 with the standard Soekris net4801 case and the fit was fine. The problem I had was that Traverse whilst claiming to support FreeBSD/OpenBSD originally were never able to produce working/stable drivers. I did interact with their tech support department for some time and they did try and resolve the issues but the drivers had been written by a contractor and we never managed to get a working/stable driver. I see they are only offering Windows/Linux drivers for the Viking and so maybe you will have more luck with that... Thanks Adam. On Thu, Jun 26, 2008 at 10:34 AM, Stuart Henderson [EMAIL PROTECTED] wrote: On 2008-06-26, David Coppa [EMAIL PROTECTED] wrote: I'd like to build a compact ADSL router with some server capabilities (http, smtp) using a net5501-70 and the adsl2 pci card in the subject. Will this card work/fit well? Anyone using It? The size should be ok for the standard case, and it says the right things about voltage. Unfortunately the manual for net5501 isn't available and the details on the website don't mention how much power can be drawn. Even if it did, you'd also need to know the power consumption of other devices (e.g. MiniPCI, hard drive if you have one). PCI Interface: 32 bit PCI Rev 2.2 3.3V or 5V Signalling Universal Keying for 3.3V or 5V PCI Power Supplies: 3.3, 5 12VDC Consumption: 8W (ADSL2+ typical) Physical Dimensions: 138mm * 55mm * 15mm (L*H*W) http://www.traverse.com.au/downloads/adsl/vikingdat_03.pdf The onboard Ethernet controller (RTL8139) makes the modem appear to the O/S as a standard Network card. Thus drivers are not a problem. ___ Soekris-tech mailing list Soekris-tech@lists.soekris.com http://lists.soekris.com/mailman/listinfo/soekris-tech -- Adam Retter Software Pimp Extraordinaire ___ Soekris-tech mailing list Soekris-tech@lists.soekris.com http://lists.soekris.com/mailman/listinfo/soekris-tech
Re: [Soekris] Want to build a router
Hi Stephen, I was in the same situation as you previously a few years ago. I bought a net4801 and have found it more than powerfull enough for my 20mbit internet cable connection, it also has a Wirlesless Atheos card in it and so acts as the WAP as well. Whilst I had previously a good knowledge of Linux and FreeBSD, I decided to go for OpenBSD becuase of its security standpoint, I really believe it is the best option for this application. Otherwise if you want something like Smoothwall, you may want to take a look at M0n0wall, which is based on FreeBSD but uses the same packet filter (Firewall) application as OpenBSD which is very well respected. I am very impresed with both the net4801 and OpenBSD as a combination and would happily recommend it to anyone else, with a bit of Googling it is very easy to get started and get OpenBSD installed on a Soekris. Thanks Adam. On Thu, May 22, 2008 at 9:08 PM, Stephen Brown Jr [EMAIL PROTECTED] wrote: I'm new to this platform, and embedded computing as well and I want to build a router for my home network. Right now I'm using Smoothwall on an old Gateway system. I'd like to stay with that, or maybe try pfsense or possibly roll my own using Debian. I run a small network with about 3-5 machines which includes a webserver, an iMac, two laptops, and another linux desktop. I also have a dedicated switch and WAP. Based on my needs, what would be the best Soekris solution to get? I'm interested in the Net5501 but I feel it might be slightly overkill for what I need and it is a bit pricey Also, are there any guides out there on setting up linux, pfsense, or smoothwall on these devices? tnx Stephen ___ Soekris-tech mailing list Soekris-tech@lists.soekris.com http://lists.soekris.com/mailman/listinfo/soekris-tech -- Adam Retter Software Pimp Extraordinaire ___ Soekris-tech mailing list Soekris-tech@lists.soekris.com http://lists.soekris.com/mailman/listinfo/soekris-tech
Re: [Soekris] PCI ADSL modem.
When I was in talks with Pulsar technical support, they offered to replace my original Pulsar with a ADSL2+ one when they released them, they believed that as it used a Realtek chipset it would already be supported under *BSD - but they could not confirm if this was the case or not at the time. Perhaps I should chase them for that replacement now they have released the ADSL2+ product and see if it works? On Mon, Apr 21, 2008 at 11:38 AM, Magnus Hagdorn [EMAIL PROTECTED] wrote: I use a pulsar ADSL modem with IPCop and a net4801. It works just fine. If I understand their new ADSL 2+ offering it is connected to the host system via a normal ethernet interface. The settings are done via some web interface. So I would have thought it would work with BSD as well. Cheers magnus ___ Soekris-tech mailing list Soekris-tech@lists.soekris.com http://lists.soekris.com/mailman/listinfo/soekris-tech -- Adam Retter Software Pimp Extraordinaire ___ Soekris-tech mailing list Soekris-tech@lists.soekris.com http://lists.soekris.com/mailman/listinfo/soekris-tech
Re: [Soekris] PCI ADSL modem.
I bought a Traverse Pulsar ADSL PCI card my my net4801, but never managed to get it working. I emailed Traverse before buying it and the promised FreeBSD and OpenBSD support, whilst some drivers did appear they were very unstable, I had some back and forth with technical support but they never managed to resolve it - the drivers were originally developed by a contractor I believe who was no longer with them. Whilst they did try and I appreciate that, it never really was enough. Taking a look at their website, it seems to be that their are no updates to their drivers since I last tried - 2005. I see also that they have a new PCI ADSL2+ card out and that they are NOT offering FreeBSD/OpenBSD drivers for this. I do not know of any other ADSL cards that are supported under OpenBSD, it seems a glaring omission to me. Thanks Adam. On Fri, Apr 18, 2008 at 8:33 AM, Andrew Back [EMAIL PROTECTED] wrote: Hello, I'm considering replacing a Net4521 OpenBSD firewall + D-Link DSL router with a Net5501 running OpenBSD as both router and firewall. Does anyone have any experience of using PCI or miniPCI ADSL cards in a Soekris device and ideally running OpenBSD? And being in the UK I'd be using PPPoA. Regards, Andrew --- Andrew Back MIEEE MBCS CITP Open Source Strategist Osmosoft - open source from BT E: [EMAIL PROTECTED] T: 07795 987822 http://www.osmosoft.com ___ Soekris-tech mailing list Soekris-tech@lists.soekris.com http://lists.soekris.com/mailman/listinfo/soekris-tech -- Adam Retter Software Pimp Extraordinaire ___ Soekris-tech mailing list Soekris-tech@lists.soekris.com http://lists.soekris.com/mailman/listinfo/soekris-tech
Re: [Soekris] PCI ADSL modem.
Hmmm. I thought earlier I remembered Sangoma doing BSD drivers for their ADSL products, but that they were hideously expensive (2005) but when I checked this page (earlier before replying) http://wiki.sangoma.com/wanpipe-freebsd-drivers right at the bottom it seems to say that the S518 is not supported?!? On Fri, Apr 18, 2008 at 2:30 PM, RB [EMAIL PROTECTED] wrote: any experience of using PCI or miniPCI ADSL cards in a Soekris device and ideally running OpenBSD? And being in the UK I'd be using PPPoA. The only PCI ADSL modem I know of that directly supports non-Windows hosts is the Sangoma S518 - ironic that a Google search for 'minipci adsl' gives its first result as a posting on this list from 2003, discussing much the same thing. What I don't know is whether it'll play nicely with the 3.3v signalling on the 5501 - they say they support 3.3v, but on a 64-bit interface. Looks like the Wanpipe drivers are provided for both Linux and FreeBSD, so if they don't compile on OpenBSD chances are it wouldn't be an extremely difficult port. ___ Soekris-tech mailing list Soekris-tech@lists.soekris.com http://lists.soekris.com/mailman/listinfo/soekris-tech -- Adam Retter Software Pimp Extraordinaire ___ Soekris-tech mailing list Soekris-tech@lists.soekris.com http://lists.soekris.com/mailman/listinfo/soekris-tech
Re: [Soekris] Needing some MiniPCI Wireless Advices
I simply bought an Atheros one that was supported by the ath0 driver in OpenBSD from eBay - which meant I got it very cheap it does a/b/g and im quite happy with it :-p I would suggest checking the supported wireless chipsets list for the OS you want to use and then getting onto eBay. Cheers Adam. On Fri, Feb 22, 2008 at 4:28 PM, nicodache [EMAIL PROTECTED] wrote: I know that Atheros-based card works well under linux, and I think it's the same under BSD. Now, just have to find one... I know that gigabyte make some, but I don't know if you can get one in brazil. Cheers On Fri, Feb 22, 2008 at 1:03 PM, mundoalem [EMAIL PROTECTED] wrote: Hello everyone, I am building my own AccessPoint based based on soekris boards and Linux, I was thinking about buying one of the MiniPCI cards offered at this site. (Look, I don't wanna make advertising or anything). http://metrix.net/nl2511mp-200mw-minipci-p-8.html However I could not get in touch with the people at this store. I am from Brazil and here it is really difficult to find good stores that sell products which are not only for Windows. So I was hoping that my importer which stays in USA could get in touch with Metrix guys. This was not possible, I don't know why they haven't responded our mails. Alright, this was just an introduction to my problem. What I really want to know is if you guys could give some advices on MiniPCI Wireless Cards that: 1) Has supoort under Linux and OpenBSD (I know some like Orinoco, but they are rare) and b/g or a/b/g protocols. 2) Works fine indoor behind walls, etc. 3) Has a reseller which I could contact (even if it is outside my country). Url's to websites would be welcome! I was wondering if this could be the place to ask such questions, please just ignore my mail if you find that I am being rude, spammer, or just if I am asking the wrong question in the wrong place. It is not my point to offend or to disrespect the mail list rules. I know where/what to buy questions sometimes is a pain in the ass. I just don't know where else to ask and google hasn't come with good alternatives to me. So thank you very much for your time. Egon ___ Soekris-tech mailing list Soekris-tech@lists.soekris.com http://lists.soekris.com/mailman/listinfo/soekris-tech ___ Soekris-tech mailing list Soekris-tech@lists.soekris.com http://lists.soekris.com/mailman/listinfo/soekris-tech -- Adam Retter Software Pimp Extraordinaire ___ Soekris-tech mailing list Soekris-tech@lists.soekris.com http://lists.soekris.com/mailman/listinfo/soekris-tech
Re: [Soekris] net4801 problem pxeboot'ing OpenBSD 4.2 from FreeBSD 6.3
Erm sorry im a bit confused now! Where does NFS come into this? If I understand the process then pxeboot is sent by TFTP which then request bsd.rd from the same TFTP source and then bootstraps bsd.rd once it is downloaded... Or am I missing something? pretty sure NFS is not involved. On Thu, Feb 21, 2008 at 1:47 PM, Bernd Walter [EMAIL PROTECTED] wrote: On Wed, Feb 20, 2008 at 11:30:30PM +, Adam Retter wrote: On Wed, Feb 20, 2008 at 11:18 PM, Stuart Henderson [EMAIL PROTECTED] wrote: On 2008/02/20 23:08, Adam Retter wrote: The console output over COM0 from the net4801 is below, but basically I have no idea what Unknown error: code 60 (from pxeboot?) means? 60 is ETIMEDOUT, according to OpenBSD's intro(2). iirc the normal OS error codes are used in the boot loader. are you aware of any network problems, bad cables or duplex mismatch maybe? Erm nope im not aware of any problems, the cables are all new and work for network traffic otherwise. The net4801 is connected to a Netgear 8-port 10/100/1000Mbit switch and the FreeBSD machine is also connected to the switch. Using the same physical setup with its current OpenBSD 3.7 operating system, I am able to SSH into the net4801 and browse the web etc (its used as a F/W and Router). Hmm, anything I can do to find out why its timing out? You already tftp'ed the loader and just NFS is failing, so you have to search for NFS related problems. Is is correct that your nfs path is named tftp:/bsd ? I don't know if the OpenBSD loader can handle DNS requests, so you might want to try with an IP address as well. -- B.Walterhttp://www.bwct.de http://www.fizon.de [EMAIL PROTECTED] [EMAIL PROTECTED][EMAIL PROTECTED] -- Adam Retter Software Pimp Extraordinaire ___ Soekris-tech mailing list Soekris-tech@lists.soekris.com http://lists.soekris.com/mailman/listinfo/soekris-tech
Re: [Soekris] net4801 problem pxeboot'ing OpenBSD 4.2 from FreeBSD 6.3
Bill, Thanks very very much :-) All it needed was the next-server option, then it booted up perfectly - im now sending this via. my new OpenBSD 4.2 net4801 router/firewall. I guess something must have changed on either the OpenBSD or FreeBSD side, I think FreeBSD switched to isc-dhcpd-3 and im not sure whether the dhcpd of pxeboot in OpenBSD has changed, but I know that I didnt used to have to use next-server to get it to work. Thanks again. Im overjoyed :-) On Thu, Feb 21, 2008 at 3:00 PM, Bill Maas [EMAIL PROTECTED] wrote: Hi Adam, [apologies for off-list reply, Reply To All is only a Shift away here] On Thu, 2008-02-21 at 10:51 +, Adam Retter wrote: On Thu, Feb 21, 2008 at 9:28 AM, Bill Maas [EMAIL PROTECTED] wrote: Hi Adam, On Wed, 2008-02-20 at 23:08 +, Adam Retter wrote: [...] CLIENT MAC ADDR: 00 00 24 C4 2C 6C CLIENT IP: 172.16.16.252 MASK: 255.255.255.240 DHCP IP: 172.16.16.245 GATEWAY IP: 172.16.16.254 172.16.16.245 172.16.16.254 No this is correct, my router (imaginary, as it will be my net4801 eventually) is on 172.16.16.254 and the FreeBSD machine issuing the DHCP lease is on 172.16.16.245 Maybe the first IP is what you meant, but it might as well indicate a typo in the next-server field in dhcpd.conf(!). not sure i have a next-server field in my dhcpd.conf, I am at work at the moment and will check this when I get home... probing: pc0 com0 com1 pci pxe![2.1] mem[639K 127M a20=on] disk: hd0+ net: mac 00:00:24:c4:2c:6c, ip 172.16.16.252, server 0.0.0.0 I would expect a local IP here for server. This would match next-server in dhcpd.conf on OpenBSD. Apparantly downloading the boot loader succeeds (as if next-server doesn't apply yet), but the boot loader apparently fails to get the TFTP server's correct address. Ah so next-server could definitely be the culprit if I am missing it, will take a look tonight. Thanks very much for your help so far :-) No, I was being overly imaginative and suspicious about default program behaviour. The two IPs just looked suspiciously similar to me. The messages for trivial errors are in fact quite clear (just generated a few): Wrong next-server (PXE ROM): PXE-E11: ARP timeout PXE-E11: ARP timeout PXE-E38: TFTP cannot open connection PXE-M0F: Exiting BootManage PXE ROM. Unreadable bsd.rd (pxeboot): booting tftp:/bsd.rd: open tftp:/bsd.rd: Operation not permitted failed(1). will try /bsd boot booting tftp:/bsd: open tftp:/bsd: No such file or directory failed(2). will try /bsd Turning timeout off. Without a next-server the DHCP IP will be used as it should, but in my output I do see it after the server keyword, and not 0.0.0.0 (which might indicate ARP trouble, and many error code 60 reports are about ARP). But the ARP/next-server theory doesn't hold as well, since pxeboot can (a) determine bsd.rd's size, and (b) determine that bsd isn't there. It doesn't look like there is a trivial answer here. Bill I'm not sure about this, I didn't write dhcpd or pxeboot;), but it looks to me as if that's what's to be happening here. Bill OpenBSD/i386 PXEBOOT 2.02 booting tftp:bsd.rd: | booting tftp:bsd.rd: 4733076read text: Unknown error: code 60 failed(60). will try /bsd boot booting tftp:/bsd: open tftp:/bsd: No such file or directory failed(2). will try /bsd Turning timeout off. boot ___ Soekris-tech mailing list Soekris-tech@lists.soekris.com http://lists.soekris.com/mailman/listinfo/soekris-tech -- What's a computer? - MES -- What's a computer? - MES ___ Soekris-tech mailing list Soekris-tech@lists.soekris.com http://lists.soekris.com/mailman/listinfo/soekris-tech -- Adam Retter Software Pimp Extraordinaire ___ Soekris-tech mailing list Soekris-tech@lists.soekris.com http://lists.soekris.com/mailman/listinfo/soekris-tech
[Soekris] net4801 problem pxeboot'ing OpenBSD 4.2 from FreeBSD 6.3
Right, this is driving me absolutely nuts! I have had a Soekris net4801 (266Mhz model) for some time now, a couple of years ago I very easily used PXE to install Open BSD 3.7 on it from FreeBSD 5 (or maybe 6, I forget), anyways I documented the whole process at the time and decided today to update my net4801 to the latest OpenBSD (4.2). I cant for the life of me get the net4801 to boot OpenBSD 4.2 using PXE. My host machine is a FreeBSD 6.3-STABLE with the ISC DHCPD version 3 port installed, I have setup dhcpd and tftpd, in /tftpboot on my FreeBSD machine I have bsd.rd and pxeboot from OpenBSD 4.2. The console output over COM0 from the net4801 is below, but basically I have no idea what Unknown error: code 60 (from pxeboot?) means? I then also updated the net4801 bios to 1.31 and tried again, but it made no difference. Im sure this should be really easy (as it was the first time), what am I doing wrong here please? comBIOS ver. 1.28 20050529 Copyright (C) 2000-2005 Soekris Engineering. net4801 0128 Mbyte MemoryCPU Geode 266 Mhz Pri Sla SAMSUNG CF/ATA LBA Xlt 1012-32-63 1020 Mbyte Slot Vend Dev ClassRev Cmd Stat CL LT HT Base1Base2 Int --- 0:00:0 1078 0001 0600 0107 0280 00 00 00 0:06:0 100B 0020 0200 0107 0290 00 3F 00 E101 A000 10 0:07:0 100B 0020 0200 0107 0290 00 3F 00 E201 A0001000 10 0:08:0 100B 0020 0200 0107 0290 00 3F 00 E301 A0002000 10 0:18:2 100B 0502 01018001 0005 0280 00 00 00 0:19:0 0E11 A0F8 0C031008 0117 0280 08 38 00 A0003000 11 5 Seconds to automatic boot. Press Ctrl-P for entering Monitor. comBIOS Monitor. Press ? for help. boot F0 NSC DP83815/DP83816 Fast Ethernet UNDI, v1.03 Copyright (C) 2002, 2003 National Semiconductor Corporation All rights reserved. Pre-boot eXecution Environment PXE-2.0 (build 082) Copyright (C) 1997-2000 Intel Corporation CLIENT MAC ADDR: 00 00 24 C4 2C 6C CLIENT IP: 172.16.16.252 MASK: 255.255.255.240 DHCP IP: 172.16.16.245 GATEWAY IP: 172.16.16.254 probing: pc0 com0 com1 pci pxe![2.1] mem[639K 127M a20=on] disk: hd0+ net: mac 00:00:24:c4:2c:6c, ip 172.16.16.252, server 0.0.0.0 OpenBSD/i386 PXEBOOT 2.02 switching console to com0 OpenBSD/i386 PXEBOOT 2.02 booting tftp:bsd.rd: | booting tftp:bsd.rd: 4733076read text: Unknown error: code 60 failed(60). will try /bsd boot booting tftp:/bsd: open tftp:/bsd: No such file or directory failed(2). will try /bsd Turning timeout off. boot ___ Soekris-tech mailing list Soekris-tech@lists.soekris.com http://lists.soekris.com/mailman/listinfo/soekris-tech
Re: [Soekris] net4801 problem pxeboot'ing OpenBSD 4.2 from FreeBSD 6.3
On Wed, Feb 20, 2008 at 11:18 PM, Stuart Henderson [EMAIL PROTECTED] wrote: On 2008/02/20 23:08, Adam Retter wrote: The console output over COM0 from the net4801 is below, but basically I have no idea what Unknown error: code 60 (from pxeboot?) means? 60 is ETIMEDOUT, according to OpenBSD's intro(2). iirc the normal OS error codes are used in the boot loader. are you aware of any network problems, bad cables or duplex mismatch maybe? Erm nope im not aware of any problems, the cables are all new and work for network traffic otherwise. The net4801 is connected to a Netgear 8-port 10/100/1000Mbit switch and the FreeBSD machine is also connected to the switch. Using the same physical setup with its current OpenBSD 3.7 operating system, I am able to SSH into the net4801 and browse the web etc (its used as a F/W and Router). Hmm, anything I can do to find out why its timing out? -- Adam Retter Software Pimp Extraordinaire ___ Soekris-tech mailing list Soekris-tech@lists.soekris.com http://lists.soekris.com/mailman/listinfo/soekris-tech
