VirtualBox 4.1.22 and Bridged Network problems
Hello :-) I cannot get Bridged Network setup in VBox 4.1.22 on my 9.1RC3 AMD64 - I get no traffic to the host interface at all. Did anyone noticed this or related problems? I have tried to watch the host interface with WireShark. I have disabled local firewall. I have set net.inet.ip.forwarding=1. Still can't get the bridged connection working :-( Any hints appreciated :-) Tomek -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ 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: VirtualBox 4.1.22 and Bridged Network problems
This was brought up a few weeks/months ago and I seem to recall that setting the interface in *promiscuous* mode (monitoring) in the Host configuration (read, in your hypervisor) was mandatory. See if that helps. On Feb 6, 2013, at 3:03 PM, CeDeROM cede...@tlen.pl wrote: Hello :-) I cannot get Bridged Network setup in VBox 4.1.22 on my 9.1RC3 AMD64 - I get no traffic to the host interface at all. Did anyone noticed this or related problems? I have tried to watch the host interface with WireShark. I have disabled local firewall. I have set net.inet.ip.forwarding=1. Still can't get the bridged connection working :-( Any hints appreciated :-) Tomek -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ 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
Re: VirtualBox 4.1.22 and Bridged Network problems
Le Wed, 6 Feb 2013 15:03:36 +0100, CeDeROM cede...@tlen.pl a écrit : Hello, I cannot get Bridged Network setup in VBox 4.1.22 on my 9.1RC3 AMD64 - I get no traffic to the host interface at all. Did anyone noticed this or related problems? Works fine here (9.1-STABLE/amd64, virtual box 4.2.6). Be sure that the virbualbox kernel modules are in sync with your kernel (ie rebuilt virtualbox-ose-kmod). Regards. ___ 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: VirtualBox 4.1.22 and Bridged Network problems
I have built 4.2.6 and its working again! Thank you! :-) -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ 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
network problems after upgrade
Hello, I recently updated a FreeBSD system that has been running fine on 6.2 to 7.0. I rebuilt world kernel, installed world kernel, mergemastered, then rebooted. Now both network cards (em0, an Intel Pro/1000 v6.7.3, and rl0, an SMC eznet-10/100) are giving continual watchdog timeouts. Ifconfig shows them as active, with appropriate settings. There are no IRQ conflicts that I can see. Pinging loopback and the ip address of each card succeeds, but we can't ping anything outside of the system. We've tried disabling ipf; we've taken out each card in turn, trying it with only one card; we've tried building the generic kernel, just in case we accidentally took out something necessary; we've taken rc.conf down to just defining the gateway and addresses for the network interfaces; at this point I don't know what to try next. I can restore from backup to cvsup and get any current changes, then rebuild, but I hate going through all of that without any reason to believe anything will change. Any ideas for further troubleshooting would be very welcome! Renee -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: NATD Internal Network problems
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Chris S. Wilson Sent: Thursday, December 29, 2005 3:08 PM To: Greg Barniskis Cc: freebsd-questions Subject: RE: NATD Internal Network problems Weird, every other router I've used forwards all the packets properly, even my backup linksys when I hook it up. Those aren't forwarding the packets properly. The CPU in your Linksys isn't capabable of routing 100Mbt of traffic from an inside host to your linksys then back to the inside host. Try it some time and see for yourself. - copy a large file around or some such. While it's happening your Internet access will roll over and die. What the commercial routers like a Cisco can do is DNS translation, assuming the DNS server is on the outside. The DNS server responds with the outside IP address and the translator in the Cisco converts it to the inside private number. So the hosts on the inside can use a regular hostname that would normally resolve to the outside of the translator, and they get the inside number and nobody knows the difference. Some other translators pull this trick by having the DNS server set to the IP address of the translator, and they proxy all the DNS queries. There's a good chance that a large number of these every other router I've used routers you have used are in fact doing this, and you just didn't even notice. It is actually extremely easy to do the same thing on a FreeBSD box running as a translator. Just turn on named, and setup the named file for the domain used on your inside net, and forward all other queries to the real DNS servers on the outside. Then set the inside hosts to use the FreeBSD box as their DNS server. This is exactly how Linksys does it. If you need instructions just ask, they are very easy. Ted Really I don't want to do the split dns stuff, sadly I will have to move away from FreeBSD for performing this operation I guess. Thanks for the help! CW. -Original Message- From: Greg Barniskis [mailto:[EMAIL PROTECTED] Sent: Thursday, December 29, 2005 3:05 PM To: Chris S. Wilson Cc: freebsd-questions Subject: Re: NATD Internal Network problems Chris S. Wilson wrote: Hello! :) I am having a problem with freebsd 5.3-release and natd. When I try to connect to a service on my internal network to an IP on my external network that has a port redirected, it wont connect. IE: 67.128.100.2 is my external IP, on my internal network I try to connect to 67.128.101.2:80 which is forwarded in my natd.conf and the connection is refused. Does anyone know why? I don't know the exact technical reasons why but I will confirm for you that this simply does not work, and the reasons why center around it being a rather tortured mess. Your inside machines should reach your inside server by its inside address. Think about how you're sending your request outside the firewall (getting the request NATed on the way out) and then back in (getting the request re-NATed), and then having the reply packets from the web server have to take the reverse of that path. Yuck. Use split DNS so that that www.example.com appears to external clients as being your external NAT server address, and appears to inside clients as the web server's real inside address. -- Greg Barniskis, Computer Systems Integrator South Central Library System (SCLS) Library Interchange Network (LINK) gregb at scls.lib.wi.us, (608) 266-6348 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.371 / Virus Database: 267.14.9/216 - Release Date: 12/29/2005 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
NATD Internal Network problems
Hello! :) I am having a problem with freebsd 5.3-release and natd. When I try to connect to a service on my internal network to an IP on my external network that has a port redirected, it wont connect. IE: 67.128.100.2 is my external IP, on my internal network I try to connect to 67.128.101.2:80 which is forwarded in my natd.conf and the connection is refused. Does anyone know why? My Config: IPFW Startup Script: /sbin/ipfw -f flush /sbin/ipfw add divert natd all from any to any via xl1 /sbin/ipfw add pass all from any to any Natd.conf: use_sockets yes same_ports yes redirect_port tcp 10.0.10.2:8- 67.128.100.2:80 Rc.conf gateway_enable=YES firewall_enable=YES natd_enable=YES natd_interface=xl1 natd_flags=-m -s -f /etc/natd.conf Thanks! Chris W ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NATD Internal Network problems
Chris S. Wilson wrote: [ ... ] IE: 67.128.100.2 is my external IP, on my internal network I try to connect to 67.128.101.2:80 which is forwarded in my natd.conf and the connection is refused. Does anyone know why? Change the - to a 0 in: redirect_port tcp 10.0.10.2:8- 67.128.100.2:80 ...? -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: NATD Internal Network problems
Hmm, still does'nt work. That seemed to be a typo however I still cant connect :( CW -Original Message- From: Chuck Swiger [mailto:[EMAIL PROTECTED] Sent: Thursday, December 29, 2005 12:42 PM To: Chris S. Wilson Cc: freebsd-questions@freebsd.org Subject: Re: NATD Internal Network problems Chris S. Wilson wrote: [ ... ] IE: 67.128.100.2 is my external IP, on my internal network I try to connect to 67.128.101.2:80 which is forwarded in my natd.conf and the connection is refused. Does anyone know why? Change the - to a 0 in: redirect_port tcp 10.0.10.2:8- 67.128.100.2:80 ...? -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NATD Internal Network problems
Chris S. Wilson wrote: Hmm, still does'nt work. That seemed to be a typo however I still cant connect :( Does telnet 10.0.10.2 80 from the firewall box work? Does normal NAT work OK (ie, can internal machines connect outside)? Does not using the external IP help: redirect_port tcp 10.0.10.2:80 80 Be prepared to invoke 'tcpdump' to see what is going on... -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: NATD Internal Network problems
Everything works great from the nat box and from the outside (people are currently using it to get into my web server from the outside). It's odd. CW. -Original Message- From: Chuck Swiger [mailto:[EMAIL PROTECTED] Sent: Thursday, December 29, 2005 12:55 PM To: Chris S. Wilson Cc: freebsd-questions@freebsd.org Subject: Re: NATD Internal Network problems Chris S. Wilson wrote: Hmm, still does'nt work. That seemed to be a typo however I still cant connect :( Does telnet 10.0.10.2 80 from the firewall box work? Does normal NAT work OK (ie, can internal machines connect outside)? Does not using the external IP help: redirect_port tcp 10.0.10.2:80 80 Be prepared to invoke 'tcpdump' to see what is going on... -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NATD Internal Network problems
Chris S. Wilson wrote: Hello! :) I am having a problem with freebsd 5.3-release and natd. When I try to connect to a service on my internal network to an IP on my external network that has a port redirected, it wont connect. IE: 67.128.100.2 is my external IP, on my internal network I try to connect to 67.128.101.2:80 which is forwarded in my natd.conf and the connection is refused. Does anyone know why? I don't know the exact technical reasons why but I will confirm for you that this simply does not work, and the reasons why center around it being a rather tortured mess. Your inside machines should reach your inside server by its inside address. Think about how you're sending your request outside the firewall (getting the request NATed on the way out) and then back in (getting the request re-NATed), and then having the reply packets from the web server have to take the reverse of that path. Yuck. Use split DNS so that that www.example.com appears to external clients as being your external NAT server address, and appears to inside clients as the web server's real inside address. -- Greg Barniskis, Computer Systems Integrator South Central Library System (SCLS) Library Interchange Network (LINK) gregb at scls.lib.wi.us, (608) 266-6348 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: NATD Internal Network problems
Weird, every other router I've used forwards all the packets properly, even my backup linksys when I hook it up. Really I don't want to do the split dns stuff, sadly I will have to move away from FreeBSD for performing this operation I guess. Thanks for the help! CW. -Original Message- From: Greg Barniskis [mailto:[EMAIL PROTECTED] Sent: Thursday, December 29, 2005 3:05 PM To: Chris S. Wilson Cc: freebsd-questions Subject: Re: NATD Internal Network problems Chris S. Wilson wrote: Hello! :) I am having a problem with freebsd 5.3-release and natd. When I try to connect to a service on my internal network to an IP on my external network that has a port redirected, it wont connect. IE: 67.128.100.2 is my external IP, on my internal network I try to connect to 67.128.101.2:80 which is forwarded in my natd.conf and the connection is refused. Does anyone know why? I don't know the exact technical reasons why but I will confirm for you that this simply does not work, and the reasons why center around it being a rather tortured mess. Your inside machines should reach your inside server by its inside address. Think about how you're sending your request outside the firewall (getting the request NATed on the way out) and then back in (getting the request re-NATed), and then having the reply packets from the web server have to take the reverse of that path. Yuck. Use split DNS so that that www.example.com appears to external clients as being your external NAT server address, and appears to inside clients as the web server's real inside address. -- Greg Barniskis, Computer Systems Integrator South Central Library System (SCLS) Library Interchange Network (LINK) gregb at scls.lib.wi.us, (608) 266-6348 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NATD Internal Network problems
Chris S. Wilson wrote: Weird, every other router I've used forwards all the packets properly, even my backup linksys when I hook it up. Probably works there because there's not a very complex packet filtering operation in the middle when using an off-the-shelf router. Keep in mind that I'm speaking from distant memory. What you describe doesn't work for me, never did, and I know it's been talked about on this list as being an undesirable thing to do anyway, given that there are better alternatives than torturing your packets. You can possibly make FreeBSD do what you want, but (IIRC) it's going to take some ipfw wizardry, or whatever you're using to drive packets into natd. Also, I believe the result of that is that you'd have to create a less secure set of rules about what is permitted to pass. In other words the real reason this doesn't work is that as a best practice, it shouldn't. -- Greg Barniskis, Computer Systems Integrator South Central Library System (SCLS) Library Interchange Network (LINK) gregb at scls.lib.wi.us, (608) 266-6348 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Network problems?
I use FreeBSD 4.11-RELEASE. In my rc.conf I have these lines: firewall_enable=YES firewall_logging=YES firewall_script=/root/ipfw.sh. In /root/ipfw.sh I have added a few more lines for ifconfig(setting IP,MAC). The problem is that, when I try to use a different MAC and IP, the apache starting freezes, and, when trying the startx command, it doesn`t do anything, it does`nt yield anything. On a 4.8 Release I tried to change the MAC before the IP, and these problems seemed to disappear. And, of course, the network card is working(UP adn RUNNING (from ifconfig)), no metter of the ip and MAC. Could it be something because of the name of the computer, is there any other files but /etc/hosts, /etc/host.conf?? Thank you. __ 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]
Network problems?
I use 4.11R of FreeBSD. In my rc.conf file I have these lines: firewall_enable=YES firewall_logging=YES firewall_script=/root/ipfw.sh In /root/ipfw.sh there are ipfw commands, and, commands for configuring the IP and MAC. When changing an entry (an IP and a MAC) with other one I experience this problem: on boot time apache freezes, and, ignoring this, startx freezes too. I have to mention that I have 2 network cards, but I use only one at a time, the second not being connected to the switch. Id doesn`t meeter the Ip or the MAC, the network device is UP and RUNNING, everytihng is ok. Could it be because of the hostname??? I can`t figure out this. Thank you for your help. __ 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: ifconfig in rc.conf network problems
On stardate Sun, 30 May 2004, the wise Joost Bekkers entered: On Sun, May 30, 2004 at 11:34:43PM +0200, Olaf Hoyer wrote: 2) put the media change in a separate shell script, and throw it unter /usr/local/etc/rc.d, so that it will be executed later on something like: cat dc0-speedchange.sh #!/bin/sh ifconfig dc0 media 100baseTX You might want to put stuff like that in /etc/start_if.dc0 It gets executed just before the ip address is set or dhclient is started. Yes, this did the trick. Thanks, Marco -- Message will arrive in the mail. Destroy, before the FBI sees it. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ifconfig in rc.conf network problems
On stardate Sun, 30 May 2004, the wise Warren Block entered: On Sun, 30 May 2004, Marco Beishuizen wrote: I used to have two ifconfig lines in my rc.conf: ifconfig_dc0=DHCP ifconfig_dc0=media autoselect The first to enable DHCP and the second to set my networkcard to 100BaseTX full duplex. Can rc.conf work that way? rc.conf is just a shell script, and you're assigning values to variables, so the second declaration would overwrite the first. As to why that would have worked for you... After dhclient runs successfully once, some of the information is kept on disk (resolv.conf, default route). Maybe it was enough? I don't know why but it did work. Now I put the media autoselect line in /etc/start_if.dc0 and that works. Thanks, Marco -- Vote for ME -- I'm well-tapered, half-cocked, ill-conceived and TAX-DEFERRED! ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
ifconfig in rc.conf network problems
I used to have two ifconfig lines in my rc.conf: ifconfig_dc0=DHCP ifconfig_dc0=media autoselect The first to enable DHCP and the second to set my networkcard to 100BaseTX full duplex. Now after an upgrade to 4.10-release this doesn't work anymore. When I put both lines in rc.conf only the second line is effective and overrides the first, but I want to use both DHCP and 100BaseTX. I need to use the media autoselect because the networkcard defaults to 10BaseT but I want to use 100Mbit. When I don't use DHCP the network is unreachable. Pinging then gives a no route to host. How do I solve this problem? Marco -- Sweater, n.: A garment worn by a child when its mother feels chilly. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ifconfig in rc.conf network problems
On Sun, 30 May 2004, Marco Beishuizen wrote: I used to have two ifconfig lines in my rc.conf: ifconfig_dc0=DHCP ifconfig_dc0=media autoselect The first to enable DHCP and the second to set my networkcard to 100BaseTX full duplex. Now after an upgrade to 4.10-release this doesn't work anymore. When I put both lines in rc.conf only the second line is effective and overrides the first, but I want to use both DHCP and 100BaseTX. I need to use the media autoselect because the networkcard defaults to 10BaseT but I want to use 100Mbit. When I don't use DHCP the network is unreachable. Pinging then gives a no route to host. There are two solutions: 1) (Untested by me) ifconfig_dc0=DHCP media 100baseTX 2) put the media change in a separate shell script, and throw it unter /usr/local/etc/rc.d, so that it will be executed later on something like: cat dc0-speedchange.sh #!/bin/sh ifconfig dc0 media 100baseTX HTH Olaf -- Olaf Hoyer[EMAIL PROTECTED] Fuerchterliche Erlebniss geben zu raten, ob der, welcher sie erlebt, nicht etwas Fuerchterliches ist. (Nietzsche, Jenseits von Gut und Boese) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ifconfig in rc.conf network problems
On Sun, May 30, 2004 at 11:34:43PM +0200, Olaf Hoyer wrote: 2) put the media change in a separate shell script, and throw it unter /usr/local/etc/rc.d, so that it will be executed later on something like: cat dc0-speedchange.sh #!/bin/sh ifconfig dc0 media 100baseTX You might want to put stuff like that in /etc/start_if.dc0 It gets executed just before the ip address is set or dhclient is started. -- greetz Joost [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ifconfig in rc.conf network problems
On Sun, 30 May 2004, Marco Beishuizen wrote: I used to have two ifconfig lines in my rc.conf: ifconfig_dc0=DHCP ifconfig_dc0=media autoselect The first to enable DHCP and the second to set my networkcard to 100BaseTX full duplex. Can rc.conf work that way? rc.conf is just a shell script, and you're assigning values to variables, so the second declaration would overwrite the first. As to why that would have worked for you... After dhclient runs successfully once, some of the information is kept on disk (resolv.conf, default route). Maybe it was enough? Now after an upgrade to 4.10-release this doesn't work anymore. When I put both lines in rc.conf only the second line is effective and overrides the first, but I want to use both DHCP and 100BaseTX. I need to use the media autoselect because the networkcard defaults to 10BaseT but I want to use 100Mbit. When I don't use DHCP the network is unreachable. Pinging then gives a no route to host. There's an example of specifying media type in the dhclient.conf man page. -Warren Block * Rapid City, South Dakota USA ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
ed1 network problems on laptop
I've got a Sony VAIO PCG-FX101 (vanilla Celeron 600 laptop). It's run FreeBSD without a problem before. I just installed a new hard drive and installed 4.8-RELEASE on it. Now, I'm having all kinds of network problems that I didn't have a few days ago with the exact same hardware/OS (except the hard drive). I'm using a SMC PC-Card NIC (comes up as ed1). When I try to cvsup my source tree or ports, I get a message like this: TreeList failed: Network write failure: Connection closed That's not the only error I've seen while cvsupping, but the only one I've seen today. It happens every time I try to cvsup. When FTPing anything, the connection hangs mid-session (unless it's a small up/download). I've been able to install some ports, but usually they hang on the FTP download. When SSHing to other hosts, I can go merrily along, but within five or ten minutes, I lose the connection. SOME SUCCESS I was able to successfully cvsup my source tree and ports tree AND portinstall XFree86-4 and xcfe4 (big downloads, LOTS of dependencies). The way it worked was this: I'd tried and tried to cvsup without luck. I left the machine on and went to the office. FROM MY OFFICE FREEBSD MACHINE, I was able to log into my home machine, su to root, flawlessly cvsup and portinstall a bunch of things. I thought my problems were somehow solved -- WRONG. When I try doing any of those things from the machine itself, I can't. Since I was able to cvsup remotely, I've rebuilt my whole system (world and kernel) to 4.8-STABLE. SOME TRIAL-AND-ERROR I've done web searches on the error string above and found people with the same problem (apparently), but no definitive solution. I've made sure that there's no IRQ conflict with the NIC (it shared IRQ 3 with the sio1, which I've commented out of the kernel and rebuilt). I've also made sure the laptop's BIOS is set for a non-PNP OS. I had 4.8-STABLE running on this machine a few days ago (on a too-small hard drive) without a hitch. No network glitches at all. Argh. Any clues?? I don't wanrt to re-install from scratch -- and doubt it would do any good! -- Michael A. Smith [EMAIL PROTECTED] Programmer at Large ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Strange FreeBSD / KDE behaviour during network problems
Hi! today our company's inet falled out for a few hours. Only intranet worked. During this time I've booted my FreeBSD-STABLE (which took quite long due to ntpdate and hostname) and tried to start KDE with startx. It did not work and din't even print messages to the console. So I rebooted and tried again. Sometimes KDE started, sometimes it didn't, and other times it started very slowly. Also not all (KDE) applications could be launched. I recently set up my first FreeBSD+XFree86+KDE based desktop machine, and ISTR having similar problems when the machine was unable to resolve its own hostname. I cured it by adding relevant entries to /etc/hosts. -- Toomas Aas | [EMAIL PROTECTED] | http://www.raad.tartu.ee/~toomas/ * What are you looking down here for? Read the message! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Strange FreeBSD / KDE behaviour during network problems
Hi there, today our company's inet falled out for a few hours. Only intranet worked. During this time I've booted my FreeBSD-STABLE (which took quite long due to ntpdate and hostname) and tried to start KDE with startx. It did not work and din't even print messages to the console. So I rebooted and tried again. Sometimes KDE started, sometimes it didn't, and other times it started very slowly. Also not all (KDE) applications could be launched. Well, I wonder what this could be. From my point of view this is rather undefinable, and the sylogs don't reveal anything useful neither. What could be the reason - and more important - how do I make my workstation work properly without inet? Thx -- +++ GMX - Mail, Messaging more http://www.gmx.net +++ NEU: Mit GMX ins Internet. Rund um die Uhr für 1 ct/ Min. surfen! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: DHCP/network problems when installing, dhclient returns status of 2
Sunday, September 29, 2002, 12:06:16 AM, you wrote: DZ Hello all. DZ I looked at the lists and this (unfortunately) looked to be the most DZ relevant list to post to. If there is a more focused list (for networking, DZ say), please direct me to it. Thanks! I think you are on the right list. DZ Otherwise DZ I've been googling all over trying to find out what the status of dhclient DZ means and coming up with nothing. DZ My setup is a little bit weird: I have a FreeBSD machine currently serving DZ happily. It is also configured to act as a basic firewall so my laptop can DZ access the Internet. Usually, I just use static settings on my laptop to DZ communicate between the server and the laptop. I just recently got the DHCP DZ server going, and all is well. Laptop (Mac OS9.2.2, Open Transport 2.7.9) DZ works A-OK, discover, offer, request, acknowledge are all great... Did you install net/isc-dhcp3/? DZ Currently, I am trying to install (using FTP) FreeBSD on a *different* DZ machine, one that should communicate just like my laptop, but I get nothing. DZ Sysinstall DHCP server-scan times out and I get the regular network DZ configuration screen. During the installation you get a option to setup one (more can be a problem). DZ If I enter my data in as best I can (what is the host/domain supposed to be? DZ I'm using urbanpush.com since that's what the frontline FreeBSD box is DZ serving, but the new backline machine doesn't have an hostname or anything. DZ I expect that the frontline doesn't know how to address the backline? Can I DZ use an IP, namely what I want the backline machine to be? I tried that and DZ still no go) I have this: The host/domain name doesn't matter. You are free to choice any host/domain name for you intranet. DZ SETTINGS: DZ Host: hilary.urbanpush.com DZ Domain: urbanpush.com DZ IPv4 Gateway: 10.0.0.1 // IP of frontline machine ie. Router DZ Name Server: 129.128.5.233 // the one I always use DZ IPv4 Address: 10.0.0.2 // IP I want this machine to be on local network DZ Netmask: 255.0.0.0 // Class A type network DZ No extra ifconfig options... You got these values by clicking DHCP rigth? DZ ALT-F2 DEBUG LOG OUTPUT: DZ During DHCP try I get this: DZ Notify: Scanning for DHCP servers... DZ Executing command 'dhclient -1 fxp0' //fxp0 - ethernet device address DZ Command 'dhclient -1 fxp0' returns status of 2 DZ To note, the frontline box (dhcpd) does not display any DHCP-related DZ messages during this attempt. Try killing dhcpd on the server and starting it in the foreground with debug options. 'dhcpd -d' you may need other flag, check 'man dhcpd' for these. DZ After I try to configure it manually (with above settings) I get this: DZ Wrote out /etc/resolv.conf DZ Wrote out /etc/hosts DZ Init routine called for network device fxp0 DZ ifconfig fxp0 inet 10.0.0.2 netmask 255.0.0.0 DZ Executing command 'ifconfig fxp0 inet 10.0.0.2 netmask 255.0.0.0' DZ Command 'ifconfig fxp0 inet 10.0.0.2 netmask 255.0.0.0' returns status of 0 DZ // I assume that's good DZ Adding default route to 10.0.0.1 DZ Executing command 'route -n add default 10.0.0.1' DZ add net default 10.0.0.1 DZ Command 'route -n add default 10.0.0.1' returns status of 0 DZ // I assume that's also good You wan't to check the /etc/rc.conf file afther the installation. If you find something like xxx_fxp0=DHCP all is ok. DZ Network initialized successfully. // Yay! DZ hostname = 'ftp.freebsd.org' // The FTP server I chose DZ dir = '/' DZ port # = '21' DZ Notify: Looking up host ftp.freebsd.org. DZ Starting DNS. DZ Looking up hostname, ftp.freebsd.org, using getaddrinfo(AI_NUMERICHOST). DZ Looking up hostname, ftp.freebsd.org, using getaddrinfo(). DZ And then it just sits there. After I hit the OK, the ethernet's LEDs flash a DZ couple times and then nothing. It doesn't timeout, it doesn't stop. It seems DZ like my Name Server is not responding, but I've never had a problem with DZ that one before. You are behind a NAT server right? Then you have to use the passive FTP mode. Normal mode doesn't work. DZ I think I will soon take the box to work and jack into a real network, where DZ I know I have a host name and everything, but I still like to know if anyone DZ has any ideas, for future reference. DZ Terribly sorry about the length. Thought I should give you as much info as I DZ could. Its better to put in a little to much then a little to less. DZ Thanks in advance for any advice/info you might be able to offer. If you arn't able to install it with DHCP, try giving it a static IP adres. You can change it later to DHCP. -- Best regards, Alex The FreeBSD handbook http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/index.html To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: DHCP/network problems when installing, dhclient returnsstatus of 2
Comments in line... DZ My setup is a little bit weird: I have a FreeBSD machine currently serving DZ happily. It is also configured to act as a basic firewall so my laptop can DZ access the Internet. Usually, I just use static settings on my laptop to DZ communicate between the server and the laptop. I just recently got the DHCP DZ server going, and all is well. Laptop (Mac OS9.2.2, Open Transport 2.7.9) DZ works A-OK, discover, offer, request, acknowledge are all great... Did you install net/isc-dhcp3/? What do you mean exactly? I have installed ISC's dhcp-3.0.1rc9 and it is working properly with my Powerbook requesting DHCP from the current server. Is that something that goes along with the package I have installed? I fear that dhclient in sysinstall is misbehaving, and not so much dhcpd on the server... but who knows...? DZ Host: hilary.urbanpush.com DZ Domain: urbanpush.com DZ IPv4 Gateway: 10.0.0.1 // IP of frontline machine ie. Router DZ Name Server: 129.128.5.233 // the one I always use DZ IPv4 Address: 10.0.0.2 // IP I want this machine to be on local network DZ Netmask: 255.0.0.0 // Class A type network DZ No extra ifconfig options... You got these values by clicking DHCP rigth? No. The DHCP request times out and gives me a blank network configuration screen. These numbers are the values I use when I select a static IP on my laptop, which also works fine. That is why I am so baffled. If all the settings are what I usually use, why am I not getting anywhere? Sigh. DZ To note, the frontline box (dhcpd) does not display any DHCP-related DZ messages during this attempt. Try killing dhcpd on the server and starting it in the foreground with debug options. 'dhcpd -d' you may need other flag, check 'man dhcpd' for these. Yep. Tried that. I had been tweaking dhcpd.conf forever just to get dhcpd to work with my laptop (works fine now: i see all the neat messages fly back and forth when I'm connected). Do you think I need a special entry in there? Something that will assign an IP based on its ethernet address (I guess I could assign it a host/domain name at that point too)? I haven't tried that yet... You wan't to check the /etc/rc.conf file afther the installation. If you find something like xxx_fxp0=DHCP all is ok. Can't get that far into installation. DHCP is set up on the current server (it requests a specific IP from the DHCP server) so I know what you mean. My problem is getting connected so I can simply install. You are behind a NAT server right? Then you have to use the passive FTP mode. Normal mode doesn't work. Yep. I've been trying the passive mode exclusively. Sorry... Forgot to mention that. I'm at work and I'm installing along and all is well. However, I'd bet these problems will persist when I return home. Network seems easier to configure in rc.conf than with these silly screens. Give me my command prompt! DZ Thanks in advance for any advice/info you might be able to offer. If you arn't able to install it with DHCP, try giving it a static IP adres. You can change it later to DHCP. Yep. It won't go. That's when it hangs. Just churns away. Not a care in the world doo doo dooo doo Thanks. Dave To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
