From: Claudio Takahasi <cktakahasi@gmail.com>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] NAP service records attributes
Date: Wed, 6 Apr 2005 11:00:20 -0300 [thread overview]
Message-ID: <e1effdeb050406070077389f4c@mail.gmail.com> (raw)
Hi,
According with Bluetooth PAN Profile specification IP4vSubnet and
IPv6Subnet NAP service record attributeID is a displayable string
containing subnet definition of the network, e.g. 10.0.0.0/8 for
IPv4 and fe80::/48 for IPv6. Based on this informartion I would like
to know if is possible add an extra attribute(IPv4Gateway).
I am working with Bluetooth linux statck(BlueZ). Considering a NAP
scenario, where a PANU connects to the NAP. After establish a PAN, it
is necessary add a route to the default gateway(NAP Bluetooth
interface). However, only the IPv4Subnet is provided and this
information is not enough for IP setup. Attach a DHCP server on NAP
interface or use a standard addressing based on subnet
information(e.g. for 10.0.0.0 the gw should be 10.0.0.1) can solve my
problem, but I want avoid these approachs.
What is the process to submit a profile change to Bluetooth SIG? Is it
feasible add an IPv4Gateway attribute?
Regards,
Claudio
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next reply other threads:[~2005-04-06 14:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-06 14:00 Claudio Takahasi [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-04-01 17:56 [Bluez-users] NAP service records attributes Claudio Takahasi
2005-04-02 5:28 ` scott.meesseman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e1effdeb050406070077389f4c@mail.gmail.com \
--to=cktakahasi@gmail.com \
--cc=bluez-users@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.