Solved - Atheros AR9285 on FreeBSD-8 [WAS: Re: Wireless networking question]
Hello Chip, On Fri, 30 Apr 2010 18:03:21 -0700 Chip Camden sterl...@camdensoftware.com wrote: On Apr 30 2010 13:39, S Roberts wrote: Hello Chip, Good to hear from you.., On Thu, 29 Apr 2010 15:52:13 -0700 Chip Camden sterl...@camdensoftware.com wrote: On Apr 26 2010 22:00, Carl Chave wrote: More info: I found the following in the output of pciconf -vl: no...@pci0:2:0:0: class=0x028000 card=0x10891a3b chip=0x002b168c rev=0x01 hdr=0x00 vendor = 'Atheros Communications Inc.' class = network From here: http://www.pcidatabase.com/vendor_details.php?id=174 It looks like someone has already patched 8.0-STABLE: http://forums.freebsd.org/showthread.php?t=6310highlight=Atheros+AR9285 The link to the .diff file 404's now, though. How can I get a copy? Or maybe I should just upgrade to STABLE? Well.., personally, I'd ping the patch author to confirm, but Yes, bumping to next STABLE would be the preferred option myself.., Regards, S Roberts Just for closure: upgrading to 8.0-STABLE went smoothly, and the wireless device works! Excellent - good to hear you got it all working. For posterity, I've updated the Subject Line so that others may benefit from this.., Regards, S Roberts Thanks for the help. ___ 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: Wireless networking question
Hello Chip, Good to hear from you.., On Thu, 29 Apr 2010 15:52:13 -0700 Chip Camden sterl...@camdensoftware.com wrote: On Apr 26 2010 22:00, Carl Chave wrote: More info: I found the following in the output of pciconf -vl: no...@pci0:2:0:0: class=0x028000 card=0x10891a3b chip=0x002b168c rev=0x01 hdr=0x00 vendor = 'Atheros Communications Inc.' class = network From here: http://www.pcidatabase.com/vendor_details.php?id=174 It looks like someone has already patched 8.0-STABLE: http://forums.freebsd.org/showthread.php?t=6310highlight=Atheros+AR9285 The link to the .diff file 404's now, though. How can I get a copy? Or maybe I should just upgrade to STABLE? Well.., personally, I'd ping the patch author to confirm, but Yes, bumping to next STABLE would be the preferred option myself.., Regards, S Roberts ___ 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: Wireless networking question
On Apr 30 2010 13:39, S Roberts wrote: Hello Chip, Good to hear from you.., On Thu, 29 Apr 2010 15:52:13 -0700 Chip Camden sterl...@camdensoftware.com wrote: On Apr 26 2010 22:00, Carl Chave wrote: More info: I found the following in the output of pciconf -vl: no...@pci0:2:0:0: class=0x028000 card=0x10891a3b chip=0x002b168c rev=0x01 hdr=0x00 vendor = 'Atheros Communications Inc.' class = network From here: http://www.pcidatabase.com/vendor_details.php?id=174 It looks like someone has already patched 8.0-STABLE: http://forums.freebsd.org/showthread.php?t=6310highlight=Atheros+AR9285 The link to the .diff file 404's now, though. How can I get a copy? Or maybe I should just upgrade to STABLE? Well.., personally, I'd ping the patch author to confirm, but Yes, bumping to next STABLE would be the preferred option myself.., Regards, S Roberts Just for closure: upgrading to 8.0-STABLE went smoothly, and the wireless device works! Thanks for the help. -- Sterling (Chip) Camden | camdensoftware.com | chipstips.com | chipsquips.com ___ 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: Wireless networking question
On Apr 26 2010 22:00, Carl Chave wrote: More info: I found the following in the output of pciconf -vl: no...@pci0:2:0:0: class=0x028000 card=0x10891a3b chip=0x002b168c rev=0x01 hdr=0x00 vendor = 'Atheros Communications Inc.' class = network From here: http://www.pcidatabase.com/vendor_details.php?id=174 It looks like someone has already patched 8.0-STABLE: http://forums.freebsd.org/showthread.php?t=6310highlight=Atheros+AR9285 The link to the .diff file 404's now, though. How can I get a copy? Or maybe I should just upgrade to STABLE? -- Sterling (Chip) Camden | camdensoftware.com | chipstips.com | chipsquips.com ___ 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: Wireless networking question
On Apr 26 2010 22:00, Carl Chave wrote: More info: I found the following in the output of pciconf -vl: no...@pci0:2:0:0: class=0x028000 card=0x10891a3b chip=0x002b168c rev=0x01 hdr=0x00 vendor = 'Atheros Communications Inc.' class = network From here: http://www.pcidatabase.com/vendor_details.php?id=174 0x002b is Atheros AR9285 Wireless LAN 802.11 a/b/g/n Controller ___ Thanks! That's a great resource. -- Sterling (Chip) Camden | camdensoftware.com | chipstips.com | chipsquips.com ___ 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: Wireless networking question
On Apr 25 2010 22:15, Kevin Kinsey wrote: Let me preface my commentary with I'm way out of my league, so #include disclaimer.h and all that ... For starters, in re: above, didn't someone suggest libpciaccess as the source for scanpci? I can't tell if you are misunderstanding what S Roberts suggested, or I am misunderstanding what you are responding. I'm pretty sure there's some misunderstanding here, though. Thanks for your response, Kevin. I did try rebuilding libpciaccess, to no avail. I also searched elsewhere. I thought we had pciconf output that stated it was an Atheros chipset? In that case, it would be the Azurewave, right? I'd suspect it might be supported under ath(4), but you'd wanna read the manpage and possibly even the source for any kind of confirmation on that; the manpage does specifically say that adapters based on the AR5005VL aren't supported. However, the manpage might be slightly out-of-date, also. Yes, pciconf says Atheros. I guess that does rule out Intel, and I see from a little searching that at least some Azurewave devices use an Atheros chipset. I, too, am a little out of my depth in this region, as is probably obvious from my posts. The other thing I recall seeing is that a new variant of a supported chipset comes out, and the driver code doesn't recognize it even though it might work well. Used to be something like a VENDOR_ID string in the source files; I don't know if it's still the case, but if it was, some people have been able to hack their own device support in rare cases simply by adding the new info to the driver file and recompiling it, but you'd want someone with a lot more $OS_foo than I have to help out with that (or tell you if it's even possible). This is open-source stuff; you might even get sam@ 's attention and get help from the writer himself if you're wearing your lucky sneakers. Yes, I've seen that done with video drivers. Perhaps I'll give it a go with the ath or uath driver, neither of which work for me out of the box (so to speak). Thanks again. -- Sterling (Chip) Camden | camdensoftware.com | chipstips.com | chipsquips.com ___ 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: Wireless networking question
More info: I found the following in the output of pciconf -vl: no...@pci0:2:0:0: class=0x028000 card=0x10891a3b chip=0x002b168c rev=0x01 hdr=0x00 vendor = 'Atheros Communications Inc.' class = network From here: http://www.pcidatabase.com/vendor_details.php?id=174 0x002b is Atheros AR9285 Wireless LAN 802.11 a/b/g/n Controller ___ 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: Wireless networking question
On Apr 24 2010 23:51, S Roberts wrote: I believe its been bundled into the libpciaccess port: http://www.freebsd.org/cgi/cvsweb.cgi/ports/devel/libpciaccess/ Doesn't seem to be there, and google isn't being helpful. A search of freshports.org didn't turn up anything either. Searching freebsd.org only shows our conversation. -- Sterling (Chip) Camden | camdensoftware.com | chipstips.com | chipsquips.com ___ 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: Wireless networking question
Chip Camden wrote: On Apr 24 2010 23:51, S Roberts wrote: I believe its been bundled into the libpciaccess port: http://www.freebsd.org/cgi/cvsweb.cgi/ports/devel/libpciaccess/ Doesn't seem to be there, and google isn't being helpful. A search of freshports.org didn't turn up anything either. Searching freebsd.org only shows our conversation. Likely your ports tree is rather out-of-date? The port directory is at /usr/ports/devel/libpciacess, and the import date on the Makefile is May 2008. Or, perhaps ports aren't installed? Try: $pkg_add -r \ ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/Packages-8-stable/devel/libpciaccess-0.10.6_1.tbz Kevin Kinsey ___ 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: Wireless networking question
Hello Chip, On Sun, 25 Apr 2010 12:10:40 -0700 Chip Camden sterl...@camdensoftware.com wrote: On Apr 24 2010 23:51, S Roberts wrote: I believe its been bundled into the libpciaccess port: http://www.freebsd.org/cgi/cvsweb.cgi/ports/devel/libpciaccess/ Doesn't seem to be there, and google isn't being helpful. A search of freshports.org didn't turn up anything either. Searching freebsd.org only shows our conversation. Hmmm.., you sure your ports system is installed / up-to-date there? Do you have any of the docs that would have shipped with the notebook? If not, I searched ASUS, and found a link to the English version manual here: http://support.asus.com/download/download.aspx?SLanguage=en-usproduct=3model=K72Ftype=mapf_type=19 I've not downloaded it, so please see if there's anything that can assist. There **are** other resources at the ASUS site - you just have to use the menu on the right to select your particular model and review the list of resources that gets returned.., Hope this helps.., Regards, S Roberts ___ 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: Wireless networking question
On Apr 25 2010 21:26, S Roberts wrote: Hmmm.., you sure your ports system is installed / up-to-date there? Do you have any of the docs that would have shipped with the notebook? If not, I searched ASUS, and found a link to the English version manual here: http://support.asus.com/download/download.aspx?SLanguage=en-usproduct=3model=K72Ftype=mapf_type=19 I've not downloaded it, so please see if there's anything that can assist. There **are** other resources at the ASUS site - you just have to use the menu on the right to select your particular model and review the list of resources that gets returned.., Hope this helps.., Regards, S Roberts Thanks for the attempt to help, but ports are up-to-date. I'm on 8.0-RELEASE amd64 -- maybe scanpci isn't available on amd64? The download for the manual is exactly the same as the paper manual that came with the notebook. It gives very little technical information. On the web site, all I could find is that it's 802.11n capable, which I already knew from the sales pamphlet. -- Sterling (Chip) Camden | camdensoftware.com | chipstips.com | chipsquips.com ___ 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: Wireless networking question
On Apr 25 2010 16:18, Chip Camden wrote: On Apr 25 2010 21:26, S Roberts wrote: Hmmm.., you sure your ports system is installed / up-to-date there? Do you have any of the docs that would have shipped with the notebook? If not, I searched ASUS, and found a link to the English version manual here: http://support.asus.com/download/download.aspx?SLanguage=en-usproduct=3model=K72Ftype=mapf_type=19 I've not downloaded it, so please see if there's anything that can assist. There **are** other resources at the ASUS site - you just have to use the menu on the right to select your particular model and review the list of resources that gets returned.., Hope this helps.., Regards, S Roberts Thanks for the attempt to help, but ports are up-to-date. I'm on 8.0-RELEASE amd64 -- maybe scanpci isn't available on amd64? The download for the manual is exactly the same as the paper manual that came with the notebook. It gives very little technical information. On the web site, all I could find is that it's 802.11n capable, which I already knew from the sales pamphlet. OK -- searching the ASUS site for Windows 7 64bit docs (that's what came on it), I find three possibilities for the wireless device: 1. Intel 1000 2. Intel 6200 3. Azurewave Looks like both of the first two are addressed by driver iwn on OpenBSD, but not on FreeBSD. The third one I don't see anywhere. Looking here: http://en.wikipedia.org/wiki/Comparison_of_open_source_wireless_drivers#FreeBSD Looks like that page was last updated for FreeBSD on April 25. In any case, I tried iwn, and that doesn't work. -- Sterling (Chip) Camden | camdensoftware.com | chipstips.com | chipsquips.com ___ 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: Wireless networking question
Chip Camden wrote: On Apr 25 2010 16:18, Chip Camden wrote: On Apr 25 2010 21:26, S Roberts wrote: Hmmm.., you sure your ports system is installed / up-to-date there? Do you have any of the docs that would have shipped with the notebook? If not, I searched ASUS, and found a link to the English version manual here: http://support.asus.com/download/download.aspx?SLanguage=en-usproduct=3model=K72Ftype=mapf_type=19 I've not downloaded it, so please see if there's anything that can assist. There **are** other resources at the ASUS site - you just have to use the menu on the right to select your particular model and review the list of resources that gets returned.., Thanks for the attempt to help, but ports are up-to-date. I'm on 8.0-RELEASE amd64 -- maybe scanpci isn't available on amd64? Let me preface my commentary with I'm way out of my league, so #include disclaimer.h and all that ... For starters, in re: above, didn't someone suggest libpciaccess as the source for scanpci? I can't tell if you are misunderstanding what S Roberts suggested, or I am misunderstanding what you are responding. I'm pretty sure there's some misunderstanding here, though. The download for the manual is exactly the same as the paper manual that came with the notebook. It gives very little technical information. On the web site, all I could find is that it's 802.11n capable, which I already knew from the sales pamphlet. OK -- searching the ASUS site for Windows 7 64bit docs (that's what came on it), I find three possibilities for the wireless device: 1. Intel 1000 2. Intel 6200 3. Azurewave Looks like both of the first two are addressed by driver iwn on OpenBSD, but not on FreeBSD. The third one I don't see anywhere. Looking here: http://en.wikipedia.org/wiki/Comparison_of_open_source_wireless_drivers#FreeBSD Looks like that page was last updated for FreeBSD on April 25. In any case, I tried iwn, and that doesn't work. I thought we had pciconf output that stated it was an Atheros chipset? In that case, it would be the Azurewave, right? I'd suspect it might be supported under ath(4), but you'd wanna read the manpage and possibly even the source for any kind of confirmation on that; the manpage does specifically say that adapters based on the AR5005VL aren't supported. However, the manpage might be slightly out-of-date, also. The other thing I recall seeing is that a new variant of a supported chipset comes out, and the driver code doesn't recognize it even though it might work well. Used to be something like a VENDOR_ID string in the source files; I don't know if it's still the case, but if it was, some people have been able to hack their own device support in rare cases simply by adding the new info to the driver file and recompiling it, but you'd want someone with a lot more $OS_foo than I have to help out with that (or tell you if it's even possible). This is open-source stuff; you might even get sam@ 's attention and get help from the writer himself if you're wearing your lucky sneakers. Kevin Kinsey ___ 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
Wireless networking question
A new notebook (ASUS K72F) has integrated wireles networking. The technical specifications are sadly lacking, so I don't know what chipset. The wired ethernet appears to use uath, but that's not working as a wlandev. Since most everything else is Intel, I figured it could be an Intel chipset, and since it supports 802.11n, I think its probably in the 6000 series. I tried all the Intel drivers that are listed here: http://en.wikipedia.org/wiki/Comparison_of_open_source_wireless_drivers#FreeBSD And none of them appeared to work. Looking a little further down, it seems that the Intel 6000 is supported by iwn on OpenBSD, but not on FreeBSD. But I could be barking up the entirely wrong tree. Can anyone shed some light here? Is there any way to query the hardware, short of opening the box (which will void the warranty)? TIA -- Sterling (Chip) Camden | camdensoftware.com | chipstips.com | chipsquips.com ___ 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: Wireless networking question
Hello Chip, On Sat, 24 Apr 2010 13:39:47 -0700 Chip Camden sterl...@camdensoftware.com wrote: A new notebook (ASUS K72F) has integrated wireles networking. The technical specifications are sadly lacking, so I don't know what chipset. The wired ethernet appears to use uath, but that's not working as a wlandev. Since most everything else is Intel, I figured it could be an Intel chipset, and since it supports 802.11n, I think its probably in the 6000 series. I tried all the Intel drivers that are listed here: http://en.wikipedia.org/wiki/Comparison_of_open_source_wireless_drivers#FreeBSD snipped Can anyone shed some light here? Is there any way to query the hardware, short of opening the box (which will void the warranty)? Easiest option would be to run a livecd of another more populous *nix flavour and see what it makes of the hardware. Needless to say, if you're so bold, you **can** always load windows and let window tell you what it is ;-) Regards, S Roberts TIA ___ 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: Wireless networking question
On Apr 24 2010 13:39, Chip Camden wrote: A new notebook (ASUS K72F) has integrated wireles networking. The technical specifications are sadly lacking, so I don't know what chipset. The wired ethernet appears to use uath, but that's not working as a wlandev. Since most everything else is Intel, I figured it could be an Intel chipset, and since it supports 802.11n, I think its probably in the 6000 series. I tried all the Intel drivers that are listed here: http://en.wikipedia.org/wiki/Comparison_of_open_source_wireless_drivers#FreeBSD And none of them appeared to work. Looking a little further down, it seems that the Intel 6000 is supported by iwn on OpenBSD, but not on FreeBSD. But I could be barking up the entirely wrong tree. Can anyone shed some light here? Is there any way to query the hardware, short of opening the box (which will void the warranty)? TIA -- Sterling (Chip) Camden | camdensoftware.com | chipstips.com | chipsquips.com ___ 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 More info: I found the following in the output of pciconf -vl: no...@pci0:2:0:0: class=0x028000 card=0x10891a3b chip=0x002b168c rev=0x01 hdr=0x00 vendor = 'Atheros Communications Inc.' class = network a...@pci0:3:0:0:class=0x02 card=0x18201043 chip=0x10631969 rev=0xc0 hdr=0x00 vendor = 'Attansic (Now owned by Atheros)' class = network subclass = ethernet Looks like the first entry show here is my wireless (guessing), because alc0 is my wired. Any ideas from that what driver I should be using? I've tried 'ifconfig wlan0 create wlandev ath0', as well as ath1..9 and uath0..9, and I always get: ifconfig: SIOCIFCREATE2: Device not configured -- Sterling (Chip) Camden | camdensoftware.com | chipstips.com | chipsquips.com ___ 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: Wireless networking question
On Apr 24 2010 21:55, S Roberts wrote: snip Easiest option would be to run a livecd of another more populous *nix flavour and see what it makes of the hardware. Needless to say, if you're so bold, you **can** always load windows and let window tell you what it is ;-) Regards, S Roberts The really sad thing is that notebook this came with Windows on it. Next time, I'll make sure I write down everything in Device Manager *before* I wipe Windows off the hard drive. Thanks for the response. -- Sterling (Chip) Camden | camdensoftware.com | chipstips.com | chipsquips.com ___ 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: Wireless networking question
Hello Chip, On Sat, 24 Apr 2010 14:00:29 -0700 Chip Camden sterl...@camdensoftware.com wrote: On Apr 24 2010 13:39, Chip Camden wrote: A new notebook (ASUS K72F) has integrated wireles networking. The technical specifications are sadly lacking, so I don't know what chipset. The wired ethernet appears to use uath, but that's not working as a wlandev. Since most everything else is Intel, I figured it could be an Intel chipset, and since it supports 802.11n, I think its probably in the 6000 series. I tried all the Intel drivers that are listed here: http://en.wikipedia.org/wiki/Comparison_of_open_source_wireless_drivers#FreeBSD And none of them appeared to work. Looking a little further down, it seems that the Intel 6000 is supported by iwn on OpenBSD, but not on FreeBSD. But I could be barking up the entirely wrong tree. Can anyone shed some light here? Is there any way to query the hardware, short of opening the box (which will void the warranty)? TIA snipped More info: I found the following in the output of pciconf -vl: no...@pci0:2:0:0: class=0x028000 card=0x10891a3b chip=0x002b168c rev=0x01 hdr=0x00 vendor = 'Atheros Communications Inc.' class = network a...@pci0:3:0:0: class=0x02 card=0x18201043 chip=0x10631969 rev=0xc0 hdr=0x00 vendor = 'Attansic (Now owned by Atheros)' class = network subclass = ethernet Not a whole lot there.., Does scanpci -v tell you any more details about the hardware? Regards, S Roberts Looks like the first entry show here is my wireless (guessing), because alc0 is my wired. Any ideas from that what driver I should be using? I've tried 'ifconfig wlan0 create wlandev ath0', as well as ath1..9 and uath0..9, and I always get: ifconfig: SIOCIFCREATE2: Device not configured ___ 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: Wireless networking question
On Apr 24 2010 22:07, S Roberts wrote: Not a whole lot there.., Does scanpci -v tell you any more details about the hardware? Regards, S Roberts I don't seem to have scanpci on my system, nor do I see it in the ports tree -- where would I find it? Thanks -- Sterling (Chip) Camden | camdensoftware.com | chipstips.com | chipsquips.com ___ 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: Wireless networking question
Hello Chip, On Sat, 24 Apr 2010 15:00:34 -0700 Chip Camden sterl...@camdensoftware.com wrote: On Apr 24 2010 22:07, S Roberts wrote: Not a whole lot there.., Does scanpci -v tell you any more details about the hardware? Regards, S Roberts I don't seem to have scanpci on my system, nor do I see it in the ports tree -- where would I find it? I believe its been bundled into the libpciaccess port: http://www.freebsd.org/cgi/cvsweb.cgi/ports/devel/libpciaccess/ Hope that helps.., Regards, S Roberts Thanks ___ 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
NetBSD networking question
Hello, my name is Shawn Hoffman, and I am the Staffing Manager for Logikos Inc. Logikos is a product software development firm located in Fort Wayne, Indiana. I am contacting you in hopes that you might be able to offer suggestions as to where we might find a contract NetBSD Administrator. We are beginning a project for a client that necessitates this background. Is there someone you know who might have an interest in a contract opportunity of this sort? If so, I would appreciate any assistance your network of contacts may offer. Thank you. Shawn Hoffman - Staffing Manager Logikos Inc, 2914 Independence Drive Fort Wayne, IN 46808 260-483-3638 260-484-5268 fax shoff...@logikos.com ___ 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: NetBSD networking question
On Tue, Jan 20, 2009 at 10:26 AM, Shawn Hoffman shoff...@logikos.comwrote: Hello, my name is Shawn Hoffman, and I am the Staffing Manager for Logikos Inc. Logikos is a product software development firm located in Fort Wayne, Indiana. I am contacting you in hopes that you might be able to offer suggestions as to where we might find a contract NetBSD Administrator. We are beginning a project for a client that necessitates this background. Is there someone you know who might have an interest in a contract opportunity of this sort? If so, I would appreciate any assistance your network of contacts may offer. Thank you. Shawn Hoffman - Staffing Manager Logikos Inc, 2914 Independence Drive Fort Wayne, IN 46808 260-483-3638 260-484-5268 fax shoff...@logikos.com Although you may find the person you need on this list, you will probably have better luck contacting the NetBSD community. You can find more information at http://netbsd.org. Best of luck, Andrew Gould ___ 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
networking question.
Hello Gurus, 192.168.0.1 is the internet server dialer (winXP) --- switch -- 192.168.0.2 FreeBSD 6.1 NAT 192.168.1.1 clients are 192.168.1.xxx everything works great, Internet goes to clients from the fbsd server all IPs can ping each other.. 192.168.1.5 can ping 192.168.0.1 To here and its great. But when any client 192.168.1.x tries to access the shared files on 192.168.0.1 it cannot. it says not a correct path, and it cannot see it, although it can PING it. I asume the diffrences in IPs although its on same LAN makes this class cannot access the other. Can someone kindly shade a light, on what should I do ? Thank you Marwan Sultan. _ FREE pop-up blocking with the new MSN Toolbar - get it now! http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: networking question.
This is more a windows problem and specific more a WINS/NETBios/name resolution problem. Do you got a dns server? Some kind of domain? What I understand from your story the following happens: Client queries on netbios level; who is \\computername to the masterbrowser list, can't find on local subnet, hence not found. Broadcasts don't travel beyond own subnet unless otherwise configured. What you should do is either connect via \\ip\share or get yourself some kind of AD DNS or a WINS Server and tell your clients to use WINS/DNS for name resolution. Then it should work. Hope this helps Patrick On Mon, November 13, 2006 22:38, Marwan Sultan wrote: Hello Gurus, 192.168.0.1 is the internet server dialer (winXP) --- switch -- 192.168.0.2 FreeBSD 6.1 NAT 192.168.1.1 clients are 192.168.1.xxx everything works great, Internet goes to clients from the fbsd server all IPs can ping each other.. 192.168.1.5 can ping 192.168.0.1 To here and its great. But when any client 192.168.1.x tries to access the shared files on 192.168.0.1 it cannot. it says not a correct path, and it cannot see it, although it can PING it. I asume the diffrences in IPs although its on same LAN makes this class cannot access the other. Can someone kindly shade a light, on what should I do ? Thank you Marwan Sultan. _ FREE pop-up blocking with the new MSN Toolbar - get it now! http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
networking question
Hello All, Well, I have FBSD 6.1-R server acting as NAT, and wired Internet HotSpot by chillispot and freerad for a building of 66 rj45 wall socket. The problem is, whenever someone having an internet account, he is able to give it to his friends to connect in the time he is not connected.. because one user at a time. but this account ment to be for a certain socket..its a personal account for 1 room. is there any way that i can controll the internet in this sockets? like to block all the sockets and unblock whatever i want.. so I will make sure this account will not run from any other socket outside the person room. those sockets are connected to each others throu 4 belkin switches hub. Well technically I knew I can Controll it by the MAC adres which chillispot already has this feature.. but i dunt want to use Mac Adrs Anyone has anyway to controll the sockets over the switches? impossible? Marwan Sultan _ Express yourself instantly with MSN Messenger! Download today it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [Mpd-users] pptp networking question
gahn wrote: wiht two default gateways, of course i could not connect to anywhere. how could i fix this? i just want to connect pptp server and get one ip address (192.168.2.10/24) with no default route on the pptp interface. This is a windows-side question.. I think windows does this (i.e., adding a default route for pptp connections) automatically. Not sure if there is any way to fix it (but I don't know much about windows). -Archie __ Archie Cobbs *CTO, Awarix* http://www.awarix.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
pptp networking question
hi: i got ppptp working or not? basically i got it configured and it seems to be working but i can'yt connect to anything on that subnet: C:\Documents and Settings\johndoipconfig Windows IP Configuration Ethernet adapter Wireless Network Connection: Connection-specific DNS Suffix . : IP Address. . . . . . . . . . . . : 192.168.1.104 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.1.1 Ethernet adapter Local Area Connection: Media State . . . . . . . . . . . : Media disconnected PPP adapter home: Connection-specific DNS Suffix . : IP Address. . . . . . . . . . . . : 192.168.2.10 Subnet Mask . . . . . . . . . . . : 255.255.255.255 Default Gateway . . . . . . . . . : 192.168.2.10 wiht two default gateways, of course i could not connect to anywhere. how could i fix this? i just want to connect pptp server and get one ip address (192.168.2.10/24) with no default route on the pptp interface. thanks a million. __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: (Yet Another) Home Networking Question
Rishi Chopra [EMAIL PROTECTED] writes: A question about the 'me' keyword and ipfw: The man page for ipfw states the following: me matches any IP address configured on an interface in the system. The address list is evaluated at the time the packet is analysed. If I set my oif to 'rl0' (a nic in my system) and I set the oip to 'me', what should the onet address be set to? Can I set the onet address to 'me' also? The oif has its address assigned by DHCP. No, that won't work. Normally, you won't need the network value unless you're serving as a gateway yourself. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: (Yet Another) Home Networking Question
A question about the 'me' keyword and ipfw: The man page for ipfw states the following: me matches any IP address configured on an interface in the system. The address list is evaluated at the time the packet is analysed. If I set my oif to 'rl0' (a nic in my system) and I set the oip to 'me', what should the onet address be set to? Can I set the onet address to 'me' also? The oif has its address assigned by DHCP. -R Lowell Gilbert wrote: Rishi Chopra [EMAIL PROTECTED] writes: Perhaps someone can help me with this small part of rc.firewall: [Ss][Ii][Mm][Pp][Ll][Ee]) # This is a prototype setup for a simple firewall. Configure this # machine as a named server and ntp server, and point all the machines # on the inside at this machine for those services. # set these to your outside interface network and netmask and ip oif=ed0 onet=192.0.2.0 omask=255.255.255.0 oip=192.0.2.1 # set these to your inside interface network and netmask and ip iif=ed1 inet=192.0.2.1 imask=255.255.255.0 iip=192.0.2.17 I'm curious about the difference between 'inet' and 'iip', what each one stands for, and how to configure 'onet/oip' if the outside interface network is configured via DHCP. Look a little more closely at the comment right before those lines. 'iif' is Inside InterFace, 'inet' is Inside NETwork, 'imask' is Inside netMASK, and 'iip' is Inside IP address. If your ouside address is assigned by DHCP, you can't set those in the script. You can use the me keyword (see man 8 ipfw), or set up the firewall in a DHCP hook, or just skip the address (it doesn't actually give you any extra security if you've got a single address on a single Ethernet network). I'm also curious about this little snippet (under the 'simple' profile): # Everything else is denied by default, unless the # IPFIREWALL_DEFAULT_TO_ACCEPT option is set in your kernel # config file. What happens if this option is set in my kernel config file? Can I safely comment out this line and use the 'simple' profile without affecting natd? It doesn't affect natd either way. Defaulting to deny is definitely the way to configure a firewall for security purposes -- don't accept anything you haven't explicitly configured yourself to let in. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: (Yet Another) Home Networking Question
Perhaps someone can help me with this small part of rc.firewall: [Ss][Ii][Mm][Pp][Ll][Ee]) # This is a prototype setup for a simple firewall. Configure this # machine as a named server and ntp server, and point all the machines # on the inside at this machine for those services. # set these to your outside interface network and netmask and ip oif=ed0 onet=192.0.2.0 omask=255.255.255.0 oip=192.0.2.1 # set these to your inside interface network and netmask and ip iif=ed1 inet=192.0.2.1 imask=255.255.255.0 iip=192.0.2.17 I'm curious about the difference between 'inet' and 'iip', what each one stands for, and how to configure 'onet/oip' if the outside interface network is configured via DHCP. I'm also curious about this little snippet (under the 'simple' profile): # Everything else is denied by default, unless the # IPFIREWALL_DEFAULT_TO_ACCEPT option is set in your kernel # config file. What happens if this option is set in my kernel config file? Can I safely comment out this line and use the 'simple' profile without affecting natd? Subhro wrote: Hi Rishi, You have to forward the ports required by WinVNC on the FreeBSD Gateway. Have you compiled IPDIVERT in your kernel? Read the ipfw manpages to find out how to forward ports. Regards Subhro Subhro Sankha Kar Indian Institute of Information Technology Block AQ-13/1, Sector V Salt Lake City PIN 700091 India -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rishi Chopra Sent: Sunday, January 11, 2004 1:42 PM To: Mike Maltese Cc: [EMAIL PROTECTED] Subject: Re: (Yet Another) Home Networking Question I was able to get my network up and running with the suggestions below. To review, my setup is the following: ISP FreeBSD Gateway Win2k Box --rl0--rl1--- ALL DHCP 192.168.0.1 192.168.0.2 rl0 is connected to the modem by ethernet and set for DHCP, the ISP's method of address asignment. rl1 is the second NIC in the BSD box, and is connected by crossover cable to the Win2k box. FreeBSD box and Win2k box can successfully ping each other, and both FreeBSD box and Win2k have working internet access. Everything is running A-OK. If I wish to host WinVNC on the Win2k box, do I need to make any changes to the Gateway? Specifically, WinVNC requires the Win2k box to be listening on 5800 and 5900; I have opened these ports (and these ports only) on the Win2k box. Do I need to change rc.conf or any other files on the gateway to specify that all incoming connections on 5800 and 5900 be forwarded from rl0 to rl1? Am I gonna have to step up to IPFW (yuck!) ?? Thanks, Rishi Mike Maltese wrote: (1) in /etc/rc.conf, I added the following natd_enable=YES natd_interface=rl0 ### public interface connected to cable modem gateway_enable=YES defaultrouter=192.168.0.1 ### LAN machines use this ifconfig_rl0=DHCP ### Astound uses dhcp ifconfig_rl1=inet 192.168.0.1 netmask 255.255.255.0 ### use for LAN hostname=idfubar.dyndns.org As a first step, try adding these lines to rc.conf: firewall_enable=YES firewall_type=open This will enable diversion of all traffic to natd. Read the man pages for natd and ipfw and http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/firewalls.html for more information. The easiest way to reinitialize the system is to type shutdown now. This will drop you into single user mode. Press return when prompted for a shell. Hit Ctrl+D and the rc system will be run through and put you back into multi-user mode. Check for connectivity from the router and the Windows box. As a side note, you can delete the defaultrouter entry. That's for your FreeBSD box, not LAN clients. It's getting reset by dhclient when it gets lease information from your ISP's DHCP server anyway. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: (Yet Another) Home Networking Question
Rishi Chopra wrote: Perhaps someone can help me with this small part of rc.firewall: [Ss][Ii][Mm][Pp][Ll][Ee]) # This is a prototype setup for a simple firewall. Configure this # machine as a named server and ntp server, and point all the machines # on the inside at this machine for those services. # set these to your outside interface network and netmask and ip oif=ed0 onet=192.0.2.0 omask=255.255.255.0 oip=192.0.2.1 # set these to your inside interface network and netmask and ip iif=ed1 inet=192.0.2.1 imask=255.255.255.0 iip=192.0.2.17 I'm curious about the difference between 'inet' and 'iip', what each one stands for, and how to configure 'onet/oip' if the outside interface network is configured via DHCP. I'm also curious about this little snippet (under the 'simple' profile): # Everything else is denied by default, unless the # IPFIREWALL_DEFAULT_TO_ACCEPT option is set in your kernel # config file. What happens if this option is set in my kernel config file? Can I safely comment out this line and use the 'simple' profile without affecting natd? [original questions responses snipped] inet = network, which is in part defined by your netmask- eg a netmask of 255.255.255.0 says that the first 3 octets are defining your network, and the last 3 define the individual host, thus a netmask of 255.255.255.0 allows for 256 hosts in theory, although .255 is the broadcast address, 0 is the network oip = actual IP address, which is a combination of the network you're on (192.0.2.0 in this case) and your host identifier (.1 in this case), so 192.0.2.1 I'm sure there are a million TCP/IP tutorials available on google, but doing a search on 'netmask' should explain anything I didn't do so well on ;-) Presumaby, IPFIREWALL_DEFAULT_TO_ACCEPT allows all packets throug the firewall as the default ruleset, which means the majority of your rules would become 'deny rules' to reject specific ports/packets etc..otherwise it's reversed, rejecting any/all packets unless you explictly allow them. Similar behavior to the functionality of the hosts.allow and hosts.deny files Obviously, denying everything explicitly not allowed by your ruleset is more securehowever, where you're unsure what ports (and protocols) specific applications or services use, expect to wind up spending a fair amount of time in refining your ruleset until all services you want allowed are in fact passed by the firewall. Accepting everything other than what you explicitly reject is better than no firewall, and isn't a bad starting point, combined with the output of netstat to monitor connections on a server, figuring out what traffic you absolutely must allow, and then eventually converting the system to a 'reject all' setup (after creating the 'allow ruleset' of course) Scott ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: (Yet Another) Home Networking Question
Rishi Chopra [EMAIL PROTECTED] writes: Perhaps someone can help me with this small part of rc.firewall: [Ss][Ii][Mm][Pp][Ll][Ee]) # This is a prototype setup for a simple firewall. Configure this # machine as a named server and ntp server, and point all the machines # on the inside at this machine for those services. # set these to your outside interface network and netmask and ip oif=ed0 onet=192.0.2.0 omask=255.255.255.0 oip=192.0.2.1 # set these to your inside interface network and netmask and ip iif=ed1 inet=192.0.2.1 imask=255.255.255.0 iip=192.0.2.17 I'm curious about the difference between 'inet' and 'iip', what each one stands for, and how to configure 'onet/oip' if the outside interface network is configured via DHCP. Look a little more closely at the comment right before those lines. 'iif' is Inside InterFace, 'inet' is Inside NETwork, 'imask' is Inside netMASK, and 'iip' is Inside IP address. If your ouside address is assigned by DHCP, you can't set those in the script. You can use the me keyword (see man 8 ipfw), or set up the firewall in a DHCP hook, or just skip the address (it doesn't actually give you any extra security if you've got a single address on a single Ethernet network). I'm also curious about this little snippet (under the 'simple' profile): # Everything else is denied by default, unless the # IPFIREWALL_DEFAULT_TO_ACCEPT option is set in your kernel # config file. What happens if this option is set in my kernel config file? Can I safely comment out this line and use the 'simple' profile without affecting natd? It doesn't affect natd either way. Defaulting to deny is definitely the way to configure a firewall for security purposes -- don't accept anything you haven't explicitly configured yourself to let in. -- Lowell Gilbert, embedded/networking software engineer, Boston area: resume/CV at http://be-well.ilk.org:8088/~lowell/resume/ username/password public ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: (Yet Another) Home Networking Question
Thanks for the generally good info; the 'me' keyword was the key piece of info that I needed =) Lowell Gilbert wrote: Rishi Chopra [EMAIL PROTECTED] writes: Perhaps someone can help me with this small part of rc.firewall: [Ss][Ii][Mm][Pp][Ll][Ee]) # This is a prototype setup for a simple firewall. Configure this # machine as a named server and ntp server, and point all the machines # on the inside at this machine for those services. # set these to your outside interface network and netmask and ip oif=ed0 onet=192.0.2.0 omask=255.255.255.0 oip=192.0.2.1 # set these to your inside interface network and netmask and ip iif=ed1 inet=192.0.2.1 imask=255.255.255.0 iip=192.0.2.17 I'm curious about the difference between 'inet' and 'iip', what each one stands for, and how to configure 'onet/oip' if the outside interface network is configured via DHCP. Look a little more closely at the comment right before those lines. 'iif' is Inside InterFace, 'inet' is Inside NETwork, 'imask' is Inside netMASK, and 'iip' is Inside IP address. If your ouside address is assigned by DHCP, you can't set those in the script. You can use the me keyword (see man 8 ipfw), or set up the firewall in a DHCP hook, or just skip the address (it doesn't actually give you any extra security if you've got a single address on a single Ethernet network). I'm also curious about this little snippet (under the 'simple' profile): # Everything else is denied by default, unless the # IPFIREWALL_DEFAULT_TO_ACCEPT option is set in your kernel # config file. What happens if this option is set in my kernel config file? Can I safely comment out this line and use the 'simple' profile without affecting natd? It doesn't affect natd either way. Defaulting to deny is definitely the way to configure a firewall for security purposes -- don't accept anything you haven't explicitly configured yourself to let in. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: (Yet Another) Home Networking Question
I was able to get my network up and running with the suggestions below. To review, my setup is the following: ISP FreeBSD Gateway Win2k Box --rl0--rl1--- ALL DHCP 192.168.0.1 192.168.0.2 rl0 is connected to the modem by ethernet and set for DHCP, the ISP's method of address asignment. rl1 is the second NIC in the BSD box, and is connected by crossover cable to the Win2k box. FreeBSD box and Win2k box can successfully ping each other, and both FreeBSD box and Win2k have working internet access. Everything is running A-OK. If I wish to host WinVNC on the Win2k box, do I need to make any changes to the Gateway? Specifically, WinVNC requires the Win2k box to be listening on 5800 and 5900; I have opened these ports (and these ports only) on the Win2k box. Do I need to change rc.conf or any other files on the gateway to specify that all incoming connections on 5800 and 5900 be forwarded from rl0 to rl1? Am I gonna have to step up to IPFW (yuck!) ?? Thanks, Rishi Mike Maltese wrote: (1) in /etc/rc.conf, I added the following natd_enable=YES natd_interface=rl0 ### public interface connected to cable modem gateway_enable=YES defaultrouter=192.168.0.1 ### LAN machines use this ifconfig_rl0=DHCP ### Astound uses dhcp ifconfig_rl1=inet 192.168.0.1 netmask 255.255.255.0 ### use for LAN hostname=idfubar.dyndns.org As a first step, try adding these lines to rc.conf: firewall_enable=YES firewall_type=open This will enable diversion of all traffic to natd. Read the man pages for natd and ipfw and http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/firewalls.html for more information. The easiest way to reinitialize the system is to type shutdown now. This will drop you into single user mode. Press return when prompted for a shell. Hit Ctrl+D and the rc system will be run through and put you back into multi-user mode. Check for connectivity from the router and the Windows box. As a side note, you can delete the defaultrouter entry. That's for your FreeBSD box, not LAN clients. It's getting reset by dhclient when it gets lease information from your ISP's DHCP server anyway. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
(Yet Another) Home Networking Question
Here's my setup: ISP FreeBSD Gateway Win2k Box --rl0--rl1--- ALL DHCP 192.168.0.1 192.168.0.2 rl0 is connected to the modem by ethernet and set for DHCP, the ISP's method of address asignment. rl1 is the second NIC in the BSD box, and is connected by crossover cable to the Win2k box. FreeBSD box and Win2k box can successfully ping each other, and FreeBSD box has working internet access. Everything has been freshly rebooted. Unfortunately, Win2k box cannot ping computers outside the local network. I'd like to share my internet connection (currently on my FreeBSD box only) with the Win2k box. Using a few articles I found on Google Groups, I got as far as this: FreeBSD Machine: (0) Generic Kernel, machine enabled as gateway using sysinstall, No firewall enabled (yet) (1) in /etc/rc.conf, I added the following natd_enable=YES natd_interface=rl0 ### public interface connected to cable modem gateway_enable=YES defaultrouter=192.168.0.1 ### LAN machines use this ifconfig_rl0=DHCP ### Astound uses dhcp ifconfig_rl1=inet 192.168.0.1 netmask 255.255.255.0 ### use for LAN hostname=idfubar.dyndns.org (2) in /etc/resolv.conf, DNS servers from ISP are listed automatically: nameserver 64.85.239.11 nameserver 64.85.239.2 (3) in /etc/hosts, (within the netmask): 192.168.0.1 idfubar.dyndns.org 192.168.0.2 computer.dyndns.org Win2k Machine: (1) start-networkdialupConnections -localareaconnection -properties -TCP/IP-properties: IP address 192.168.0.2 subnet mask 255.255.255.0 default gateway 192.168.0.1 preferred DNS server 64.85.239.11 alternate DNS server 64.85.239.2 What else do I need in order to get my Win2k box surfing? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: (Yet Another) Home Networking Question
(1) in /etc/rc.conf, I added the following natd_enable=YES natd_interface=rl0 ### public interface connected to cable modem gateway_enable=YES defaultrouter=192.168.0.1 ### LAN machines use this ifconfig_rl0=DHCP ### Astound uses dhcp ifconfig_rl1=inet 192.168.0.1 netmask 255.255.255.0 ### use for LAN hostname=idfubar.dyndns.org As a first step, try adding these lines to rc.conf: firewall_enable=YES firewall_type=open This will enable diversion of all traffic to natd. Read the man pages for natd and ipfw and http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/firewalls.html for more information. The easiest way to reinitialize the system is to type shutdown now. This will drop you into single user mode. Press return when prompted for a shell. Hit Ctrl+D and the rc system will be run through and put you back into multi-user mode. Check for connectivity from the router and the Windows box. As a side note, you can delete the defaultrouter entry. That's for your FreeBSD box, not LAN clients. It's getting reset by dhclient when it gets lease information from your ISP's DHCP server anyway. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: (Yet Another) Home Networking Question
hostname=idfubar.dyndns.org is wrong. This needs to be a fake domain name. Dyndns.org is real name. Hostname=idfubar.fbsdhome.com is better. To enable NATD you need ipfw firewall. These two statements are options for IPFW/Nated. Your win box can not reach public internet because it's private ip address is non-routable on the public internet, that why they are reserved for LANs. 1) in /etc/rc.conf, I added the following natd_enable=YES natd_interface=rl0 ### public interface connected to cable modem IPFW is not the firewall for the newbe, IPFILTER/IPNAT is easier. I have how-to if you are interested. BY the way you did real good job documenting your problem. Thanks -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Rishi Chopra Sent: Friday, December 12, 2003 9:45 PM To: [EMAIL PROTECTED] Subject: (Yet Another) Home Networking Question Here's my setup: ISP FreeBSD Gateway Win2k Box --rl0--rl1--- ALL DHCP 192.168.0.1 192.168.0.2 rl0 is connected to the modem by ethernet and set for DHCP, the ISP's method of address asignment. rl1 is the second NIC in the BSD box, and is connected by crossover cable to the Win2k box. FreeBSD box and Win2k box can successfully ping each other, and FreeBSD box has working internet access. Everything has been freshly rebooted. Unfortunately, Win2k box cannot ping computers outside the local network. I'd like to share my internet connection (currently on my FreeBSD box only) with the Win2k box. Using a few articles I found on Google Groups, I got as far as this: FreeBSD Machine: (0) Generic Kernel, machine enabled as gateway using sysinstall, No firewall enabled (yet) (1) in /etc/rc.conf, I added the following natd_enable=YES natd_interface=rl0 ### public interface connected to cable modem gateway_enable=YES defaultrouter=192.168.0.1 ### LAN machines use this ifconfig_rl0=DHCP ### Astound uses dhcp ifconfig_rl1=inet 192.168.0.1 netmask 255.255.255.0 ### use for LAN hostname=idfubar.dyndns.org (2) in /etc/resolv.conf, DNS servers from ISP are listed automatically: nameserver 64.85.239.11 nameserver 64.85.239.2 (3) in /etc/hosts, (within the netmask): 192.168.0.1 idfubar.dyndns.org 192.168.0.2 computer.dyndns.org Win2k Machine: (1) start-networkdialupConnections -localareaconnection -properties -TCP/IP-properties: IP address 192.168.0.2 subnet mask 255.255.255.0 default gateway 192.168.0.1 preferred DNS server 64.85.239.11 alternate DNS server 64.85.239.2 What else do I need in order to get my Win2k box surfing? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: (Yet Another) Home Networking Question
hostname=idfubar.dyndns.org is wrong. This needs to be a fake domain name. Dyndns.org is real name. Hostname=idfubar.fbsdhome.com is better. DynDNS is a dynamic DNS service. Nothing wrong here. Have a look at http://www.dyndns.org. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: (Yet Another) Home Networking Question
Rishi Chopra wrote: Here's my setup: snip What else do I need in order to get my Win2k box surfing? You did do a great job documenting the problem. You have also gotten good advice thus far. One thing you yet lack, according to the handbook, and it's a bit of a job. The GENERIC kernel doesn't ship with the following options, which you are supposed to need. options IPFIREWALL options IPDIVERT Add them to /usr/src/sys/i386/conf/GENERIC, run make buildkernel and make installkernel as root, then reboot and try again. (You do have /usr/src, right?) That is, unless there's some way to do this other than that...I didn't find it...but afterwards I'm natting happily all over the farm ;-) Kevin Kinsey ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: (Yet Another) Home Networking Question
One thing you yet lack, according to the handbook, and it's a bit of a job. The GENERIC kernel doesn't ship with the following options, which you are supposed to need. options IPFIREWALL options IPDIVERT Add them to /usr/src/sys/i386/conf/GENERIC, run make buildkernel and make installkernel as root, then reboot and try again. (You do have /usr/src, right?) That is, unless there's some way to do this other than that...I didn't find it...but afterwards I'm natting happily all over the farm ;-) The ipfw KLD should load on demand. I believe the it builds with divert enabled and defaults to block all. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
