Services depending on net are shut down AFTER the non-null network interface:
=== Begin ===
* Stopping br0
* Bringing down br0
* Destroying bridge br0 ...
* Removing port eth0 ... [ ok ]
* Removing port tap0 ... [ ok ]
[ ok ]
[ ok ]
* Unmounting network filesystems ...
* Failed to simply unmount filesystems
[ !! ]
* Stopping portmap ... [ ok ]
* Stopping squid ...2006/04/02 00:26:39| aclParseIpData: Bad host/IP: 'rd1.hitbox.com'
2006/04/02 00:26:39| aclParseIpData: Bad host/IP: 'banner.puretec.de'
2006/04/02 00:26:39| aclParseIpData: Bad host/IP: 'ads.babeclicks.com'
2006/04/02 00:26:39| aclParseAclLine: WARNING: empty ACL: acl to_ad_hosts dst rd1.hitbox.com banner.puretec.de ads.babeclicks.com
squid: ERROR: No running copy
[ ok ]
* Stopping uml_switch ... [ ok ]
* Stopping eth1
* Bringing down eth1
* Shutting down eth1 ... [ ok ]
* Stopping lo
* Shutting down lo ... [ ok ]
=== End ===
RC_NET_STRICT_CHECKING is set to "no". eth0, tap0 (part of br0) and eth1 (needed for pppoe) are set up as "null" in /etc/conf.d/net.
I'd expect the system not to regard "null" interfaces as fulfilling the "net" dependancy. They're raw physical devices providing no (IP level) network connectivity themselves.
you forgot `emerge info`