Koozali.org: home of the SME Server

Changing the network interface

Offline smer

  • *
  • 12
  • +0/-0
Re: Changing the network interface
« Reply #15 on: January 07, 2008, 08:34:14 AM »
I am willing to help the developers in this. I have several types of USB modems. I have the scripts that will get them to work in CentOS (which SMEServer is based on). I can share the scripts and howtos with the team and do the testing. Please, let me know if the developers are interested in incoporating them.

FYI, I was able to use my speedtouch modem to connect to my ISP in SMEServer but do not know how to manage the rest. To get it to connect I installed the following packages:

linux-atm-2.5.0-0.20050118.2.i386.rpm
linux-atm-libs-2.5.0-0.20050118.2.i386.rpm

and used the following scripts:

Code: [Select]
# /etc/ppp/peers/speedtch
noipdefault
defaultroute
user xxxxx@1024.xxxxx.net
noauth
updetach
usepeerdns
plugin rp-pppoe.so
nas0

### You may need to uncomment these
### options to connect with some ISP's.
### They disable compression.

# noaccomp
# nobsdcomp
# nodeflate
# nopcomp
# noccp
# novj

### If the firmware loads and pppd won't
### connect uncomment this option to make
### pppd be more verbose in the system log

# debug

### For more details (and more options)
### Read man pppd

and

Code: [Select]
#!/bin/bash
#pppoe DSL connection dial file
modprobe ppp_generic
modprobe pppoatm
modprobe br2684
count=0
while [[ $((count++)) -lt 40 ]]
do
  sync=$(dmesg | grep "ADSL line is up" )
  if [ ! -z "$sync" ]
  then
    br2684ctl -b -c 0 -a vci.vpi
    sleep 3
    ifconfig nas0 192.168.2.1 netmask 255.255.255.0 up
    sleep 10
    pppd call speedtch
    exit 0
  fi
  sleep 1
done

I edited pap-secrets and chap-secrets also. I have to do this step everytime I reconfigure the system.

After connecting I got ppp0 in addition to nas0 (192.168.2.1 netmask 255.255.255.0) which was created before dialing.
« Last Edit: January 07, 2008, 08:41:36 AM by smer »

Offline cactus

  • *
  • 4,880
  • +3/-0
    • http://www.snetram.nl
Re: Changing the network interface
« Reply #16 on: January 07, 2008, 09:59:10 AM »
I am willing to help the developers in this. I have several types of USB modems. I have the scripts that will get them to work in CentOS (which SMEServer is based on). I can share the scripts and howtos with the team and do the testing. Please, let me know if the developers are interested in incoporating them.
I doubt if they are willing, but the best way to find out is to add it as a New Feature Request in the bugtracker, perhaps including your scripts as attachements as they are always more willing to implement stuff when they do not need to reinvent the wheel :-)
Be careful whose advice you buy, but be patient with those who supply it. Advice is a form of nostalgia, dispensing it is a way of fishing the past from the disposal, wiping it off, painting over the ugly parts and recycling it for more than its worth ~ Baz Luhrmann - Everybody's Free (To Wear Sunscreen)

Offline imcintyre

  • *
  • 609
  • +0/-0
Re: Changing the network interface
« Reply #17 on: January 07, 2008, 04:08:00 PM »
Perhaps if it is a "contrib" or a how to...

Offline smer

  • *
  • 12
  • +0/-0
Re: Changing the network interface
« Reply #18 on: January 08, 2008, 07:48:08 AM »
I think it will be a useless howto at this stage since the user will be able to connect to ISP but will not be able to use the new interface. I will keep trying to get SMEServer to recognize the new interface, if I succeed, I will provide a complete howto. I hope the developers at least add another list for the interfaces includes: ppp0, ppp1, nas0, nas1, tun0, tun1, tap0 and tap1. These are the interfaces that I know that USB modems use.