I have two problems that I think are co-related. The first is that output is dumped onto my console (no X, yet). It doesn't matter if I am in the middle of typing a command or in a program such as vi or the manpages, the output is dumped where the cursor is - though it doesn't affect anything (i.e., commands still work after be split up and it doesn't write into the files from vi). But, it is still very annoying! The messages, about 3 different ones, are:

(the italicized parts are replaced by the actual values)

Code:

DATE & TIME last message repeated N times
DATE & TIME dhclient: send_packet: Input/output error
DATE & TIME /netbsd: arplookup: unable to enter address for 192.168.0.1@00 MAC-ADRESS on nfe0 (host is not on local network)

The messages for this first problem don't matter (though, they relate to the second problem) - the problem is that they keeping dumping onto the console every couple of seconds.

The second problem (from which the specific error messages stem, I think) is that I can't always get my local gateway. If I soft boot into NetBSD, then all is fine. But, if I hard boot into NetBSD, then I have issues. It will not locate my local gateway - though I have my IP address. This is at least an improvement over 3.1 which wouldn't even let me get my IP address via DHCP on a hard boot. So on a hard boot, I can't ping say - www.google.com - though I can on a soft boot.

I get my IP address via DHCP from my ISP and my modem/router is statically set to 192.168.0.1. So say my address from my ISP is 62.24.38.124 - then the two are on different networks and I get the error messages - though I can ping using names on a soft boot with this setup and I can ping addresses on the network (i.e., 62.24.38.108 - even though it is only connected via the internet).

__________________
And the WORD was made flesh, and dwelt among us. (John 1:14)

The first is that output is dumped onto my console (no X, yet).. it is still very annoying!

There are a number of types of syslog messages sent to /dev/console by default. If you don't want to see them, just work on a different tty - e.g. Ctrl + Alt + F2.

Quote:

Originally Posted by JMJ_coder

DATE & TIME /netbsd: arplookup: unable to enter address for 192.168.0.1@00 MAC-ADRESS on nfe0 (host is not on local network)

What is your IP address/subnet while you're seeing this message? Perhaps delete your arp cache and see if the message appears again later: # arp -da

Quote:

Originally Posted by JMJ_coder

I get my IP address via DHCP from my ISP and my modem/router is statically set to 192.168.0.1. So say my address from my ISP is 62.24.38.124 - then the two are on different networks and I get the error messages - though I can ping using names on a soft boot with this setup and I can ping addresses on the network (i.e., 62.24.38.108 - even though it is only connected via the internet).

Your modem/router is also a NAT device, right? Shouldn't your NetBSD box's IP address be on the 192.168.0/24 network?

Your modem/router is also a NAT device, right? Shouldn't your NetBSD box's IP address be on the 192.168.0/24 network?

I don't believe the modem has a public IP address. All it has is the 192.168.0.1 address - and that address is locked in the modem's programming from the factory. And the computer doesn't have a NAT address. It is only assigned the address from the ISP (whether the ISP uses NAT on their end, I don't know, but I don't run NAT from my end).

The network works except for those two glitches - no DNS from a hard boot and those ugly error messages.

__________________
And the WORD was made flesh, and dwelt among us. (John 1:14)

Thank you. Well, we're getting somewhere. Adding the alias (I went the route of ifconfig ... alias) it resolves the ARP and DNS error. But, even though I put it in my rc.conf file, it will not assign the alias on a hard boot. So on a hard boot, I still have no DNS and I get that ARP error. If I enter the alias via the command line manually, it is immediately resolved. It will assign the alias on a soft boot.

Also, I am still getting the dhclient and last message errors. I could not look at them by using the tips given earlier in this thread, but it would be nice to know why I am getting these errors.

Quote:

Originally Posted by anomie

But now I am again thinking we are not on the same page about how your network is set up. Could you just post the results of:

# ifconfig -a

# route show | grep default

??

I think the modem acts almost as a network bridge. The results you are looking for are:

Note: the ifconfig was run from Slackware and not NetBSD (I don't have my 4.0 setup completely setup yet). The only differences are device names and NetBSD has an additional device fwiw0 (I think that is the correct name) set to address 0.0.0.0

But the results are similar on NetBSD after you boot? Publicly routable IP address for your NIC, and publicly routable IP address (which belongs to your ISP) for the gateway?

Not exactly sure what you are asking. It is the same setup for the network - computer -> DSL modem -> ISP. The same information is received from the DHCP server - an IP address and a gateway address (both can on completely different networks from session to session - i.e., 75.12.1.29 (IP) 75.12.1.254 (G) to 76.212.227.63 (IP) 76.212.227.74 (G)). The DSL modem never appears to receive a public IP address - it is always 192.168.0.1/16.

__________________
And the WORD was made flesh, and dwelt among us. (John 1:14)

Some new insights - it isn't so much the computer booting cold, as it is the modem do so. When the modem is powered on initially, it doesn't start negotiating with the ISP until the DHCP client tells it to, then it starts talking and very quickly dhclient gets enough information to go on, but the modem is still negotiating. So that when I first login (with some very quick typing, I might add ), I can ping the internet via DNS, but ifconfig shows the IP address as the private address - no alias (I wonder if you try to create an alias of the same address if it drops it). Within a matter of seconds, the modem is finished negotiating and gives dhclient the IP address, which displays via ifconfig - still no alias.

The reason it works on a soft boot is because the modem is still retaining all the DHCP information on a line that is still leased to me and it doesn't spend half a minute having to negotiate with the ISP after dhclient thinks it is done.

__________________
And the WORD was made flesh, and dwelt among us. (John 1:14)

I found out that you can't assign an alias with the same IP address as the one the interface currently has, so I had to check to see if it was the same and if it was, change it (it was going to change anyway) to set the alias properly. Alias is set and all is peachy keen.

Only two side effects of this -

1) for that half-minute to minute while the modem is finishing up all its loose ends, you can't reach the internet (big deal!).
2) when it runs through the if statement and assigns 192.168.1.63 and 192.168.1.64 becomes the alias - when the IP address if finally set, it makes 192.168.1.64 the IP address and the address from DHCP becomes the alias. I don't know why, but it still works the same.

I am still getting the dhclient error, but I have no clue as to why. I guess I just have to redirect the error message someplace else.

__________________
And the WORD was made flesh, and dwelt among us. (John 1:14)