News: This forum is now permanently frozen.
Pages: [1]
Topic: Soekris/Sangoma T1  (Read 4968 times)
« on: March 30, 2007, 19:55:34 »
pstorkey *
Posts: 2


A couple of years ago, Manuel was selling a couple of Soekris/Sangoma WANPIPE T1 cards with a custom M0n0wall image that included drivers and a web interface for the T1 cards.

http://m0n0.ch/wall/list/showmsg.php?id=206/50

Does anyone know if such an image was ever made publicly available? Or does anyone have any advice on how to add support for these cards to M0n0wall?

Thanks,

Pete
« Reply #1 on: March 31, 2007, 20:46:44 »
cmb *****
Posts: 851

It was never publicly released. Probably because Manuel didn't really know if it worked with a real T1, and didn't want to deal with support issues since it would be difficult for him to support without having access to a real T1. Alternatively, he may not be able to release it due to contract obligations since this was done for a company, though since they never paid up any contract should be null and void.

It'd be nice if Manuel could make it available, even if unsupported and not in any official release. Maybe somebody else would want to pick up on the project and finish it to release quality.
« Reply #2 on: April 01, 2007, 10:18:05 »
Manuel Kasper
Administrator
*****
Posts: 364

Right - it would be a shame to just let this rot on my hard disk.

http://m0n0.ch/wall/downloads-local/net48xx-wanpipe-1.11.img

But please, *no* questions about this anywhere but in this forum thread!

Under "Extensions -> T1 configuration", you'll need to enable the T1 interface, set the desired mode (Cisco HDLC, Frame Relay or PPP) and input the required parameters (depending on the mode). After a reboot, this will then automatically become your WAN interface (WAN -> wagaw0).

It's only been tested with two A101u connected back-to-back, and never on a real T1, so YMMV. Since it is implemented as an extension, it should (at least in theory Wink be relatively easy to port to 1.23 (or even 1.3b); all the WANPIPE drivers would have to be recompiled for the newer FreeBSD release though.

If you give it a try, please let us know if it works...
« Reply #3 on: April 02, 2007, 18:04:51 »
pstorkey *
Posts: 2

Right - it would be a shame to just let this rot on my hard disk.

http://m0n0.ch/wall/downloads-local/net48xx-wanpipe-1.11.img

But please, *no* questions about this anywhere but in this forum thread!

If you give it a try, please let us know if it works...

Thank you very much for this, Manuel! I will test it and let you know how it goes.

Pete
« Reply #4 on: May 29, 2008, 17:06:50 »
dhosh *
Posts: 2

HI, Manuel ....
We just purchased a 4801-60 with the Sangoma A102 card (I tought they only had the A101's, but came with a 102).
On boot-up, I see the wagaw0 interface as the WAN, but it does not show up in the GUI interface uner interfaces, nor at the initial shell where you can assign interfaces.  Neither of those should be a big deal though, if it defaults to being the WAN (at least for our purposes).

The WAN interface shows 'up' in the Status/Interfaces screen, although just above the WAN, in small print, it says something to the effect :  ifconfig: interface wagaw0 not found. 

I have the T1 interface configured, although I don't see where the Frame Relay portion can be disabled, but that portion may be disregarded, depending on how the rest of the screen is set up. 

Any ideas?
Thanks,
Dennis
« Reply #5 on: May 29, 2008, 19:15:23 »
Manuel Kasper
Administrator
*****
Posts: 364

The WAN interface shows 'up' in the Status/Interfaces screen, although just above the WAN, in small print, it says something to the effect :  ifconfig: interface wagaw0 not found. 

Then the WANPIPE driver probably hasn't recognized your card (which doesn't come as a surprise, considering that the drivers and firmware in that special image are now about 3.5 years old). Sorry, but you're probably SOL with that image; it'd have to be updated for new WANPIPE drivers at least (or perhaps better to rip out the WANPIPE m0n0wall "module" from that image and try to make it work with a recent m0n0wall version).
« Reply #6 on: May 29, 2008, 21:36:13 »
dhosh *
Posts: 2

bummer ...I guess we'll see if there's a off -the-shelf OS that'll work with this hardware combo before attempting to re-invent the wheel.  m0n0wall and pfsense, and the Soekris stuff, we're familiar with, though... just not with a T1 card!

...But thanks for the quick response!

Best regards,
Dennis
« Reply #7 on: September 16, 2009, 16:52:01 »
Biggen *
Posts: 8

Any new info on this?

My bandwidth requirements have changed and now I require a T1 to be installed in my facility.  Instead of going the Cisco route, I'd love to continue using my Soekris Net 5501 and M0n0wall.  I was looking at the
Sangoma A101 as a possible integrated CSU/DSU.

Has anyone been successful using M0n0wall with a T1.  M0n0wall was is such a lightweight firewall it seems it would be perfect for digital circuits.
 
Pages: [1]
 
 
Powered by SMF 1.1.20 | SMF © 2013, Simple Machines