Re: how do I configure a USB device?

Hello Martin,

mjb wrote:

http://www.euclideanspace.com/tech/pc/shuttle/mods/irda/
Is it alright to include your messages as I have done?

Feel invited to do so! :-)) But skip the dead end roads of our solution
path. They only irritate people. So the loop of your exchanging the
running /etc/init/irda with another script doesn't require documentation.

My proposal: After all is done, we make a straight documentation how to
configure this device and how to verify it via console commands.

I guess you think too complicated. SuSE is a German abbreviation for
"Software und System-Entwicklung". They are professionals. YaST is the most
powerful system administration tool I know about. Other distributions lack
this tool. That's why admins have to climb back stages to configure things
manually.

If YaST really happans to fail, e.g. due to fraudy hardware, it still offers
you a graphical interface to change things manually, provided people know
what they are doing.

1. your Stick gets recognized as new hardware right out of the box.

2. YaST offers you the network configuration dialog, since your stick
introduces itself as a network device.

3. Since your ethernet card is configured via DHCP, you get a warning
message, that you are about to change temporary files instead of the
original ones.

4. To prevent this, all it needs to do is stopping the DHCP client service
before you add your "usb network card" with the YaST network module. Then
start the DHCP client service again, reboot and look what happens.

Then as root do

#> ifconfig

You should see irda0 together with eth0, both with assigned IP-addresses.
Provided the irda service is still being started automatically as it
already did.

If really should happen what you fear, crippeling your network connection,
all you need to do is delete your network card configurations via YaST and
reboot to be sure. It then gets offered again as "not yet configured". To
configure it again is simply choosing DHCP in the YaST configuration
dialogue.

All configuration of eth0 already comes from outside, e.g. some WLAN-router
or cable modem acting as a DHCP server.

Greetings

Tarper
.

Relevant Pages

  • [opensuse] Re: local network to ADSL router not available after boot - manual reconfiguration ne
    ... I have a perplexing problem connecting to my ADSL router and local network. ... After every boot I have to use YasT to reconfigure network device, that is to say - delete it - press next etc. Card is then shown in Yast as not configured. ... If I do not delete the configuration first with YasT, but just edit the configuration, then I do not get a IP-address assigned via DHCP, and cannot connect to network. ...
    (SuSE)
  • Re: Wireless card initial use (newbie) (9.2)?
    ... > recognised by yast and I took the default options of dhcp. ... > initiate a scan for signals etc, and do not know if some things will ... When it is not in range of a wireless network it is all dead. ... understand the kwifi manager configuration entries, ...
    (alt.os.linux.suse)
  • [opensuse] local network to ADSL router not available after boot - manual reconfiguration needed
    ... After every boot I have to use YasT to reconfigure network device, that is to say - delete it - press next etc. Card is then shown in Yast as not configured. ... If I do not delete the configuration first with YasT, but just edit the configuration, then I do not get a IP-address assigned via DHCP, and cannot connect to network. ...
    (SuSE)
  • Re: how do I configure a USB device?
    ... I need some help in configuring an infra red to USB adapter on suse 10.0. ... It seems to have been detected at low level by YaST when I plug in to USB ... Obviously your USB adapter is recognized as a network device. ... configuration page but that seems to assume a serial interface. ...
    (alt.os.linux.suse)
  • Re: Remote Access and Outlook Web Access on SBS 2003
    ... that's how the *Wizard* configured your network. ... NETWORKING CONFIGURATION SUMMARY ... Restrict default Web site of IIS to only respond to ...
    (microsoft.public.windows.server.sbs)