Drivers Ntt-me Modems
2021年7月2日Download here: http://gg.gg/v7om1
*Drivers Ntt-me Modems Compatible
*Drivers Ntt-me Modems Reviews
*Drivers Ntt-me Modems Wireless
ethernet via PC Card
Besides analyzing the key market drivers, challenges, commercial commitments and vendor strategies, the report package also presents forecasts for NFV, SDN, wireless network infrastructure, small cells, WiFi offload, DAS (Distributed Antenna Systems), C-RAN (Cloud RAN) and mobile backhaul equipment from 2015 to 2020 at a regional as well as a. In Japan, External Link: NTT-ME sells an 802.11 compliant router – the MN128-SOHO Slotin Air Pack – that includes a PCMCIA wireless access card. Performance Most commercial wireless routers offer throughput up to 11 Mb/s, depending on the encryption level.
It is possible to set up an ethernet connection using the original netBook OS (build 156) plus the alpa-release ethernet drivers, or better, upgrade your netBook to the latest OS (build 450), which includes final release versions of the ethernet drivers.
To set up an ethernet config, use the ’Ethernet’ control panel icon. First of all the, you must select the correct ’Device’ when creating an Ethernet control panel entry. Refer to the (W)LAN compatibility list to see which driver to select (the chipset column).
There are two ways to configure TCP/IP addressing information; either manually or via DHCP (dynamic host configuration protocol). If you are using only a hub to connect your LAN together, you will have to use manual configuration; if you have a ’cleverer’ box, such as a router or gateway, then the chances are it will have a DHCP server built-in, and can supply all the addressing information your netBook will need.
* DHCP. If a DHCP server is available (a server that hands out IP addresses and other network config info to machines on the LAN), all you will need to do is select ’DHCP’ as the Configuration method.
* manual. The minimum information you will need is an IP address for your machine and the subnet mask to use. If the LAN is further connected to the broader internet, you will also need the address of the default gateway (the piece of equipment that actually connects to the internet, which could be a PC or a router), and at least one DNS address (DNS - domain name servers - are the servers thatconvert a web site address into a TCP/IP address). The remaining configitems are optional. Go here if youneed a quick refresher about private LAN IP addressing.
Once you have entered the configuration information, you will need to perform a low-level test of your connection. To do this, download FLFinger. This program can perform a ’ping’, whichis the simplest form of contact you can make to another computer on aLAN. Choose the IP address or domain name of a different machine on yourLAN, start a Ping, and the ’Connect to Internet’ dialog should appear.Select the ethernet configuration that you set up in Control Panel, andwait for the results (N.B. You should now see the lights on the connector ’dongle’ working - the Link light should be on, and the Data light should flicker). If you get a string of OKs, you know that you have successfully made a TCP/IP connection; any further problems you experience beyond this will be to do with the configuration of the software you are using that uses the TCP/IP connection you have made. If your ping does not work,then you have a problem. If the lights on the dongle do not illuminate, then a serious problem with support for your card is suggested - I can only suggest contacting Psion support to see if your card is supported. If you do get lights on the dongle, then re-check your configuration information (or enter manual config instead of DHCP).
For those who like to know what goes where, the IP information obtained via DHCP is stored in C:SystemTempDHCPLease.txt. Also, it is possible to set up a ’hosts’ file (C:SystemDatahosts for the format do a search on your PC for a file called ’hosts’) , to map domain names to the IP addresses of local machines, and thus prevent your internet connection dialling up needlessly.
ethernet via wireless PC Card
(thanks to _JJ_ at the PDAStreet forums for some of this info)
As a starter, the list of compatible PC cards listed in my (W)LAN compatibility list will tell you the first line in what card to get for the Psion - this is the biggest limitation, since the current OS supports only two wireless chipsets. The other part of the equation is a wireless access point - the other endof your wireless network link. This will plug into the ADSL or cable modemso as to connect your wireless LAN to the broader internet.
In theory, any wireless access point that supports 802.11b WiFi should work with any netBook-supported PC Card. There are several types of wireless access point, however. In the situation where you have no wired networking kit at present, the simplest type to get is a ’home gateway’. This will share the broadband internet connection amongst all computers within range of its aerials. If you already have a wired ethernet LAN, then ’wireless bridge’ devices are available that you can plug into your existing wired ethernet hub.
I have divided this howto guide into three sections:
How to configure my PC Card?
I have only used Lucent-type cards. These use the ’802_11 Lucent’ setting in the ethernet control panel. I suggest that you ’copy’ this setting, so as to make your own based on its defaults, name your new copy and hit the ’Edit’ button. The wireless-specific settings are on the ’Service’ tab and within the ’Options’ button on that page. Here is what I have learnt about what the settings mean and what you should set them to:
*Name- simply the name for this set of settings. It willappear in the ’Connect to Internet’ dialog.
*Configuration method- either DHCP or manual. See the section above about ethernet in general to choose which to use.
*Hostname - not compulsory. You might want to set it to ’netBook’ so as to identify it when configuring the wireless access point.
*Device - refer to the (W)LAN compatibility list to see which driver to use for your card.
Tap the ’Options’ button. If you’re using the Cisco driver, the only option you’ll get is SSID, which must match the value you’ve set on your access point. The Lucent driver has a ton more options, to whit:
*WaveLAN network name - This is equivalent to ’SSID’. This parameter is the name of your wireless network. I have discovered that it is not compulsory, since the netBook will simply pick up whatever wireless network it can find. That said, some access points can be configured to only accept connections from wireless clients that already know the SSID.
*Peer to Peer mode - this is dead handy. It allows you to connect two wireless client devices directly to eachother, with no need for an access point. When using this mode, both devices must have the same WaveLAN network name. It is known not to work at all with some chipsets.
*AP density - I’m not certain, but I think this refers to the numberof access points you have in the vicinity, and consequently the powerthreshold to use when searching for an access point. For us lowly home users,having only one access point, this is best set to ’low’, although I’m guessingmore power will be used, so perhaps worth experimenting with.
*Transmit rate - allows you to choose the base transmit rate the wireless connection will use. Works fine with Lucent cards, but with Intersil the best transmit rate I’ve actually achieved (whatever this is set to) is 4Mbps.
*Fixed - this sets whether the transmit rate is fixed to whateveryou set it to or is allowed to ramp to meet the network conditions (i.e.a slower rate if the signal is poor). With an Intersil card, uncheckedI get 2Mbps, checked I get 4Mbps. Go figure.
*Medium reservation - this sets the RTS/CTS frame length, i.e. the number of octets in a message above which a handshake will occur, in a range 0 to 2347. The default is 2347 which equates to disabling RTS/CTS.
*Card power management - checking this will lower your bandwidth noticeably, but will save battery power. Wireless cards use a fair amount of juice, so this might be worth using.
*Receive all multicasts - setting this option will make the card wake up whenmulticasts (packets sent to all nodes on the network) are sent. I’m not surewhen these are important, but this option only comes into play if you startusing power management so have a play and see.
*Maximum sleep duration - once again, raising the value in this box will savepower, but may begin to make your connection a little flaky.
*Enable Encryption - this page is where you set up WEP (Wired Equivalent Privacy). What it does is encrypt the data being sent between the card and the access point, so as (in theory) to make a wireless connection ’equivalently as private’ as a wired ethernet connection. In truth, WEP is easy to defeat with the appropriate software, and so should not be relied upon if security is paramount. Worse, it degrades the performance of your connection by anything up to 50%, and simply does not workwith some chipsets!
Right! Now you’re ready for some..
Initial Tests
Once you have configured the card, attempt a Ping as described in the last paragraph of my general ethernetguide. The first sign that things are working is that the light(s)on your wireless card will start to flicker (if they do not, then youhave chosen the wrong driver or your card is simply not supported by yourmachine). Once you’ve initiated the ping, open NetstatRF, which you’llfind on your extras bar. This will show you raw radio information aboutyour wireless connection, and will at least tell you if the radio partis working, even if you fail to get a ping.
If you ping successfully, all is well and good, move onto the next section. If you do not get a ping, either your TCP/IP configuration is wrong at the netBook or access point end (go here for my quick TCP/IP refresher guide). If this is all correctly set up, all I can suggest is restarting your access point, or perhaps selecting channel 1 on the access point; one of these is what got it going for me.
Once you’ve made a connection, browsed your first web page, and grinned at how massively cool wireless ethernet really is, you’re ready to improve your security.Security Issues
If you’ve now got yourself a wireless ethernet network, and perhaps you’ve connected this to the broader internet via some sort of broadband connection, then I’m afraid you have opened up your computer systems to new forms of security risk. Virus protection alone will not protect your computers here on in!
The security issues relate to the broadband connection and to the wireless ethernet; I’ll discuss them in turn.
Wireless Side
Now that you’ve got a wireless access point, you must keep in mind that you LAN is now accessible to all computers within range, not just those inside your house! If you do not want strangers either using your internet connection, or potentially spying on the data you send via your wireless connection, then you must take steps to protect your LAN.
MAC Filtering.
The very first and best thing you can do, if your wireless access point supports it, is to filter connections by MAC address. All network cards have a totally unique ID number called the MAC (Media Access Control) address. Somewhere in the config of your access point may well be the option to only allow connections from a editable list of MAC addresses. You are strongly advised to enable this feature, and add the MAC addresses of all your wireless ethernet cards. The address of the card will either be printed on the card itself, or can be obtained from the DHCP table elsewherein your access point’s configuration screens.
SSID restriction.
The second thing you can do to protect your network, once again only if your access point supports it, is to only accept connections fromclients that have the same SSID as is set on the access point. This isnot as good a security feature as MAC address filtering, but its betterthan nothing.
WEP.
Okay, so your network is now protected from being used by unauthorised clients. Your connection however remains open to ’sniffing’. In order to prevent a client within range from ’listening in’ on the data you transmit to and from your access point, you must encryt that data in some way.
Wireless LANs have a feature built-in to support this, called WEP (Wired Equivalent Privacy). This is easy to set up, but has a number of pitfalls:
*it uses a poor encryption algorithm, that is easily broken using appropriate software (AirSnort).
*it is poorly implemented in many wireless network cards, and can cause a degradation in speed of anything upto 50%.
*the netBook driver only supports WEP for cards that use the Lucent Hermes chipset. If you enable WEP when using a cards that has the (much more common) Intersil Prism II chipset, your connection will simply not work at all!
*64 bit (AKA 40 bit) WEP is the only format guaranteed to work between kit from different manufacturers (i.e. PC card from one manufacturer, access point from another). I have used alphanumeric keys successfully with this level of WEP.
Broadband Side
When you move from a telephone line to a broadband connection, you no longer dial up when you wish to access the internet; your computer connects up as soon as it is switched on and boots up. This means that the computer connected to the ADSL or cable modem tends to keep the same IP address for much longer periods of time, and consequently the machine becomes a target for a new class of ’viruses’ - so-called ’worms’. These pieces of code do not subvert the use of your computer awayfrom you at all, their aim is not to damage your computer but simply to’borrow’ some of your computer’s processing time to do their master’s bidding. This could include being an unwitting participant in directed denial of sevice (DDOS) attacks (ping or ICMP floods). Other more recent typesof intrusion include unexpected Windows Messaging pop-ups, and other trackingsoftware that keeps an eye on your browsing behaviour, and then targetsyou with advertising for products that it considers might be of interestto you. Whether you want this to happen is a judgement call, but personallyI consider the installation of software on my computer without my permissionto be a brazen invasion of my privacy.
The solution is a so-called ’firewall’, separating your local network of computers (your LAN), from the broader internet. The better class of home gateway tends to have a firewall built in. For the more technically-minded (and for those desirous of higher security and lower costs!), an alternative is a cheap old PC (even a 486 or Pentium I) with only 32Mb RAM or so, upon which you can install a GPL- licensed (and therefore free!) firewall product such as Smoothwall. I have this configuration and can vouch for its simplicity and solidity :o)
(W)LAN card compatibility matrix
First of all, here are the proven results of testing bynetBook/7Book users. Please read the notes andtext following the table; many more cards are supported thanthis list might suggest, conversely some cards are available in multiple configurations, not all of which are supported!
Xerox red light cameras. For MalayBook refer to the netBook column, and for 7Books (Series 7 modified with a netBook personality module) the OS number refers to the OS revision the machine was originally supplied with -this gives a rough guide to the amount of current the PCMCIA slot cansupply.Make/ModelChipsetFCC IDMax. current (mA)4netBook7Book (OS 751)117Book (OS 754)7Book (OS 756)Belkin F5D6020Intersil Prism II/Atmel 107K7SF5D6020350yesBuffalo Technology WLI-PCM-L11GPLucent Hermes285yesyesyesyesCisco Aironet 340Cisco580yesnoCisco Aironet 350Cisco500
yesnoDell Truemobile 1100Intersil Prism II 7350yesnoDell Truemobile 11502Lucent HermesIMRWLPCE24H285yesyesyesyesEnterasys Roamabout2Lucent HermesIMRWLPCE24H285yesyesyesyesLinksys WPC11 (not V2.5 or V.3)Intersil Prism II 707J-GL2411010700350yesyesLucent/Orinoco/Avaya Silver2Lucent HermesIMRWLPCE24H285yesyesyesyesLucent/Orinoco/Avaya Gold2Lucent HermesIMRWLPCE24H285yesyesyesyesNetGear MA4018Intersil Prism II7PD5LMWP100yesyesyesPsion CombineIT gold card LANGlobal 10/100 EthernetCombineITLGPF0C-001E1Pyes1Psion CombineIT gold card v.90 56K + 10/100 Ethernet9CombineITyesyesPsion Dacom NETGlobal 56k+fax+1059Dacom (Olitech/SMC)yesno/yes6yesPsion Dacom 10/100 Ethernet LAN Global9DacomnonononoSMC EZConnect (#SMC2632W)Intersil Prism II/Atmel37yesyes
Notes:
1 - early cards need hardware patch to stop occasional triple-beep reset.
2 - the aerial on these cards obscures the stylus hole.
3 - two chipsets used; only the older card works (picture here), using Intersil Prism II chipset. Newer chipset is Atmel (’Prism 2.5’) and card will be marked ’V2’.
4 - check here and here for more on power consumption.
5 - need to change modem setting ’Wait For Dialtone’ to ’on’ from the default of ’off’. Sometimes setting ’Modem Type’ to ’fixed line’ helps too.
6 - the Dacom modem is intermittent with the 751 release.
7 - WEP does not work with the Intersil Prism chipset; it only works with the reference Lucent Hermes chipset.
8 - NetGear MA401 must be an older model (check the FCC ID). Newer models use the unsupported Prism 2.5 chipset (FCC ID: PD5LMWP200).
9 - if your modem will not connect, try reducing the Speed in the control panel entry for this card to 57600.
10 - only the V.1 has the Intersil chipset and is supported. V.2 has Atmel chipset, its FCCID is different (K7SF5D6021) and is not supported.
11 - the 751 vintage 7Book is only just capable of supplying enough power; concurrent CF card access may cause a triple-beep reset.
Beyond the list above, here is information gathered from a variety of sources, that should help you to work out if a card not listed above will work or not. First of all, check this URL (http://www.bawia.org/cards.html). It provides the most concise explanation I’ve found of the chipsets out there that our machines support.
Another method (thanks be to Fladda from Psionplace forums) is to use the FCC’s searchable database to find out more info about a given card via is FCC ID. Go to this address: http://gullfoss2.fcc.gov/cgi-bin/ws.exe/prod/oet/forms/reports/Search_Form.hts?form=Generic_Search, and (to quote Fladda’s post), ’Use the ’grantee code’ search option. First three digits of the FCC ID number are the grantee code. So for the PD5LMWP100 the grantee code is PD5, this is a Chinese company called Delta who are the OEM for Netgear.’
The Lucent chipset has been rebranded multiple times over the past couple of years, so the following list of card/chipset brands should also work:
*Orinoco
*Agere
*Proxim
*Avaya
The following list of cards was found by Fladda at this URL (http://resin.csoft.net/cgi-bin/man.cgi?section=4&topic=wi). All use either Lucent’s original chipset (Hermes) or Intersil’s copy of the reference design (Prism II), and should therefore work. One thing lacking from
https://diarynote-jp.indered.space
*Drivers Ntt-me Modems Compatible
*Drivers Ntt-me Modems Reviews
*Drivers Ntt-me Modems Wireless
ethernet via PC Card
Besides analyzing the key market drivers, challenges, commercial commitments and vendor strategies, the report package also presents forecasts for NFV, SDN, wireless network infrastructure, small cells, WiFi offload, DAS (Distributed Antenna Systems), C-RAN (Cloud RAN) and mobile backhaul equipment from 2015 to 2020 at a regional as well as a. In Japan, External Link: NTT-ME sells an 802.11 compliant router – the MN128-SOHO Slotin Air Pack – that includes a PCMCIA wireless access card. Performance Most commercial wireless routers offer throughput up to 11 Mb/s, depending on the encryption level.
It is possible to set up an ethernet connection using the original netBook OS (build 156) plus the alpa-release ethernet drivers, or better, upgrade your netBook to the latest OS (build 450), which includes final release versions of the ethernet drivers.
To set up an ethernet config, use the ’Ethernet’ control panel icon. First of all the, you must select the correct ’Device’ when creating an Ethernet control panel entry. Refer to the (W)LAN compatibility list to see which driver to select (the chipset column).
There are two ways to configure TCP/IP addressing information; either manually or via DHCP (dynamic host configuration protocol). If you are using only a hub to connect your LAN together, you will have to use manual configuration; if you have a ’cleverer’ box, such as a router or gateway, then the chances are it will have a DHCP server built-in, and can supply all the addressing information your netBook will need.
* DHCP. If a DHCP server is available (a server that hands out IP addresses and other network config info to machines on the LAN), all you will need to do is select ’DHCP’ as the Configuration method.
* manual. The minimum information you will need is an IP address for your machine and the subnet mask to use. If the LAN is further connected to the broader internet, you will also need the address of the default gateway (the piece of equipment that actually connects to the internet, which could be a PC or a router), and at least one DNS address (DNS - domain name servers - are the servers thatconvert a web site address into a TCP/IP address). The remaining configitems are optional. Go here if youneed a quick refresher about private LAN IP addressing.
Once you have entered the configuration information, you will need to perform a low-level test of your connection. To do this, download FLFinger. This program can perform a ’ping’, whichis the simplest form of contact you can make to another computer on aLAN. Choose the IP address or domain name of a different machine on yourLAN, start a Ping, and the ’Connect to Internet’ dialog should appear.Select the ethernet configuration that you set up in Control Panel, andwait for the results (N.B. You should now see the lights on the connector ’dongle’ working - the Link light should be on, and the Data light should flicker). If you get a string of OKs, you know that you have successfully made a TCP/IP connection; any further problems you experience beyond this will be to do with the configuration of the software you are using that uses the TCP/IP connection you have made. If your ping does not work,then you have a problem. If the lights on the dongle do not illuminate, then a serious problem with support for your card is suggested - I can only suggest contacting Psion support to see if your card is supported. If you do get lights on the dongle, then re-check your configuration information (or enter manual config instead of DHCP).
For those who like to know what goes where, the IP information obtained via DHCP is stored in C:SystemTempDHCPLease.txt. Also, it is possible to set up a ’hosts’ file (C:SystemDatahosts for the format do a search on your PC for a file called ’hosts’) , to map domain names to the IP addresses of local machines, and thus prevent your internet connection dialling up needlessly.
ethernet via wireless PC Card
(thanks to _JJ_ at the PDAStreet forums for some of this info)
As a starter, the list of compatible PC cards listed in my (W)LAN compatibility list will tell you the first line in what card to get for the Psion - this is the biggest limitation, since the current OS supports only two wireless chipsets. The other part of the equation is a wireless access point - the other endof your wireless network link. This will plug into the ADSL or cable modemso as to connect your wireless LAN to the broader internet.
In theory, any wireless access point that supports 802.11b WiFi should work with any netBook-supported PC Card. There are several types of wireless access point, however. In the situation where you have no wired networking kit at present, the simplest type to get is a ’home gateway’. This will share the broadband internet connection amongst all computers within range of its aerials. If you already have a wired ethernet LAN, then ’wireless bridge’ devices are available that you can plug into your existing wired ethernet hub.
I have divided this howto guide into three sections:
How to configure my PC Card?
I have only used Lucent-type cards. These use the ’802_11 Lucent’ setting in the ethernet control panel. I suggest that you ’copy’ this setting, so as to make your own based on its defaults, name your new copy and hit the ’Edit’ button. The wireless-specific settings are on the ’Service’ tab and within the ’Options’ button on that page. Here is what I have learnt about what the settings mean and what you should set them to:
*Name- simply the name for this set of settings. It willappear in the ’Connect to Internet’ dialog.
*Configuration method- either DHCP or manual. See the section above about ethernet in general to choose which to use.
*Hostname - not compulsory. You might want to set it to ’netBook’ so as to identify it when configuring the wireless access point.
*Device - refer to the (W)LAN compatibility list to see which driver to use for your card.
Tap the ’Options’ button. If you’re using the Cisco driver, the only option you’ll get is SSID, which must match the value you’ve set on your access point. The Lucent driver has a ton more options, to whit:
*WaveLAN network name - This is equivalent to ’SSID’. This parameter is the name of your wireless network. I have discovered that it is not compulsory, since the netBook will simply pick up whatever wireless network it can find. That said, some access points can be configured to only accept connections from wireless clients that already know the SSID.
*Peer to Peer mode - this is dead handy. It allows you to connect two wireless client devices directly to eachother, with no need for an access point. When using this mode, both devices must have the same WaveLAN network name. It is known not to work at all with some chipsets.
*AP density - I’m not certain, but I think this refers to the numberof access points you have in the vicinity, and consequently the powerthreshold to use when searching for an access point. For us lowly home users,having only one access point, this is best set to ’low’, although I’m guessingmore power will be used, so perhaps worth experimenting with.
*Transmit rate - allows you to choose the base transmit rate the wireless connection will use. Works fine with Lucent cards, but with Intersil the best transmit rate I’ve actually achieved (whatever this is set to) is 4Mbps.
*Fixed - this sets whether the transmit rate is fixed to whateveryou set it to or is allowed to ramp to meet the network conditions (i.e.a slower rate if the signal is poor). With an Intersil card, uncheckedI get 2Mbps, checked I get 4Mbps. Go figure.
*Medium reservation - this sets the RTS/CTS frame length, i.e. the number of octets in a message above which a handshake will occur, in a range 0 to 2347. The default is 2347 which equates to disabling RTS/CTS.
*Card power management - checking this will lower your bandwidth noticeably, but will save battery power. Wireless cards use a fair amount of juice, so this might be worth using.
*Receive all multicasts - setting this option will make the card wake up whenmulticasts (packets sent to all nodes on the network) are sent. I’m not surewhen these are important, but this option only comes into play if you startusing power management so have a play and see.
*Maximum sleep duration - once again, raising the value in this box will savepower, but may begin to make your connection a little flaky.
*Enable Encryption - this page is where you set up WEP (Wired Equivalent Privacy). What it does is encrypt the data being sent between the card and the access point, so as (in theory) to make a wireless connection ’equivalently as private’ as a wired ethernet connection. In truth, WEP is easy to defeat with the appropriate software, and so should not be relied upon if security is paramount. Worse, it degrades the performance of your connection by anything up to 50%, and simply does not workwith some chipsets!
Right! Now you’re ready for some..
Initial Tests
Once you have configured the card, attempt a Ping as described in the last paragraph of my general ethernetguide. The first sign that things are working is that the light(s)on your wireless card will start to flicker (if they do not, then youhave chosen the wrong driver or your card is simply not supported by yourmachine). Once you’ve initiated the ping, open NetstatRF, which you’llfind on your extras bar. This will show you raw radio information aboutyour wireless connection, and will at least tell you if the radio partis working, even if you fail to get a ping.
If you ping successfully, all is well and good, move onto the next section. If you do not get a ping, either your TCP/IP configuration is wrong at the netBook or access point end (go here for my quick TCP/IP refresher guide). If this is all correctly set up, all I can suggest is restarting your access point, or perhaps selecting channel 1 on the access point; one of these is what got it going for me.
Once you’ve made a connection, browsed your first web page, and grinned at how massively cool wireless ethernet really is, you’re ready to improve your security.Security Issues
If you’ve now got yourself a wireless ethernet network, and perhaps you’ve connected this to the broader internet via some sort of broadband connection, then I’m afraid you have opened up your computer systems to new forms of security risk. Virus protection alone will not protect your computers here on in!
The security issues relate to the broadband connection and to the wireless ethernet; I’ll discuss them in turn.
Wireless Side
Now that you’ve got a wireless access point, you must keep in mind that you LAN is now accessible to all computers within range, not just those inside your house! If you do not want strangers either using your internet connection, or potentially spying on the data you send via your wireless connection, then you must take steps to protect your LAN.
MAC Filtering.
The very first and best thing you can do, if your wireless access point supports it, is to filter connections by MAC address. All network cards have a totally unique ID number called the MAC (Media Access Control) address. Somewhere in the config of your access point may well be the option to only allow connections from a editable list of MAC addresses. You are strongly advised to enable this feature, and add the MAC addresses of all your wireless ethernet cards. The address of the card will either be printed on the card itself, or can be obtained from the DHCP table elsewherein your access point’s configuration screens.
SSID restriction.
The second thing you can do to protect your network, once again only if your access point supports it, is to only accept connections fromclients that have the same SSID as is set on the access point. This isnot as good a security feature as MAC address filtering, but its betterthan nothing.
WEP.
Okay, so your network is now protected from being used by unauthorised clients. Your connection however remains open to ’sniffing’. In order to prevent a client within range from ’listening in’ on the data you transmit to and from your access point, you must encryt that data in some way.
Wireless LANs have a feature built-in to support this, called WEP (Wired Equivalent Privacy). This is easy to set up, but has a number of pitfalls:
*it uses a poor encryption algorithm, that is easily broken using appropriate software (AirSnort).
*it is poorly implemented in many wireless network cards, and can cause a degradation in speed of anything upto 50%.
*the netBook driver only supports WEP for cards that use the Lucent Hermes chipset. If you enable WEP when using a cards that has the (much more common) Intersil Prism II chipset, your connection will simply not work at all!
*64 bit (AKA 40 bit) WEP is the only format guaranteed to work between kit from different manufacturers (i.e. PC card from one manufacturer, access point from another). I have used alphanumeric keys successfully with this level of WEP.
Broadband Side
When you move from a telephone line to a broadband connection, you no longer dial up when you wish to access the internet; your computer connects up as soon as it is switched on and boots up. This means that the computer connected to the ADSL or cable modem tends to keep the same IP address for much longer periods of time, and consequently the machine becomes a target for a new class of ’viruses’ - so-called ’worms’. These pieces of code do not subvert the use of your computer awayfrom you at all, their aim is not to damage your computer but simply to’borrow’ some of your computer’s processing time to do their master’s bidding. This could include being an unwitting participant in directed denial of sevice (DDOS) attacks (ping or ICMP floods). Other more recent typesof intrusion include unexpected Windows Messaging pop-ups, and other trackingsoftware that keeps an eye on your browsing behaviour, and then targetsyou with advertising for products that it considers might be of interestto you. Whether you want this to happen is a judgement call, but personallyI consider the installation of software on my computer without my permissionto be a brazen invasion of my privacy.
The solution is a so-called ’firewall’, separating your local network of computers (your LAN), from the broader internet. The better class of home gateway tends to have a firewall built in. For the more technically-minded (and for those desirous of higher security and lower costs!), an alternative is a cheap old PC (even a 486 or Pentium I) with only 32Mb RAM or so, upon which you can install a GPL- licensed (and therefore free!) firewall product such as Smoothwall. I have this configuration and can vouch for its simplicity and solidity :o)
(W)LAN card compatibility matrix
First of all, here are the proven results of testing bynetBook/7Book users. Please read the notes andtext following the table; many more cards are supported thanthis list might suggest, conversely some cards are available in multiple configurations, not all of which are supported!
Xerox red light cameras. For MalayBook refer to the netBook column, and for 7Books (Series 7 modified with a netBook personality module) the OS number refers to the OS revision the machine was originally supplied with -this gives a rough guide to the amount of current the PCMCIA slot cansupply.Make/ModelChipsetFCC IDMax. current (mA)4netBook7Book (OS 751)117Book (OS 754)7Book (OS 756)Belkin F5D6020Intersil Prism II/Atmel 107K7SF5D6020350yesBuffalo Technology WLI-PCM-L11GPLucent Hermes285yesyesyesyesCisco Aironet 340Cisco580yesnoCisco Aironet 350Cisco500
yesnoDell Truemobile 1100Intersil Prism II 7350yesnoDell Truemobile 11502Lucent HermesIMRWLPCE24H285yesyesyesyesEnterasys Roamabout2Lucent HermesIMRWLPCE24H285yesyesyesyesLinksys WPC11 (not V2.5 or V.3)Intersil Prism II 707J-GL2411010700350yesyesLucent/Orinoco/Avaya Silver2Lucent HermesIMRWLPCE24H285yesyesyesyesLucent/Orinoco/Avaya Gold2Lucent HermesIMRWLPCE24H285yesyesyesyesNetGear MA4018Intersil Prism II7PD5LMWP100yesyesyesPsion CombineIT gold card LANGlobal 10/100 EthernetCombineITLGPF0C-001E1Pyes1Psion CombineIT gold card v.90 56K + 10/100 Ethernet9CombineITyesyesPsion Dacom NETGlobal 56k+fax+1059Dacom (Olitech/SMC)yesno/yes6yesPsion Dacom 10/100 Ethernet LAN Global9DacomnonononoSMC EZConnect (#SMC2632W)Intersil Prism II/Atmel37yesyes
Notes:
1 - early cards need hardware patch to stop occasional triple-beep reset.
2 - the aerial on these cards obscures the stylus hole.
3 - two chipsets used; only the older card works (picture here), using Intersil Prism II chipset. Newer chipset is Atmel (’Prism 2.5’) and card will be marked ’V2’.
4 - check here and here for more on power consumption.
5 - need to change modem setting ’Wait For Dialtone’ to ’on’ from the default of ’off’. Sometimes setting ’Modem Type’ to ’fixed line’ helps too.
6 - the Dacom modem is intermittent with the 751 release.
7 - WEP does not work with the Intersil Prism chipset; it only works with the reference Lucent Hermes chipset.
8 - NetGear MA401 must be an older model (check the FCC ID). Newer models use the unsupported Prism 2.5 chipset (FCC ID: PD5LMWP200).
9 - if your modem will not connect, try reducing the Speed in the control panel entry for this card to 57600.
10 - only the V.1 has the Intersil chipset and is supported. V.2 has Atmel chipset, its FCCID is different (K7SF5D6021) and is not supported.
11 - the 751 vintage 7Book is only just capable of supplying enough power; concurrent CF card access may cause a triple-beep reset.
Beyond the list above, here is information gathered from a variety of sources, that should help you to work out if a card not listed above will work or not. First of all, check this URL (http://www.bawia.org/cards.html). It provides the most concise explanation I’ve found of the chipsets out there that our machines support.
Another method (thanks be to Fladda from Psionplace forums) is to use the FCC’s searchable database to find out more info about a given card via is FCC ID. Go to this address: http://gullfoss2.fcc.gov/cgi-bin/ws.exe/prod/oet/forms/reports/Search_Form.hts?form=Generic_Search, and (to quote Fladda’s post), ’Use the ’grantee code’ search option. First three digits of the FCC ID number are the grantee code. So for the PD5LMWP100 the grantee code is PD5, this is a Chinese company called Delta who are the OEM for Netgear.’
The Lucent chipset has been rebranded multiple times over the past couple of years, so the following list of card/chipset brands should also work:
*Orinoco
*Agere
*Proxim
*Avaya
The following list of cards was found by Fladda at this URL (http://resin.csoft.net/cgi-bin/man.cgi?section=4&topic=wi). All use either Lucent’s original chipset (Hermes) or Intersil’s copy of the reference design (Prism II), and should therefore work. One thing lacking from
https://diarynote-jp.indered.space
コメント