From: Pavel Ruzicka <pavouk@pavouk.org>
To: bluez-users@lists.sourceforge.net
Cc: "Sammy" <sammy@autumn.ccl.itri.org.tw>
Subject: Re: [Bluez-users] PAN,just one connected line???
Date: Fri, 6 Aug 2004 09:30:08 +0200 [thread overview]
Message-ID: <200408060930.08633.pavouk@pavouk.org> (raw)
In-Reply-To: <00be01c47b6a$e84062a0$7053608c@ccl.itri.org.tw>
Hello,
> There are four nodes had been connected by pand.
> but after i assign the static IP to every interface,
> the 'ping' command can't work normally besides the line between PANU1 and
> GN(the first connection). I don't know it is normal or i loss some
> configuration ...
this will not work, because your BNEP interfaces are in independent networks
with same IP space. You ha two choices:
1. Routing
----------------
You can give independent IP spaces for BNEP interfaces.
10.0.0.0/30
10.0.0.4/30
10.0.0.8/30
...
It means 10.0.0.1 on BNEP0 on GN, 10.0.0.2 on BNEP0 on PANU1
with mask 255.255.255.252
You must have enabled IP forwarding on GN for connecting between PANUs.
On PANUs it's great to set default gateway to GNs IP address.
2. Bridging
-------------------
You must enable bridge support on GN.
Complete manual is here:
http://bluez.sourceforge.net/contrib/HOWTO-PAN
Best regards,
Pavel Ruzicka
-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2004-08-06 7:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-06 4:07 [Bluez-users] PAN,just one connected line??? Sammy
2004-08-06 7:30 ` Pavel Ruzicka [this message]
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=200408060930.08633.pavouk@pavouk.org \
--to=pavouk@pavouk.org \
--cc=bluez-users@lists.sourceforge.net \
--cc=sammy@autumn.ccl.itri.org.tw \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox