Re: Is there way to get filename for specific LBA?

2011-09-01 Thread Doug Hardie

On 31 August 2011, at 20:50, Carl Johnson wrote:

 per...@pluto.rain.com writes:
 
 Robert Bonomi bon...@mail.r-bonomi.com wrote:
 
 Aug 31 05:13:24 da kernel: ad6: WARNING - READ_DMA UDMA ICRC
 error (retrying request) LBA=107491647
 ... I looked at bsdlabel a   it's partition f, /home. But what
 is the file name?
 
 There's *no* easy way to find out.  You'll have to grovel through
 all the filesystem metadata, and the layers of index blocks for
 every file until you find the 'rgiht' one.
 
 This is what icheck -B was for, but icheck(8) no longer exists and
 that particular bit of functionality does not seem to be provided in
 fsck(8).
 
 One current userland utility (other than fsck) which does know
 how to grovel through the metadata and index blocks is dump(8),
 but you'd have to hack on it to report which inode was using a
 particular block.
 
 It looks like the best bet would be fsdb, assuming that it is a UFS
 file system.  That does have a 'findblk' command to find a file
 containing a block, but you would need to calculate the block offset in
 the filesystem first.  It doesn't look like it would be easy, as was
 said earlier.

I created a utility some years ago that did that for UFS.  I believe it works 
for UFS2 but haven't verified it.  If you want to try it, send me a note and 
I'll ship you the code direct.

-- Doug___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Is there way to get filename for specific LBA?

2011-09-01 Thread Polytropon
On Wed, 31 Aug 2011 20:50:18 -0700, Carl Johnson wrote:
 per...@pluto.rain.com writes:
  One current userland utility (other than fsck) which does know
  how to grovel through the metadata and index blocks is dump(8),
  but you'd have to hack on it to report which inode was using a
  particular block.
 
 It looks like the best bet would be fsdb, assuming that it is a UFS
 file system.  That does have a 'findblk' command to find a file
 containing a block, but you would need to calculate the block offset in
 the filesystem first.  It doesn't look like it would be easy, as was
 said earlier.

Recently I had a similar problem with a disk (500GB SATA,
/dev/ad6 attached to controller ata3, one UFS data partition)
that had errors when accessing certain files or directories
like

TIMEOUT - READ_DMA48 retrying (1 retry left) LBA=419149408

or

WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=9488927

Then also gvfs_done errors were displayed, and the disk then
magically disappeared.

On system startup, fsck failed:

unknown: TIMEOUT - READ_DMA48 retrying (1 retry left) LBA=419149408
ata3: timeout waiting to issue command
ata3: error issuing READ_DMA48 command

There were

CANNOT READ BLK: 419149408
UNEXPECTED SOFT UPDATE INCONSISTENCY

and several more of such errors. The summary states:

THE FOLLOWING DISK SECTORS COULD NOT BE READ: 419149408, 419149409, 419149410, 4
19149411, 419149412, 419149413, 419149414, 419149415, 419149416, 419149417, 4191
49418, 419149419, 419149420, 419149421, 419149422, 419149423, 419149424, 4191494
25, 419149426, 419149427, 419149428, 419149429, 419149430, 419149431, 419149432,
 419149433, 419149434, 419149435, 419149436, 419149437, 419149438, 419149439, 41
9149440, 419149441, 419149442, 419149443, 419149444, 419149445, 419149446, 41914
9447, 419149448, 419149449, 419149450, 419149451, 419149452, 419149453, 41914945
4, 419149455, 419149456, 419149457, 419149458, 419149459, 419149460, 419149461,
419149462, 419149463, 419149464, 419149465, 419149466, 419149467, 419149468, 419
149469, 419149470, 419149471, 419149472, 419149473, 419149474, 419149475, 419149
476, 419149477, 419149478, 419149479, 419149480, 419149481, 419149482, 419149483
, 419149484, 419149485, 419149486, 419149487, 419149488, 419149489, 419149490, 4
19149491, 419149492, 419149493, 419149494, 419149495, 419149496, 419149497, 4191
49498, 419149499, 419149500, 419149501, 419149502, 419149503, 419149504, 4191495
05, 419149506, 419149507, 419149508, 419149509, 419149510, 419149511, 419149512,
 419149513, 419149514, 419149515, 419149516, 419149517, 419149518, 419149519, 41
9149520, 419149521, 419149522, 419149523, 419149524, 419149525, 419149526, 41914
9527, 419149528, 419149529, 419149530, 419149531, 419149532, 419149533, 41914953
4, 419149535,

CANNOT READ BLK: 419525632
UNEXPECTED SOFT UPDATE INCONSISTENCY

THE FOLLOWING DISK SECTORS COULD NOT BE READ: 419525632, 419525633, 419525634, 4
19525635, 419525636, 419525637, 419525638, 419525639, 419525640, 419525641, 4195
25642, 419525643, 419525644, 419525645, 419525646, 419525647, 419525648, 4195256
49, 419525650, 419525651, 419525652, 419525653, 419525654, 419525655, 419525656,
 419525657, 419525658, 419525659, 419525660, 419525661, 419525662, 419525663,
CYLINDER GROUP 1115: BAD MAGIC NUMBER
UNEXPECTED SOFT UPDATE INCONSISTENCY

After that, fsck suggested to re-run the procedure because
the file system couldn't be marked clean. I just had a look
at the device files and...

# ll /dev/ad*
crw-r-  1 root  operator0, 108 Aug 23 01:40 /dev/ad4
crw-r-  1 root  operator0, 113 Aug 23 01:40 /dev/ad4s1
crw-r-  1 root  operator0, 116 Aug 23 03:40 /dev/ad4s1a
crw-r-  1 root  operator0, 117 Aug 23 01:40 /dev/ad4s1b
crw-r-  1 root  operator0, 118 Aug 23 03:40 /dev/ad4s1d
crw-r-  1 root  operator0, 119 Aug 23 03:40 /dev/ad4s1e
crw-r-  1 root  operator0, 120 Aug 23 03:40 /dev/ad4s1f
crw-r-  1 root  operator0, 121 Aug 23 03:40 /dev/ad4s1g
crw-r-  1 root  operator0, 122 Aug 23 03:40 /dev/ad4s1h

Tadaa! You see: /dev/ad6 isn't _there_ anymore!

I rebooted the system, skipped _any_ checks of /dev/ad6 and
carefully mounted it (being given the correct warning):

# mount -t ufs -o ro /dev/ad6 /mnt

I could then browse the disk, but when entering some directories,
error messaged (as above) did show up again. Then the disk was
empty, and finally it was gone.

As I had the original data on another disk, it wasn't a data
loss for me, but a very interesting behaviour of a disk!

When browsing the disk with the Midnight Commander, many files
were size 0, prefixed with !, and colored red. This indicates
that they couldn't be stat()ed. This traditionally shows that
the file system is damaged. A dying disk could be the reason.
But malfunctioning controllers and software errors also could
be, even though it's often the _disk_ that needs replacing.



With this 

Re: Resetting bootloader on a CF

2011-09-01 Thread Polytropon
On Wed, 31 Aug 2011 23:47:22 +0200, bsd wrote:
 Part of the solution seems to be : 
 
 1. Mount the CF on a FBSD 
 2. Initialize the bootloader with : 
 
 # fdisk -B /dev/disk

Erm... You should _not_ mount (as in /sbin/mount) the CF
in order to change MBR data; mounting should be restricted
to its humano-mechanical part. :-)



 3. This is where I need you help… 
 
 
 How can I re-install a boot loader ? 
 
 Should I use the command : 
 
 # fdisk -B -b /boot/boot0 device
 
 
 Any other suggestion, guidance will be welcome. 

You can use sysinstall for that: Configure, select the CF card
to work on, don't chance anything with the slices in the fdisk
editor, just make sure the slice is marked active, and in the
next step, select the default MBR to be written.

The command line way should be:

# fdisk -BI /dev/da0
# fdisk -B -b /boot/mbr /dev/da0

(Assumption: /dev/da0 is the CF card.)

Note that the first step will re-initialize the card. If you don't
want to build it from scratch, i. e. _only_ modify the MBR, the
second command should do it.

See man fdisk for details on the fdisk commands.





-- 
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: printing to Kyocera FS-1030D

2011-09-01 Thread Conrad J. Sabatier
On Wed, 3 Aug 2011 13:22:51 -0500
Ryan Coleman edi...@d3photography.com wrote:

 Screw off. Top posting is actually a default in the mail software
 community. And I will always do it.

Thanks for the warning.

 More annoying: Extra spaces and not removing the cruff from the
 bottom of emails. And condescending asshats.

Even more annoying: people who respond rudely to a politely-worded
reminder re: basic netiquette.

Fare thee well.

 On Aug 3, 2011, at 1:08 PM, Robert Bonomi wrote:
 
  
  Pierre, please do not 'top post' replies -- it makes the 'logic' of
  the message hard to follow,  to wit:

[snip]

-- 
Conrad J. Sabatier
conr...@cox.net
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Resetting bootloader on a CF

2011-09-01 Thread Michael Sierchio
It occurs to me that there may be a couple of other wrinkles.  There
are kernel boot parameters that tell which kind of console to use, and
there are switches you can twiddle in /boot/loader.conf, notably

#console=vidconsole   # A comma separated list of console(s)

   console   (``vidconsole'') ``comconsole'' selects serial console,
 ``vidconsole'' selects the video console, and
 ``nullconsole'' selects a mute console (useful for sys-
 tems with neither a video console nor a serial port).

Also make sure that /etc/ttys launches a getty process for whatever
console you are using.   I.e., make sure it doesn't look like this one
(mine) - make sure that at least ttyv0 is on.

console noneunknown off secure
#
ttyv0   /usr/libexec/getty Pc cons25  off secure
# Virtual terminals
ttyv1   /usr/libexec/getty Pc cons25  off secure
ttyv2   /usr/libexec/getty Pc cons25  off secure
ttyv3   /usr/libexec/getty Pc cons25  off secure
ttyv4   /usr/libexec/getty Pc cons25  off secure
ttyv5   /usr/libexec/getty Pc cons25  off secure
ttyv6   /usr/libexec/getty Pc cons25  off secure
ttyv7   /usr/libexec/getty Pc cons25  off secure
ttyv8   /usr/local/bin/xdm -nodaemon  xterm   off secure
# Serial terminals
# The 'dialup' keyword identifies dialin lines to login, fingerd etc.
ttyd0   /usr/libexec/getty std.9600   dialup  on  secure

On Thu, Sep 1, 2011 at 12:59 AM, Polytropon free...@edvax.de wrote:
 On Wed, 31 Aug 2011 23:47:22 +0200, bsd wrote:
 Part of the solution seems to be :

 1. Mount the CF on a FBSD
 2. Initialize the bootloader with :

 # fdisk -B /dev/disk

 Erm... You should _not_ mount (as in /sbin/mount) the CF
 in order to change MBR data; mounting should be restricted
 to its humano-mechanical part. :-)



 3. This is where I need you help…


 How can I re-install a boot loader ?

 Should I use the command :

 # fdisk -B -b /boot/boot0 device


 Any other suggestion, guidance will be welcome.

 You can use sysinstall for that: Configure, select the CF card
 to work on, don't chance anything with the slices in the fdisk
 editor, just make sure the slice is marked active, and in the
 next step, select the default MBR to be written.

 The command line way should be:

        # fdisk -BI /dev/da0
        # fdisk -B -b /boot/mbr /dev/da0

 (Assumption: /dev/da0 is the CF card.)

 Note that the first step will re-initialize the card. If you don't
 want to build it from scratch, i. e. _only_ modify the MBR, the
 second command should do it.

 See man fdisk for details on the fdisk commands.





 --
 Polytropon
 Magdeburg, Germany
 Happy FreeBSD user since 4.0
 Andra moi ennepe, Mousa, ...
 ___
 freebsd-questions@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Problem reading from tape drive -- SOLVED, or at least a workaround

2011-09-01 Thread Renee Gehlbach



Is there any way I could test to make sure this is in fact what's happening?

Try writing several files to the tape,  each in it's own operation,
and issue a 'mt -bsf' between each operation.

THEN try reading from the tape.  with just successive 'read' operations.
   *NO* 'mt' positioning

If everything is working 'properly', there will be *ONLY*ONE* file on the tape.

If there is an O/S failure to 'backspace on close' you'll get all the original
files, one on each read attempt.

If the O/S has a _complete_ 'failure to backspace', you'll get a tape that
functions identially to your earlier tests -- you can find all the file
by 'mt -fsf' between reads

Other things to try.
   1) *write* a multi-file tape under Unbuntu, and try to read it under FreeBSD.
   2) *write* a multi-file tape under FreeBSD, and try to read it under Unbuntu.
   3) If there are read issues, see if  the 'mt -fsf' hack allows you to
  find everything.

OK, it's definitely an O/S failure to backspace on close, because the 
tape does read properly when I manually backspace after each file.

   Unfortunately, the workaround of running mt -fsf
after every file read

if it worked, 'mf -bsf' after every _write_ would be a better solution.grin
But it probably suffers from the same 'not really usable' defect.
*cheers* And YES That's a usable workaround!  Luckily enough, Bacula 
will run a script after each backup job, all I'll have to do is add a mt 
-bsf command to that script!



_I_ have no clue what 'bacula' is -- sounds sort-of like a Transylvanian
back-up utility.  One with 'fangs' init, and issues with mirrors.grin
Close!  It's a multi-platform client-server backup application.  Its 
tagline used to be something like Comes in the night, and sucks the 
essence from your computers.  When I went to check the precise wording, 
though, it's no longer on their logo.  I guess someone objected.too 
bad, I got a kick from that tagline.  I find it to be a great 
open-source replacement for backup exec.  I can have the Bacula server 
and tape drive on one FreeBSD or Linux box, and install clients on all 
of my other FreeBSD  Linux servers, and Linux  Windows desktops to 
back them all up to that one tape drive.



Thanks for all of your help!!
Renee
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


rsync connection to Windows 2008 Server

2011-09-01 Thread jhall
I have run into a problem that I cannot find the answer to using Google 
and I am hoping someone has seen this before. 

I am connecting to a Windows 2008 server running cwRsync as a daemon.  One 
of my six sites will not connect to the server.  No error messages are 
seen in the cwRsync log file or the Event Viewer on the Windows 2008 
computer. 

My network configuration is as follows.

STL --WAN-- Firewall --IPsec Tunnel -- 192.168.100.56.

On the remote computer, using the following command line, and I receive 
the following messages. 
rsync -avz  /home 192.168.100.56::Homes
rsync: read error: Connection reset by peer (54)
rsync error: error in rsync protocol data stream (code 12) at io.c(604) 
[sender=2.6.9] 

Looking at tcpdump, I think the connection is started, but the computer on 
my end is not responding after a certain time. 

12:00:17.817759 IP (tos 0x0, ttl  64, id 64973, offset 0, flags [DF], 
proto: TCP (6), length: 64) N-ST-LOUIS.65460  192.168.100.56.rsync: S, 
cksum 0x9834 (correct), 1279331061:1279331061(0) win 65535 mss 
1460,nop,wscale 1,nop,nop,timestamp 486332914 0,sackOK,eol 
12:00:17.817891 IP (tos 0x0, ttl  64, id 64973, offset 0, flags [DF], 
proto: TCP (6), length: 64) N-ST-LOUIS.65460  192.168.100.56.rsync: S, 
cksum 0x9834 (correct), 1279331061:1279331061(0) win 65535 mss 
1460,nop,wscale 1,nop,nop,timestamp 486332914 0,sackOK,eol 
12:00:17.871976 IP (tos 0x0, ttl  63, id 11982, offset 0, flags [none], 
proto: TCP (6), length: 52) 192.168.100.56.rsync  N-ST-LOUIS.65460: S, 
cksum 0xb379 (correct), 992395985:992395985(0) ack 1279331062 win 5640 
mss 1380,nop,nop,sackOK,nop,wscale 0 
12:00:17.872064 IP (tos 0x0, ttl  64, id 64974, offset 0, flags [DF], 
proto: TCP (6), length: 40) N-ST-LOUIS.65460  192.168.100.56.rsync: ., 
cksum 0x889c (correct), 1:1(0) ack 1 win 33120 
12:00:17.872233 IP (tos 0x0, ttl  64, id 64974, offset 0, flags [DF], 
proto: TCP (6), length: 40) N-ST-LOUIS.65460  192.168.100.56.rsync: ., 
cksum 0x889c (correct), 1:1(0) ack 1 win 33120 
12:00:17.872280 IP (tos 0x0, ttl  64, id 64975, offset 0, flags [DF], 
proto: TCP (6), length: 52) N-ST-LOUIS.65460  192.168.100.56.rsync: P, 
cksum 0x0923 (correct), 1:13(12) ack 1 win 33120 
12:00:17.872349 IP (tos 0x0, ttl  64, id 64975, offset 0, flags [DF], 
proto: TCP (6), length: 52) N-ST-LOUIS.65460  192.168.100.56.rsync: P, 
cksum 0x0923 (correct), 1:13(12) ack 1 win 33120 
12:00:17.872592 IP (tos 0x0, ttl  63, id 11984, offset 0, flags [none], 
proto: TCP (6), length: 40) 192.168.100.56.rsync  N-ST-LOUIS.65460: ., 
cksum 0x0f00 (correct), 1:1(0) ack 13 win 64240 
12:00:38.882477 IP (tos 0x0, ttl  63, id 12123, offset 0, flags [none], 
proto: TCP (6), length: 40) 192.168.100.56.rsync  N-ST-LOUIS.65460: R, 
cksum 0x4848 (correct), 992395986:992395986(0) win 4344 

For testing, my firewall rules were set to pass in quick all, pass out 
quick all.  The remote server is at the end of an ipsec tunnel maintained 
by racoon.  Ping times are reasonable 53ms between sites.  What really 
baffles me is the other five (5) sites I maintain are connecting without 
any problems.  All are running the same version of rsync. 

Any suggestions would be greatly appreciated.

Thanks,


Jay

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re:rsync connection to Windows 2008 Server

2011-09-01 Thread Sergio Tam
2011/9/1  jh...@socket.net:
 I have run into a problem that I cannot find the answer to using Google
 and I am hoping someone has seen this before.

 I am connecting to a Windows 2008 server running cwRsync as a daemon.  One
 of my six sites will not connect to the server.  No error messages are
 seen in the cwRsync log file or the Event Viewer on the Windows 2008
 computer.

 My network configuration is as follows.

 STL --WAN-- Firewall --IPsec Tunnel -- 192.168.100.56.

 On the remote computer, using the following command line, and I receive
 the following messages.
 rsync -avz  /home 192.168.100.56::Homes
 rsync: read error: Connection reset by peer (54)
 rsync error: error in rsync protocol data stream (code 12) at io.c(604)
 [sender=2.6.9]

 Looking at tcpdump, I think the connection is started, but the computer on
 my end is not responding after a certain time.

 12:00:17.817759 IP [...]


http://www.itefix.no/i2/node/11042

http://lists.samba.org/archive/rsync/2003-December/008119.html


Regards
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Wrong directory of FreeBSD 9.0-BETA2

2011-09-01 Thread Alvaro Castillo
i386 and amd64

ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/i386/ISO-IMAGES/9.0/
ftp://ftp.freebsd.org/pub/FreeBSD/releases/amd64/amd64/ISO-IMAGES/9.0/

Should be on?
ftp://ftp.freebsd.org/pub/FreeBSD/ISO-IMAGES-i386
ftp://ftp.freebsd.org/pub/FreeBSD/ISO-IMAGES-amd64

Cheers!

--
netSys--
http://www.byteandbit.info
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re[2]: vpn using pptpclient in FreeBSD

2011-09-01 Thread Коньков Евгений
Здравствуйте, Marco.

Вы писали 31 августа 2011 г., 23:14:14:

MB On Wed, 31 Aug 2011, the wise Mike Tancsa wrote:

 use mpd5 from the ports. It is well supported and works very well both
 as a client and server.

 There is a sample config in the mpd.conf.example where all you need to
 do is change the userid and passwd and server IP...

 pptp_client:
 #
 # PPTP client: only outgoing calls, auto reconnect,
 # ipcp-negotiated address, one-sided authentication,
 # default route points on ISP's end
 #

create bundle static B1
set iface route default
set ipcp ranges 0.0.0.0/0 0.0.0.0/0

create link static L1 pptp
set link action bundle B1
set auth authname MyLogin
set auth password MyPass
set link max-redial 0
set link mtu 1460
set link keep-alive 20 75
set pptp peer 1.2.3.4
set pptp disable windowing
open

MB I used the mpd.conf above but mpd5 doesn't work either. It looks like it
MB makes a connection but I don't have a vpn connection and it didn't log in.

MB I do get a lot of output though:

MB ...
MB process 9290 started, version 5.5 (r...@yokozuna.lan 17:08 30-Jul-2011)
MB CONSOLE: listening on 127.0.0.1 5005
MB web: listening on 0.0.0.0 5006
MB [B1] Bundle: Interface ng0 created
MB [L1] [L1] Link: OPEN event
MB [L1] LCP: Open event
MB [L1] LCP: state change Initial -- Starting
MB [L1] LCP: LayerStart
MB [L1] PPTP call successful
MB [L1] Link: UP event
MB [L1] LCP: Up event
MB [L1] LCP: state change Starting -- Req-Sent
MB [L1] LCP: SendConfigReq #1
MB [L1]   ACFCOMP
MB [L1]   PROTOCOMP
MB [L1]   ACCMAP 0x000a
MB [L1]   MRU 1500
MB [L1]   MAGICNUM 1b3bd364
MB [L1] LCP: SendConfigReq #2
MB [L1]   ACFCOMP
MB [L1]   PROTOCOMP
MB [L1]   ACCMAP 0x000a
MB [L1]   MRU 1500
MB [L1]   MAGICNUM 1b3bd364
MB [L1] LCP: rec'd Configure Reject #2 (Req-Sent)
MB [L1]   ACFCOMP
MB [L1]   PROTOCOMP
MB [L1] LCP: SendConfigReq #3
MB [L1]   ACCMAP 0x000a
MB [L1]   MRU 1500
MB [L1]   MAGICNUM 1b3bd364
MB [L1] LCP: rec'd Configure Nak #3 (Req-Sent)
MB [L1]   ACCMAP 0x000a
MB [L1] LCP: SendConfigReq #4
MB [L1]   ACCMAP 0x000a
MB [L1]   MRU 1500
MB [L1]   MAGICNUM 1b3bd364
MB [L1] LCP: rec'd Configure Ack #4 (Req-Sent)
MB [L1]   ACCMAP 0x000a
MB [L1]   MRU 1500
MB [L1]   MAGICNUM 1b3bd364
MB [L1] LCP: state change Req-Sent -- Ack-Rcvd
MB [L1] LCP: rec'd Configure Request #1 (Ack-Rcvd)
MB [L1]   AUTHPROTO CHAP MSOFTv2
MB [L1] LCP: SendConfigAck #1
MB [L1]   AUTHPROTO CHAP MSOFTv2
MB [L1] LCP: state change Ack-Rcvd -- Opened
MB [L1] LCP: auth: peer wants CHAP, I want nothing
MB [L1] LCP: LayerUp
MB [L1] CHAP: rec'd CHALLENGE #1 len: 21
MB [L1]   Name: 
MB [L1] CHAP: Using authname 
MB [L1] CHAP: sending RESPONSE #1 len: 69
MB [L1] CHAP: rec'd CHALLENGE #2 len: 21
MB [L1]   Name: 
MB [L1] CHAP: Using authname xx
MB [L1] CHAP: sending RESPONSE #2 len: 69
MB [L1] CHAP: rec'd SUCCESS #2 len: 46
MB [L1]   MESG: S=6FF41EBC586F72996FE28623516DEB70E57D6B5D
MB [L1] LCP: authorization successful
MB [L1] Link: Matched action 'bundle B1 '
MB [L1] Link: Join bundle B1
MB [B1] Bundle: Status update: up 1 link, total bandwidth 64000 bps
MB [B1] IPCP: Open event
MB [B1] IPCP: state change Initial -- Starting
MB [B1] IPCP: LayerStart
MB [B1] IPCP: Up event
MB [B1] IPCP: state change Starting -- Req-Sent
MB [B1] IPCP: SendConfigReq #1
MB [B1]   IPADDR 0.0.0.0
MB [B1]   COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
MB [B1] IPCP: rec'd Configure Request #0 (Req-Sent)
MB [B1]   IPADDR 130.115.3.34
MB [B1] 130.115.3.34 is OK
MB [B1] IPCP: SendConfigAck #0
MB [B1]   IPADDR 130.115.3.34
MB [B1] IPCP: state change Req-Sent -- Ack-Sent
MB [L1] rec'd unexpected protocol CCP, rejecting
MB [B1] IPCP: SendConfigReq #2
MB [B1]   IPADDR 0.0.0.0
MB [B1]   COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
MB [B1] IPCP: rec'd Configure Reject #2 (Ack-Sent)
MB [B1]   COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
MB [B1] IPCP: SendConfigReq #3
MB [B1]   IPADDR 0.0.0.0
MB [B1] IPCP: rec'd Configure Nak #3 (Ack-Sent)
MB [B1]   IPADDR 130.115.77.13
MB [B1] 130.115.77.13 is OK
MB [B1] IPCP: SendConfigReq #4
MB [B1]   IPADDR 130.115.77.13
MB [B1] IPCP: rec'd Configure Ack #4 (Ack-Sent)
MB [B1]   IPADDR 130.115.77.13
MB [B1] IPCP: state change Ack-Sent -- Opened
MB [B1] IPCP: LayerUp
MB [B1]   130.115.77.13 - 130.115.3.34
MB [B1] IFACE: Add route 0.0.0.0/0 130.115.3.34 failed: File exists
MB [B1] IFACE: Up event
MB [L1] LCP: no reply to 1 echo request(s)
MB [L1] PPTP call terminated
MB [L1] Link: DOWN event
MB [L1] LCP: Down event
MB [L1] LCP: state change Opened -- Starting
MB [L1] Link: Leave bundle B1
MB [B1] Bundle: Status update: up 0 links, total bandwidth 9600 bps
MB [B1] IPCP: Close event
MB [B1] IPCP: state change Opened -- Closing
MB [B1] IPCP: SendTerminateReq #5
MB [B1] IPCP: LayerDown
MB [B1] IFACE: Down event
MB [B1] IPCP: Down event
MB [B1] IPCP: LayerFinish
MB [B1] Bundle: No NCPs left. 

Re: Tablet Digitizer

2011-09-01 Thread Warren Block

On Thu, 1 Sep 2011, Gary Dunn wrote:


On Tue, 2011-08-30 at 12:55 -0600, Warren Block wrote:

On Mon, 29 Aug 2011, Gary Dunn wrote:


I have studied that and the source to what seems to be a driver,
fujitsu-usb-touchscreen.


This may be what you already have:
http://spareinfo.blogspot.com/2010/10/linux-on-fujitsu-u810-p1620-t1010.html

Whether it's trustworthy, compiles on FreeBSD, or works with xorg 7.5,
don't know.


Yes, that is on the Ubuntu side, but I cannot make any sense of it on
the FreeBSD side.

I compared my Ubuntu Xorg.0.log with my FreeBSD Xorg.0.log. Quite
different. Here is an interesting bit. Starting at an identical line,
Ubuntu finds Fujitsu Component USB Touch Panel just before the
keyboard, while FreeBSD goes straight to the keyboard. Is this
significant?


Well, it's Linux's evdev, which is roughly similar to devd(8).  Likely 
that can be ignored on FreeBSD by just using another InputDevice 
section.  Beyond that, it might require input from the freebsd-x11 list 
and possibly also the freebsd-usb list.  If the components are there, it 
may be as simple as an x11-drivers/xf86-input-fujitsu-usb-touchscreen 
port.  Maybe one of the existing drivers there is for a relatively 
similar USB touchscreen?

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re[2]: vpn using pptpclient in FreeBSD

2011-09-01 Thread Marco Beishuizen

On Thu, 1 Sep 2011, the wise Коньков Евгений wrote:


Notice: [B1] IFACE: Add route 0.0.0.0/0 130.115.3.34 failed: File exists
You already have default route in your system
why you set up the default again?
Notice in conf:
 set iface route default


With help from Mike Tancsa I've changed the config a bit and getting less 
errors now, but still not a working vpn connection. My mpd.conf is now:

...
# Default configuration is pptp_client

default:
load pptp_client

pptp_client:
#
# PPTP client: only outgoing calls, auto reconnect,
# ipcp-negotiated address, one-sided authentication,
# default route points on ISP's end
#

create bundle static B1
set iface route 130.115.0.0/16
set ipcp ranges 0.0.0.0/0 0.0.0.0/0

set bundle enable compression
set ccp yes mppc
set mppc yes e40
set mppc yes e128
set bundle enable crypt-reqd
set mppc yes stateless

create link static L1 pptp
set link action bundle B1
set auth authname xx
set auth password x
set link max-redial 0
set link mtu 1460
set link keep-alive 20 75
set pptp peer vpn-eur-pptp.eur.nl
set pptp disable windowing
open
...

It looks like it's setting up a correct connection, but the site of the 
library I would like to access isn't accessible when mpd5 is running:

...
process 2965 started, version 5.5 (r...@yokozuna.lan 17:08 30-Jul-2011)
CONSOLE: listening on 127.0.0.1 5005
web: listening on 0.0.0.0 5006
[B1] Bundle: Interface ng0 created
[L1] [L1] Link: OPEN event
[L1] LCP: Open event
[L1] LCP: state change Initial -- Starting
[L1] LCP: LayerStart
[L1] PPTP call successful
[L1] Link: UP event
[L1] LCP: Up event
[L1] LCP: state change Starting -- Req-Sent
[L1] LCP: SendConfigReq #1
[L1]   ACFCOMP
[L1]   PROTOCOMP
[L1]   ACCMAP 0x000a
[L1]   MRU 1500
[L1]   MAGICNUM 0a9219e0
[L1] LCP: SendConfigReq #2
[L1]   ACFCOMP
[L1]   PROTOCOMP
[L1]   ACCMAP 0x000a
[L1]   MRU 1500
[L1]   MAGICNUM 0a9219e0
[L1] LCP: rec'd Configure Reject #2 (Req-Sent)
[L1]   PROTOCOMP
[L1] LCP: SendConfigReq #3
[L1]   ACFCOMP
[L1]   ACCMAP 0x000a
[L1]   MRU 1500
[L1]   MAGICNUM 0a9219e0
[L1] LCP: rec'd Configure Reject #3 (Req-Sent)
[L1]   ACFCOMP
[L1] LCP: SendConfigReq #4
[L1]   ACCMAP 0x000a
[L1]   MRU 1500
[L1]   MAGICNUM 0a9219e0
[L1] LCP: rec'd Configure Nak #4 (Req-Sent)
[L1]   ACCMAP 0x000a
[L1] LCP: SendConfigReq #5
[L1]   ACCMAP 0x000a
[L1]   MRU 1500
[L1]   MAGICNUM 0a9219e0
[L1] LCP: rec'd Configure Ack #5 (Req-Sent)
[L1]   ACCMAP 0x000a
[L1]   MRU 1500
[L1]   MAGICNUM 0a9219e0
[L1] LCP: state change Req-Sent -- Ack-Rcvd
[L1] LCP: rec'd Configure Request #1 (Ack-Rcvd)
[L1]   AUTHPROTO CHAP MSOFTv2
[L1] LCP: SendConfigAck #1
[L1]   AUTHPROTO CHAP MSOFTv2
[L1] LCP: state change Ack-Rcvd -- Opened
[L1] LCP: auth: peer wants CHAP, I want nothing
[L1] LCP: LayerUp
[L1] CHAP: rec'd CHALLENGE #1 len: 21
[L1]   Name: 
[L1] CHAP: Using authname x
[L1] CHAP: sending RESPONSE #1 len: 69
[L1] CHAP: rec'd CHALLENGE #2 len: 21
[L1]   Name: 
[L1] CHAP: Using authname xx
[L1] CHAP: sending RESPONSE #2 len: 69
[L1] rec'd proto IPCP during authenticate phase
[L1] rec'd proto CCP during authenticate phase
[L1] CHAP: sending RESPONSE #2 len: 69
[L1] CHAP: rec'd SUCCESS #2 len: 46
[L1]   MESG: S=F1619D8A3373D2F43E6652E992CA564D66B1C1A4
[L1] LCP: authorization successful
[L1] Link: Matched action 'bundle B1 '
[L1] Link: Join bundle B1
[B1] Bundle: Status update: up 1 link, total bandwidth 64000 bps
[B1] IPCP: Open event
[B1] IPCP: state change Initial -- Starting
[B1] IPCP: LayerStart
[B1] CCP: Open event
[B1] CCP: state change Initial -- Starting
[B1] CCP: LayerStart
[B1] IPCP: Up event
[B1] IPCP: state change Starting -- Req-Sent
[B1] IPCP: SendConfigReq #1
[B1]   IPADDR 0.0.0.0
[B1]   COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
[B1] CCP: Up event
[B1] CCP: state change Starting -- Req-Sent
[B1] CCP: SendConfigReq #1
[B1]   MPPC
[B1] 0x0160:MPPE(40, 128 bits), stateless
[B1] CCP: rec'd Configure Nak #1 (Req-Sent)
[B1]   MPPC
[B1] 0x0140:MPPE(128 bits), stateless
[B1] CCP: SendConfigReq #2
[B1]   MPPC
[B1] 0x0140:MPPE(128 bits), stateless
[B1] CCP: rec'd Configure Ack #2 (Req-Sent)
[B1]   MPPC
[B1] 0x0140:MPPE(128 bits), stateless
[B1] CCP: state change Req-Sent -- Ack-Rcvd
[B1] IPCP: rec'd Configure Request #1 (Req-Sent)
[B1]   IPADDR 130.115.3.35
[B1] 130.115.3.35 is OK
[B1] IPCP: SendConfigAck #1
[B1]   IPADDR 130.115.3.35
[B1] IPCP: state change Req-Sent -- Ack-Sent
[B1] CCP: rec'd Configure Request #1 (Ack-Rcvd)
[B1]   MPPC
[B1] 0x0160:MPPE(40, 128 bits), stateless
[B1] CCP: SendConfigNak #1
[B1]   MPPC
[B1] 0x0140:MPPE(128 bits), stateless
[B1] CCP: rec'd Configure Request #2 (Ack-Rcvd)
[B1]   MPPC
[B1] 0x0140:MPPE(128 bits), stateless
[B1] CCP: SendConfigAck #2
[B1]   MPPC
[B1] 

Re: wlan setup

2011-09-01 Thread Derek Funk
I have tried what the handbook says and a custom entry to devd.conf as
one forum showed.

wlan0 associates with the access point but does not get an IP.

Drivers are loaded.  No error messages in /var/log for wpa_supplicant.

I have even tried using background_dhclient in rc.conf.

This is an issue with freebsd not my access point.  Windows, ubuntu and
my cellphone have no problems obtaining an IP.

I have no idea what is happening.  It looks straight forward from the
handbook.  Unless this is a bug.  I guess I'll have to ditch freebsd for
awhile.

Derek
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org