The wanpipe card worked great on LRP and when I replaced the kernel with eigerstein. I 
am only switching in an effort to get ipsec running. 

-----Original Message-----
From:   Doug O'Halloran [SMTP:[EMAIL PROTECTED]]
Sent:   Tuesday, November 20, 2001 7:03 AM
To:     [EMAIL PROTECTED]
Subject:        Re: [Leaf-user] wanpipe

Hi Eddie,

To answer your initial question... no, but I have been running one for a
while now (thing just never dies).

I'm not certain if you got the wanpipe to function at all with the LRP
or eigerstein versions.  Actually, I'm not even certain what version I'm
currently running, it's been a while.

But, here's some info from my modules & network.conf that *may* help
you, as well as some info from the wanpipe.conf:

Based on my comments in the code, this was added for a Sangoma S514/ft1
connected to a T1 line & Cisco on the other end.  If memory servers this
was using Sangoma's 2.14beta drivers.  It went up, went live and has
been routing ever since.

# uptime
 06:36:45 up 481 Days (11565h), load average: 0.00 0.00 0.00


/etc/modules wanpipe section:

###Sangoma WANPIPE cards:
wanrouter
sdladrv
wanpipe


/etc/network.conf two sections, one for the configuration, one for the
setup:

#duplicate the 'eth0_*' section for the sangoma
# Sangoma S514/ft1 
chdlc0_....
.
.
.
########################################################################
# Interface activation/deactivation functions
#
########################################################################

if_up () {
.
.
.
        ch*)
                wanconfig -f /etc/wanrouter/wanpipe1.conf
                wanconfig card wanpipe1 dev $1 start
                ip addr add $IPADDR peer $PTPADDR dev $1
                ip link set $1 up
                # Fair queuing - this can be selected for any interface
                ip_frQoS $1
                ;;
.
.
.

/etc/wanconfig/wanpipe.conf
#*****************************************
# Device Definition Section              *
#*****************************************
[devices]
wanpipe1 = WAN_CHDLC, Cisco HDLC
#****************************************
# Network Interfaces Definitions        *
#****************************************
#
[interfaces]
chdlc0 = wanpipe1, ,WANPIPE, PRI port connection (high speed 2Mbps)
#********************************************
# Link configuration section                *
#********************************************
#
#------------------------ WANPIPE 1 

[wanpipe1]
        # ----- Hardware configuration ---------------
S514CPU         = A             # S514 PCI Card CPU: A or B      
PCISlot         = 0             # PCI Slot num: 0 for autodetect 
CommPort        = PRI           # PRI: High speed (2 MBps) primary port
Firmware        = /usr/lib/wanrouter/cdual514.sfm       
        # ----- Physical interface configuration -----
Interface       = V35           # physical interface type, RS232/V35
Clocking        = External      # Tx/Rx clock source, External/Internal
BaudRate        = 1540000       # data transfer rate in bps
        # ----- Media-specific configuration ---------
MTU             = 1500          # maximum data transfer unit, bytes
TTL             = 0x7F          # Time To Live parameter for UDP packets
UDPPORT         = 9000          # UDP Port, used by cpipemon debugger
#*************************************************************
# Logical channel (interface) configuration sections.        *
#*************************************************************
#
[chdlc0]

        # --------- Link Management parameters ---------
MULTICAST       = NO            # Enable Multicasting
IGNORE_DCD      = NO            # Ignore DCD 
IGNORE_CTS      = NO            # Ignore CTS 
IGNORE_KEEPALIVE= NO            # Ignore Keep alives 
HDLC_STREAMING = NO             # Options YES or NO
KEEPALIVE_TX_TIMER   = 10000    # Interval between Keep Alive          
KEEPALIVE_RX_TIMER   = 11000    # Interval to expect Keepalives
KEEPALIVE_ERR_MARGIN = 5        # Consecutive keepalive timeouts       
SLARP_TIMER     = 0             # Used for STATIC IP addressing


Eddie Wilson wrote:
> 
> Has anyone configured Dachstein-CD to use a wanpipe card?
> 
> I started with LRP 2.9.8 then switched to eigerstein kernel to support
> ipsec. I am unable to get ipsec running so I have decided to start from
> scratch with Dachstein-CD.
> 
> I have had no previous problems with wanpipe but I don't get an interface
> using DCD. The drivers seem to load without error messages but no device is
> created.
> 
> Eddie Wilson
> 
> _______________________________________________
> Leaf-user mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/leaf-user

-- 
HTH,
Doug


_______________________________________________
Leaf-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-user

Reply via email to