Yuri, I strongly suggest you tell the ipcop developers about this! The probably don't read this list.
Good to see you got it working. The other ways would have been to 1. change the code in /home/httpd/cgi-bin/pppsetup.cgi (i think thats where it is); or 2. take a look at /var/ipcop/ppp/settings* /var/ipcop has all sorts of stuff stored there. very handy to know. I have looked around the ipcop settings & internals a bit while debugging various bits, its quite worthwhile. my methods would have required considerable hacking around, yours works great. good unix solution, as volker pointed out. On Sat, 17 Jan 2004 22:42:09+1300 Yuri de Groot <[EMAIL PROTECTED]> wrote: > For those who where following the saga of my modem on my IPCOP box: > > Following Mr Sawtell's suggestion 'dmesg | grep tty': > ttyS04 at port 0xe400 (irq = 10) is a 16550A > > Since /dev/ttyS4 would correspond to COM5 in DOSspeak, and the web > interface to set up the dailer in IPCOP only offers COM1 - COM4, I did > this: > > cd /dev > rm ttyS3 > ln -sf ttyS4 ttyS3 > After that it worked! > > This is a PCI modem with a real UART, not some lousy winmodem. > It cost me $45 (New Zealand Dollars 45NZD = ~25USD AFAIK). > > From /proc/pci: > > Bus 0, device 18, function 0: > Communication controller: Lucent Microelectronics Venus Modem > (V90, > 56KFlex) (rev 0). > IRQ 10. > Master Capable. No bursts. Min Gnt=252.Max Lat=14. > Non-prefetchable 32 bit memory at 0xfedffc00 [0xfedffcff]. > I/O at 0xe400 [0xe4ff]. > I/O at 0xe800 [0xe8ff]. > I/O at 0xecc8 [0xeccf]. > > Now if the stupid web interface allowed me to specify any device eg > '/dev/ttyS4' instead of just a dropdown box with only the four options > COM1 to COM4, I would have had this thing going without so much > wailing and gnashing of teeth. > > Yuri > >
