Re: OpenBSD network trouble (offtopic?)

From: Nicholas Brenckle (nicholas.brenckle@yale.edu)
Date: Sun Oct 24 1999 - 14:56:44 EDT


Check your dmesg out after booting. My OpenBSD box did strange thing with my
CDrom when installing and after install did strange things with my nic (3c905).
I ended up having to go into config mode on boot (wd0? /bsd -c I forget what
the wd0 part was right now, its sunday :) and defining the card. Eventually I
built a kernal (see the FAQ for this) and that stopped it.

Im not doing any routing with it tho, so this may have nothing to do with your
problem. How are you liking OpenBSD? So far I was impressed with the quality o
f
the software/time that went into it. (Check out the /etc/passwd file when your
pw's are using blowfish... crazy..) BUT really not happy after using the simple
menus of the last few linux distros. I got lazy and command lines dont help. Im
going to stick with it for the task I had in mind tho which is exactly what you
are doing, only on a dialup connect to Yale, not a LAN.

As for having more then one PC in a dorm room, dorms and offices run on totally
different political systems so you can't really compare the two. They even
differ from med side to central campus side so the best bet for the right answe
r
is to ask your CA and if they dont know, move up the chain through Academic
Computing to someone who does.

-Nick

Chad Glendenin wrote:

> Sorry if the following is off topic; I know this is LINUX-list...
>
> Since Yale's hubs won't let me add my own hub to extend the network, and
> since I have only one ethernet jack but more than one computer, I figured I
> would use my ancient pentium box as a basic firewall and let the other
> computers talk to the internet through that box using IP Aliasing.
>
> So I start happily installing OpenBSD on it, and everything is going fine. I
> defined the two network interfaces in the machine. It dropped me into a
> shell so I could test the setup and make sure things were working. No
> problems. I am able to ping www.yahoo.com through ep2 (the NIC connected to
> Yale) and I am able to ping 192.168.0.2 (the only other machine attached to
> my hub right now) through ep3 (the NIC connected to my hub). The
> installation finishes, and I reboot the machine. As soon as the system
> comes up, I try to ping www.yahoo.com. No problem. Then I try to ping
> 192.168.0.2. No response. I try 'tcpdump -i ep3' while pinging it
> (192.168.0.10 is the BSD box):
>
> 16:22:56.269716 arp who-has 192.168.0.2 tell 192.168.0.10
> 16:22:57.260165 arp who-has 192.168.0.2 tell 192.168.0.10
> 16:22:58.260149 arp who-has 192.168.0.2 tell 192.168.0.10
>
> When pinging, I can see the lights blinking on the hub for both computers
> (indication send/receive activity), but all I get is this:
>
> PING 192.168.0.2 (192.168.0.2): 56 data bytes
> ping: sendto: Host is down
> ping: wrote 192.168.0.2 64 chars, ret=-1
>
> Is it correct that through my local hub is a direct connection, so it
> doesn't need any special routing information? I really have no idea what
> changes between the installation and actually booting the real system that
> causes the second network interface to stop working (I've done the
> installation a few times; networking always works perfectly while
> installing, but when I boot the system, only the Yale connection works).
>
> I've read the man pages, the OpenBSD.org FAQ, and all the networking
> chapters in Lehey's "The Complete FreeBSD," but I still have no clue.
> Here's some other information:
>
> $ ifconfig ep3
> ep3: flags=8863<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST>
> media: Ethernet 10baseT
> inet 192.168.0.10 netmask 0xffffff00 broadcast 192.168.0.255
> $ netstat -rn
> Routing tables
>
> Internet:
> Destination Gateway Flags Refs Use Mtu
> Interface
> default 130.132.72.1 UGS 1 343 - ep2
> 127/8 127.0.0.1 UGRS 0 0 - lo0
> 127.0.0.1 127.0.0.1 UH 2 12 - lo0
> 130.132.72/24 link#3 UC 0 0 - ep2
> 130.132.72.1 0:e0:34:9d:34:0 UHL 1 0 - ep2
> 192.168.0/24 link#4 UC 0 0 - ep3
> 224/4 127.0.0.1 URS 0 0 - lo0
>
> Encap:
> Source address/netmask Port Destination address/netmask Port
> Proto SA(Address/SPI/Proto)
> $ route show
> Routing tables
>
> Internet:
> Destination Gateway Flags
> default college.net.yale.e UG
> 127.0.0.0 localhost UG
> localhost localhost UH
> ug99-11-subnet.n link#3 U
> college.net.yale 0:e0:34:9d:34:0 UH
> 192.168.0.0 link#4 U
> BASE-ADDRESS.MCA localhost U
>
> Any help is greatly appreciated.
>
> Chad



This archive was generated by hypermail 2b29 : Wed Apr 27 2005 - 03:30:03 EDT