From: Aben Siatris <aben@webcom.sk>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] No more bluez.o in 2.6?
Date: Sat, 10 Apr 2004 17:43:00 +0200 [thread overview]
Message-ID: <200404101743.00181.aben@webcom.sk> (raw)
In-Reply-To: <20040408150950.GB5539@magma.epfl.ch>
> > > pppd[3693]: pppd 2.4.1 started by root, uid 0
> > > pppd[3693]: Using interface ppp0
> > > pppd[3693]: Connect: ppp0 <--> /dev/pts/1
> > > dund[3704]: RFCOMM TTY creation failed. Operation
> > >
> > > pppd[3693]: LCP: timeout sending Config-Requests
> > ^---- same error with mi ipaq :))
> > now i use connect to PAN and all working rights.
> >
> > # /usr/bin/pand --listen --role NAP
> > - disabled DHCP in iPAQ, using 192.168.20.2 gateway 192.168.20.1
> > - connect (all ok)
> > - on server - ifconfig bnep0 192.168.20.1 netmask 255.255.255.0
> > - now routing and iptables nat :)
> >
> > all working fine :)
>
> That's sound great, could you give some more details on what sould be
> done?
> pand --listen --role NAP
> OK
> ifconfig bnep0 192.168.20.1 netmask 255.255.255.0
> SIOCSIFADDR: No such device
> bnep0: unknown interface: No such device
> SIOCSIFNETMASK: No such device
>
> And I don't have anything in /udev/bnep, how to create it in dev?
>
> Thank you very much,
ad first, you must make connection.
tip - add ifconfig and iptables to hotplug and
to /etc/init.d/net.bnep0.
tail from /var/messages
Apr 10 17:23:04 gentoo_aben pand[15975]: New connection from 08:00:28:84:C2:E4 bnep0
Apr 10 17:23:04 gentoo_aben default.hotplug[15977]: arguments (net) env (OLDPWD=/ DEVPATH=/class/net/bnep0 PATH=/bin:/sbin:/usr/sbin:/usr/bin ACTION=add PWD=/etc/hotplug HOME=/ SHLVL=2 INTERFACE=bnep0 DEBUG=yes SEQNUM=647 _=/bin/env)
Apr 10 17:23:04 gentoo_aben default.hotplug[15977]: invoke /etc/hotplug/net.agent ()
Apr 10 17:23:04 gentoo_aben net.agent[15977]: script=/etc/init.d/net.bnep0 in action add
Apr 10 17:23:04 gentoo_aben net.agent[15977]: adding bnep0
and now i am in lan and internet with mi ipaq
(sorry for my english :)
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2004-04-10 15:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-07 17:23 [Bluez-users] No more bluez.o in 2.6? Gregoire Favre
2004-04-07 21:43 ` Gregoire Favre
2004-04-08 7:48 ` Aben Siatris
2004-04-08 15:09 ` Gregoire Favre
2004-04-08 16:29 ` Marcel Holtmann
2004-04-10 15:43 ` Aben Siatris [this message]
[not found] ` <20040410160451.GB26618@magma.epfl.ch>
2004-04-10 16:45 ` Aben Siatris
2004-04-10 17:37 ` Gregoire Favre
2004-04-08 9:47 ` Marcel Holtmann
2004-04-08 15:00 ` Gregoire Favre
2004-04-08 16:02 ` Michal Semler (volny.cz)
2004-04-09 12:40 ` Gregoire Favre
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=200404101743.00181.aben@webcom.sk \
--to=aben@webcom.sk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox