[opensuse] Leap 42.2: WLAN AP and bridging setup
Hi, my small home server (a Shuttle DS47D) has two ethernet ports, eth0 is connected to the fiber modem, eth1 is my local network where the shuttle acts as DHCP/NFS/CUPS server. So far, so good. The Shuttle also has a wireless card (RTL8188CE 802.11b/g/n WiFi Adapter), and I want to set it up as an access point: While the fiber modem does have an WLAN AP, it directly connects to the outside network of our house :( So while I have internet from that, I'm 'outside' and cannot access services in my private net :( So I installed hostapd. First I had tried only hostapd, and this did not work - I was always disconnected :( I figured out I'd need to set up a bridge with eth1 and wlan0, so I could get an IP address. But when I fire up yast, to create a bridge, it only offers wlan0 and eth0 as possible interfaces for bridging. eth1 *is* visible in the overview - just not available for bridging. Would anyone know why? And does anyone have a similar setup running who could give me some hint/jumpstart? Thanks, Pit -- Dr. Peter "Pit" Suetterlin http://www.astro.su.se/~pit Institute for Solar Physics Tel.: +34 922 405 590 (Spain) P.Suetterlin@royac.iac.es +46 8 5537 8559 (Sweden) Peter.Suetterlin@astro.su.se -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 10/01/2017 à 11:55, pit a écrit :
The Shuttle also has a wireless card (RTL8188CE 802.11b/g/n WiFi Adapter), and I want to set it up as an access point:
I don't see why you would need any special software to do so. Configure it in yast and in susefirewall2 may be you have to use a different network than the ethernet one (192.168.1.xx if the other is 0.xx) jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
jdd wrote:
Le 10/01/2017 à 11:55, pit a écrit :
The Shuttle also has a wireless card (RTL8188CE 802.11b/g/n WiFi Adapter), and I want to set it up as an access point:
I don't see why you would need any special software to do so. Configure it in yast and in susefirewall2
may be you have to use a different network than the ethernet one (192.168.1.xx if the other is 0.xx)
No, I do not want to use it to connect to a WiFi network - I want it to be an accesspoint so that other wireless devices (laptop, TV) can connect to my local network. For this hostapd is needed.... Pit -- Dr. Peter "Pit" Suetterlin http://www.astro.su.se/~pit Institute for Solar Physics Tel.: +34 922 405 590 (Spain) P.Suetterlin@royac.iac.es +46 8 5537 8559 (Sweden) Peter.Suetterlin@astro.su.se -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 10/01/2017 à 12:06, pit a écrit :
jdd wrote:
Le 10/01/2017 à 11:55, pit a écrit :
The Shuttle also has a wireless card (RTL8188CE 802.11b/g/n WiFi Adapter), and I want to set it up as an access point:
I don't see why you would need any special software to do so. Configure it in yast and in susefirewall2
may be you have to use a different network than the ethernet one (192.168.1.xx if the other is 0.xx)
No, I do not want to use it to connect to a WiFi network - I want it to be an accesspoint so that other wireless devices (laptop, TV) can connect to my local network. For this hostapd is needed....
Pit
no, it's not AFAIK wifi is wifi, a network like any other jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/10/2017 06:34 AM, jdd wrote:
no, it's not AFAIK
wifi is wifi, a network like any other
Actually, it's not. An access point provides various functions that a user does not. For example, you cannot log into a client, the way you would an access point. The closest thing a client would have to an access point is an ad hoc network, where clients can peer. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/10/2017 06:01 AM, jdd wrote:
Le 10/01/2017 à 11:55, pit a écrit :
The Shuttle also has a wireless card (RTL8188CE 802.11b/g/n WiFi Adapter), and I want to set it up as an access point:
I don't see why you would need any special software to do so. Configure it in yast and in susefirewall2
may be you have to use a different network than the ethernet one (192.168.1.xx if the other is 0.xx)
jdd
I don't think that would produce an access point. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 10/01/2017 à 13:10, James Knott a écrit :
On 01/10/2017 06:01 AM, jdd wrote:
Le 10/01/2017 à 11:55, pit a écrit :
The Shuttle also has a wireless card (RTL8188CE 802.11b/g/n WiFi Adapter), and I want to set it up as an access point:
I don't see why you would need any special software to do so. Configure it in yast and in susefirewall2
may be you have to use a different network than the ethernet one (192.168.1.xx if the other is 0.xx)
jdd
I don't think that would produce an access point.
did you try it? what would make connecting to a wifi server different than plugin a cable in a free slot? (apart firewall settings - may be need nat). by the way I already did so (I don't have wifi right now to test again) jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/10/2017 07:22 AM, jdd wrote:
did you try it? what would make connecting to a wifi server different than plugin a cable in a free slot? (apart firewall settings - may be need nat).
As I mentioned in another note, an access point has several functions that a client doesn't. For example, it normally announces itself periodically, clients don't. It has authentication, via WPA2, that the client can use to connect. It can support multiple connections, while a client connects to one AP, etc. You really ought to read up on WiFi. O'Reilly has some good books that describe it. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 10/01/2017 à 13:29, James Knott a écrit :
On 01/10/2017 07:22 AM, jdd wrote:
did you try it? what would make connecting to a wifi server different than plugin a cable in a free slot? (apart firewall settings - may be need nat).
As I mentioned in another note, an access point has several functions that a client doesn't. For example, it normally announces itself periodically,
certainly not, many are even hidden (no SSID visible) clients don't. It has authentication, via WPA2, that the
client can use to connect.
this yes, may be usefull It can support multiple connections, while a
client connects to one AP, etc. You really ought to read up on WiFi. O'Reilly has some good books that describe it.
as I said, I already configured this pretty easily, but for the use I had it could be fully open https://www.suse.com/documentation/sled11/book_sle_admin/data/sec_wireless_w... it needs a compatible wifi card jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
jdd wrote:
It can support multiple connections, while a
client connects to one AP, etc. You really ought to read up on WiFi. O'Reilly has some good books that describe it.
as I said, I already configured this pretty easily, but for the use I had it could be fully open
https://www.suse.com/documentation/sled11/book_sle_admin/data/sec_wireless_w...
it needs a compatible wifi card
Hmm, even the sled documentation doesn't give proper information how to set up an access point. It does confirm though that it won't work with WPA. So I tried it with the open configuration in master mode, but even with that it won't bring up the interface (iwconfig will still report it as Managed and Not-Associated). I cannot connect to it from other devices. Are you sure you didn't just set up an ad-hoc ptp connection? Pit -- Dr. Peter "Pit" Suetterlin http://www.astro.su.se/~pit Institute for Solar Physics Tel.: +34 922 405 590 (Spain) P.Suetterlin@royac.iac.es +46 8 5537 8559 (Sweden) Peter.Suetterlin@astro.su.se -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 10/01/2017 à 14:09, pit a écrit :
Are you sure you didn't just set up an ad-hoc ptp connection?
yes, I wanted to share doc for a meeting, where I had to come without luggage apart a backpack :-) that said, a separate AP is very cheap and this one is very simple to configure (I did this very often) jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
jdd wrote:
Le 10/01/2017 à 14:09, pit a écrit :
Are you sure you didn't just set up an ad-hoc ptp connection?
yes, I wanted to share doc for a meeting, where I had to come without luggage apart a backpack :-)
Hmm, so I must be doing something stupid then. But even if I got that to work, it's not a permanent option without WPA
that said, a separate AP is very cheap and this one is very simple to configure (I did this very often)
Yeah, I know. But that means another powersupply and another ETH port on the switch blocked. Plus the card and the computer are there, and I'm somewhat nerdish sometimes :o Pit -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 10/01/2017 à 14:48, pit a écrit :
Yeah, I know. But that means another powersupply and another ETH port on the switch blocked. Plus the card and the computer are there, and I'm somewhat nerdish sometimes :o
Pit
no, your question was/is fine and should have an answer :-) jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/10/2017 08:09 AM, pit wrote:
jdd wrote:
It can support multiple connections, while a
client connects to one AP, etc. You really ought to read up on WiFi. O'Reilly has some good books that describe it.
as I said, I already configured this pretty easily, but for the use I had it could be fully open
https://www.suse.com/documentation/sled11/book_sle_admin/data/sec_wireless_w...
it needs a compatible wifi card Hmm, even the sled documentation doesn't give proper information how to set up an access point. It does confirm though that it won't work with WPA.
That link also contains: "If however you want to use your WLAN card as access point, set the Operating Mode to Master. Note that not all WLAN cards support this mode." How many WiFi NICs actually support it?
So I tried it with the open configuration in master mode, but even with that it won't bring up the interface (iwconfig will still report it as Managed and Not-Associated). I cannot connect to it from other devices.
Are you sure you didn't just set up an ad-hoc ptp connection?
Pit
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
James Knott wrote:
That link also contains:
"If however you want to use your WLAN card as access point, set the Operating Mode to Master. Note that not all WLAN cards support this mode."
How many WiFi NICs actually support it?
Many. You can check this with 'iw list', it has to have AP in the 'Supported interface modes' section (which both the Shuttle and my laptop do). Pit -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/10/2017 07:41 AM, jdd wrote:
As I mentioned in another note, an access point has several functions that a client doesn't. For example, it normally announces itself periodically,
certainly not, many are even hidden (no SSID visible)
That's why I said normally. BTW, hiding the SSID is false security, as it's not hard to discover. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 11/01/2017 à 00:01, James Knott a écrit :
On 01/10/2017 07:41 AM, jdd wrote:
As I mentioned in another note, an access point has several functions that a client doesn't. For example, it normally announces itself periodically,
certainly not, many are even hidden (no SSID visible)
That's why I said normally. BTW, hiding the SSID is false security, as it's not hard to discover.
sure by the way I could activate the wifi card in my desktop, launch YaST and choose "master", but whatever I try it's never configured: the IP I choose for the interface do not show in ifconfig is there any mean to check if the card is master compatible? thanks jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 11/01/2017 à 10:14, jdd a écrit :
check if the card is master compatible
probably not # iwconfig wlan0 IEEE 802.11bgn ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=20 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:off # iwconfig wlan0 mode master Error for wireless request "Set Mode" (8B06) : SET failed on device wlan0 ; Invalid argument. jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Maybe I should read all posts before starting to reply :o jdd wrote:
Le 11/01/2017 à 10:14, jdd a écrit :
check if the card is master compatible
probably not
# iwconfig
wlan0 IEEE 802.11bgn ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=20 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:off
# iwconfig wlan0 mode master Error for wireless request "Set Mode" (8B06) : SET failed on device wlan0 ; Invalid argument.
I had the same issues when trying to set it up with yast. But the card is master capable, just the setup did not work. But good to know it also seems to fail for you now. I'll keep that in mind. Meanwhile I managed to get the bridge working by doing it manual (changing the config files directly). Weird enough, now, if I use yast again to check the config and go to the bridged devices tab, all three are there. Something must have messed up my network stack maybe? Or it somehow collided with configuration files still in sysconfig/network (I deleted them today for the manual setup....) Following iwconfig things are fine: wlan0 IEEE 802.11bgn Mode:Master Tx-Power=20 dBm Retry short limit:7 RTS thr:off Fragment thr:off Power Management:off But I'm sitting in the office and cannot yet check if I finally can use it. Later tonight hopefully.... Pit -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
jdd wrote:
by the way I could activate the wifi card in my desktop, launch YaST and choose "master", but whatever I try it's never configured: the IP I choose for the interface do not show in ifconfig
is there any mean to check if the card is master compatible?
Yes, see my other reply: 'iw list' needs 'AP' as supported mode. Pit -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
James Knott wrote:
On 01/10/2017 06:01 AM, jdd wrote:
Le 10/01/2017 à 11:55, pit a écrit :
The Shuttle also has a wireless card (RTL8188CE 802.11b/g/n WiFi Adapter), and I want to set it up as an access point:
I don't see why you would need any special software to do so. Configure it in yast and in susefirewall2
may be you have to use a different network than the ethernet one (192.168.1.xx if the other is 0.xx)
jdd
I don't think that would produce an access point.
It indeed doesn't :( There *is* an option 'master' for the wireless setup in yast, but there is no real help in the 'Help', and selecting 'WPA' switches mode back to Managed. Master mode setup seemed possible with WEP, but when activating the network this fails. Pit -- Dr. Peter "Pit" Suetterlin http://www.astro.su.se/~pit Institute for Solar Physics Tel.: +34 922 405 590 (Spain) P.Suetterlin@royac.iac.es +46 8 5537 8559 (Sweden) Peter.Suetterlin@astro.su.se -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
pit wrote:
I figured out I'd need to set up a bridge with eth1 and wlan0, so I could get an IP address. But when I fire up yast, to create a bridge, it only offers wlan0 and eth0 as possible interfaces for bridging. eth1 *is* visible in the overview - just not available for bridging.
Would anyone know why? And does anyone have a similar setup running who could give me some hint/jumpstart?
It's been a while since I've used YaST for setting up a bridge, but ISTR that the interfaces to be bridged must be unconfigured. If for some reason YaST won't pick eth1, you can always edit the config file yourself, but I would guess you might find clues as to why in the yast log file. -- Per Jessen, Zürich (0.1°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Per Jessen wrote:
pit wrote:
I figured out I'd need to set up a bridge with eth1 and wlan0, so I could get an IP address. But when I fire up yast, to create a bridge, it only offers wlan0 and eth0 as possible interfaces for bridging. eth1 *is* visible in the overview - just not available for bridging.
Would anyone know why? And does anyone have a similar setup running who could give me some hint/jumpstart?
It's been a while since I've used YaST for setting up a bridge, but ISTR that the interfaces to be bridged must be unconfigured. If for some reason YaST won't pick eth1, you can always edit the config file yourself, but I would guess you might find clues as to why in the yast log file.
Thought about this, too. But if I first delete all configurations, no IF showed up at all in the bridged devices tab :( And on my first try eth0 had been configured, but did show up in the list. I glanced through the yast2 log, but didn't find obvious hints. Pit -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Tue, 10 Jan 2017 14:27:17 +0100, pit wrote:
Per Jessen wrote:
pit wrote:
I figured out I'd need to set up a bridge with eth1 and wlan0, so I could get an IP address. But when I fire up yast, to create a bridge, it only offers wlan0 and eth0 as possible interfaces for bridging. eth1 *is* visible in the overview - just not available for bridging.
Would anyone know why? And does anyone have a similar setup running who could give me some hint/jumpstart?
It's been a while since I've used YaST for setting up a bridge, but ISTR that the interfaces to be bridged must be unconfigured. If for some reason YaST won't pick eth1, you can always edit the config file yourself, but I would guess you might find clues as to why in the yast log file.
Thought about this, too. But if I first delete all configurations, no IF showed up at all in the bridged devices tab :(
That sounds good actually. If you then continue to create a bridge device, do you get to chose from all of your interfaces? /Per -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Per Jessen wrote:
Thought about this, too. But if I first delete all configurations, no IF showed up at all in the bridged devices tab :(
That sounds good actually. If you then continue to create a bridge device, do you get to chose from all of your interfaces?
Ah, no, that's what I meant: I deleted all configurations, then created a bridge, but was not offered *any* devices to attach :( In the meantime, I connected monitor and keyboard, and tried it with switching the two ethernet IFs, i.e., create the bridge using eth0 and wlan0 (and putting eth1 as external IF). This worked, but still hostapd would not associate me. So this obviously wasn't a crucial part of my problems (an irritating one nevertheless). Will have to stop experimenting now, and continue tomorrow. Still some combinations left to try.... Pit -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
pit wrote:
Per Jessen wrote:
Thought about this, too. But if I first delete all configurations, no IF showed up at all in the bridged devices tab :(
That sounds good actually. If you then continue to create a bridge device, do you get to chose from all of your interfaces?
Ah, no, that's what I meant: I deleted all configurations, then created a bridge, but was not offered *any* devices to attach :(
Hmm, yeah, that's no good. I haven't actually tried this with leap422, maybe I'll experiment with it. You could try just creating one manually - e.g. /etc/sysconfig/network/ifcfg-br1 : BOOTPROTO='static' BRIDGE='yes' BRIDGE_FORWARDDELAY='0' BRIDGE_PORTS='eth0 eth1' BRIDGE_STP='off' BROADCAST='' ETHTOOL_OPTIONS='' IPADDR='' MTU='' NAME='' NETMASK='' NETWORK='' REMOTE_IPADDR='' STARTMODE='auto' USERCONTROL='no' -- Per Jessen, Zürich (0.4°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Tue, 10 Jan 2017 17:08:05 +0100, Per Jessen wrote:
pit wrote:
Per Jessen wrote:
Thought about this, too. But if I first delete all configurations, no IF showed up at all in the bridged devices tab :(
That sounds good actually. If you then continue to create a bridge device, do you get to chose from all of your interfaces?
Ah, no, that's what I meant: I deleted all configurations, then created a bridge, but was not offered *any* devices to attach :(
Hmm, yeah, that's no good. I haven't actually tried this with leap422, maybe I'll experiment with it.
I took my leap422 desktop, added two NICs, fired up yast lan. Created a bridge device, under "bridged devices" I see all three interfaces listed, including the already configured eth0. I added eth1 and eth2 to the bridge: The created config: BOOTPROTO='static' BRIDGE='yes' BRIDGE_FORWARDDELAY='0' BRIDGE_PORTS='eth1 eth2' BRIDGE_STP='off' BROADCAST='' ETHTOOL_OPTIONS='' IPADDR='' MTU='' NAME='' NETMASK='255.255.255.0' NETWORK='' REMOTE_IPADDR='' STARTMODE='auto' /Per -- Posted with pan 0.139 from openSUSE Leap42.2 office34: Cyrix 486DX2/66MHz, 4096Mb RAM, #9 GXE -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/10/2017 02:55 AM, pit wrote:
While the fiber modem does have an WLAN AP, it directly connects to the outside network of our house
Wait, what? That just seems wrong. You sure you have things plugged into the right ports? You didn't mention the brand of fiber modem, or if you have access to its control panel. Are you sure its "outside" and not just on a separate subnet? I do this with a variety of bog standard wifi router/access points, but I know nothing about the shuttle. My modem feeds ONLY my opensuse gateway machine which runs a dhcp server (and other stuff) and also does routing via iptables I turn off dhcp server in the AP. I put it in AP only mode (varies by make). So my wifi is on the same subnet as the rest of my home network. -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
John Andersen wrote:
On 01/10/2017 02:55 AM, pit wrote:
While the fiber modem does have an WLAN AP, it directly connects to the outside network of our house
Wait, what? That just seems wrong.
I agree (as it's not what I'd prefer). But it is correct. My 'modem' is only a bridge (i.e., invisible), and any device gets a fully valid IP address. This is how it works with my provider (bredbandsbolaget, Stockholm). And that was (one of) the reason(s) to put my private network behind my own gateway.
You sure you have things plugged into the right ports? You didn't mention the brand of fiber modem, or if you have access to its control panel.
It only has a power button, a WLAN on/off button, and the phone jack output (for IP telephony). If I didn't need the latter I could directly go without it.
Are you sure its "outside" and not just on a separate subnet?
Well, in my case, yes. The inside net is my own 192.168 subnet, outside is some 85.228 address. When I only connect via the modem, all address there are indeed within a logical subnet. But still device-to-device performance was really bad (streaming HD movie from my computer to TV produced hickups....).
I do this with a variety of bog standard wifi router/access points, but I know nothing about the shuttle.
Well, it is just a small fanless computer that I use as gateway that happens to have a (Realtek) WiFi that I have no other use for than making an access point of it ;^>
My modem feeds ONLY my opensuse gateway machine which runs a dhcp server (and other stuff) and also does routing via iptables
Same here.
I turn off dhcp server in the AP.
Yes, yours is a router, not a bridge as mine. DHCP in my case is done somewhere in the cellar of the building (or even further away) - I have no access to this... Thanks, Pit -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hi, so it finally works. The key issue had been my failure to set up the bridge device properly with yast. I finally did this the old-fashioned manual way by editing/creating the respective ifcfg-{br0,eth0} files and then restarting the network. The configuration of hostapd was then just as described in many online tutorials. In addition, I had to change also the relevant interface information for the firewall and dhcpd, and after restarting both services I can now connect to the access point created that way, get a proper IP address and see all my local network (typing/sending this from the laptop connected via WLAN). :D Thanks to all who contributed information and ideas! All the best, Pit -- Dr. Peter "Pit" Suetterlin http://www.astro.su.se/~pit Institute for Solar Physics Tel.: +34 922 405 590 (Spain) P.Suetterlin@royac.iac.es +46 8 5537 8559 (Sweden) Peter.Suetterlin@astro.su.se -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (6)
-
James Knott -
jdd -
John Andersen -
Per Jessen -
Peter Suetterlin -
pit