Re: network routing malfunction
On Wed, May 23, 2012 at 3:32 PM, Pierre Abbat wrote: > I have a VPN; sometimes it doesn't work properly. > > chausie is the Linux box, which runs the VPN; it has eth0 and ppp0. darner is > the DragonFly box; it has em0. linksys is a router; chausie's eth0 and > darner's em0 are connected to the LAN side. sco is behind NAT on the other > end of the VPN. > > I woke up and finished a drawing and had to copy it to sco. My telnet session > to sco had broken during the night. (sco doesn't have ssh; I telnet over the > VPN.) I checked the VPN and found it had dropped, so I restarted it. I tried > telnetting and failed. I tried pinging and succeeded, but running tcpdump on > chausie showed that packets were not going through chausie. I ran "route > show" and "traceroute sco" on darner and then packets started going through > chausie and I logged in to sco. How come? Are you saying that ping was working even if you didn't see the packets going through chausie? Which route is darner using to reach sco? Did it change before and after the traceroute? > > Pierre > -- > Don't buy a French car in Holland. It may be a citroen.
Re: pppoe
2012/3/19 Andrey N. Oktyabrski : > Good day. > > How can I configure PPPoE interface? Now I use "ppp" program with this > configuration: > pppoe: > set device PPPoE:fxp0 #Interface to adsl-modem-bridge > set authname > set authkey > set dial > set login > add default HISADDR > nat enable yes > > $ ps ax | grep ppp > 254 ?? SLs 4:39.48 /usr/sbin/ppp -quiet -ddial -nat pppoe > > ... and see this in the "top": > 254 root 0 6460K 0K RUN 0 4:42 4:42 16.11% ppp > > > Is it possible to use anything other than "ppp"? ng_pppoe? How to configure > it? "man ng_pppoe" does not give me any useful information. Can anybody to > give me and example? Or I must compile mpd and use it? Hi, As far as I know, ppp is currently the only way to configure PPPoE sessions on DragonFly. The ppp userland program makes use of ng_pppoe kernel counterpart to deal with the PADIs/PADOs etc of the PPPoE session. Your configuration seems correct. You should get a tun0 interface with an ip address if everything goes well. Cheers Nuno
Re: Unable to boot vkernel: "Permission denied"
On Mon, Mar 14, 2011 at 9:23 PM, Chirag Kantharia wrote: > Hello, > > I'm trying to setup a VKERNEL environment on my x86_64 desktop. > Following the excellent article on setting up VKERNEL environment at > http://www.dragonflybsd.org/docs/newhandbook/vkernel/ I was able to > setup a root filesystem and compile the VKERNEL64 (all default > settings) kernel. After setting the sysctl vm.vkernel_enable, trying > to launch the vkernel, using ./boot/kernel -m 64m, I get > "./boot/kernel: Permission denied". > > Upon googling, I found > http://www.mail-archive.com/users@crater.dragonflybsd.org/msg11456.html, > but the sysctl seems to be set correctly. > > Using ktrace, it looks like the execve failed with "Permission > denied". The permissions for the ./boot/kernel file seem to be right. > > $ ls -lo ./boot/kernel > total 23400 > -r-xr-xr-x 1 root wheel schg 23930386 Mar 14 20:28 kernel > > What am I missing? > > Thanks, > > -- > Chirag Kantharia > > Hi Chirag, Do you have permission to create the memory file? Cheers, Nuno
Re: Why did you choose DragonFly?
On Mon, Sep 20, 2010 at 8:33 PM, Samuel J. Greear wrote: > This mail is intended for the infrequent responders and lurkers on the > list just as much as the regular posters. > > What has drawn you to use the DragonFly BSD operating system and/or > participate in its development by following this list? Technical > features, methodologies, something about the community? I suspect the > HAMMER filesystem to be the popular choice, but what other features > affect or do you see affecting your day to day life as an > administrator, developer, or [insert use case here], now or in the > future? > > Thanks in advance for your response. > > Best, > Sam > The lwkt and SSI goals really pleased me when DragonFly forked off FreeBSD (and still do), so I followed loosely for a while. But it wasn't until later when I attended EuroBSDCon in Milan and watched the talk from Jeffrey Hsu about the networking threads in DragonFly that it really tickled me. At about that time, the vkernel technology was just about to see daylight and when it did I finally surrendered. I think vkernels are a very cool feature! Last but certainly not least, I find this community very welcoming and comfortable. People are just great! I wish I could make it to CCC more often.. In conclusion, at first it was because of the goals and innovation from a developer point of view, but later it was because of the people involved too :) Thanks guys! Nuno
Re: CCC Congress (25C3) 2008
On Wed, Oct 8, 2008 at 2:44 PM, Matthias Schmidt <[EMAIL PROTECTED]> wrote: > Hi, > > I just wanted to know who's coming to the annual Chaos Computer Club > Congress (25C3) this year in Berlin? Some guys (Sascha, Simon) already > confirmed it on IRC, but how about others? > > More information: http://events.ccc.de/congress/2008/ I'll try to make it this year again. Have you guys already reserved a place to stay? Cheers, Nuno
Re: setting up vkernel
On Sat, Oct 18, 2008 at 3:50 PM, dark0s Optik <[EMAIL PROTECTED]> wrote: > Ok, newfs /dev/vn0s0a and mount /dev/vn0s0a /mnt done. > Now, I type: > > #cd /usr/src > #make installworld DESTDIR=/mnt > make: don't know how to make installworld. Stop > # It looks like you don't have the source code under /usr/src. To put it there do: cd /usr make release-src-cvsup or make head-src-cvsup respectively to install release or head source code under /usr/src. Cheers Nuno
Re: setting up vkernel
On Sat, Oct 18, 2008 at 3:03 PM, dark0s Optik <[EMAIL PROTECTED]> wrote: > No, what I must modify? > When editing the disklabel with "disklabel -e vn0s0" just copy the last line ( that starts with "c:" ) and insert another one just like it above and change "c:" with "a:" and change the "unused" keyword with "4.2BSD". This will create the a: partition. Then you should be able to do the newfs. Cheers, Nuno
Re: setting up vkernel
On Sat, Oct 18, 2008 at 11:59 AM, dark0s Optik <[EMAIL PROTECTED]> wrote: > I have typed: > > mkdir /home/var.vkernel > ln -s /home/var.vkernel /var/vkernel > > dd if=/dev/zero of=/var/vkernel/rootimg.01 bs=1m count=2048 > vnconfig -c -s labels vn0 /var/vkernel/rootimg.01 > disklabel -e vn0s0 Did you to add the a: partition at this point? > > after I close vi with :wq > > and I typed > > newfs /dev/vn0s0a > newfs: /dev/vn0s0a: in unavailable > > What is the problem? > > Regards, > savio > > -- > only the paranoid will survive >
Re: moused + modular xorg 'sticking' ?
On Nov 8, 2007 9:06 PM, Joerg Sonnenberger <[EMAIL PROTECTED]> wrote: > On Thu, Nov 08, 2007 at 12:05:25PM -0800, Matthew Dillon wrote: > > :I know that various signal handlers used floating point and the issues > > :reported fall into the category of "likely overwritten FPU state". > > : > > :Joerg > > > > Should we start saving and restoring the FP context? The ucontext > > structure does have enough space reserved for it. During the LWP > > work we expanded the FP save space to 512 bytes. > > Yes, please. This is a bug after all :-) Here's a nice regression test for this issue. http://www.openbsd.org/cgi-bin/cvsweb/src/regress/sys/kern/signal/fpsig/ Nuno
Re: moused + modular xorg 'sticking' ?
On Nov 8, 2007 6:07 AM, Sepherosa Ziehau <[EMAIL PROTECTED]> wrote: > On Nov 8, 2007 10:14 AM, Joe Talbott <[EMAIL PROTECTED]> wrote: > > > > On Wed, Nov 07, 2007 at 07:25:48PM -0500, Chris Turner wrote: > > > > > > Hello all - > > > > > > fishing for similar experiences - > > > > > > has anyone had any problems with ps2 mice getting 'stuck' under X? > > > > My problem with "/dev/sysmouse" is that my mouse pointer will go to > upper left corner and can't move anymore. This can easily be > reproduced by trying to select a bootmark entry in firefox "bookmarks" > manual. After I switched to use "/dev/psm0", the problem seems to go > away. I have the exact same problem, only in my case I use a usb mouse. I thought this was related to somebody adding floating point operations in a signal handler or something, possibly related to the following link. http://mail-index.netbsd.org/pkgsrc-users/2007/08/06/0008.html But maybe I am just confused. Nuno
Re: DragonFly get-together at 24c3
On 11/7/07, Simon 'corecode' Schubert <[EMAIL PROTECTED]> wrote: > So who is coming? I am for sure (just booked the flight). I just booked a flight too. Now I need a place to stay. :-) Nuno
Bugtracker inaccessible
Hi, I can't access the bugtracker at http://bugs.dragonflybsd.org . Is it down? Cheers, Nuno
Re: Bugtracker inaccessible
On 9/14/07, Nuno Antunes <[EMAIL PROTECTED]> wrote: > Hi, > > I can't access the bugtracker at http://bugs.dragonflybsd.org . Is it down? > It's up again. Thanks Simon! Cheers, Nuno
Dragonfly 1.6 upgraded by cvs
On 8/29/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Hi ALL, Hi > i realised, that the 1.6 kernel "generic" used to detect my HD ( my laptop > only has this HD ) as "ad0" ... > but the new kernel ( i only took out floppy soupport on the kernelconfig > ... maybe this is a problem ? - my laptop has no floppy ? ) > detects the HD as ad1. This is just a "me too". I also have a system where the only hard disk started to be detected as da1 instead of da0 (this was somewhere between 1.8 and 1.10). For the curious, a current dmesg is attached. > THIS is a problem because the rootfilesystem used to be on "ad 0 s3a" > ... for "ad 1 s3a" there is no entry in /dev ... so i could not manage to > mount it. > > because i am a little bit naiv i thought changeing the FStab from ad0 to > ad1 would do... > ( i booted in kernel.old and changed FStab ) I did have a da1 in /dev so changing fstab did work for me so i forgot about the problem. > but now none of the kernels can locate the rootfilesystem... > > - without mounted root i am not able to write at the disc; > > so how to cope with my problem? Can you boot a live cd to fix it? > ( i would prefere to know how to create devices in /dev or to say the > kernel that my HD has to be ad0 ) cd /dev ./MAKEDEV ad1 Good luck! Nuno whitewidow.dmesg Description: Binary data
Re: dd vs. truncate for creating vkernel root images
Forgot to copy to [EMAIL PROTECTED] On 4/12/07, Nuno Antunes <[EMAIL PROTECTED]> wrote: On 4/12/07, Nuno Antunes <[EMAIL PROTECTED]> wrote: > On 4/12/07, Justin C. Sherrill <[EMAIL PROTECTED]> wrote: > > On Wed, April 11, 2007 6:00 pm, Nuno Antunes wrote: > > > Hi all, > > > > > > Is there any advantage in using > > > 'dd if=/dev/zero of=/var/vkernel/rootimg.01 bs=1m count=2048' > > > over the much quicker > > > 'truncate -s 2G /var/vkernel/rootimg.01' > > > other than getting a root image filled with zeros? > > > > Have you tried it? What happened? > > > > > > Yes I have, and it works. Vkernels can use a root image created this > way. So does it mean that the file will grow on demand (up to the > established size, of course)? > > Thanks, > Nuno > Here are my image sizes: whitewidow# ll -h /var/vkernel/devel.rootimg.01 -rw-rw-r-- 1 root wheel 512M Apr 12 00:32 /var/vkernel/devel.rootimg.01 whitewidow# du -sh /var/vkernel/devel.rootimg.01 339M/var/vkernel/devel.rootimg.01 And inside the vkernel: # df -h Filesystem Size Used Avail Capacity Mounted on /dev/vkd0a 496M 186M 270M41%/ Cheers, Nuno
Re: dd vs. truncate for creating vkernel root images
On 4/12/07, Justin C. Sherrill <[EMAIL PROTECTED]> wrote: On Wed, April 11, 2007 6:00 pm, Nuno Antunes wrote: > Hi all, > > Is there any advantage in using > 'dd if=/dev/zero of=/var/vkernel/rootimg.01 bs=1m count=2048' > over the much quicker > 'truncate -s 2G /var/vkernel/rootimg.01' > other than getting a root image filled with zeros? Have you tried it? What happened? Yes I have, and it works. Vkernels can use a root image created this way. So does it mean that the file will grow on demand (up to the established size, of course)? Thanks, Nuno
dd vs. truncate for creating vkernel root images
Hi all, Is there any advantage in using 'dd if=/dev/zero of=/var/vkernel/rootimg.01 bs=1m count=2048' over the much quicker 'truncate -s 2G /var/vkernel/rootimg.01' other than getting a root image filled with zeros? Thanks, Nuno
Re: bfe0: couldn't map memory
On 1/13/07, Nuno Antunes <[EMAIL PROTECTED]> wrote: On 1/13/07, Sepherosa Ziehau <[EMAIL PROTECTED]> wrote: > On 1/13/07, Nuno Antunes <[EMAIL PROTECTED]> wrote: > > Hi, > > > > I'm having trouble getting my bfe network interface card to work on > > dragonfly. The following appears on dmesg (hand transcribed): > > > > bfe0: irq 17 at device 1.0 on pci6 > > bfe0: couldn't map memory > > device_probe_and_attach: bfe0 attach returned 6 > > > > The interface does not appear on "ifconfig -a" > > > > Any help would be very appretiated. > > http://leaf.dragonflybsd.org/mailarchive/users/2006-01/msg00097.html > > Hope this will be helpful. > > Best Regards, > sephe > > -- > Live Free or Die > Hi Sephe, Thanks for the tip. A BIOS upgrade solved it. Hmm. I recently started getting this error again, it knocked my head out trying to find the reason (but it's working now). I tried no-optimizations (even removed /etc/make.conf), trying GENERIC, no SMP, always the same error. There was a difference when I tried NATA though, it gave me: bfe0: MII without any PHY! Maybe options PCI_MAP_FIXUP for NATA had something to do with this? Anyway, it turned out to be that I had disabled PXE booting at the BIOS. Having it enabled allows bfe to work correctly on DFly on this laptop (note that it was working of FreeBSD and Windows on the same laptop without PXE enabled). The BIOS upgrade I had done before must have restored the default enable PXE booting, that's why it worked after the upgrade (until I disabled it later and started to get the error again scratching my head why...). Could it be there's some issue with pci memory/port mapping that enabling PXE cirumvents? I'm way off my knowledge here.. Anyways, I just though I could tell the tale.. Thanks, Nuno
Re: hardware compatibility - Nvidia SATA controller
On 2/2/07, Jon Nathan <[EMAIL PROTECTED]> wrote: * Nuno Antunes <[EMAIL PROTECTED]> [02-02-2007 17:23]: > > On 2/2/07, Jon Nathan <[EMAIL PROTECTED]> wrote: > >Hello, > > > >I'm trying to install Dragonfly BSD 1.8 on a Dell XPS 600. It has an > >integrated Nvidia Nforce 4 Intel Edition SATA RAID Controller, but > >Dragonfly can't find the hard disk attached to it. > > > >I looked for hardware compatibility lists, but couldn't find anything > >referencing different SATA chipsets and what was supported. Mailing > >list searches seem to indicate that ATAng was not really implemented, > >but that was a while ago: > > > >http://leaf.dragonflybsd.org/mailarchive/kernel/2003-11/msg00043.html > > > >Any info on this chipset? Thanks, > > > >-Jon > > > Hello Jon, > > Have you tried NATA? > > For NATA, add options PCI_MAP_FIXUP to your kernel, comment out the > old ata devices, add device nata, device natadisk and device natapicd. > Credits due to [EMAIL PROTECTED] :-) > > Cheers, > Nuno If this isn't in the kernel on the install CD, it's probably not much use to me. You seem to imply that ata and nata are mutually exclusive above. Is this the case? If not, is there a chance that nata could be added to the kernel for future releases? -Jon Yes, i think NATA is mutually exclusive with ATA and it's not enabled by default. NATA is supposed to replace old ATA in the future when more testing is performed. Nuno.
Re: hardware compatibility - Nvidia SATA controller
On 2/2/07, Jon Nathan <[EMAIL PROTECTED]> wrote: Hello, I'm trying to install Dragonfly BSD 1.8 on a Dell XPS 600. It has an integrated Nvidia Nforce 4 Intel Edition SATA RAID Controller, but Dragonfly can't find the hard disk attached to it. I looked for hardware compatibility lists, but couldn't find anything referencing different SATA chipsets and what was supported. Mailing list searches seem to indicate that ATAng was not really implemented, but that was a while ago: http://leaf.dragonflybsd.org/mailarchive/kernel/2003-11/msg00043.html Any info on this chipset? Thanks, -Jon Hello Jon, Have you tried NATA? For NATA, add options PCI_MAP_FIXUP to your kernel, comment out the old ata devices, add device nata, device natadisk and device natapicd. Credits due to [EMAIL PROTECTED] :-) Cheers, Nuno
Re: DRAGONFLY-1.8.0 RELEASED!
Many thanks and congratulations for this briliant piece of work! Cheers, Nuno
Re: ipw3945 WLAN driver
On 11/19/06, Sepherosa Ziehau <[EMAIL PROTECTED]> wrote: On 19 Nov 2006 09:15:38 GMT, Johannes Hofmann <[EMAIL PROTECTED]> wrote: > Thomas Schlesinger <[EMAIL PROTECTED]> wrote: > > Am Dienstag, 14. November 2006 18:40 schrieb Thomas Schlesinger: > >> Hi, > >> > >> are there plans to port the ipw3945 driver from OpenBSD in the near future? > >> > >> Thomas > > > > Ok, I take this as "no" ;-) I did a preliminary port several months ago: http://leaf.dragonflybsd.org/~sephe/wpi.tbz It is known to crash some place arround firmware loading. I do not have hardware to keep going, so if you are interested, you can continue it or start from scratch (NetBSD's wpi port may be a better start point than OpenBSD's) I will be glad to commit it, if you can knock it out :-) Best Regards, sephe Hello Sephe, I have the hardware and I am willing to test this and try to make it work on my laptop. I tweaked your preliminary port a bit so that it compiles on HEAD. The interface is correctly detected when I load the module. But now I'm stuck. How do I upload the firmware? I've installed pkgsrc sysutils/wpi-firmware. I tried the following but I get an error: class# ipwcontrol wpi0 -f /usr/pkg/libdata/if_wpi/ipw3945.ucode ipwcontrol: Can't load /usr/pkg/libdata/if_wpi/ipw3945.ucode to driver: Bad address Thanks, Nuno
Re: bfe0: couldn't map memory
On 1/13/07, Sepherosa Ziehau <[EMAIL PROTECTED]> wrote: On 1/13/07, Nuno Antunes <[EMAIL PROTECTED]> wrote: > Hi, > > I'm having trouble getting my bfe network interface card to work on > dragonfly. The following appears on dmesg (hand transcribed): > > bfe0: irq 17 at device 1.0 on pci6 > bfe0: couldn't map memory > device_probe_and_attach: bfe0 attach returned 6 > > The interface does not appear on "ifconfig -a" > > Any help would be very appretiated. http://leaf.dragonflybsd.org/mailarchive/users/2006-01/msg00097.html Hope this will be helpful. Best Regards, sephe -- Live Free or Die Hi Sephe, Thanks for the tip. A BIOS upgrade solved it. Cheers, Nuno
bfe0: couldn't map memory
Hi, I'm having trouble getting my bfe network interface card to work on dragonfly. The following appears on dmesg (hand transcribed): bfe0: irq 17 at device 1.0 on pci6 bfe0: couldn't map memory device_probe_and_attach: bfe0 attach returned 6 The interface does not appear on "ifconfig -a" Any help would be very appretiated. Thanks, Nuno
Re: bfe0: couldn't map memory
On 1/13/07, Nuno Antunes <[EMAIL PROTECTED]> wrote: Hi, I'm having trouble getting my bfe network interface card to work on dragonfly. Ooh, this is on HEAD from yesterday. Thanks, Nuno
Re: Preview tag bumped
On 11/28/06, Matthew Dillon <[EMAIL PROTECTED]> wrote: The next major release (1.8) is slated for January. I hope to have at least a basic userland kernel binary operating by then. Hi, What this userland kernel binary? Is this something like 'user mode linux'? will it allow to perform kernel development without running a Virtual Machine software like VMWare? If it is, it will certainly be very helpful. :-) Thanks, Nuno
