Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.os.linux.hardware > #783 > unrolled thread

Linux <--> Win7: via blueTooth?

Back to article view | Back to comp.os.linux.hardware

Contents

  Linux <--> Win7: via blueTooth? no.top.post@gmail.com - 2011-11-08 00:53 +0000
    Re: Linux <--> Win7: via blueTooth? "David H. Lipman" <DLipman~nospam~@Verizon.Net> - 2011-11-07 21:01 -0500
      Re (2): Linux <--> Win7: via blueTooth? no.top.post@gmail.com - 2011-11-08 09:49 +0000
    Re: Linux <--> Win7: via blueTooth? The Natural Philosopher <tnp@invalid.invalid> - 2011-11-08 07:03 +0000
      Re (2): Linux <--> Win7: via blueTooth? no.top.post@gmail.com - 2011-11-08 09:49 +0000
        Re: Re (2): Linux <--> Win7: via blueTooth? The Natural Philosopher <tnp@invalid.invalid> - 2011-11-08 14:31 +0000
          Re (3): Linux <--> Win7: via blueTooth? no.top.post@gmail.com - 2011-11-09 09:08 +0000
    Re: Linux <--> Win7: via blueTooth? Stan Bischof <stan@worldbadminton.com> - 2011-11-08 15:39 +0000
      Re (2): Linux <--> Win7: via blueTooth? no.top.post@gmail.com - 2011-11-09 09:08 +0000
        Re: Re (2): Linux <--> Win7: via blueTooth? Stan Bischof <stan@worldbadminton.com> - 2011-11-09 17:45 +0000

#783 — Linux <--> Win7: via blueTooth?

Even the wiki/S, just give  list/S of various makes and the
incompatibility problems.  This seems very complex.

>  The Toshiba stack supports one of the more comprehensive list of
>  Bluetooth profiles including: [95]SPP, [96]DUN, [97]FAX, [98]LAP,
>  [99]OPP, [100]FTP, [101]HID, [102]HDP, [103]HCRP, [104]PAN,
>  [105]BIP, [106]HSP, [107]HFP (including Skype support), [108]A2DP,
>  [109]AVRCP .................

Has anyone transfered files: linux <--> Win7 ?
My newest Linux is Slak13 with knl 2.6.29.6

== TIA.

[toc] | [next] | [standalone]

#784

From: <no.top.post@gmail.com>

> Even the wiki/S, just give  list/S of various makes and the
> incompatibility problems.  This seems very complex.
>
>>  The Toshiba stack supports one of the more comprehensive list of
>>  Bluetooth profiles including: [95]SPP, [96]DUN, [97]FAX, [98]LAP,
>>  [99]OPP, [100]FTP, [101]HID, [102]HDP, [103]HCRP, [104]PAN,
>>  [105]BIP, [106]HSP, [107]HFP (including Skype support), [108]A2DP,
>>  [109]AVRCP .................
>
> Has anyone transfered files: linux <--> Win7 ?
> My newest Linux is Slak13 with knl 2.6.29.6
>

If the Linux BlueTooth supports PAN (Personal Area Networking) then you should be able to 
peer Linux with Windows 7.  You'll have to setup each TCP/IP stack on both platforms for 
the same network (ex: 192.168.2.x)



-- 
Dave
Multi-AV Scanning Tool - http://multi-av.thespykiller.co.uk
http://www.pctipp.ch/downloads/dl/35905.asp 

[toc] | [prev] | [next] | [standalone]

#787 — Re (2): Linux <--> Win7: via blueTooth?

In article <j9a2hn030ct@news7.newsguy.com>, "David H. Lipman" <DLipman~nospam~@Verizon.Net> wrote: 

> From: <no.top.post@gmail.com>
> 
> > Even the wiki/S, just give  list/S of various makes and the
> > incompatibility problems.  This seems very complex.
> >
> >>  The Toshiba stack supports one of the more comprehensive list of
> >>  Bluetooth profiles including: [95]SPP, [96]DUN, [97]FAX, [98]LAP,
> >>  [99]OPP, [100]FTP, [101]HID, [102]HDP, [103]HCRP, [104]PAN,
> >>  [105]BIP, [106]HSP, [107]HFP (including Skype support), [108]A2DP,
> >>  [109]AVRCP .................
> >
> > Has anyone transfered files: linux <--> Win7 ?
> > My newest Linux is Slak13 with knl 2.6.29.6
> >
> 
> If the Linux BlueTooth supports PAN (Personal Area Networking) then you should be able to 
> peer Linux with Windows 7.  You'll have to setup each TCP/IP stack on both platforms for 
> the same network (ex: 192.168.2.x)
> 
The `man` that I'm looking at talk at the level of:
Enable authentication, Enable page & inquiry scan...

I need to get the 2 devices communicating before I decide *IF*
I want to learn about setting up network routing tables.

== TIA
> -- 
> Dave
> Multi-AV Scanning Tool - http://multi-av.thespykiller.co.uk
> http://www.pctipp.ch/downloads/dl/35905.asp 

[toc] | [prev] | [next] | [standalone]

#785

no.top.post@gmail.com wrote:
> Even the wiki/S, just give  list/S of various makes and the
> incompatibility problems.  This seems very complex.
> 
>>  The Toshiba stack supports one of the more comprehensive list of
>>  Bluetooth profiles including: [95]SPP, [96]DUN, [97]FAX, [98]LAP,
>>  [99]OPP, [100]FTP, [101]HID, [102]HDP, [103]HCRP, [104]PAN,
>>  [105]BIP, [106]HSP, [107]HFP (including Skype support), [108]A2DP,
>>  [109]AVRCP .................
> 
> Has anyone transfered files: linux <--> Win7 ?

sure. If there is an IP link then samba on te linux allows it to act as 
a Windoesn't file server.

The SMB client is NOT os smart in Linux, but can be made to work.

> My newest Linux is Slak13 with knl 2.6.29.6
> 
> == TIA.
> 

[toc] | [prev] | [next] | [standalone]

#788 — Re (2): Linux <--> Win7: via blueTooth?

In article <j9ak7a$4kc$5@news.albasani.net>, The Natural Philosopher <tnp@invalid.invalid> wrote: 

> no.top.post@gmail.com wrote:
> > Even the wiki/S, just give  list/S of various makes and the
> > incompatibility problems.  This seems very complex.
> > 
> >>  The Toshiba stack supports one of the more comprehensive list of
> >>  Bluetooth profiles including: [95]SPP, [96]DUN, [97]FAX, [98]LAP,
> >>  [99]OPP, [100]FTP, [101]HID, [102]HDP, [103]HCRP, [104]PAN,
> >>  [105]BIP, [106]HSP, [107]HFP (including Skype support), [108]A2DP,
> >>  [109]AVRCP .................
> > 
> > Has anyone transfered files: linux <--> Win7 ?
> 
> sure. If there is an IP link then samba on te linux allows it to act as 
> a Windoesn't file server.
> 
> The SMB client is NOT os smart in Linux, but can be made to work.
> 
By using fd0 & USBstik, I've avoided looking into samba.
Can you list the sequential hurdles that need to be confirmed?
Like for an old dialup, they may be:
-> modem LED shows powered-up 
-> modem LEDs change shows signal received from serial port
-> AT-string set to sound dial-tone & dialing shows ...

Apparently an early step to do before considering `samba`, 
is confirmation that both sides detect each other.
What's the easiest way to do that ?

> > My newest Linux is Slak13 with knl 2.6.29.6
> > 
== TIA.

[toc] | [prev] | [next] | [standalone]

#790 — Re: Re (2): Linux <--> Win7: via blueTooth?

no.top.post@gmail.com wrote:
> In article <j9ak7a$4kc$5@news.albasani.net>, The Natural Philosopher <tnp@invalid.invalid> wrote: 
> 
>> no.top.post@gmail.com wrote:
>>> Even the wiki/S, just give  list/S of various makes and the
>>> incompatibility problems.  This seems very complex.
>>>
>>>>  The Toshiba stack supports one of the more comprehensive list of
>>>>  Bluetooth profiles including: [95]SPP, [96]DUN, [97]FAX, [98]LAP,
>>>>  [99]OPP, [100]FTP, [101]HID, [102]HDP, [103]HCRP, [104]PAN,
>>>>  [105]BIP, [106]HSP, [107]HFP (including Skype support), [108]A2DP,
>>>>  [109]AVRCP .................
>>> Has anyone transfered files: linux <--> Win7 ?
>> sure. If there is an IP link then samba on te linux allows it to act as 
>> a Windoesn't file server.
>>
>> The SMB client is NOT os smart in Linux, but can be made to work.
>>
> By using fd0 & USBstik, I've avoided looking into samba.
> Can you list the sequential hurdles that need to be confirmed?
> Like for an old dialup, they may be:
> -> modem LED shows powered-up 
> -> modem LEDs change shows signal received from serial port
> -> AT-string set to sound dial-tone & dialing shows ...
> 
> Apparently an early step to do before considering `samba`, 
> is confirmation that both sides detect each other.
> What's the easiest way to do that ?

ping is a good start..

not sure if boxes are wired net, wifi or whether this here blue tooth 
bloke is in the way..


> 
>>> My newest Linux is Slak13 with knl 2.6.29.6
>>>
> == TIA.
> 
> 

[toc] | [prev] | [next] | [standalone]

#793 — Re (3): Linux <--> Win7: via blueTooth?

In article <j9beg8$ucq$1@news.albasani.net>, The Natural Philosopher <tnp@invalid.invalid> wrote: 

> no.top.post@gmail.com wrote:
> > In article <j9ak7a$4kc$5@news.albasani.net>, The Natural Philosopher <tnp@invalid.invalid> wrote: 
> > 
> >> no.top.post@gmail.com wrote:
> >>> Even the wiki/S, just give  list/S of various makes and the
> >>> incompatibility problems.  This seems very complex.
> >>>
> >>>>  The Toshiba stack supports one of the more comprehensive list of
> >>>>  Bluetooth profiles including: [95]SPP, [96]DUN, [97]FAX, [98]LAP,
> >>>>  [99]OPP, [100]FTP, [101]HID, [102]HDP, [103]HCRP, [104]PAN,
> >>>>  [105]BIP, [106]HSP, [107]HFP (including Skype support), [108]A2DP,
> >>>>  [109]AVRCP .................
> >>> Has anyone transfered files: linux <--> Win7 ?
> >> sure. If there is an IP link then samba on te linux allows it to act as 
> >> a Windoesn't file server.
> >>
> >> The SMB client is NOT os smart in Linux, but can be made to work.
> >>
> > By using fd0 & USBstik, I've avoided looking into samba.
> > Can you list the sequential hurdles that need to be confirmed?
> > Like for an old dialup, they may be:
> > -> modem LED shows powered-up 
> > -> modem LEDs change shows signal received from serial port
> > -> AT-string set to sound dial-tone & dialing shows ...
> > 
> > Apparently an early step to do before considering `samba`, 
> > is confirmation that both sides detect each other.
> > What's the easiest way to do that ?
> 
> ping is a good start..
> 
If it doesn't connect automagically, would I get the IP for ping from the 'partner'?
Before `ping`, there's <what dev is it: via `dmesg`, `lsusb`..etc>,
which opens a whole canOworms.

> not sure if boxes are wired net, wifi or whether this here blue tooth 
> bloke is in the way.
> 
> > 
> >>> My newest Linux is Slak13 with knl 2.6.29.6
> >>>
> > == TIA.

[toc] | [prev] | [next] | [standalone]

#791

In comp.os.linux.misc no.top.post@gmail.com wrote:
> Even the wiki/S, just give  list/S of various makes and the
> incompatibility problems.  This seems very complex.
> 
>>  The Toshiba stack supports one of the more comprehensive list of
>>  Bluetooth profiles including: [95]SPP, [96]DUN, [97]FAX, [98]LAP,
>>  [99]OPP, [100]FTP, [101]HID, [102]HDP, [103]HCRP, [104]PAN,
>>  [105]BIP, [106]HSP, [107]HFP (including Skype support), [108]A2DP,
>>  [109]AVRCP .................
> 
> Has anyone transfered files: linux <--> Win7 ?
> My newest Linux is Slak13 with knl 2.6.29.6
> 

haven't actually done it, but PAN is available natively by
default on the Windows side and on the linux side all
you should have to do is start the bluetooth service,
a PAN daemon, and set up an IP address. Odds are you won't
have to mess with physical level transport or the like
unless you have something really ancient that's not
incompatible with other hardware on the other side.

I expect that you'll be setting a corresponding IP address
on the Windows side via the command line ( if you're
familiar with it ) or via the Control Panel ( if you
prefer the GUI ).

Once basic network is established you're home free- just use
whatever transport mechanism you want. Even old insecure ftp
would be fine since you're p-p anyhow.

This should be pretty easy. Of course don't be surprised when
you find a very slow connection, as bluetooth is NOT fast. If
it ends up being too slow just fire up wifi or plug in a network
cable and you'll be many tiems faster.

Stan

[toc] | [prev] | [next] | [standalone]

#792 — Re (2): Linux <--> Win7: via blueTooth?

In article <4eb94d33$0$1734$742ec2ed@news.sonic.net>, Stan Bischof <stan@worldbadminton.com> wrote: 

> In comp.os.linux.misc no.top.post@gmail.com wrote:
> > Even the wiki/S, just give  list/S of various makes and the
> > incompatibility problems.  This seems very complex.
> > 
> > Has anyone transfered files: linux <--> Win7 ?
> > My newest Linux is Slak13 with knl 2.6.29.6
> > 
> 
> haven't actually done it, but PAN is available natively by
> default on the Windows side and on the linux side all
> you should have to do is start the bluetooth service,
> a PAN daemon, and set up an IP address. Odds are you won't
> have to mess with physical level transport or the like
> unless you have something really ancient that's not
> incompatible with other hardware on the other side.
> 
> I expect that you'll be setting a corresponding IP address
> on the Windows side via the command line ( if you're
> familiar with it ) or via the Control Panel ( if you
> prefer the GUI ).
> 
> Once basic network is established you're home free- just use
> whatever transport mechanism you want. Even old insecure ftp
> would be fine since you're p-p anyhow.
> 
> This should be pretty easy. Of course don't be surprised when
> you find a very slow connection, as bluetooth is NOT fast. If
> it ends up being too slow just fire up wifi or plug in a network
> cable and you'll be many tiems faster.
> 
> Stan
Thanks, I thought the kiddies automagically just connected
their mouse, earphones ..etc. by bluetooth.

I had to buy this Win7-device because my wireless-modem connection
had no linux driver, and ONCE I confirmed that its wifi could just detect
nearby transmitters and connect automatically. So I expected bluetooth
to be similar.

Can I familiarise my self with bluetooth, from Win7 perspective,
without messing my new linux setup, by plugging the dongle into
the Win7-netbook, which HAS built-in bluetooth?
Ie. test it only on the Win7-netbook?

I'm confused, that the dongle came with a mini-CD,
and the netbook wanted to go on-line: apparently to fetch driver/S.

[toc] | [prev] | [next] | [standalone]

#796 — Re: Re (2): Linux <--> Win7: via blueTooth?

In comp.os.linux.misc no.top.post@gmail.com wrote:
> In article <4eb94d33$0$1734$742ec2ed@news.sonic.net>, Stan Bischof <stan@worldbadminton.com> wrote: 
> 
>> 
>> This should be pretty easy. Of course don't be surprised when
>> you find a very slow connection, as bluetooth is NOT fast. If
>> it ends up being too slow just fire up wifi or plug in a network
>> cable and you'll be many tiems faster.
>> 
>> Stan
> Thanks, I thought the kiddies automagically just connected
> their mouse, earphones ..etc. by bluetooth.
> 

They do- but that's different from what you are asking.

Bluetooth is just a communications channel, like "wifi"
or "ethernet" that is used by various programs to
connect and share information of one form or another.
However, just because you have two bluetooth devices
( wifi devices, ethernet devices, etc ) that doesn't
mean that they can talk to each other- it just means
that they have the _hardware_ and drivers needed
to talk to each other.

What's needed is software on both ends that speaks
the same language ( protocol, like MSTP, HTTP, etc )
and is set up to connect. Your computer has a peripheral
driver ( software ) that knows how to communicate
with the software in keyboards, for instance. Thus the
keyboard and computer can automatically set up a connection
and send the needed data back and forth.

You are asking for two computers to send files back
and forth- a much more complex task. Now if you had
software ( which you don't by default ) on both machines
that understood bluetooth and shared a common protocol
for exchanging files and file system information and the like
then what you want would indeed be doable. Since you don't
the next best thing is to use ethernet-over-bluetooth,
set up IP addresses and then jump into ssh or ftp
or whatever for the actual file transfers.

That is, seamless PAN is possible- but it isn't implemented
in any sort of ubiquitous manner that makes it automatic.

Stan

[toc] | [prev] | [standalone]

Back to top | Article view | comp.os.linux.hardware

csiph-web