Re: Can't get Version 5 networking running

["Michael D. Spence" <spence%panix.com@localhost>]

> On Fri, 18 Sep 2009 08:06:16 -0400
> "Michael D. Spence" <spence%panix.com@localhost> wrote:
>
>>
>> I installed a new Dlink DFE-530 TX+ in my NetBSD Vers 5 system on
>> Tuesday. This system faces Verizon FIOS and acts as a firewall for
>> the rest of the network.
>>
>> The system recognized it as vr0.  Here are the lines from dmesg.
>>
>>   vr0 at pci2 dev 10 function 0: VIA VT6105 (Rhine III) 10/100
>> Ethernet vr0: interrupting at ioapic0 pin 22
>>   vr0: Ethernet address: 00:24:01:08:93:22
>>   ukphy0 at vr0 phy 1: Generic IEEE 802.3u media interface
>>
>> I configured it to be the connection to the internal network:
>>
>>     fxp0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
>>      address: 00:e0:18:4a:51:e4
>>      media: Ethernet autoselect (none)
>>     ex0: flags=8822<BROADCAST,NOTRAILERS,SIMPLEX,MULTICAST> mtu 1500
>>      address: 00:60:08:9a:53:6c
>>      media: Ethernet 100baseTX full-duplex
>>     vr0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
>>      address: 00:24:01:08:93:22
>>      media: Ethernet autoselect (100baseTX full-duplex)
>>      status: active
>>      inet 192.168.1.6 netmask 0xffffff00 broadcast
>> 192.168.1.255 inet6 fe80::224:1ff:fe08:9322%vr0 prefixlen 64 scopeid
>> 0x3 lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 33192
>>      inet 127.0.0.1 netmask 0xff000000
>>      inet6 ::1 prefixlen 128
>>      inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4
>>
>>
>> This worked flawlessly until Thursday evening when I tried to set up
>> the new ActionTec router that Verizon sent me to replace the one that
>> died.  (This router would normally be connected to ex0, but I took
>> it away to keep things simpler.)
>>
>> Now, all I ever get is
>>
>>     ping: sendto: Network is unreachable
>>     ping: sendt
>>     ----192.168.1.73 PING Statistics----
>>     5 packets transmitted, 0 packets received, 100.0% packet loss
>>     ping: sendto: Network is unreachable
>>
>>
>> Even though route show says it should be ok
>>
>>     Routing tables
>>
>>     Internet:
>>     Destination        Gateway            Flags
>>     loopback           127.0.0.1          UGR
>>     localhost          127.0.0.1          UH
>>     192.168.1.0/24     link#3             U
>>     192.168.1.6        00:24:01:08:93:22  UHL
>>     192.168.1.10       00:0d:88:67:c9:b4  UHL
>>     192.168.1.64       00:22:3f:0b:f2:03  UHL
>>     192.168.1.73       00:50:da:10:51:d5  UHL
>>
> What is the interface on those routes?
>

link#3 is vr0.  As it turns out, ipf.conf was stale and hadn't been
updated from fxp0 to vr0.  Darn sysadmin and his overly
clever scripts.  (Oh wait, that would be me <g>.)
m