Hello Cory, Thursday, February 15, 2007, 2:40:51 AM, you wrote:
> Hello all, > My OpenBSD firewall is still randomly stopping routing packets and I > still can't figure out why. :-( > I made the suggested patch to if_ether.c, ut now I just get the > following line in /var log messages: > Feb 14 18:08:41 bytor /bsd: arpresolve: can't allocate llinfo for > 192.168.1.1:no link address > Symptoms: Firewall can ping the wifi router (to which ADSL modem is > attached), but pinging anything beyond it fails. If I try to traceroute > to some place beyond the router, it doesn't show the router as the first > hop. (If it can ping the router, shouldn't it show up a the first hop on > a traceroute?). Even though the firewall can ping the router, it cannot > ping my laptop, even though the route to both goes out ral0. The laptop > cannot ping the firewall either. I know the router is still working > because my laptop can still access the internet through it once I reset > the default gateway to the router instead of the firewall. IPv6 ssh > connections form the laptop to the firewall stay active. > Things is, "arp -a" and "route -n show -inet" show extactly the same > thing whether the problem is currently in progress or everything is > working perfectly. No NICs accidentally have addresses on the wrong segment. > I had routed running, but stopping it has made no difference. > Anybody have any ideas? > [EMAIL PROTECTED] 1:03:58 [9]/etc> arp -a > bytor (192.168.0.1) at 00:0e:0c:bc:38:9d on em1 static > xanadu (192.168.0.2) at 00:0e:0c:b9:4d:ed on em1 > heechee.wireless (192.168.1.1) at 00:13:10:0e:0b:08 on ral0 > snowdog.wireless (192.168.1.3) at 00:12:17:60:fe:40 on ral0 > redbarchetta.wireless.fenris.cjb.net (192.168.1.191) at > 00:18:de:20:4f:2e on ral0 > bytor (192.168.16.1) at 00:0e:0c:b9:50:74 on em0 static > snowdog (192.168.16.2) at 00:15:f2:e8:7f:51 on em0 > [EMAIL PROTECTED] 1:04:03 [10]/etc> route -n show -inet > Routing tables > Internet: > Destination Gateway Flags Refs Use Mtu Interface > default 192.168.1.1 UGS 16 188916 - ral0 > 127.0.0.1 127.0.0.1 UH 2 6049 33224 lo0 > 192.168.0/24 link#3 UC 2 0 - em1 > 192.168.0.1 00:0e:0c:bc:38:9d UHLc 9 996889 - lo0 > 192.168.0.2 00:0e:0c:b9:4d:ed UHLc 1 56064 - em1 > 192.168.1/24 link#4 UC 3 0 - ral0 > 192.168.1.1 00:13:10:0e:0b:08 UHLc 2 3272 - ral0 > 192.168.1.3 00:12:17:60:fe:40 UHLc 0 483 - ral0 > 192.168.1.191 00:18:de:20:4f:2e UHLc 0 4587 - ral0 > 192.168.2/24 link#1 UC 0 0 - fxp0 > 192.168.16/24 link#2 UC 2 0 - em0 > 192.168.16.1 00:0e:0c:b9:50:74 UHLc 0 50 - lo0 > 192.168.16.2 00:15:f2:e8:7f:51 UHLc 5 392664 - em0 > [EMAIL PROTECTED] 1:04:13 [11]/etc> cat hostname.ral0 > inet 192.168.1.2 255.255.255.0 192.168.1.255 nwid fenris nwkey > 0x0A18135EB54723927B64AB65BC > inet6 alias 2001:05c0:92cf:1::c0a8:0102 64 > [EMAIL PROTECTED] 1:06:08 [12]/etc> cat hostname.em0 > inet 192.168.16.1 255.255.255.0 192.168.16.255 > inet6 alias 2001:05c0:92cf:10::c0a8:1001 64 > [EMAIL PROTECTED] 1:06:18 [13]/etc> cat hostname.em1 > inet 192.168.0.1 255.255.255.0 192.168.0.255 > inet6 alias 2001:05c0:92cf:0::c0a8:0001 64 > [EMAIL PROTECTED] 1:06:33 [14]/etc> cat hostname.fxp0 > inet 192.168.2.1 255.255.255.0 192.168.2.255 > inet6 alias 2001:5c0:92cf:2::c0a8:0201 64 I had this issue before and it turned out to be a bad NIC. -- Best regards, Shane homepage: http://craz1.homelinux.com
