Re: FreeBSD 8.3-STABLE #0 r237184 if_tun auto-up upon create.
18.06.2012 09:47, Jason Hellenthal пишет: Hoping someone here might be able to clue me in on what I am seeing. FreeBSD 8.3-STABLE #0 r237184 When creating a if_tun(4) device... ifconfig tun0 create With these line in rc.conf(5) cloned_interfaces=tun0 ifconfig_tun0=metric 100 down And sysctl net.link.tun.devfs_cloning=0 The resulting tun0 device results in state... tun0: flags=8011UP,POINTOPOINT,MULTICAST metric 100 mtu 1500 After removing the ifconfig_tun0= and running ifconfig create... tun0: flags=8010POINTOPOINT,MULTICAST metric 0 mtu 1500 Why would the device enter a UP/DOWN state if there is no addressing information being fed to it ? and especially with a directive of down ? That's because the word up is automatically added by system rc-scripts for ifconfig_XXX lines, so real ifconfig statement in your case is: ifconfig tun0 metric 100 down up Eugene Grosbein ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: PORTS_MODULES
Howdy, This is an FYI to let people know about a really nice feature for those that have ports installed which include kernel modules. You can place a list in /etc/src.conf like this: PORTS_MODULES= emulators/virtualbox-ose-kmod sysutils/fusefs-kmod x11/nvidia-driver which will cause those modules to be built and installed with all the proper matching stuff at the same time as buildkernel and installkernel. This feature has existed for a while, but has had issues. Thanks to a team effort it's a lot more robust now, and ready for prime time (in HEAD, and the -STABLE branches for now, soon to be in 9.1-RELEASE). Enjoy, Doug nice! does it also work when cross-compiling? ie, using an amd64-freebsd-8.3 kernel to compile for i386-freebsd-8.2 thanks, danny ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: PORTS_MODULES
On Mon, Jun 18, 2012 at 12:40 AM, Daniel Braniss da...@cs.huji.ac.il wrote: Howdy, This is an FYI to let people know about a really nice feature for those that have ports installed which include kernel modules. You can place a list in /etc/src.conf like this: PORTS_MODULES= emulators/virtualbox-ose-kmod sysutils/fusefs-kmod x11/nvidia-driver which will cause those modules to be built and installed with all the proper matching stuff at the same time as buildkernel and installkernel. This feature has existed for a while, but has had issues. Thanks to a team effort it's a lot more robust now, and ready for prime time (in HEAD, and the -STABLE branches for now, soon to be in 9.1-RELEASE). Enjoy, Doug nice! does it also work when cross-compiling? ie, using an amd64-freebsd-8.3 kernel to compile for i386-freebsd-8.2 In theory, yes, however some of the environment required to bootstrap some ports might be missing, depending on how the ports module pokes around for data in /usr/src, etc. Thanks! -Garrett ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
[wifi] wifimgr for freebsd
Hi, I made a wifi script based on the wlanconfig in bsdinstaller. here is the code: https://github.com/gihnius/freebsd-wifi I think we can make it more suitable for many devices and normal use. Any idea to write a normal feature script to use freebsd wifi easily ? and thanks to the author of wlanconfig. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
vlan+iwn panic
Hi list, I encoutered a panic with FreeBSD 9 Stable creating vlan with wlan0 (iwn0) parent. Panic occur when upping the vlan : Unread portion of the kernel message buffer: Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x0 fault code = supervisor read data, page not present instruction pointer = 0x20:0x0 stack pointer = 0x28:0xff800024b3f0 frame pointer = 0x28:0xff800024b4b0 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 12 (swi4: clock) trap number = 12 panic: page fault cpuid = 0 KDB: stack backtrace: #0 0x80625896 at kdb_backtrace+0x66 #1 0x805ed71e at panic+0x1ce #2 0x80887690 at trap_fatal+0x290 #3 0x808879fc at trap_pfault+0x21c #4 0x80887ff5 at trap+0x365 #5 0x80872713 at calltrap+0x8 #6 0x807b9968 at nd6_output+0x18 #7 0x807b41ed at ip6_output+0x11dd #8 0x807b4c8c at mld_dispatch_packet+0xdc #9 0x807b5121 at mld_dispatch_queue+0x21 #10 0x807b7ac0 at mld_fasttimo+0x640 #11 0x8064fdbb at pffasttimo+0x2b #12 0x80603540 at softclock+0x3c0 #13 0x805bf3e4 at intr_event_execute_handlers+0x104 #14 0x805c0b64 at ithread_loop+0xa4 #15 0x805bc04f at fork_exit+0x11f #16 0x80872c3e at fork_trampoline+0xe This problem doesn't occur with atheros card on SOEKRIS (i386) Regards David ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Unable to boot 9 stable/release on HP EliteBook 8560p
Hi, I have an Elitebook but I am unable to even load the kernel or get to a point where user interaction is posible. The bootloader reboots the machine just before or after the amount of memory is shown. Anyone with simliar problems an newer HP notebooks? Gr Matthias ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Unable to boot 9 stable/release on HP EliteBook 8560p
I have had a similar problem with my HP Elitebook 8540p and I solved it by moving the sata controller from ahci to ide in the bios. Cordially. Q. Schwerkolt On 06/18/12 13:19, Matthias Gamsjager wrote: Hi, I have an Elitebook but I am unable to even load the kernel or get to a point where user interaction is posible. The bootloader reboots the machine just before or after the amount of memory is shown. Anyone with simliar problems an newer HP notebooks? Gr Matthias ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Unable to boot 9 stable/release on HP EliteBook 8560p
On Mon, Jun 18, 2012 at 1:38 PM, Quentin Schwerkolt develloper.u...@hotmail.fr wrote: I have had a similar problem with my HP Elitebook 8540p and I solved it by moving the sata controller from ahci to ide in the bios. Cordially. Q. Schwerkolt Thx this fixed the booting :) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Unable to boot 9 stable/release on HP EliteBook 8560p
On Jun 18, 2012 9:34 PM, Matthias Gamsjager mgamsja...@gmail.com wrote: On Mon, Jun 18, 2012 at 1:38 PM, Quentin Schwerkolt develloper.u...@hotmail.fr wrote: I have had a similar problem with my HP Elitebook 8540p and I solved it by moving the sata controller from ahci to ide in the bios. I've had several problems with Linux on HP machines lately that have been fixed with BIOS upgrades. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: vlan+iwn panic
Le 18/06/2012 ? 12:52:19+0200, David ROFFIAEN a écrit Hi list, I encoutered a panic with FreeBSD 9 Stable creating vlan with wlan0 (iwn0) parent. Panic occur when upping the vlan : I've same problem whitout vlan. Just sometime (rarely) when the signal of the wifi is very weak the system crash with something very close. Regards. -- Albert SHIH DIO bâtiment 15 Observatoire de Paris 5 Place Jules Janssen 92195 Meudon Cedex Téléphone : 01 45 07 76 26/06 86 69 95 71 xmpp: j...@jabber.obspm.fr Heure local/Local time: lun 18 jui 2012 15:28:58 CEST ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: mpt: Unable to memory map registers
On Saturday, June 16, 2012 6:10:47 am Andrey Zonov wrote: On 6/15/12 9:24 PM, John Baldwin wrote: On Friday, June 15, 2012 2:12:06 am Andrey Zonov wrote: On 6/13/12 7:10 PM, John Baldwin wrote: On Tuesday, June 12, 2012 5:57:34 pm Andrey Zonov wrote: On 6/13/12 12:51 AM, John Baldwin wrote: On Tuesday, June 12, 2012 3:53:09 pm Andrey Zonov wrote: On 6/12/12 10:06 PM, John Baldwin wrote: [snip] Ok, I've added some more debugging. The patch is a bit larger now and you can fetch it from www.freebsd.org/~jhb/patches/pcib_debug.patch New dmesg is in attach. Sheesh, found another bug (wasn't masking 'front' properly). Try updated patch (same URL). Great! It works! Excellent. I've committed the 2 bugs needed to fix your box. However, there is another bug that this exposed that I'd like you to test. Can you update to the latest HEAD, apply the updated pcib_debug.patch, and boot with 'hw.pci.pcib_clear=1' set from the loader? That should exercise the bug I'm worried about and see if my fixes for that (recursively growing windows) works correctly. Attached. Hmm, it doesn't seem like hw.pci.pcib_clear was set (the pcibX devices still tried to allocate their initial windows). Ooops. Thanks. Unfortunately, this didn't actually exercise what I wanted, but that is ok. However, this did uncover another bug it seems: pcib7: ACPI PCI-PCI bridge at device 0.3 on pci5 pci6: ACPI PCI bus on pcib7 pci6: domain=0, physical bus=6 found- vendor=0x1000, dev=0x0054, revid=0x02 pcib3: attempting to grow I/O port window for (0xd000-0xdfff,0x1000) front candidate range: 0xd000-0xdfff pcib3: bus_adjust_resource(0xc000, 0xefff) pci0: bus_adjust_resource(pcib3, 0x1c, 0xc000, 0xefff) pcib0: bus_adjust_resource(pcib3, 0x1c, 0xc000, 0xefff) acpi0: bus_adjust_resource(pcib3, 0x1c, 0xc000, 0xefff) nexus0: bus_adjust_resource(pcib3, 0x1c, 0xc000, 0xefff) pcib3: grew I/O port window to 0xc000-0xefff pcib3: allocated I/O port range (0xd000-0xdfff) for rid 1c of pcib7 pcib7: allocated initial I/O port window of 0xd000-0xdfff This grew the range too large resulting in this failure later on: pcib9: failed to allocate initial I/O port window (0xc000-0xcfff,0x1000) Can you try the updated pcib_debug.patch? It has some more printf's for this case. -- John Baldwin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: FreeBSD 8.3-STABLE #0 r237184 if_tun auto-up upon create.
On Mon, Jun 18, 2012 at 02:37:27PM +0700, Eugene Grosbein wrote: 18.06.2012 09:47, Jason Hellenthal пишет: Hoping someone here might be able to clue me in on what I am seeing. FreeBSD 8.3-STABLE #0 r237184 When creating a if_tun(4) device... ifconfig tun0 create With these line in rc.conf(5) cloned_interfaces=tun0 ifconfig_tun0=metric 100 down And sysctl net.link.tun.devfs_cloning=0 The resulting tun0 device results in state... tun0: flags=8011UP,POINTOPOINT,MULTICAST metric 100 mtu 1500 After removing the ifconfig_tun0= and running ifconfig create... tun0: flags=8010POINTOPOINT,MULTICAST metric 0 mtu 1500 Why would the device enter a UP/DOWN state if there is no addressing information being fed to it ? and especially with a directive of down ? That's because the word up is automatically added by system rc-scripts for ifconfig_XXX lines, so real ifconfig statement in your case is: ifconfig tun0 metric 100 down up Ugh! thanks. guess Ill just have to stick with start_if.tun0 I could swear I have other interfaces that don't do that but at least I know what I am looking for now. Thanks again -- - (2^(N-1)) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Cannot get flashplugin to work
Running 9.0 STABLE Cannot get the linux flashplugin to work on either firefox or chrome. Followed the handbook exactly. Using ports I installed the following. * installed nspluginwrapper which also installed linux_base_f10 * installed linux-f10-flashplugin11 * linked libflashplayer.so into /usr/local/lib/browser_plugins/ (checked that the link is in the directory) * ran nspluginwrapper -v -a -i (this ran fine) mount shows that linprocfs is on /compat/linux/proc about:plugins shows that flashplayer is enabled in both firefox and chrome. The plugins do not work anywhere I try. I get messages like plugins-missing. Tried running firefox and chrome from the command line to check error messages. This is what shows up: *** NSPlugin Wrapper *** ERROR: NPP_New() wait for reply: Connection closed *** NSPlugin Wrapper *** WARNING:(/work/a/ports/www/nspluginwrapper/work/nspluginwrapper-1.4.4/src/npw-wrapper.c:2150):invoke_NPP_Destroy: assertion failed: (rpc_method_invoke_possible(plugin-connection)) I have updated my ports collection and tried deinstalling and reinstalling and have the same problem. Any ideas? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Cannot get flashplugin to work
On Mon, 18 Jun 2012 10:25:10 -0500, Michael Gass mg...@csbsju.edu wrote: Cannot get the linux flashplugin to work on either firefox or chrome. 9-STABLE here without issues. Can you post: /etc/rc.conf /etc/fstab output of `kldstat` output of `mount` output of `uname -a` Thanks! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: How to bind a route to a network adapter and not IP
On Monday 18 June 2012 00:00:51 H wrote: sth...@nethelp.no wrote: I loose packets because I use a WLAN adapter. Sometimes the link is down for various reasons, and then the routes start changing for manually created routes, and I want to prevent that. well that is certainly not a reason for changing routes I have the feeling you are not explaining good enough what really is going on and it may help sending your configurations and an example of routes and IP addresses before and after this route change Why is this so hard to understand? Link down leads to static route is deleted. This is standard FreeBSD behavior, and has been this way for as long as I can remember (btw, I believe this behavior is from the original BSD, not FreeBSD specific). You can show this by having a static default route pointing to an address on an Ethernet interface which has link. And then pulling the TP cable from the Ethernet interface. Observe that the default route is automatically removed. may be you have not understood your own problem yet because so far is nothing to be understood because none of your statements is correct, it is also not FreeBSD's standard behavior and never has been as long as there is the valid IP address on the related interface, no static route will be deleted, you can even boot without cable and the [default] static route is there so you need to explain better your problem in order to understand it probably you have some other stuff running, thirdparty network manager or something, incorrect or incomplete ppoe or dhc configuration or whatever leads to the problem FYI static routes usually are the manually configured routes, so what you say is redundant and not correct, I guess you're loosing some kind of dynamic route since WL networks usually do not run RIP/OSPF/BGP I guess the route you apparently loose is coming from some dhcp server and may be your dhclient configuration is incomplete or none existent, but here now it would be useful to see your config Hi, I think we need to distinguish between two matters. One is where the route is directly reachable on the local-net of the network adapter, and ARP is valid/responding. The second case is when the route is not directly reachable. The second case is where the problem happens, like Stian kindly explained. # For example: ifconfig wlan0 10.0.0.2 255.255.255.0 up # Assume the router is at 10.0.0.1 # And we want to reach a certain destination through 10.0.0.1 # Then we do: route add 10.22.1.1 10.0.0.1 # # First the FreeBSD network stack will resolve the ethernet address for # 10.0.0.1, and all 10.22.1.1 IP packets will get sent to 10.0.0.1. # However, if the wlan0 link goes down, which sometimes happen, then the route for 10.22.1.1 is deleted. This is sometimes very annoying, and also, if it happens that the 10.22.1.1 is reachable from another network adapter, then traffic sometimes can end up mis-routed. --HPS ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Cannot get flashplugin to work
On Mon, Jun 18, 2012 at 11:13:10AM -0500, Mark Felder wrote: On Mon, 18 Jun 2012 10:25:10 -0500, Michael Gass mg...@csbsju.edu wrote: Cannot get the linux flashplugin to work on either firefox or chrome. 9-STABLE here without issues. Can you post: /etc/rc.conf /etc/fstab output of `kldstat` output of `mount` output of `uname -a` Thanks! Here is the info: % uname -a FreeBSD ap200.home.net 9.0-STABLE FreeBSD 9.0-STABLE #0: Sat May 19 09:07:23 CDT 2012 root@:/usr/obj/usr/src/sys/AP20120519 i386 % kldstat Id Refs AddressSize Name 1 31 0xc040 74b158 kernel 21 0xc0b4c000 4e0c snd_ess.ko 32 0xc0b51000 4c68 snd_sbc.ko 41 0xc0b56000 4854 sem.ko 51 0xc0b5b000 70ec apm.ko 61 0xc4187000 8000 linprocfs.ko 72 0xc41a 2b000linux.ko 81 0xc4232000 2000 linux_adobe.ko 91 0xc43ca000 2000 green_saver.ko % mount /dev/ada0p2 on / (ufs, local, soft-updates) devfs on /dev (devfs, local, multilabel) /dev/ada0p4 on /tmp (ufs, local, soft-updates) /dev/ada0p5 on /var (ufs, local, soft-updates) /dev/ada0p6 on /usr (ufs, local, soft-updates) linprocfs on /compat/linux/proc (linprocfs, local) % cat /etc/rc.conf hostname=ap200.home.net keymap=us.iso.kbd #ifconfig_fxp0=DHCP ifconfig_fxp0=SYNCDHCP sshd_enable=YES moused_type=auto moused_enable=YES moused_flags=-A 1.8 saver=green blanktime=900 ntpd_enable=YES # powerd_enable=YES # Set dumpdev to AUTO to enable crash dumps, NO to disable dumpdev=NO dbus_enable=YES hald_enable=YES apm_enable=YES linux_enable=YES Running 9.0 STABLE Cannot get the linux flashplugin to work on either firefox or chrome. Followed the handbook exactly. Using ports I installed the following. * installed nspluginwrapper which also installed linux_base_f10 * installed linux-f10-flashplugin11 * linked libflashplayer.so into /usr/local/lib/browser_plugins/ (checked that the link is in the directory) * ran nspluginwrapper -v -a -i (this ran fine) mount shows that linprocfs is on /compat/linux/proc about:plugins shows that flashplayer is enabled in both firefox and chrome. The plugins do not work anywhere I try. I messages like plugins-missing. Tried running firefox and chrome from the command line to check error messages. This is what shows up: *** NSPlugin Wrapper *** ERROR: NPP_New() wait for reply: Connection closed *** NSPlugin Wrapper *** WARNING:(/work/a/ports/www/nspluginwrapper/work/nspluginwrapper-1.4.4/src/npw-wrapper.c:2150):invoke_NPP_Destroy: assertion failed: (rpc_method_invoke_possible(plugin-connection)) I have updated my ports collection and tried deinstalling and reinstalling and have the same problem. Any ideas? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: acpidump -dt broken in 9 stable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2012-06-16 08:34:45 -0400, Konstantin Belousov wrote: On Fri, Jun 15, 2012 at 09:57:45PM -0700, mnln.l4 wrote: Just upgrade from 9.0 to 9 stable. `acpidump -dt` shows error message realpath tmp file: No such file or directory It is related to the recent change made to realpath(3) This was a bug/specific operation in acpidump relying on non-conforming realpath(3) behaviour. The r235948 should be merged. Committed as r237232. Thanks for letting me know. Jung-uk Kim -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.19 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk/fZkUACgkQmlay1b9qnVPwUgCgr8mQhgFSd3+Se8PapbbAN71P 0jkAoLL5LKm8xTIRDk0VBVdghNFYMXL6 =CqQO -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: acpidump -dt broken in 9 stable
On Mon, Jun 18, 2012 at 01:32:53PM -0400, Jung-uk Kim wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2012-06-16 08:34:45 -0400, Konstantin Belousov wrote: On Fri, Jun 15, 2012 at 09:57:45PM -0700, mnln.l4 wrote: Just upgrade from 9.0 to 9 stable. `acpidump -dt` shows error message realpath tmp file: No such file or directory It is related to the recent change made to realpath(3) This was a bug/specific operation in acpidump relying on non-conforming realpath(3) behaviour. The r235948 should be merged. Committed as r237232. Thanks for letting me know. Thank you for handling this. pgp2iuNit9KsA.pgp Description: PGP signature
Re: Cannot get flashplugin to work
In article op.wf3wn8m734t2sn@tech304 you write: On Mon, 18 Jun 2012 10:25:10 -0500, Michael Gass mg...@csbsju.edu wrote: Cannot get the linux flashplugin to work on either firefox or chrome. 9-STABLE here without issues. Can you post: /etc/rc.conf /etc/fstab output of `kldstat` output of `mount` output of `uname -a` In addition try running nspluginwrapper as user instead of as root, I think /usr/local/lib/browser_plugins has been dropped from the search path of some(?) browsers in the meantime. HTH, :) Juergen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: How to bind a route to a network adapter and not IP
On Monday 18 June 2012 12:54 Hans Petter Selasky wrote: On Monday 18 June 2012 00:00:51 H wrote: sth...@nethelp.no wrote: I loose packets because I use a WLAN adapter. Sometimes the link is down for various reasons, and then the routes start changing for manually created routes, and I want to prevent that. well that is certainly not a reason for changing routes I have the feeling you are not explaining good enough what really is going on and it may help sending your configurations and an example of routes and IP addresses before and after this route change Why is this so hard to understand? Link down leads to static route is deleted. This is standard FreeBSD behavior, and has been this way for as long as I can remember (btw, I believe this behavior is from the original BSD, not FreeBSD specific). You can show this by having a static default route pointing to an address on an Ethernet interface which has link. And then pulling the TP cable from the Ethernet interface. Observe that the default route is automatically removed. may be you have not understood your own problem yet because so far is nothing to be understood because none of your statements is correct, it is also not FreeBSD's standard behavior and never has been as long as there is the valid IP address on the related interface, no static route will be deleted, you can even boot without cable and the [default] static route is there so you need to explain better your problem in order to understand it probably you have some other stuff running, thirdparty network manager or something, incorrect or incomplete ppoe or dhc configuration or whatever leads to the problem FYI static routes usually are the manually configured routes, so what you say is redundant and not correct, I guess you're loosing some kind of dynamic route since WL networks usually do not run RIP/OSPF/BGP I guess the route you apparently loose is coming from some dhcp server and may be your dhclient configuration is incomplete or none existent, but here now it would be useful to see your config Hi, I think we need to distinguish between two matters. One is where the route is directly reachable on the local-net of the network adapter, and ARP is valid/responding. The second case is when the route is not directly reachable. The second case is where the problem happens, like Stian kindly explained. # For example: ifconfig wlan0 10.0.0.2 255.255.255.0 up # Assume the router is at 10.0.0.1 # And we want to reach a certain destination through 10.0.0.1 # Then we do: route add 10.22.1.1 10.0.0.1 no no no my friend, wrong again that is a static route and it goes away same way it was created, manually or by deleting the IP address 10.0.0.2 from the related interface wether there is or not an active link on that interface does not matter Hans # # First the FreeBSD network stack will resolve the ethernet address for # 10.0.0.1, and all 10.22.1.1 IP packets will get sent to 10.0.0.1. # However, if the wlan0 link goes down, which sometimes happen, then the route for 10.22.1.1 is deleted. This is sometimes very annoying, and also, if it happens that the 10.22.1.1 is reachable from another network adapter, then traffic sometimes can end up mis-routed. --HPS ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org -- HM +55 17 8111.3300 signature.asc Description: This is a digitally signed message part.
Re: How to bind a route to a network adapter and not IP
On Monday 18 June 2012 23:03:34 H wrote: On Monday 18 June 2012 12:54 Hans Petter Selasky wrote: On Monday 18 June 2012 00:00:51 H wrote: sth...@nethelp.no wrote: I loose packets because I use a WLAN adapter. Sometimes the link is down for various reasons, and then the routes start changing for manually created routes, and I want to prevent that. well that is certainly not a reason for changing routes I have the feeling you are not explaining good enough what really is going on and it may help sending your configurations and an example of routes and IP addresses before and after this route change Why is this so hard to understand? Link down leads to static route is deleted. This is standard FreeBSD behavior, and has been this way for as long as I can remember (btw, I believe this behavior is from the original BSD, not FreeBSD specific). You can show this by having a static default route pointing to an address on an Ethernet interface which has link. And then pulling the TP cable from the Ethernet interface. Observe that the default route is automatically removed. may be you have not understood your own problem yet because so far is nothing to be understood because none of your statements is correct, it is also not FreeBSD's standard behavior and never has been as long as there is the valid IP address on the related interface, no static route will be deleted, you can even boot without cable and the [default] static route is there so you need to explain better your problem in order to understand it probably you have some other stuff running, thirdparty network manager or something, incorrect or incomplete ppoe or dhc configuration or whatever leads to the problem FYI static routes usually are the manually configured routes, so what you say is redundant and not correct, I guess you're loosing some kind of dynamic route since WL networks usually do not run RIP/OSPF/BGP I guess the route you apparently loose is coming from some dhcp server and may be your dhclient configuration is incomplete or none existent, but here now it would be useful to see your config Hi, I think we need to distinguish between two matters. One is where the route is directly reachable on the local-net of the network adapter, and ARP is valid/responding. The second case is when the route is not directly reachable. The second case is where the problem happens, like Stian kindly explained. # For example: ifconfig wlan0 10.0.0.2 255.255.255.0 up # Assume the router is at 10.0.0.1 # And we want to reach a certain destination through 10.0.0.1 # Then we do: route add 10.22.1.1 10.0.0.1 no no no my friend, wrong again that is a static route and it goes away same way it was created, manually or by deleting the IP address 10.0.0.2 from the related interface wether there is or not an active link on that interface does not matter Hi, Can it be that dhclient which I'm running on this interface with manual routes disrupts stuff then ?? --HPS ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Kernel modules are broken after updating to the latest FreeBSD 9-STABLE
Yesterday I updated to the latest version of FreeBSD 9-STABLE. I always follow the procedure in the manual - http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html And I use the GENERIC config with no modifications. The system boots fine, however quite a few important kernel modules no longer works. Specifically nullfs, fdescfs, zfs, zlib, xfs, while some other modules like geom_mirror and geom_raid works. I get the following error messages: KLD nullfs.ko: depends on kernel - not available or version mismatch linker_load_file: Unsupported file type KLD fdescfs.ko: depends on kernel - not available or version mismatch linker_load_file: Unsupported file type What could have gone wrong? What can I do to fix this? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Kernel modules are broken after updating to the latest FreeBSD 9-STABLE
On Mon, 18 Jun 2012, Olav Gjerde wrote: Yesterday I updated to the latest version of FreeBSD 9-STABLE. I always follow the procedure in the manual - http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html And I use the GENERIC config with no modifications. The system boots fine, however quite a few important kernel modules no longer works. Specifically nullfs, fdescfs, zfs, zlib, xfs, while some other modules like geom_mirror and geom_raid works. I get the following error messages: KLD nullfs.ko: depends on kernel - not available or version mismatch linker_load_file: Unsupported file type KLD fdescfs.ko: depends on kernel - not available or version mismatch linker_load_file: Unsupported file type What could have gone wrong? What can I do to fix this? Did you miss the buildkernel/installkernel steps? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
