Hello List

Mike Hauber m.hauber at mchsi.com
Wed Nov 10 12:51:09 PST 2004


On Wednesday 10 November 2004 08:20 am, Ben Haysom 
proclaimed:
>
> god# uname -a
> FreeBSD god.mshome.net 5.1-RELEASE FreeBSD 5.1-RELEASE
> #0: Thu Jun  5 02:55:42 GMT 2003
> root at wv1u.btc.adaptec.com:/usr/obj/usr/src/sys/GENERIC 
> i386
>
> god#  ifconfig -a
> rl0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST>
> mtu 1500 inet 192.168.1.2 netmask 0xffffff00 broadcast
> 192.168.1.255 inet6 fe80::205:5dff:fe42:713e%rl0
> prefixlen 64 scopeid 0x1 ether 00:05:5d:42:71:3e
>         media: Ethernet autoselect (none)
>         status: no carrier
> sis0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST>
> mtu 1500 inet6 fe80::240:f4ff:fe59:68ed%sis0 prefixlen 64
> scopeid 0x2 inet 192.168.0.36 netmask 0xffffff00
> broadcast 192.168.0.255 ether 00:40:f4:59:68:ed
>         media: Ethernet autoselect (10baseT/UTP)
>         status: active

Okay, so let's look at this...

ISP -- modem -- rl0 -- fbsd -- sis0 -- LAN

The kernal obviously has the drivers up and running (else 
the output of ifconfig wouldn't have shown the interfaces)

For _some_ reason, rl0 is showing a status of "no carrier."

This tells me one of two things...

1.  The cable between rl0 and the modem is not connected.
2.  The cable is faulty.

If the NIC has lights on it, you should be able to tell by 
the status light on the NIC.

>
> god# more /etc/rc.conf
>
> gateway_enable="YES"
> hostname="god.mshome.net"
> inetd_enable="YES"
> sendmail_enable="NO"
> sshd_enable="YES"
> ifconfig_sis0="inet 192.168.0.2 netmask 255.255.255.0"
> sendmail_enable="YES"
> nfs_server_enable="NO"
> sshd_enable="YES"
> ifconfig_rl0="inet 192.168.1.2  netmask 255.255.255.0"
> defaultrouter="192.168.1.1"
> linux_enable="YES"
> sendmail_enable="NONE"
> nis_server_enable="YES"
> nis_client_enable="NO"
> rpcbind_enable="YES"
> ifconfig_sis0="DHCP"
> hostname="god.mshome.net"
>

Lots of repeats/changes, but let's see...

You have DHCP set up on sis0, but you do not have DHCP set 
up on rl0.  Is there a reason for this?  I always ran DHCP 
and let the ISP cough up all the info the server needs to 
connect (such as default router).

What it _looks_ like you've done is specify local IP 
addresses to both network cards, and then tried to get the 
server to try to connect to the ISP through the internal 
NIC.  I _think_ what you want to do in this case is as 
follows:

1.  Change the line that says: ifconfig_sis0="DHCP"  so that 
is says: ifconfig_rl0="DHCP"  This way, your internal 
network will be able to communicate with the server again, 
and dhclient will attempt to get the info from your ISP.
      
2.  Go through the rc.conf file and remove repeated and/or 
changed lines.  Make sure that you don't delete the lines 
you want -- only the ones that are unnecessary.  For 
example, if the following three lines are in rc.conf, then 
_only_ the last is applicable.  

sendmail_enable="YES"
sendmail_enable="NO"
sendmail_enable="NONE"

I know it may sound picky, but if you cleaned the file up a 
bit, you'll probably see what's going on with more clarity.

3.  Remove the line that says: defaultrouter="192.168.1.1"

That should take care of rc.conf

> god# more /etc/hosts
>
> ::1                     localhost.mshome.net localhost
>
> 127.0.0.1               localhost.mshome.net localhost
> 192.168.1.2             god.mshome.net god
> 192.168.1.2             god.mshome.net.
>

no problems there...

>
> dmesg -a gives a load of stuff... do you really want me
> to post all that?

Actually, not in this case...  I just wanted to make sure 
that your system was picking up on the NICs, and your 
output from ifconfig shows that it had no problem with it.

Let me know how it goes.

Good luck,

Mike


More information about the freebsd-questions mailing list