Re: troubleshooting network settings
On 08/06/2006, at 12:06 AM, Alex Zbyslaw wrote: Malcolm Fitzgerald wrote: Malcolm Fitzgerald wrote: I am running freeBSD v6.0 security on a home network behind an adsl router. I cannot connect to localhost from a browser (apache is running!) I cannot connect to localhost port 22 (KPackage tries to use ssh) On 29/05/2006, at 11:37 PM, Kevin Kinsey wrote: Hmm, is that all? Unusual; I'd think the loopback _should_ be set up correctly. `ifconfig lo0 inet 127.0.0.1 netmask 255.255.255.0` ?? If that fixes it, then we have to figure out *why* it's not being doing automatically. Problem during init/rc, most likely ... weird. I've not had time to address this problem for a week. Going through all the advice again I found that this advice is good. That fixes the problem. Any pointers on getting it done automatically? What does /etc/rc.conf show for lo0 related things? (And just to check your defaults as well...) egrep lo0 /etc/rc.conf /etc/defaults/* Mine shows: /etc/defaults/rc.conf:ifconfig_lo0=inet 127.0.0.1 # default loopback device configuration. Same here malcolm ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: troubleshooting network settings
Malcolm Fitzgerald wrote:
On 08/06/2006, at 12:06 AM, Alex Zbyslaw wrote:
Malcolm Fitzgerald wrote:
On 29/05/2006, at 11:37 PM, Kevin Kinsey wrote:
Hmm, is that all? Unusual; I'd think the loopback _should_ be set
up correctly.
`ifconfig lo0 inet 127.0.0.1 netmask 255.255.255.0` ??
If that fixes it, then we have to figure out *why* it's not being
doing automatically. Problem during init/rc, most likely ... weird.
I've not had time to address this problem for a week. Going through
all the advice again I found that this advice is good. That fixes
the problem. Any pointers on getting it done automatically?
What does /etc/rc.conf show for lo0 related things? (And just to
check your defaults as well...)
egrep lo0 /etc/rc.conf /etc/defaults/*
Mine shows:
/etc/defaults/rc.conf:ifconfig_lo0=inet 127.0.0.1 # default
loopback device configuration.
Same here
Just to confirm, since I didn't really read the beginning of this
thread, when you reboot your machine, the setting for lo0 is already
wrong, yes?
Since we now know that the rc settings look ok, maybe some script is
doing the dirty, so what does
egrep 'lo0|ifconfig' /etc/rc.d/* /usr/local/etc/rc.d/*
show? I do have numerous hits in /etc/rc.d, none of which look like
they would affect lo0 unless you specified lo0 in /etc/rc.conf. I have
no hits in /usr/local/etc/rc.d/*, which is what I would expect -- if you
get any hits there then follow them up to see what they are doing. If
you get hits in /etc/rc.d not in my list then have a look. (I'm still
on FreeBSD 5 so if you are on 6 then you may get slightly fewer or more
hits, but I wouldn't expect too drastic differences).
My hits are:
/etc/rc.d/atm1: ifconfig ${natm} up
/etc/rc.d/dhclient: ifconfig ${ifn}
/etc/rc.d/initdiskless: iflist=`ifconfig -l`
/etc/rc.d/initdiskless: set -- `ifconfig ${i}`
/etc/rc.d/ip6addrctl: if ifconfig lo0 inet6 /dev/null 21; then
/etc/rc.d/ip6addrctl: if ifconfig lo0 inet6 /dev/null 21; then
/etc/rc.d/netif:# it will call ifconfig(8) to show, in long
format, the configured
/etc/rc.d/netif:ifconfig ${ifn}
/etc/rc.d/netif:ifconfig_up ${ifn} cfg=0
/etc/rc.d/netif:ifconfig_down ${ifn} cfg=0
/etc/rc.d/network_ipv6: ipv6_network_interfaces=`ifconfig -l`
/etc/rc.d/network_ipv6: ifconfig $i up
/etc/rc.d/pflog:if ! ifconfig pflog0 up; then
/etc/rc.d/rtadvd: for i in `ifconfig -l` ; do
/etc/rc.d/rtadvd:
lo0|gif[0-9]*|stf[0-9]*|faith[0-9]*|lp[0-9]*|sl[0-9]*|tun[0-9]*)
/etc/rc.d/sppp: # to go _before_ the general ifconfig since in the case
--Alex
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: troubleshooting network settings
Malcolm Fitzgerald wrote: I am running freeBSD v6.0 security on a home network behind an adsl router. I cannot connect to localhost from a browser (apache is running!) I cannot connect to localhost port 22 (KPackage tries to use ssh) On 29/05/2006, at 11:37 PM, Kevin Kinsey wrote: Hmm, is that all? Unusual; I'd think the loopback _should_ be set up correctly. `ifconfig lo0 inet 127.0.0.1 netmask 255.255.255.0` ?? If that fixes it, then we have to figure out *why* it's not being doing automatically. Problem during init/rc, most likely ... weird. I've not had time to address this problem for a week. Going through all the advice again I found that this advice is good. That fixes the problem. Any pointers on getting it done automatically? malcolm ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: troubleshooting network settings
Malcolm Fitzgerald wrote: Malcolm Fitzgerald wrote: I am running freeBSD v6.0 security on a home network behind an adsl router. I cannot connect to localhost from a browser (apache is running!) I cannot connect to localhost port 22 (KPackage tries to use ssh) On 29/05/2006, at 11:37 PM, Kevin Kinsey wrote: Hmm, is that all? Unusual; I'd think the loopback _should_ be set up correctly. `ifconfig lo0 inet 127.0.0.1 netmask 255.255.255.0` ?? If that fixes it, then we have to figure out *why* it's not being doing automatically. Problem during init/rc, most likely ... weird. I've not had time to address this problem for a week. Going through all the advice again I found that this advice is good. That fixes the problem. Any pointers on getting it done automatically? What does /etc/rc.conf show for lo0 related things? (And just to check your defaults as well...) egrep lo0 /etc/rc.conf /etc/defaults/* Mine shows: /etc/defaults/rc.conf:ifconfig_lo0=inet 127.0.0.1 # default loopback device configuration. --Alex ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: troubleshooting network settings
Hmm, is that all? Unusual; I'd think the loopback _should_ be set up correctly. `ifconfig lo0 inet 127.0.0.1 netmask 255.255.255.0` ?? If that fixes it, then we have to figure out *why* it's not being doing automatically. Problem during init/rc, most likely ... weird. I've not had time to address this problem for a week. Going through all the advice again I found that this advice is good. That fixes the problem. Any pointers on getting it done automatically? Is the following line in /etc/defaults/rc.conf? ifconfig_lo0=inet 127.0.0.1 # default loopback device configuration. If not, add it there, or simply in /etc/rc.conf Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: troubleshooting network settings
On 08/06/2006, at 2:42 AM, Steve Bertrand wrote: Hmm, is that all? Unusual; I'd think the loopback _should_ be set up correctly. `ifconfig lo0 inet 127.0.0.1 netmask 255.255.255.0` ?? If that fixes it, then we have to figure out *why* it's not being doing automatically. Problem during init/rc, most likely ... weird. I've not had time to address this problem for a week. Going through all the advice again I found that this advice is good. That fixes the problem. Any pointers on getting it done automatically? Is the following line in /etc/defaults/rc.conf? ifconfig_lo0=inet 127.0.0.1 # default loopback device configuration. Yes, that line is in /etc/defaults/rc.conf malcolm ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: troubleshooting network settings
Malcolm Fitzgerald wrote: On 31/05/2006, at 11:30 PM, Steve Bertrand wrote: Take a look at the 'ServerName' directive in your httpd.conf file. Try uncommenting said directive, and put your IP address beside it. This line is already in place ServerName 127.0.0.1:80 I can confirm this behavior with www/apache22 for a FBD_6_1 machine not in DNS. My solution: I commented out the load of mod_unique_id in httpd.conf making everything work just fine. Looking at the documentation of mod_unique_id convinced me that I would only need it for some sort of server-side application that could not provide itself with a concept of a session. I haven't dug into the mod_unique_id code to find out what it is trying to resolve. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: troubleshooting network settings
Take a look at the 'ServerName' directive in your httpd.conf file. Try uncommenting said directive, and put your IP address beside it. This line is already in place ServerName 127.0.0.1:80 What about something like: ServerName 192.168.1.10:80 ...or whatever your LAN/WAN IP is? Does that help? Try removing the localhost addr from there and replacing it with a NIC IP and see what happens. I have to admit, I haven't followed the entire thread, so if this has been mentioned, I apologize in advance. Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: troubleshooting network settings
On 02/06/2006, at 10:54 AM, Steve Bertrand wrote: Take a look at the 'ServerName' directive in your httpd.conf file. Try uncommenting said directive, and put your IP address beside it. This line is already in place ServerName 127.0.0.1:80 What about something like: ServerName 192.168.1.10:80 That works for the numbered address, though it is extremely slow, about a minute to respond and virtual hosting doesn't work. At this point Apache is running but localhost loopback address is lost. malcolm ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: troubleshooting network settings
There we have it. Apache is unable to resolve bsd-box. This hostname should be resolvable, otherwise Apache will not work. Adding it to /etc/hosts is the easiest way: 192.168.1.104 bsd-box bsd-box.yourdomain.com This line was already in /etc/hosts; 127.0.0.1 localhost localhost.home.net bsd-box bsd-box.home.net and I've added this line 192.168.1.104 bsd-box bsd-box.home.net In addition to Jorn's advice, check /etc/defaults/rc.conf. The file should exist and have permissions like so: $ ls -l /etc/defaults/rc.conf -r--r--r-- 1 root wheel 31735 May 15 18:48 /etc/defaults/rc.conf and it should have the following line within: $ grep lo0 /etc/defaults/rc.conf ifconfig_lo0=inet 127.0.0.1 # default loopback device configuration. All present. Still cannot connect to localhost. Take a look at the 'ServerName' directive in your httpd.conf file. Try uncommenting said directive, and put your IP address beside it. From httpd.conf, look particularily at the last paragraph: # ServerName gives the name and port that the server uses to identify itself. # This can often be determined automatically, but we recommend you specify # it explicitly to prevent problems during startup. # # If this is not set to valid DNS name for your host, server-generated # redirections will not work. See also the UseCanonicalName directive. # # If your host doesn't have a registered DNS name, enter its IP address here. # You will have to access it by its address anyway, and this will make # redirections work in a sensible way. However, I would think the hosts file would have done it though, but it's worth a try. Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: troubleshooting network settings
On 31/05/2006, at 11:30 PM, Steve Bertrand wrote: Take a look at the 'ServerName' directive in your httpd.conf file. Try uncommenting said directive, and put your IP address beside it. This line is already in place ServerName 127.0.0.1:80 malcolm ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: troubleshooting network settings
Malcolm Fitzgerald wrote: Malcolm Fitzgerald wrote: Running that command returns this: ifconfig: -inet: bad value Bah! I'm on the road too much lately. No dash before inet ... KDK -- At social gatherings, I would amuse everyone by standing uponst the coffee table and striking meself repeatedly upon the head with a brick. -- H. R. Gumby ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: troubleshooting network settings
On 30/05/2006, at 10:29 PM, Kevin Kinsey wrote: Malcolm Fitzgerald wrote: Malcolm Fitzgerald wrote: Running that command returns this: ifconfig: -inet: bad value Bah! I'm on the road too much lately. No dash before inet ... here's the output bsd-box# ifconfig lo0 inet 127.0.0.1 netmask 255.255.255.0 bsd-box# ifconfig -a rl0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 options=8VLAN_MTU inet6 fe80::2e0:4cff:fe08:e02a%rl0 prefixlen 64 scopeid 0x1 inet 192.168.1.104 netmask 0xff00 broadcast 192.168.1.255 ether 00:e0:4c:08:e0:2a media: Ethernet autoselect (100baseTX full-duplex) status: active plip0: flags=108810POINTOPOINT,SIMPLEX,MULTICAST,NEEDSGIANT mtu 1500 lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384 inet 127.0.0.1 netmask 0xff00 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 bsd-box# apachectl graceful httpd not running, trying to start bsd-box# tail -f /var/log/httpd-error.log [Tue May 30 22:33:13 2006] [alert] (EAI 8)hostname nor servname provided, or not known: mod_unique_id: unable to find IPv4 address of bsd-box. Configuration Failed [Tue May 30 22:43:26 2006] [info] Init: Seeding PRNG with 136 bytes of entropy [Tue May 30 22:43:26 2006] [info] Init: Generating temporary RSA private keys (512/1024 bits) [Tue May 30 22:43:26 2006] [info] Init: Generating temporary DH parameters (512/1024 bits) [Tue May 30 22:43:26 2006] [warn] Init: Session Cache is not configured [hint: SSLSessionCache] [Tue May 30 22:43:26 2006] [info] Init: Initializing (virtual) servers for SSL [Tue May 30 22:43:26 2006] [info] Server: Apache/2.2.2, Interface:mod_ssl/2.2.2, Library: OpenSSL/0.9.7e-p1 [Tue May 30 22:43:51 2006] [alert] (EAI 8)hostname nor servname provided, or not known: mod_unique_id: unable to find IPv4 address of bsd-box. Configuration Failed ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: troubleshooting network settings
Malcolm Fitzgerald wrote: On 30/05/2006, at 10:29 PM, Kevin Kinsey wrote: Malcolm Fitzgerald wrote: Malcolm Fitzgerald wrote: Running that command returns this: ifconfig: -inet: bad value Bah! I'm on the road too much lately. No dash before inet ... here's the output [snip] [Tue May 30 22:43:26 2006] [info] Init: Seeding PRNG with 136 bytes of entropy [Tue May 30 22:43:26 2006] [info] Init: Generating temporary RSA private keys (512/1024 bits) [Tue May 30 22:43:26 2006] [info] Init: Generating temporary DH parameters (512/1024 bits) [Tue May 30 22:43:26 2006] [warn] Init: Session Cache is not configured [hint: SSLSessionCache] [Tue May 30 22:43:26 2006] [info] Init: Initializing (virtual) servers for SSL [Tue May 30 22:43:26 2006] [info] Server: Apache/2.2.2, Interface:mod_ssl/2.2.2, Library: OpenSSL/0.9.7e-p1 [Tue May 30 22:43:51 2006] [alert] (EAI 8)hostname nor servname provided, or not known: mod_unique_id: unable to find IPv4 address of bsd-box. Configuration Failed There we have it. Apache is unable to resolve bsd-box. This hostname should be resolvable, otherwise Apache will not work. Adding it to /etc/hosts is the easiest way: 192.168.1.104 bsd-box bsd-box.yourdomain.com Jorn ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: troubleshooting network settings
Malcolm Fitzgerald wrote: On 30/05/2006, at 10:29 PM, Kevin Kinsey wrote: Malcolm Fitzgerald wrote: Malcolm Fitzgerald wrote: Running that command returns this: ifconfig: -inet: bad value Bah! I'm on the road too much lately. No dash before inet ... here's the output bsd-box# ifconfig lo0 inet 127.0.0.1 netmask 255.255.255.0 bsd-box# ifconfig -a rl0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 options=8VLAN_MTU inet6 fe80::2e0:4cff:fe08:e02a%rl0 prefixlen 64 scopeid 0x1 inet 192.168.1.104 netmask 0xff00 broadcast 192.168.1.255 ether 00:e0:4c:08:e0:2a media: Ethernet autoselect (100baseTX full-duplex) status: active plip0: flags=108810POINTOPOINT,SIMPLEX,MULTICAST,NEEDSGIANT mtu 1500 lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384 inet 127.0.0.1 netmask 0xff00 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 In addition to Jorn's advice, check /etc/defaults/rc.conf. The file should exist and have permissions like so: $ ls -l /etc/defaults/rc.conf -r--r--r-- 1 root wheel 31735 May 15 18:48 /etc/defaults/rc.conf and it should have the following line within: $ grep lo0 /etc/defaults/rc.conf ifconfig_lo0=inet 127.0.0.1 # default loopback device configuration. If all these aren't true, that would explain why the loopback isn't configured. Kevin Kinsey -- There's an old proverb that says just about whatever you want it to. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: troubleshooting network settings
bsd-box# ifconfig lo0 inet 127.0.0.1 netmask 255.255.255.0 bsd-box# ifconfig -a rl0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 options=8VLAN_MTU inet6 fe80::2e0:4cff:fe08:e02a%rl0 prefixlen 64 scopeid 0x1 inet 192.168.1.104 netmask 0xff00 broadcast 192.168.1.255 ether 00:e0:4c:08:e0:2a media: Ethernet autoselect (100baseTX full-duplex) status: active plip0: flags=108810POINTOPOINT,SIMPLEX,MULTICAST,NEEDSGIANT mtu 1500 lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384 inet 127.0.0.1 netmask 0xff00 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 On 31/05/2006, at 2:28 AM, Jorn Argelo wrote: There we have it. Apache is unable to resolve bsd-box. This hostname should be resolvable, otherwise Apache will not work. Adding it to /etc/hosts is the easiest way: 192.168.1.104 bsd-box bsd-box.yourdomain.com This line was already in /etc/hosts; 127.0.0.1 localhost localhost.home.net bsd-box bsd-box.home.net and I've added this line 192.168.1.104 bsd-box bsd-box.home.net In addition to Jorn's advice, check /etc/defaults/rc.conf. The file should exist and have permissions like so: $ ls -l /etc/defaults/rc.conf -r--r--r-- 1 root wheel 31735 May 15 18:48 /etc/defaults/rc.conf and it should have the following line within: $ grep lo0 /etc/defaults/rc.conf ifconfig_lo0=inet 127.0.0.1 # default loopback device configuration. All present. Still cannot connect to localhost. malcolm ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: troubleshooting network settings
There are a myriad of factors that could have caused those services to be inaccessible. First try to check if those services are running. Try sockstat -4 [EMAIL PROTECTED] sockstat -4 USER COMMANDPID FD PROTO LOCAL ADDRESS FOREIGN ADDRESS root httpd 504 30 tcp4 *:80 *:* root sshd 474 3 tcp4 *:22 *:* if you don't see that :80 and :22 entry at the LOCAL ADDRESS column those services might not be running. If they are not running and you are sure that you have already installed apache from the ports collection, check your /etc/rc.conf file if you have these entries: sshd_enable=YES apache_enable=YES If they are both running this could be a problem in the configuration of your firewall. Also check the /etc/hosts file if you have an entry for your localhost. Maybe you're computer cannot open those services because your computer couldn't resolve the ip address of your localhost :) If it is still not working. hmmm. try to verify if the firewall is really the one causing the problem. Add the following line in your /etc/rc.conf file firewall_enable=YES firewall_type=OPEN if it works. change the firewall type to something more secure.. customize the /etc/rc.firewall and set the firewall_type to which ever setting you think would fit your needs :) hope this helps :) === Gil A. Virtucio Janitor/Kolektor/Messenger/Driver Asia Solution Phillippines Inc. 28/F Antel Global Corporate Center 3 Doña Julia Vargas Avenue, Ortigas Center, Pasig Mobile # : +63-916-3989695 === - Original Message - From: Malcolm Fitzgerald [EMAIL PROTECTED] To: [EMAIL PROTECTED] ORG freebsd-questions@freebsd.org Sent: Monday, May 29, 2006 9:48 AM Subject: Re: troubleshooting network settings Malcolm Fitzgerald wrote: I am running freeBSD v6.0 security on a home network behind an adsl router. I cannot connect to localhost from a browser (apache is running!) I cannot connect to localhost port 22 (KPackage tries to use ssh) What can cause these problems? How can I troubleshoot them? I am very new to freeBSD, so part of my question is where do I begin?. I have a copy of Complete freeBSD beside me but can't get the magical incantations right. Suggestions appreciated. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: troubleshooting network settings
Malcolm Fitzgerald wrote: On 29/05/2006, at 1:10 PM, Kevin Kinsey wrote: Malcolm Fitzgerald wrote: I am running freeBSD v6.0 security on a home network behind an adsl router. I cannot connect to localhost from a browser (apache is running!) I cannot connect to localhost port 22 (KPackage tries to use ssh) What can cause these problems? How can I troubleshoot them? I am very new to freeBSD, so part of my question is where do I begin?. I have a copy of Complete freeBSD beside me but can't get the magical incantations right. Suggestions appreciated. New to Nix like systems in general, or just new to FreeBSD? Here are a few suggestions ... no magic bullet here, though: First, check to see if the interface exists: $ ifconfig lo0 lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4 inet 127.0.0.1 netmask 0xff00 So, we have a loopback interface (in this case on both IPv4 and IPv6). bsd-box# ifconfig -a rl0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 options=8VLAN_MTU inet6 fe80::2e0:4cff:fe08:e02a%rl0 prefixlen 64 scopeid 0x1 inet 192.168.1.104 netmask 0xff00 broadcast 192.168.1.255 ether 00:e0:4c:08:e0:2a media: Ethernet autoselect (100baseTX full-duplex) status: active plip0: flags=108810POINTOPOINT,SIMPLEX,MULTICAST,NEEDSGIANT mtu 1500 lo0: flags=8008LOOPBACK,MULTICAST mtu 16384 Hmm, is that all? Unusual; I'd think the loopback _should_ be set up correctly. `ifconfig lo0 -inet 127.0.0.1 netmask 255.255.255.0` ?? If that fixes it, then we have to figure out *why* it's not being doing automatically. Problem during init/rc, most likely ... weird. KDK ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: troubleshooting network settings
On 29/05/2006, at 11:37 PM, Kevin Kinsey wrote: Malcolm Fitzgerald wrote: On 29/05/2006, at 1:10 PM, Kevin Kinsey wrote: Malcolm Fitzgerald wrote: I am running freeBSD v6.0 security on a home network behind an adsl router. I cannot connect to localhost from a browser (apache is running!) I cannot connect to localhost port 22 (KPackage tries to use ssh) What can cause these problems? How can I troubleshoot them? I am very new to freeBSD, so part of my question is where do I begin?. I have a copy of Complete freeBSD beside me but can't get the magical incantations right. Suggestions appreciated. New to Nix like systems in general, or just new to FreeBSD? Here are a few suggestions ... no magic bullet here, though: First, check to see if the interface exists: $ ifconfig lo0 lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4 inet 127.0.0.1 netmask 0xff00 So, we have a loopback interface (in this case on both IPv4 and IPv6). bsd-box# ifconfig -a rl0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 options=8VLAN_MTU inet6 fe80::2e0:4cff:fe08:e02a%rl0 prefixlen 64 scopeid 0x1 inet 192.168.1.104 netmask 0xff00 broadcast 192.168.1.255 ether 00:e0:4c:08:e0:2a media: Ethernet autoselect (100baseTX full-duplex) status: active plip0: flags=108810POINTOPOINT,SIMPLEX,MULTICAST,NEEDSGIANT mtu 1500 lo0: flags=8008LOOPBACK,MULTICAST mtu 16384 Hmm, is that all? Unusual; I'd think the loopback _should_ be set up correctly. `ifconfig lo0 -inet 127.0.0.1 netmask 255.255.255.0` ?? If that fixes it, then we have to figure out *why* it's not being doing automatically. Problem during init/rc, most likely ... weird. Running that command returns this: ifconfig: -inet: bad value malcolm ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: troubleshooting network settings
Check /etc/rc.conf inetd_enable=YES Check /etc/inetd.conf sshstream tcp nowait root/usr/sbin/sshd sshd -i -4 Malcolm Fitzgerald wrote: I am running freeBSD v6.0 security on a home network behind an adsl router. I cannot connect to localhost from a browser (apache is running!) I cannot connect to localhost port 22 (KPackage tries to use ssh) What can cause these problems? How can I troubleshoot them? I am very new to freeBSD, so part of my question is where do I begin?. I have a copy of Complete freeBSD beside me but can't get the magical incantations right. Suggestions appreciated. malcolm ___ 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]
Re: troubleshooting network settings
Malcolm Fitzgerald wrote: I am running freeBSD v6.0 security on a home network behind an adsl router. I cannot connect to localhost from a browser (apache is running!) I cannot connect to localhost port 22 (KPackage tries to use ssh) What can cause these problems? How can I troubleshoot them? I am very new to freeBSD, so part of my question is where do I begin?. I have a copy of Complete freeBSD beside me but can't get the magical incantations right. Suggestions appreciated. On 29/05/2006, at 10:58 AM, Kouji Ito wrote: Check /etc/rc.conf inetd_enable=YES I added that line. No change after rebooting Check /etc/inetd.conf sshstream tcp nowait root/usr/sbin/sshd sshd -i -4 It is now uncommented. Every line in that file was commented out No change after rebooting malcolm ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: troubleshooting network settings
Sorry. (1) Commented /etc/inetd.conf #sshstream tcp nowait root/usr/sbin/sshd sshd -i -4 (2) Add /etc/rc.conf sshd_enable=YES (3) Send HUP signal to inetd # pkill -HUP inetd (4) Start sshd # cd /etc/rc.d # sh sshd start (5) Try ssh login # ssh -l user_name localhost How about? I tryed . inchiki# ifconfig -a fxp0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 options=bRXCSUM,TXCSUM,VLAN_MTU inet6 fe80::208:dff:fe87:be0d%fxp0 prefixlen 64 scopeid 0x1 inet 0.0.0.0 netmask 0xff00 broadcast 0.255.255.255 ether 00:08:0d:87:be:0d media: Ethernet autoselect (none) status: no carrier lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2 inet 127.0.0.1 netmask 0xff00 tun0: flags=8010POINTOPOINT,MULTICAST mtu 1500 fxp0 is down. lo0 is up. inchiki# ps -ax | grep sshd 1003 ?? Is 0:00.03 /usr/sbin/sshd sshd is running. inchiki# ssh -l kouji localhost Password:XX : : % logged in at kouji user. Malcolm Fitzgerald wrote: Malcolm Fitzgerald wrote: I am running freeBSD v6.0 security on a home network behind an adsl router. I cannot connect to localhost from a browser (apache is running!) I cannot connect to localhost port 22 (KPackage tries to use ssh) What can cause these problems? How can I troubleshoot them? I am very new to freeBSD, so part of my question is where do I begin?. I have a copy of Complete freeBSD beside me but can't get the magical incantations right. Suggestions appreciated. On 29/05/2006, at 10:58 AM, Kouji Ito wrote: Check /etc/rc.conf inetd_enable=YES I added that line. No change after rebooting Check /etc/inetd.conf sshstream tcp nowait root/usr/sbin/sshd sshd -i -4 It is now uncommented. Every line in that file was commented out No change after rebooting malcolm ___ 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]
Re: troubleshooting network settings
Do you have the firewall enabled in rc.conf (ipfw)? On May 28, 2006, at 5:34 PM, Malcolm Fitzgerald wrote: I am running freeBSD v6.0 security on a home network behind an adsl router. I cannot connect to localhost from a browser (apache is running!) I cannot connect to localhost port 22 (KPackage tries to use ssh) What can cause these problems? How can I troubleshoot them? I am very new to freeBSD, so part of my question is where do I begin?. I have a copy of Complete freeBSD beside me but can't get the magical incantations right. Suggestions appreciated. malcolm ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions- [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: troubleshooting network settings
Malcolm Fitzgerald wrote: I am running freeBSD v6.0 security on a home network behind an adsl router. I cannot connect to localhost from a browser (apache is running!) I cannot connect to localhost port 22 (KPackage tries to use ssh) What can cause these problems? How can I troubleshoot them? I am very new to freeBSD, so part of my question is where do I begin?. I have a copy of Complete freeBSD beside me but can't get the magical incantations right. Suggestions appreciated. New to Nix like systems in general, or just new to FreeBSD? Here are a few suggestions ... no magic bullet here, though: First, check to see if the interface exists: $ ifconfig lo0 lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4 inet 127.0.0.1 netmask 0xff00 So, we have a loopback interface (in this case on both IPv4 and IPv6). --- $ ping localhost PING localhost (127.0.0.1): 56 data bytes 64 bytes from 127.0.0.1: icmp_seq=0 ttl=64 time=0.088 ms This checks name resolution. If the machine doesn't know where localhost is, you probably need to add a hint in /etc/hosts (but that should've been done already, IIRC). - $ netstat -anf inet | grep 80 tcp4 0 0 *.80 *.* LISTEN This shows a server listening on port 80 ... the http port. Grep 22 for sshd. Incidentally, you can find that sort of thing (what port number to look for) out this way: $ grep ssh /etc/services ssh 22/tcp#Secure Shell Login ssh 22/udp#Secure Shell Login sshell 614/tcp#SSLshell sshell 614/udp x11-ssh 6010/tcp #Unofficial name, for convenience x11-ssh 6010/udp -- This is often useful in this type of situation - we'll check to see if something is actually running, and whether it returns a meaningful error message if it's not: $ telnet localhost 22 Trying ::1... Connected to localhost. Escape character is '^]'. SSH-2.0-OpenSSH_4.2p1 FreeBSD-20050903 To leave, press the escape character (shown), and then type quit --- Are you running a firewall? If so, the loopback interface should allow all traffic. (Of course, if it's not, you'll have lots of trouble --- but then, you are having a little, right?) This box is running ipfw: $ ipfw show ipfw: socket: Operation not permitted Whoops! Better use root credentials for that. I use sudo, a 3rd party app (as do many FBSD users); you may need to actually use su to get root before looking at firewall rules. $ sudo ipfw show 00100 47450 15295315 divert 8668 ip from any to any via xl0 00200 1279040 547068572 allow ip from any to any via lo0 So this box is doing NAT (rule 100) and is allowing traffic on the loopback interface (which is from/to 127.0.0.1/localhost rule 200). --- If that's not enough to give some clue, write the list again with some more information. HTH, Kevin Kinsey ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
