Mac Projects - NetBSD 1.6 on LC475

Installed fine, starts up NetBSD fine.
Problems! Can't configure Networking properly.

Followed instructions from links found on NetBSD website, but they seem out-of-date... I can't see any IP addresses past my router.

Pinging any other address just hangs 'ping', I have to terminate the process.

Can anyone shed any light on this subject?

Comments

Hello, I'm more of a Linux user per say, but alot of commands carry over from one unix to another...

The basic command to view and setup a Network Interface is ifconfig. Not ipconfig, but ifconfig. go figure. Anyways, if you have the command, then read the man page. >man ifconfig or ifconfig /man

ifconfig eth0 192.168.0.1 255.255.255.0 up &

usually starts the network interface. Use your own IP setting ofcourse.

Hope this helps,

Jay.

Eudimorphodon's picture

Dumb question: Did you set a default gateway?

route add default ipofyourrouter

To make it stick after reboots:

echo "ipaddressofrouter" > /etc/mygate

In linux I added the ifconfig command to /etc/rc.d/rc.config

Eudimorphodon's picture

In linux I added the ifconfig command to /etc/rc.d/rc.config

NetBSD isn't linux. So far as that goes, Linux isn't Linux. Each distribution uses its own configuration file layout.

I understand that. NetBSD is unix based, Linux is unix based. They all have a similar basic structure.

Eudimorphodon's picture

I understand that. NetBSD is unix based, Linux is unix based. They all have a similar basic structure.

Note what I said: their *configuration file* layouts differ. Extensively and randomly, completely according to the whims of their creators.

Putting a file where you suggest will accomplish precisely dick on NetBSD. Interface configurations on NetBSD are stored in /etc/ifconfig.{nameofinterface}:

http://netbsd.org/Documentation/network/#configuration_files

Which, I might note, is completely different from its relative, FreeBSD:

http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/advanced-networking.html

Which lumps everything into the /etc/rc.conf file.

And of course both of those are completely different from Redhat linux and friends, who store their information in various files under /etc/sysconfig. Which of course is different from Slackware, which sticks it /etc/rc.d/rc.inet1...

Understand?

--Peace

Lemme boil it down to the basics. If you know how to use flavor, you can use them all. Just figuring out where the different config files are placed.

Please respond to the guy that needs help, lets not start a separate thread.

Thanks, Jay.

Eudimorphodon's picture

Lemme boil it down to the basics. If you know how to use flavor, you can use them all. Just figuring out where the different config files are placed.

Please respond to the guy that needs help, lets not start a separate thread.

Thanks, Jay.

I did. I pointed out that he should follow the instructions for his particular OS, not just put a configuration file in the wrong place and hope it does something.

Anyway.

I made my initial comments to help out the person that started this thread. Not to argue semantics with someone that obviosly knows everything and needs no help.

Jay.

At the top of this thread, when I mentioned where to save your networks settings in /etc/rc.d/rc.config. I was directing that to the person that started the discussion, because I left that out of my first post. I'm sorry you took it all wrong.

Cheers! Jay.

Thanks all, Jay & Eudimorphidon. Yes I have read various man pages and tried several combinations. Tried to ensure the eth0 interface was active, and as I said I have followed instructions as per ageing links from NetBSD website. Looks like what I need to do is post the contents of the various networking config files and see if anyone can spot what's missing or incorrect.

piltdownman's picture

do you have dhcpd running?

OK all, I somehow got it working. I'm not sure if it was as a result of enabling DHCP or not, but I did get it to ftp to my own machine and the netbsd ftp server (then I forgot the u/name and password to get in!)
So therefore it works.

But PING still does not work at all, so maybe I did get networking to resolve hostnames once before but didn't realize because I may have tried to use ping as the test.

so the other night I tried again, and it was not happening. Then, because it's on the 475, I was getting lots of segmentation faults.

And now a new version of NetBSD is out. It's time to start over.