Hi,
A draft howto follows. It'll be useful for people to post questions/suggestions etc. here.
The howto assumes you have read the ibdriver readme file, in particular about how to compile the driver:
The Suse documentation wiki/project would seem to be a natural place to post a version that has most wrinkles ironed out. this would likely increase the awareness of the ib driver....
For Suse 10.2 using 'NetworkManager'
1) make; make install
2) Create the file (note the file extension)
/etc/modprobe.d/iburst.modeprobe
options ib-net ifname="eth%d" debug=9
NOTE:
Hard coding an ethN does not seem to be possible. It appears that SUSE/NetworkManager 'fallsback' to some routine that continually increments the eth counter each time it is inserted - even after a reboot...
Such behavior can indicate trouble with the confige file above?
3) Start a console as 'su' to monitor activity
tail -f /var/log/messages
4) plug and unplug (or vice versa) the iburst PCMCIA card
5) In the console from step three you should see something like:
Dec 22 10:31:23 mv-laptop ifup: Network interface is managed from NetworkManager
Dec 22 10:31:23 mv-laptop ifup: NetworkManager will be advised to set up eth2
Dec 22 10:31:23 mv-laptop ifup: but it cannot be assured from here.
NOTE 1:
eth2 is the key piece of information. On your system it may be eth0, or eth4, etc.
From now on we'll refer to this as ethN. You should substitute appropriately.
NOTE 2:
If your configuration file is not quite correct SUSE's NetworkManager will keep incrementing the eth counter each time you remove and insert the iburst card. To check that things are 'good to continue' remove and insert the card a few times and confirm that you keep getting the same ethN value in the messages screen. Also, bear in mind we will 'hardcode' this ethN value in a couple of files so you want to make sure that this is the ethernet scenario you will most frequently encounter. It appears possible to setup several ethN and DSLN configuration files if you have more than one useage scenario - but I have not done this so this is just conjecture.
4) cp /etc/sysconfig/network/ifcfg.template /etc/sysconfig/network/ifcfg-ethN
Edit the following entries:
STARTMODE=hotplug
IPADDR='10.0.99.1' # This is important
NETMASK='255.255.255.0'
MTU='1492' # Some suggests 1352 to ensure reliable service - seems to be ISP/environment dependent?
NAME='iBurst User Terminal'
USERCONTROL='yes'
NOTE:
If you use YaST to edit the above file (as of SUSE 10.2):
* Network address setup screen:
- you must assign the ethN some static IP address and netmask 255.255.255.0.
* Hostname and server screen:
- Change host name via dhcp
- write hostname to /etc/hosts
- "hostname" and "domain name" feilds can be what you like
* Routing
- leave all empty
* Advanced... hardware details
- leave all empty (ethN will be a feild you can't change)
* Advanced... DHCP options
- Request broadcast reposnse
- DHCP client identifier is empty
- Hostname to send is 'AUTO'
* Advanced... additional addresses is not available using NetworkManager
* Advanced... IPv6
- enabled
5. Open YaST from the SuSE menu in KDE and select Network Devices->Network Card to confirm the iBurst card appears in the configuration.
6. From within YaST select Network Devices->DSL and configure the ethN interface corresponding to the iBurst card as DSL service (you will need your username@realm and password to configure the provider).
- this will create a dslN interface, N maybe 0 or 1, etc. and does not have to be the same as ethN
- YaSt will also prompt you to create a ISP provider configuration, named.... providerN (not the same N as before)
7. Using KNetworkManager, (right click the network icon in the system tray), select:
Dial up connections >> Connect to <Provider name> via DSL (dsl0)
8. If the messages console launched in step 3 you should see something like:
22 17:38:25 mv-laptop ifup: dsl0
Dec 22 17:38:25 mv-laptop ifup-ppp: interface dsl0 is up
Dec 22 17:38:25 mv-laptop pppd[11305]: Plugin rp-pppoe.so loaded.
Dec 22 17:38:25 mv-laptop pppd[11305]: RP-PPPoE plugin version 3.3 compiled against pppd 2.4.4
Dec 22 17:38:25 mv-laptop pppd[11305]: Plugin passwordfd.so loaded.
Dec 22 17:38:25 mv-laptop pppd[11305]: pppd 2.4.4 started by root, uid 0
Dec 22 17:38:25 mv-laptop pppd[11305]: Interface eth2 has MTU of 1352 -- should be 1500. You may have serious connection problems.
Dec 22 17:38:25 mv-laptop pppd[11305]: PPP session is 8
Dec 22 17:38:25 mv-laptop kernel: ppp0 renamed to dsl0
Dec 22 17:38:25 mv-laptop pppd[11305]: Renamed interface ppp0 to dsl0
Dec 22 17:38:25 mv-laptop pppd[11305]: Using interface dsl0
Dec 22 17:38:25 mv-laptop pppd[11305]: Connect: dsl0 <--> eth2
Dec 22 17:38:25 mv-laptop rename_netiface: oldname ppp0 does not exist
Dec 22 17:38:26 mv-laptop pppd[11305]: CHAP authentication succeeded: CHAP authentication success, unit 1171
Dec 22 17:38:26 mv-laptop pppd[11305]: CHAP authentication succeeded
Dec 22 17:38:26 mv-laptop pppd[11305]: peer from calling number 02:C0:EE:05:0A:93 authorized
Dec 22 17:38:27 mv-laptop pppd[11305]: local IP address 124.109.64.213
Dec 22 17:38:27 mv-laptop pppd[11305]: remote IP address 124.109.64.1
Dec 22 17:38:27 mv-laptop pppd[11305]: primary DNS address 203.98.90.25
Dec 22 17:38:27 mv-laptop pppd[11305]: secondary DNS address 203.98.90.27
Dec 22 17:38:27 mv-laptop modify_resolvconf: Service pppd modified /etc/resolv.conf. See info block in this file
Step 4) .... NOTE: before you remove the iburst card, or at least before you re-insert it, you should run: ifdown ethN
Where ethN is the interface name you noted when the card was _first_ inserted.
Step 6.1) Run: ifup ethN
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
A draft howto follows. It'll be useful for people to post questions/suggestions etc. here.
The howto assumes you have read the ibdriver readme file, in particular about how to compile the driver:
The Suse documentation wiki/project would seem to be a natural place to post a version that has most wrinkles ironed out. this would likely increase the awareness of the ib driver....
For Suse 10.2 using 'NetworkManager'
1) make; make install
2) Create the file (note the file extension)
/etc/modprobe.d/iburst.modeprobe
options ib-net ifname="eth%d" debug=9
NOTE:
Hard coding an ethN does not seem to be possible. It appears that SUSE/NetworkManager 'fallsback' to some routine that continually increments the eth counter each time it is inserted - even after a reboot...
Such behavior can indicate trouble with the confige file above?
3) Start a console as 'su' to monitor activity
tail -f /var/log/messages
4) plug and unplug (or vice versa) the iburst PCMCIA card
5) In the console from step three you should see something like:
Dec 22 10:31:23 mv-laptop ifup: Network interface is managed from NetworkManager
Dec 22 10:31:23 mv-laptop ifup: NetworkManager will be advised to set up eth2
Dec 22 10:31:23 mv-laptop ifup: but it cannot be assured from here.
NOTE 1:
eth2 is the key piece of information. On your system it may be eth0, or eth4, etc.
From now on we'll refer to this as ethN. You should substitute appropriately.
NOTE 2:
If your configuration file is not quite correct SUSE's NetworkManager will keep incrementing the eth counter each time you remove and insert the iburst card. To check that things are 'good to continue' remove and insert the card a few times and confirm that you keep getting the same ethN value in the messages screen. Also, bear in mind we will 'hardcode' this ethN value in a couple of files so you want to make sure that this is the ethernet scenario you will most frequently encounter. It appears possible to setup several ethN and DSLN configuration files if you have more than one useage scenario - but I have not done this so this is just conjecture.
4) cp /etc/sysconfig/network/ifcfg.template /etc/sysconfig/network/ifcfg-ethN
Edit the following entries:
STARTMODE=hotplug
IPADDR='10.0.99.1' # This is important
NETMASK='255.255.255.0'
MTU='1492' # Some suggests 1352 to ensure reliable service - seems to be ISP/environment dependent?
NAME='iBurst User Terminal'
USERCONTROL='yes'
NOTE:
If you use YaST to edit the above file (as of SUSE 10.2):
* Network address setup screen:
- you must assign the ethN some static IP address and netmask 255.255.255.0.
* Hostname and server screen:
- Change host name via dhcp
- write hostname to /etc/hosts
- "hostname" and "domain name" feilds can be what you like
* Routing
- leave all empty
* Advanced... hardware details
- leave all empty (ethN will be a feild you can't change)
* Advanced... DHCP options
- Request broadcast reposnse
- DHCP client identifier is empty
- Hostname to send is 'AUTO'
* Advanced... additional addresses is not available using NetworkManager
* Advanced... IPv6
- enabled
5. Open YaST from the SuSE menu in KDE and select Network Devices->Network Card to confirm the iBurst card appears in the configuration.
6. From within YaST select Network Devices->DSL and configure the ethN interface corresponding to the iBurst card as DSL service (you will need your username@realm and password to configure the provider).
- this will create a dslN interface, N maybe 0 or 1, etc. and does not have to be the same as ethN
- YaSt will also prompt you to create a ISP provider configuration, named.... providerN (not the same N as before)
7. Using KNetworkManager, (right click the network icon in the system tray), select:
Dial up connections >> Connect to <Provider name> via DSL (dsl0)
8. If the messages console launched in step 3 you should see something like:
22 17:38:25 mv-laptop ifup: dsl0
Dec 22 17:38:25 mv-laptop ifup-ppp: interface dsl0 is up
Dec 22 17:38:25 mv-laptop pppd[11305]: Plugin rp-pppoe.so loaded.
Dec 22 17:38:25 mv-laptop pppd[11305]: RP-PPPoE plugin version 3.3 compiled against pppd 2.4.4
Dec 22 17:38:25 mv-laptop pppd[11305]: Plugin passwordfd.so loaded.
Dec 22 17:38:25 mv-laptop pppd[11305]: pppd 2.4.4 started by root, uid 0
Dec 22 17:38:25 mv-laptop pppd[11305]: Interface eth2 has MTU of 1352 -- should be 1500. You may have serious connection problems.
Dec 22 17:38:25 mv-laptop pppd[11305]: PPP session is 8
Dec 22 17:38:25 mv-laptop kernel: ppp0 renamed to dsl0
Dec 22 17:38:25 mv-laptop pppd[11305]: Renamed interface ppp0 to dsl0
Dec 22 17:38:25 mv-laptop pppd[11305]: Using interface dsl0
Dec 22 17:38:25 mv-laptop pppd[11305]: Connect: dsl0 <--> eth2
Dec 22 17:38:25 mv-laptop rename_netiface: oldname ppp0 does not exist
Dec 22 17:38:26 mv-laptop pppd[11305]: CHAP authentication succeeded: CHAP authentication success, unit 1171
Dec 22 17:38:26 mv-laptop pppd[11305]: CHAP authentication succeeded
Dec 22 17:38:26 mv-laptop pppd[11305]: peer from calling number 02:C0:EE:05:0A:93 authorized
Dec 22 17:38:27 mv-laptop pppd[11305]: local IP address 124.109.64.213
Dec 22 17:38:27 mv-laptop pppd[11305]: remote IP address 124.109.64.1
Dec 22 17:38:27 mv-laptop pppd[11305]: primary DNS address 203.98.90.25
Dec 22 17:38:27 mv-laptop pppd[11305]: secondary DNS address 203.98.90.27
Dec 22 17:38:27 mv-laptop modify_resolvconf: Service pppd modified /etc/resolv.conf. See info block in this file
9) Browse the www!
References:
http://www.linuxquestions.org/questions/showthread.php?t=428601&highlight=iburst
Step 4) .... NOTE: before you remove the iburst card, or at least before you re-insert it, you should run: ifdown ethN
Where ethN is the interface name you noted when the card was _first_ inserted.
Step 6.1) Run: ifup ethN