Why network doesn't get initialized on system startup?
I have two similar machines, on one rc.conf has: wlans_ath0=wlan0 ifconfig_wlan0=ssid wifi-net-id weptxkey 1 deftxkey 1 wepmode on wepkey 0x1234567890 DHCP and it gets initialized at startup. On another rc.conf has: wlans_ndis0=wlan0 ifconfig_wlan0=ssid wifi-net-id weptxkey 1 deftxkey 1 wepmode on wepkey 0x1234567890 DHCP and this one doesn't get initialized at startup. The only difference is that the second one uses ndis0 with some preloaded ndis driver. It shouldn't matter. How can I make an interface to get initialized at startup and why it doesn't do this by itself? Yuri ___ 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: Why network doesn't get initialized on system startup?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 8/19/10 2:00 AM, Yuri wrote: On another rc.conf has: wlans_ndis0=wlan0 ifconfig_wlan0=ssid wifi-net-id weptxkey 1 deftxkey 1 wepmode on wepkey 0x1234567890 DHCP and this one doesn't get initialized at startup. Are you loading the ndis(4) kernel module at boot via loader.conf? - -- Glen Barber -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQEcBAEBAgAGBQJMbQL5AAoJEFJPDDeguUajLbMH/Atp8JcOOsKcwGGs2rujobIC xjZuOQGAtAr7pisuFiDvqiax4zyDLg8xiiSFQxYKjGNJIxdp2ltl96/rvBakrhfp gKegUBO6RG+QQIHLE8IDkcxzx+xLxOYBkVIzhlofDlPtgZqc9EzKq7ipbnG5mW4H TtkpuZtX+AWWyBYf3DxNgndfHYETTKXDYDvt1ELyFnAZta0e7mYH4FkUb0/j/4sp hpk408HwUR5VCFNL6OP9NW9aAemxLy5KHWJ8NSl/HgNktEcyIYCHAwUno1/QPHFi EHXaaqGOBr+EPyBIRyDM533t1HH9ztDoDnLrblBYre4LMs+lO4X7zPThAgAs4iM= =oL1E -END PGP SIGNATURE- ___ 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: Why network doesn't get initialized on system startup?
On 08/19/2010 03:10, Glen Barber wrote: Are you loading the ndis(4) kernel module at boot via loader.conf? Yes, all ndis-related drivers (ndis.ko, if_ndis.ko and actual ndis driver converted from windows one) are loaded from loader.conf. When system comes up ndis0 is fully functional and I can initialize it by hand fine. It just doesn't happen on startup. Yuri ___ 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: Why network doesn't get initialized on system startup?
Thursday, 19 August 2010 at 9:08:21 -0700, Yuri said: On 08/19/2010 03:10, Glen Barber wrote: Are you loading the ndis(4) kernel module at boot via loader.conf? Yes, all ndis-related drivers (ndis.ko, if_ndis.ko and actual ndis driver converted from windows one) are loaded from loader.conf. When system comes up ndis0 is fully functional and I can initialize it by hand fine. It just doesn't happen on startup. I can't remember where I saw this, but when you're using ndis you need to use SYNCDHCP instead of DHCP in ifconfig/rc.conf. Works for me no problem with a broadcom chip using ndis. Regards, Peter Harrison. Yuri ___ 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
