NAT gateway
I'm setting up a FreeBSD 4.4 box again after a system crash. It's intended to be a gateway. I can communicate with the other hosts on my network, but I can't communicate outside the network. netstat -r shows that I have the default route; ppp is connecting to my ISP and getting the dynamically assigned address. But I can't ping or traceroute outside my LAN. (They work fine internally.) I'm using NAT and I have the kernel recompiled with IPFIREWALL and IPDIVERT. In rc.conf, natd and the firewall are enabled. Does anyone have any suggestions? Bob Hall To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Starting natd
I'm setting up a FBSD 4.4 box as a gateway. I've got natd_enable="YES" natd_interface="ppp0" in rc.config, but I can't get natd to run without entering natd -interface ppp0 at the comand prompt. I assume this is a configuration problem, but I've been through the files several times and can't find an error. Can someone tell me how to get natd to run automatically? Bob Hall To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: Starting natd
At 11:41 PM 10/26/2002 +0300, you wrote: On Sat, Oct 26, 2002 at 02:18:01PM -0500, Robert Hall wrote: Date: Sat, 26 Oct 2002 14:18:01 -0500 To: [EMAIL PROTECTED] From: Robert Hall <[EMAIL PROTECTED]> Subject: Starting natd I'm setting up a FBSD 4.4 box as a gateway. I've got natd_enable="YES" natd_interface="ppp0" in rc.config, but I can't get natd to run without entering natd -interface ppp0 at the comand prompt. I assume this is a configuration problem, but I've been through the files several times and can't find an error. Can someone tell me how to get natd to run automatically? If you use user ppp ( ppp(8) not pppd(8)) I suggest you to use build in nat in rc.conf : ppp_nat="YES" But if you for some reasons want to use natd, then you must first start ppp or pppd before starting natd. Note if you use ppp set interface to tun0 not to ppp0. I'm using kernel ppp (pppd). It is already set up and it runs. I have set up FreeBSD boxes before with this configuration, and natd started automatically and ran without any intervention on my part. For some reason, it doesn't do that this time, and I have to start it manually. I'm hoping someone can tell me why, so I can fix it. Bob Hall To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: Starting natd
At 12:18 AM 10/28/2002 +0200, D. Penev wrote: On Sun, Oct 27, 2002 at 02:18:21PM -0500, Robert Hall wrote: Date: Sun, 27 Oct 2002 14:18:21 -0500 To: [EMAIL PROTECTED] From: Robert Hall <[EMAIL PROTECTED]> Subject: Re: Starting natd At 11:41 PM 10/26/2002 +0300, you wrote: On Sat, Oct 26, 2002 at 02:18:01PM -0500, Robert Hall wrote: Date: Sat, 26 Oct 2002 14:18:01 -0500 To: [EMAIL PROTECTED] From: Robert Hall <[EMAIL PROTECTED]> Subject: Starting natd I'm setting up a FBSD 4.4 box as a gateway. I've got natd_enable="YES" natd_interface="ppp0" in rc.config, but I can't get natd to run without entering natd -interface ppp0 at the comand prompt. I assume this is a configuration problem, but I've been through the files several times and can't find an error. Can someone tell me how to get natd to run automatically? If you use user ppp ( ppp(8) not pppd(8)) I suggest you to use build in nat in rc.conf : ppp_nat="YES" But if you for some reasons want to use natd, then you must first start ppp or pppd before starting natd. Note if you use ppp set interface to tun0 not to ppp0. I'm using kernel ppp (pppd). It is already set up and it runs. I have set up FreeBSD boxes before with this configuration, and natd started automatically and ran without any intervention on my part. For some reason, it doesn't do that this time, and I have to start it manually. I'm hoping someone can tell me why, so I can fix it. Put in rc.conf: natd_flags="-dynamic" Thanks, that did it. But I've never needed that flag before. Bob Hall To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
DHCP using ral
I'm trying to set up a connection between an FBSD box and a wireless access point. The background is that there's no security on this network; as the person who set it up says, "You just start your computer and it works!" I have an XP box with a wireless NIC working, but I don't want to use the XP box as the gateway for my personal lan to an insecure network. On the XP box, if I point a browser to 192.168.1.1, I'm told that the router is "WRT54GX2", which I take to be a popular Linksys router. I don't have physical access to the router and I don't have the password for the router. I've got a wireless Linksys NIC that uses the ral driver facing the wireless router. The NIC facing my lan uses the em driver and is working fine. "uname -a" says FreeBSD 7.2-RELEASE #0. In rc.conf I have ifconfig_ral0="DHCP" After booting, if I ping 192.168.1.1, I get "no route to host" and I have no lease file in /var/db. "ifconfig ral0" tells me that I have no inet address associated with ral0, status is "no carrier", and the ssid is an empty string. "dhclient ral0" sends a series of DHCPDISCOVER messages, but I get no DHCPOFFER messages, and I get an empty lease file. If I run "ifconfig ral0" again, inet is 0.0.0.0, status is "associated", and ssid is the proper ssid for the wireless router. "ifconfig ral0 list scan" gives the proper information for the router. At some point I did get a proper lease. I don't know when or how. I've never had a usable connection to the router from the FBSD box, and I've never had access to the nameservers listed in the lease. If I rename the old lease file to dhcp.leases.ral0, and then run "dhclient ral0", I send 3 DHCPREQUEST messages, 2 DHCPDISCOVER messages, 2 DHCPREQUEST messages, and 6 DHCPDISCOVER messages. dhclient tells me that no DHCPOFFERs were received, and it binds to the address in lease file, 192.168.1.104. However, "ifconfig ral0" shows no inet address. I still can't ping the router. "ifconfig ral0 inet 192.168.1.104 netmask 255.255.255.0" assigns the specified values. Ping no longer tells me that there's no route to the host, but I'm getting about 95% packet loss. "netstat -r" now shows that link1 (ral0) is the gateway to 192.168.1.0. I still don't have a usable connection. resolv.conf says "nameserver 192.168.0.1", which is the nameserver for my personal lan. I can't nslookup URLs outside of my lan. If I manually add the nameservers in the dhcp lease, I can nslookup www.google.com. But ping has 100% packet loss. /etc/hosts associates 127.0.0.1 with localhost.krig.net, and 192.168.0.6 with stamfordbru.krig.net, which is correct for my lan. I'm stumped. :) I don't know if this is related; the XP box is telling me that the router has no connection to the internet, but it obviously does have a connection because the XP box can load web pages and I can use my gmail account. Thanks for any 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: DHCP using ral
On Mon, Jun 29, 2009 at 1:35 PM, Brent Bloxam wrote: > Robert Hall wrote: >> >> "ifconfig ral0 inet 192.168.1.104 netmask 255.255.255.0" assigns the >> specified values. Ping no longer tells me that there's no route to the >> host, but I'm getting about 95% packet loss. "netstat -r" now shows >> that link1 (ral0) is the gateway to 192.168.1.0. I still don't have a >> usable connection. >> > > Not especially helpful but I thought I'd throw this out there, Linksys > routers by default define their DHCP range as 192.168.1.100 - 192.168.1.149, > so pick an address outside that space if you're trying to assign statically. Good point. I tried that, but 192.168.1.104 and 192.168.1.150 work the same. No difference that I can tell > You can often get away with setting the IP of the router (default of > 192.168.1.1 for Linksys) as your DNS, as many Linksys routers have a built > in DNS proxy. Ah. That doesn't solve the problem, but it works and it's useful. > Are you sure you're getting a strong enough signal from the AP? I think I am. The XP box is reporting a strong signal, and it's on the self below the FBSD box. Of course, the XP box is also reporting no Internet connection, and I'm using it to reply to you, so who knows. The XP box with a Belkin NIC works pretty well. The boxes are very close, so I'm guessing that signal strength is not an issue. > Have you had > success with this WiFi card accessing other APs? I have no other APs I can try it with. The only other AP within range is none of my business. > Do you have access to a > different WiFi card you could try? No. This Linksys card was the only PCI card at the local MicroCenter that was supported by FBSD 7.2. :) Thanks for your interest in my problem. :) ___ 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 NICs on 7.2
I've been trying to get a Linksys WMP54G v. 4.1 to work on FBSD 7.2. It sort of works with the ral driver; I can set the ssid and inet and other values, but it won't associate with the access point or establish a useful connection. I've tried compiling ndis drivers for both the Linksys and a Belkin F5D7000 v. 7032 that I bought for my XP box. Both drivers crash the system when they load, leading to a reboot. Groveling through vmcore doesn't give me any clues about why the Belkin ndis crashes. The Linksys crash sends a message that it can't open /compat/ndis/rt2561s.bin. I googled for the firmware files and put them in /compat/ndis, but ndis still crashes. Both cards work fine on the XP box. Has anyone gotten either card to work on 7.2, either by using the ral driver or by compiling an ndis driver? ___ 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 NICs on 7.2
On Wed, Jul 1, 2009 at 1:55 PM, Paul B. Mahol wrote: > On 7/1/09, Robert Hall wrote: >> I've been trying to get a Linksys WMP54G v. 4.1 to work on FBSD 7.2. >> It sort of works with the ral driver; I can set the ssid and inet and >> other values, but it won't associate with the access point or >> establish a useful connection. > > Does it get any scan results? Yes. Scanning seems to work fine. > What kind of AP setup: NONE, WEP, WPA, WPA2 ... ? No security. >> I've tried compiling ndis drivers for both the Linksys and a Belkin >> F5D7000 v. 7032 that I bought for my XP box. Both drivers crash the >> system when they load, leading to a reboot. Groveling through vmcore >> doesn't give me any clues about why the Belkin ndis crashes. The >> Linksys crash sends a message that it can't open >> /compat/ndis/rt2561s.bin. I googled for the firmware files and put >> them in /compat/ndis, but ndis still crashes. Both cards work fine on >> the XP box. BTW, I'm not getting the open file failed message any longer, but the ndis driver still crashes the system. > You are using i386 FreeBSD, right? I should have posted this originally: $ uname -a FreeBSD stamfordbru.krig.net 7.2-RELEASE FreeBSD 7.2-RELEASE #3: Wed Jul 1 11:40:35 EDT 2009 r...@stamfordbru.krig.net:/usr/obj/usr/src/sys/STAMFORDBRU0 i386 ___ 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 NICs on 7.2
> And what about TX/RX signal? I don't know where to look for that. :) > Could you put backtrace somewhere? > http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-gdb.html Backtrace from crashing with a Belkin ndis: (kgdb) backtrace #0 doadump () at pcpu.h:196 #1 0xc055bcc3 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:418 #2 0xc055bece in panic (fmt=Variable "fmt" is not available. ) at /usr/src/sys/kern/kern_shutdown.c:574 #3 0xc079041c in trap_fatal (frame=0xd5f9571c, eva=0) at /usr/src/sys/i386/i386/trap.c:939 #4 0xc0790680 in trap_pfault (frame=0xd5f9571c, usermode=0, eva=0) at /usr/src/sys/i386/i386/trap.c:852 #5 0xc0790fd9 in trap (frame=0xd5f9571c) at /usr/src/sys/i386/i386/trap.c:530 #6 0xc077dbbb in calltrap () at /usr/src/sys/i386/i386/exception.s:159 #7 0xc32b5239 in BLKWGDv7_sys_drv_data_start () from /boot/modules/BLKWGDv7_sys.ko Previous frame inner to this frame (corrupt stack?) And from a Linksys crash (kgdb) backtrace #0 doadump () at pcpu.h:196 #1 0xc055bcc3 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:418 #2 0xc055bece in panic (fmt=Variable "fmt" is not available. ) at /usr/src/sys/kern/kern_shutdown.c:574 #3 0xc079041c in trap_fatal (frame=0xd600cb98, eva=382216) at /usr/src/sys/i386/i386/trap.c:939 #4 0xc0790680 in trap_pfault (frame=0xd600cb98, usermode=0, eva=382216) at /usr/src/sys/i386/i386/trap.c:852 #5 0xc0790fd9 in trap (frame=0xd600cb98) at /usr/src/sys/i386/i386/trap.c:530 #6 0xc077dbbb in calltrap () at /usr/src/sys/i386/i386/exception.s:159 #7 0xc329dde6 in rt61_sys_drv_data_start () from /boot/modules/./rt61_sys.ko Previous frame inner to this frame (corrupt stack?) I hope this is what you were asking for. :) ___ 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 NICs on 7.2
On Thu, Jul 2, 2009 at 6:04 AM, Paul B. Mahol wrote: > On 7/2/09, Robert Hall wrote: >>> And what about TX/RX signal? >> >> I don't know where to look for that. :) > > It is part of scan output. I don't remember seeing that in the output. I'll put the Linksys back in the FBSD box and look for it. Does it have another name? I can't find it on the ifconfig man page. On the XP box, the Linksys utility says that the transmit rate is 12 Mbps and the receive rate is 5.5 Mbps. When I move the Linksys NIC to the FBSD box, I get: $ ifconfig ral0 list scan SSIDBSSID CHAN RATE S:N INT CAPS livingroom 00:13:10:b9:e7:d66 54M -93:-95 100 E I think the "54M" is what you're asking for? I looked in man ifconfig and couldn't find TX or RX so I'm guessing that you're asking about the rate at which data is passed. Thanks for your 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 NICs on 7.2
On Thu, Jul 2, 2009 at 4:14 PM, Paul B. Mahol wrote: >> $ ifconfig ral0 list scan >> SSID BSSID CHAN RATE S:N INT CAPS >> livingroom 00:13:10:b9:e7:d6 6 54M -93:-95 100 E > > 93 is too low. Paul, I really appreciate your help. I'm obviously not an expert on either wireless networks or radio communication in general. But I doubt the accuracy of the scan. First of all, there's an XP box less than a foot away getting a "very good" signal (according to both the MS and the Belkin utilities), and successfully communicating with the wireless network. When I move the FBSD box and put the XP box in it's place, the XP box continues to report a good signal and continues to communicate with the network. While the XP box is reporting variations in rate and signal, the FBSD box reports no change. Secondly, when I run "ifconfig ral0 up scan", the scan hangs. It never completes or reports results. According to the man page, it's supposed to complete the scan, report the results, and exit. I have to Ctrl-C and run "ifconfig ral0 list scan" to get the results. So I know that at least part of the scan function doesn't work and I know that it's not detecting changes in rate and signal that are being reported by the XP box. 1) The XP box works fine with the Linksys NIC in it. 2) Both the XP and FBSD boxes are Dell Optiplex GX270, so they have identical hardware aside from the wireless NICs. 3) The md5 checksum for the install CD is correct, so I should have a good installation of 7.2 4) I seem to be getting a good signal, good enough to communicate with the network. 5) Both the Belkin and the Linksys work fine in the XP box. 6) The FBSD box always reports the same data, regardless of changes in conditions. 7) If I move the boxes and test them in the same physical location, oriented in the same direction, the XP box works and the FBSD box doesn't. So my guess is that output from a scan is the result of a problem in the driver, and not the result of actual conditions. If I thought I could solve this with a high gain antenna, I'd buy one in a second. But at the moment I have pretty good reason to believe that the problem isn't signal strength. I'd still like to compile a working ndis driver for either the Belkin F5D7000 v.7032 or the Linksys WMP54G v.4.1, if that is possible, or get the ral driver to work with the Linksys. I'd be willing to move from 7.2 to 6.4 if anyone has had success with that. ___ 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"
