Re: [Leaf-user] wanpipe
Perplexing... So, it appears the modules are loading ok in both instances. >From Michael's quote of 'Starting all WANPIPE devices:', one can narrow his down to the wanpipe.lrp from Sangoma, as the one from LRP 2.9.8 has a different start message. One thing I noticed in the Dachstein-CD changelog was the moving of ifconfig from a few packages into it's own separate one. Check and see if it still exists in /sbin. If not, you'll have to add it to your syslinux.cfg or lrpkg.cfg? file as wanrouter depends on it. One would suspect that there'd be some sort of message in syslog though. As well, check under /proc/net/wanrouter for any files & cat them for any clues. You might also want to peruse ftp://ftp.sangoma.com/linux/ and try to identify the exact version of the modules you're running, it could be that newer ones would help. HTH, Doug. Eddie Wilson wrote: > > My log appears much the same. > > wanpipe: Probing for WANPIPE hardware > wanpipe: S508-ISA card found, port 0x360 > wanpipe: Allocating maximum 2 devices: wanpipe1 - wanpipe2 > > Looks normal but no interface exists. > > -Original Message- > From: Michael D. Schleif [SMTP:[EMAIL PROTECTED]] > Sent: Monday, November 26, 2001 12:03 AM > To: Doug O'Halloran > Cc: [EMAIL PROTECTED]; '[EMAIL PROTECTED]' > Subject:Re: [Leaf-user] wanpipe > <...snip...> > In my case, syslogd messages show that the four (4) .O files from > Sangoma's wanpipe.lrp are functioning and without error. There is *no* > ominous statement like your example. > > For me, the most startling indicator is this: > > Starting all WANPIPE devices: > > When I review /usr/sbin/wanrouter, case start), I cannot see any > condition under which *NOTHIING* more is echo'd than this line, unless > there is *NO* file in /etc/wanpipe/ ;< > > Nevertheless, that line is all that I see, then starting the eth0 > interface. Sometimes, depending on which errant configuration > permutation I use, I will get three of these: > > Cannot find device "wanpipe1" > > Or, this: > > Error: an inet prefix is expected rather than "dev". > > Any ideas? > > > "Michael D. Schleif" wrote: > > > > > > Any luck on this? > > > > > > I've spent much of the last two days trying to get this to work -- > > > without success ;< > > > > > > As Eddie said, everything appears to work, except there is *no* > > > interface . . . > > > > > > 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. > > -- > > Best Regards, > > mds > mds resource > 888.250.3987 > > Dare to fix things before they break . . . > > Our capacity for understanding is inversely proportional to how much we > think we know. The more I know, the more I know I don't know . . . > > ___ > Leaf-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/leaf-user ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
RE: [Leaf-user] wanpipe
My log appears much the same. wanpipe: Probing for WANPIPE hardware wanpipe: S508-ISA card found, port 0x360 wanpipe: Allocating maximum 2 devices: wanpipe1 - wanpipe2 Looks normal but no interface exists. -Original Message- From: Michael D. Schleif [SMTP:[EMAIL PROTECTED]] Sent: Monday, November 26, 2001 12:03 AM To: Doug O'Halloran Cc: [EMAIL PROTECTED]; '[EMAIL PROTECTED]' Subject: Re: [Leaf-user] wanpipe Doug O'Halloran wrote: > > When you say 'everything appears to work', what do you mean? > > Does dmesg or tailing /var/log/messages say anything about your card? > Anything like: "Damn... Adapter won't start!" <- from latest sdladrv.c > > When it was working under LRP 2.9.8, were you loading a wanpipe.lrp in > syslinux.cfg? If you just changed your kernel to Eigerstein, and it > still worked, maybe your old version had some of the config tools > already installed. From perusing the Dachstein-CD, it doesn't appear to > be there. > > Again, it's been a while since I played with one, but a little bit more > detail would be helpful. In my case, syslogd messages show that the four (4) .O files from Sangoma's wanpipe.lrp are functioning and without error. There is *no* ominous statement like your example. For me, the most startling indicator is this: Starting all WANPIPE devices: When I review /usr/sbin/wanrouter, case start), I cannot see any condition under which *NOTHIING* more is echo'd than this line, unless there is *NO* file in /etc/wanpipe/ ;< Nevertheless, that line is all that I see, then starting the eth0 interface. Sometimes, depending on which errant configuration permutation I use, I will get three of these: Cannot find device "wanpipe1" Or, this: Error: an inet prefix is expected rather than "dev". Any ideas? > "Michael D. Schleif" wrote: > > > > Any luck on this? > > > > I've spent much of the last two days trying to get this to work -- > > without success ;< > > > > As Eddie said, everything appears to work, except there is *no* > > interface . . . > > > > 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. -- Best Regards, mds mds resource 888.250.3987 Dare to fix things before they break . . . Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
Re: [Leaf-user] wanpipe
Doug O'Halloran wrote: > > When you say 'everything appears to work', what do you mean? > > Does dmesg or tailing /var/log/messages say anything about your card? > Anything like: "Damn... Adapter won't start!" <- from latest sdladrv.c > > When it was working under LRP 2.9.8, were you loading a wanpipe.lrp in > syslinux.cfg? If you just changed your kernel to Eigerstein, and it > still worked, maybe your old version had some of the config tools > already installed. From perusing the Dachstein-CD, it doesn't appear to > be there. > > Again, it's been a while since I played with one, but a little bit more > detail would be helpful. In my case, syslogd messages show that the four (4) .O files from Sangoma's wanpipe.lrp are functioning and without error. There is *no* ominous statement like your example. For me, the most startling indicator is this: Starting all WANPIPE devices: When I review /usr/sbin/wanrouter, case start), I cannot see any condition under which *NOTHIING* more is echo'd than this line, unless there is *NO* file in /etc/wanpipe/ ;< Nevertheless, that line is all that I see, then starting the eth0 interface. Sometimes, depending on which errant configuration permutation I use, I will get three of these: Cannot find device "wanpipe1" Or, this: Error: an inet prefix is expected rather than "dev". Any ideas? > "Michael D. Schleif" wrote: > > > > Any luck on this? > > > > I've spent much of the last two days trying to get this to work -- > > without success ;< > > > > As Eddie said, everything appears to work, except there is *no* > > interface . . . > > > > 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. -- Best Regards, mds mds resource 888.250.3987 Dare to fix things before they break . . . Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
Re: [Leaf-user] wanpipe
Eddie, When you say 'everything appears to work', what do you mean? Does dmesg or tailing /var/log/messages say anything about your card? Anything like: "Damn... Adapter won't start!" <- from latest sdladrv.c When it was working under LRP 2.9.8, were you loading a wanpipe.lrp in syslinux.cfg? If you just changed your kernel to Eigerstein, and it still worked, maybe your old version had some of the config tools already installed. From perusing the Dachstein-CD, it doesn't appear to be there. Again, it's been a while since I played with one, but a little bit more detail would be helpful. Doug. "Michael D. Schleif" wrote: > > Any luck on this? > > I've spent much of the last two days trying to get this to work -- > without success ;< > > As Eddie said, everything appears to work, except there is *no* > interface . . . > > 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. > > -- > > Best Regards, > > mds > mds resource > 888.250.3987 > > Dare to fix things before they break . . . > > Our capacity for understanding is inversely proportional to how much we > think we know. The more I know, the more I know I don't know . . . > > ___ > Leaf-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/leaf-user ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
Re: [Leaf-user] wanpipe
Any luck on this? I've spent much of the last two days trying to get this to work -- without success ;< As Eddie said, everything appears to work, except there is *no* interface . . . 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. -- Best Regards, mds mds resource 888.250.3987 Dare to fix things before they break . . . Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
RE: [Leaf-user] wanpipe
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= 154 # 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 = 1# 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
[Leaf-user] wanpipe
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
