On 07/12/10 10:55 PM, Peter Memishian wrote:
> No, I had a simpler address but it seems like that was the bug I was > hitting (based on public summary). Is there a way to see the entire > bug, suggested fix or webrev for the fix? bugs.opensolaris.org > doesn't show the interesting details. Anyway, moving to b138 solved > the issue. > > Thanks Meem (and Sowmini) .. .. Perhaps your local address (e.g., from DHCP) was in the .224 to .240 range?
OK, this was bugging me too much. So I booted back to b137 disk. The issue was ipfilter was enabled for whatever reason. And thats why when I disabled network/physical:default, ipfilter would also stop running (since nwam was already disabled) allowing the network to work fine. Now I know that I never enabled ipfilter. Does ipfilter gets enabled by default these days? Anyway, ipf.conf was empty. Other output was: # ipfstat -ioh 1 block out log all 0 pass out quick on lo0 all 0 pass out quick proto udp from any to any port = bootps 0 block in log all 0 pass in quick on lo0 all 0 pass in quick proto udp from any to any port = bootpc # svcs |grep ipfilter online 17:37:27 svc:/network/ipfilter:default # svcadm disable network/ipfilter:default # ping 192.168.1.1 192.168.1.1 is alive # hostname orion1 #cat /etc/hosts ::1 orion1.local localhost loghost 127.0.0.1 orion1.local localhost loghost 192.168.1.60 orion1 Apart from other things, it might be nice if ipfilter is blocking all traffic and ratio of blocked packets to allowed packets in some time period is too high, can ipf atleast issue a message on console etc. Granted, once I booted back today, it took me few minutes to figure out the issue but I suspect it might be more challenging to regular users. Anyway, thanks for the help guys ... Sunay _______________________________________________ networking-discuss mailing list [email protected]
