Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 27 Feb 2000 18:09:59 +0100
From:      rene@xs4all.nl
To:        questions@freebsd.org, alexlh@funk.org, _@r4k.net
Subject:   routing blues
Message-ID:  <18756.000227@xs4all.nl>

next in thread | raw e-mail | index | archive | help
Hello questions,

  I've tried getting 2 NICs to work today, and sofar have failed to
  get the second one to work. I'd like to be able to ping a device
  attached to that second interface, ofcourse.


  {DSL-modem} -----  [ FreeBSD-box.ep0 ]
                     [ FreeBSD-box.xl0 ] ----   [ HUB ]
                                                   |
                                                   |
                                          [NT Workstation ]

  I know it's probably just my config, and I guess I don't quite grasp
  yet how the kernel decides what NIC gets a certain packet. Can
  someone explain?

  Here's the deal:

[root@messenger:/ date/time: Sun Feb 27/17:50:38]
 1# dmesg | grep -e ep0
ep0 at 0x300-0x30f irq 10 on isa
ep0: utp[*UTP*] address 00:20:af:92:f1:49

[root@messenger:/ date/time: Sun Feb 27/17:50:49]
 2# dmesg | grep -e xl0
xl0: <3Com 3c905B-TX Fast Etherlink XL> rev 0x30 int a irq 10 on pci0.12.0
xl0: Ethernet address: 00:10:5a:c0:33:b3
xl0: autoneg complete, link status good (half-duplex, 100Mbps)

[root@messenger:/ date/time: Sun Feb 27/17:50:52]
 3# netstat -nr
Routing tables

Internet:
Destination        Gateway            Flags     Refs     Use     Netif Expire
10/24              link#1             UC          0        0      xl0
10.0.0.1           0:10:5a:c0:33:b3   UHLW        0        4      lo0
10.0.0.2           0:10:5a:c0:32:13   UHLW        3      177      xl0   1101
10.0.0.138         10.0.0.139         UHW3        0       11      ep0   3219
10.0.0.139         0:20:af:92:f1:49   UHLS        0        6      xl0
10.0.0.255         ff:ff:ff:ff:ff:ff  UHLWb       2       59      xl0
127.0.0.1          127.0.0.1          UH          0       28      lo0

[root@messenger:/ date/time: Sun Feb 27/17:51:23]
 4# ping 10.0.0.1
PING 10.0.0.1 (10.0.0.1): 56 data bytes
64 bytes from 10.0.0.1: icmp_seq=0 ttl=255 time=0.097 ms
64 bytes from 10.0.0.1: icmp_seq=1 ttl=255 time=0.070 ms
^C
--- 10.0.0.1 ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.070/0.084/0.097/0.014 ms

  The NT workstation, works hapilly.

[root@messenger:/ date/time: Sun Feb 27/17:51:34]
 5# ping 10.0.0.138
PING 10.0.0.138 (10.0.0.138): 56 data bytes
^C
--- 10.0.0.138 ping statistics ---
5 packets transmitted, 0 packets received, 100% packet loss

  The other device (a modem, in this case), directly attached to the
  ep0 NIC.

[root@messenger:/ date/time: Sun Feb 27/17:51:44]
 6# tail /var/log/messages
Feb 27 17:51:40 messenger /kernel: arplookup 10.0.0.138 failed: could not allocate llinfo
Feb 27 17:51:40 messenger /kernel: arpresolve: can't allocate llinfo for 10.0.0.138rt
Feb 27 17:51:41 messenger /kernel: arplookup 10.0.0.138 failed: could not allocate llinfo
Feb 27 17:51:41 messenger /kernel: arpresolve: can't allocate llinfo for 10.0.0.138rt
Feb 27 17:51:42 messenger /kernel: arplookup 10.0.0.138 failed: could not allocate llinfo
Feb 27 17:51:42 messenger /kernel: arpresolve: can't allocate llinfo for 10.0.0.138rt
Feb 27 17:51:43 messenger /kernel: arplookup 10.0.0.138 failed: could not allocate llinfo
Feb 27 17:51:43 messenger /kernel: arpresolve: can't allocate llinfo for 10.0.0.138rt
Feb 27 17:51:44 messenger /kernel: arplookup 10.0.0.138 failed: could not allocate llinfo
Feb 27 17:51:44 messenger /kernel: arpresolve: can't allocate llinfo for 10.0.0.138rt

  Generated by the #5 PING command.

[root@messenger:/ date/time: Sun Feb 27/17:52:50]
 8# ping 10.0.0.139
PING 10.0.0.139 (10.0.0.139): 56 data bytes
^C
--- 10.0.0.139 ping statistics ---
7 packets transmitted, 0 packets received, 100% packet loss

  Even pinging the NIC itself won't work.


Greetings, 
 rene <mailto:rene@xs4all.nl>

http://www.business2.com/articles/2000/02/content/getalife_3.html
When your central nervous system is wired to a computer, time bombards you like surround-sound in an action flick. 




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?18756.000227>