|
NetBSD General Other questions regarding NetBSD which do not fit in any of the categories below. |
|
Thread Tools | Display Modes |
|
|||
Network failure and output dumping onto console
Hello,
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 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) |
|
|||
Quote:
However, it usually is best that the administrator know about these kind of errors ASAP instead of ignoring them and/or sifting a logfile! |
|
|||
Hello,
Quote:
Thanks for the tip on redirecting the output.
__________________
And the WORD was made flesh, and dwelt among us. (John 1:14) |
|
|||
Hello,
Quote:
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) |
|
||||
That sounds screwy to me (but I'm sure ISP's have done stranger things).
How about simply creating a static alias on your NIC, e.g. 192.168.0.50/24? Then at boot time you'd be on the same network as your 192.168.0.1 device.
__________________
Kill your t.v. |
|
|||
Hello,
Quote:
P.S. - I did find the modem log that gives me the initial IP address (192.168.1.64) and subnet (255.255.0.0 - this is for the whole LAN).
__________________
And the WORD was made flesh, and dwelt among us. (John 1:14) |
|
||||
See this netbsd-users thread for notes on setting up an alias.
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 ??
__________________
Kill your t.v. |
|
|||
Hello,
Quote:
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:
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 Code:
eth0 Link encap:Ethernet HWaddr 00:1A:92:51:E4:0D inet addr:76.212.227.73 Bcast:76.212.227.255 Mask:255.255.255.0 inet6 addr: fe80::21a:92ff:fe51:e40d/64 Scope:Link UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1494 errors:0 dropped:0 overruns:0 frame:0 TX packets:1727 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1096456 (1.0 MiB) TX bytes:326868 (319.2 KiB) Interrupt:17 Base address:0x2000 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:8 errors:0 dropped:0 overruns:0 frame:0 TX packets:8 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:400 (400.0 b) TX bytes:400 (400.0 b) Code:
default 76.212.227.74 UG Note that the actual IP address of both my IP and the default gateway change dynamically upon each DHCP request.
__________________
And the WORD was made flesh, and dwelt among us. (John 1:14) |
|
||||
Quote:
Quote:
__________________
Kill your t.v. |
|
|||
Hello,
ifconfig nfe0 inet 192.168.1.64 netmask 255.255.0.0 alias This works except during a hard boot. 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) |
|
|||
Hello,
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) |
|
||||
Quote:
Code:
ifaliases_nfe0="inet 192.168.1.64 netmask 255.255.0.0"
__________________
Kill your t.v. |
|
||||
Quote:
__________________
Kill your t.v. |
|
|||
Hello,
I think I tried that one first - and I think it worked, but I migrated to ifconfig to explore other options.
__________________
And the WORD was made flesh, and dwelt among us. (John 1:14) |
|
|||
Hello,
Quote:
Code:
IP=`ifconfig nfe0 | grep -E 'inet.[0-9]' | awk '{print $2}'` if [ "$IP" = "192.168.1.64" ]; then ifconfig nfe0 inet 192.168.1.63 netmask 255.255.0.0 fi ifconfig nfe0 inet 192.168.1.64 netmask 255.255.0.0 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) |
|
|||
Hello,
A big thank you to anomie for helping me track down that error.
__________________
And the WORD was made flesh, and dwelt among us. (John 1:14) |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
dwm status bar won't display apm output | asemisldkfj | General software and network | 6 | 16th August 2009 11:07 PM |
Digital sound output | Zodox | FreeBSD General | 5 | 12th November 2008 02:21 PM |
C and file input/output | 18Googol2 | Programming | 3 | 20th August 2008 04:02 PM |
strange security run output | deadeyes | FreeBSD Security | 5 | 2nd July 2008 04:51 PM |
PHP Dumping Core Every 15 seconds?? | Michael | FreeBSD General | 2 | 21st June 2008 08:17 PM |