Re: [leaf-user] libsnl?

2003-01-04 Thread Mike Noyes
On Wed, 2002-12-11 at 06:00, Brad Fritz wrote:
 On Wed, 11 Dec 2002 09:02:07 +0100 Robit wrote:
  How can I view the package dependency?
 
 LEAF packages don't (currently) have built-in dependency tracking
 or checking.  Typical approaches include:
 
   1) Load the package, run the binaries, and see if it complains
  about missing pieces.
   
   2) Look online for package documentation.  (google and LEAF
  mailing list searches often produce good results.)
 
   3) Check the package itself, particularly in
  var/lib/lrpkg/pkgname.help .  (Packages are just
  gzipped tarballs.)

Brad,
I pulled the dependencies using ldd from perl5.lrp when I committed it
to our bin/packages tree in CVS.

http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/leaf/bin/packages/glibc-2.0/perl5.lrp

ldd-ver.sh
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/leaf/devel/mhnoyes/sf-admin/ldd-ver.sh?rev=1.3content-type=text/vnd.viewcvs-markup

-- 
Mike Noyes mhnoyes @ users.sourceforge.net
http://sourceforge.net/users/mhnoyes/
http://leaf-project.org/  http://sitedocs.sf.net/  http://ffl.sf.net/




---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

leaf-user mailing list: [EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-user
SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html



Re: [leaf-user] Win2K DNS Problem

2003-01-04 Thread Brad Fritz

On Sat, 04 Jan 2003 11:58:26 EST Kory Krofft wrote:

 Brad: Output from tcpdump as well as an Ethereal dump
 are at:
 http:home.woh.rr.com/kkrofft/etherealout
 http:home.woh.rr.com/kkrofft/tcpdump.txt

The tcpdump output is only for the Bering external interface,
but the ethereal (pcap capture) file contains DNS traffic
between the Win2k host and Bering.


 Both were run at the same time and were active as I tried to access 
 www.yahoo.com,
 www.etrade.com, and www.dogpile.com. I had flushed the dnscache and did
 experience the lag during this experiment. Yahoo eventually resolved 
 after 3 attempts
 the other two never did.

Interesting.  There is only one query in the pcap dump for
www.yahoo.com and it was successful.  The response looks
to have taken about one millisecond.  (It must have already
been in the dnscache cache.)

  brad@lab:~$ tcpdump -n -r etherealout port 53 | grep yahoo
  11:17:57.106379 192.168.1.1.1055  192.168.1.254.53:  \
14+ A?  www.yahoo.com. (31)
  11:17:57.107171 192.168.1.254.53  192.168.1.1.1055:  \
14 13/0/0 CNAME www.yahoo.akadns.net., A 64.58.76.230, \
A 64.58.76.178, A 64.58.76.222, A 64.58.76.224, A 64.58.76.176, \
A 64.58.76.223, A 64.58.76.228, A 64.58.76.179, A 64.58.76.229, \
A 64.58.76.225, A 64.58.76.177, A 64.58.76.227 (257) (DF)

There is no record of queries to etrade.com or dogpile.com:

  brad@lab:~$ tcpdump -n -r etherealout port 53 \
| grep -c -i -e dogpile -e etrade
  0

 I reran  nslookup and now get
 C:\nslookup www.yahoo.net
 DNS request timed out.
 timeout was 2 seconds.
 *** Can't find server name for address 192.168.1.254: Timed out
 *** Default servers are not available
 Server:  UnKnown
 Address:  192.168.1.254
 
 Non-authoritative answer:
 Name:yahoo.com
 Addresses:  64.58.79.230, 66.218.71.198
 Aliases:  www.yahoo.net
 
 I think the reason I was not seeing the non authoritative part was the way
 I issued the command previously.
 
 I have disabled the Win2K/Pro DNS client and since then I have seen no 
 lags so that
 may be the solution.

Sounds like the Win2K/Pro DNS cache was preventing queries from
ever making it to Bering.

--Brad



---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

leaf-user mailing list: [EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-user
SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html



[leaf-user] new WISP-Dist beta available (build 2469)

2003-01-04 Thread Vladimir I.
Hi All,

Two new builds in one day. :)

This one adds support for layer 2 (MAC) bridging in menu configuration 
interface, as well as network scripts. Please check it and let me know 
if you have any problems. This build is a beta before a stable release 
to SourceForge files area. Get it from 
http://www.hazard.maks.net/wisp-dist/downloads


New: support for layer 2 bridging in the configuration interface
New: support for layer 2 bridging in the network scripts
New: automatic WDS configuration if layer 2 bridging is enabled on 
Prism wireless cards in AP mode
New: wireless statistics are available through SNMP (.1.3.6.1.4.1.2021 
tree)
New: kernel 2.4.20
New: MMS (Windows Media)/tftp/PPTP/SNMP basic/talk/quake3 conntrack+nat
 (you may need to uncomment them in /etc/modules)
New: updated PCMCIA
New: new hostap_cs driver
New: update wireless extensions version in 2.4.20
New: DHCP relay; uncomment RCDLINKS and set MASTER_DHCP_SERVER
 in /etc/init.d/dhcrelay to enable it
New: hostapd support; delete /etc/pcmcia/hostap_cs.conf and rename
 /etc/pcmcia/hostap_cs_hapd.conf.disabled to 
/etc/pcmcia/hostap_cs_hapd.conf
Bugfix: updated AiroNet driver
Bugfix: updated rtl8139 driver from Donald Becker (no overrun lockup 
problem)
Bugfix: updated orinoco driver to 0.13
Bugfix: new wireless utils (fix WEP key removal bug)
Bugfix: include and load modules for DiskOnChip in initrd



--
Best Regards,
Vladimir
Systems Engineer (RHCE)



---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

leaf-user mailing list: [EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-user
SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html


[leaf-user] Qmail.lrp problem was: permissions

2003-01-04 Thread PASI RAUHANIEMI
Sorry! I thought that my LRP building Linux does not have qmail users  groups, but it 
has, allthought qmail is not installed. That was making permission changes to my 
qmail.lrp files. It seems ok now! just corrected server/$1 ( I hope it does not make 
troubles)  everything is started ok.  Still get file exists errors about 
/var/log/qmail/qmail/* at first start, but logs seems to work.   
-
Sunpoint tiedottaa:

Puhelintuki numerossa 0600-10 900 1,83E/min+pvm

Tutustu myös Etätukeen tästä
http://www.sunpoint.net/SunAds/click.htm?mode=footerid=70jump=http%3A%2F%2Fwww.pilotvastauspalvelu.fi%2Fdefault.asp%3Fsivu%3D3


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

leaf-user mailing list: [EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-user
SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html



Re: [leaf-user] ez-ipupdate dynamic DNS service providers

2003-01-04 Thread John Desmond
Greg-

I've been using DynDNS for several months without any
problems at all. I have a dynamic IP address. Setup
was easy. Use the custom DNS services for a one-time
start-up fee of $30.
http://support.dyndns.org/mydyndns/custom/howto/

It's been great fun having my own domain, my own
server and an infinite supply of email addresses! I'm
using qmail on the firewall to interface to the
server/workstation behind it and am growing more
confident of the setup every day. Let me know if you
need any help.

-John

--- Greg Morgan [EMAIL PROTECTED] wrote:
 I own my very own domain name.  I want to point it
 at my leaf box and 
 have a dynamic IP.  Can anyone provide feedback on
 their experiences 
 with any of the dynamic DNS service providers listed
 here?
 

http://leaf.sourceforge.net/devel/jnilo/ezipupd1.html
 
 Thanks,
 Greg Morgan
 
 
 

---
 This sf.net email is sponsored by:ThinkGeek
 Welcome to geek heaven.
 http://thinkgeek.com/sf


 leaf-user mailing list:
 [EMAIL PROTECTED]

https://lists.sourceforge.net/lists/listinfo/leaf-user
 SR FAQ:
http://leaf-project.org/pub/doc/docmanager/docid_1891.html


__
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

leaf-user mailing list: [EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-user
SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html



[leaf-user] Bering goes comatose fpr short periods.

2003-01-04 Thread John Desmond
I'm using Bering 1.0-rc3 - June 2002 with Verizon DSL.
I've noticed over the months that I would occasionally
lose connectivity and would have to reboot. Tonight I
waited it out and eventually got the connection
partially back. When I first noticed the problem, it
appeared that Bering had gone opaque again but I had
the time to investigate. We could not browse the web
from either of our computers behind the router. I can
ping between all the computers on the local net and to
Bering and back.

I can ping *some* Internet sites: www.yahoo.com is ok.
Can't ping www.ebay.com or www.50megs.com, but I can
now browse all three sites. (Bering came out of its
coma partially).

I started looking at the logs and noticed that some
entries are missing:
(packet logging edited out)
Dec 31 13:59:57 firewall -- MARK --
Dec 31 17:59:57 firewall -- MARK --
Jan 2 05:59:57 firewall -- MARK --
Jan 2 09:59:57 firewall -- MARK --
Jan 2 13:59:57 firewall -- MARK --
Jan 2 17:59:57 firewall -- MARK --
Jan 2 21:59:57 firewall -- MARK --
Jan 3 01:59:57 firewall -- MARK --
Jan 3 05:59:57 firewall -- MARK --
Jan 3 09:59:57 firewall -- MARK --
Jan 3 17:59:57 firewall -- MARK --
Jan 3 21:59:57 firewall -- MARK --
Jan 4 05:59:57 firewall -- MARK --
Jan 4 09:59:57 firewall -- MARK --
Jan 4 13:59:57 firewall -- MARK --
Jan 4 21:59:57 firewall -- MARK --

As you can see, some MARKs are missing. I saw that
the Jan 4 17:59:57 was missing but soon after I
started digging around, the system started logging
again with the 21:59:57 entry and started logging
packets again, too.

I've attached some data from the weblet which also
seems to be working OK. I haven't rebooted, so if
there's some diagnostic I can use, please let me know.

-John

==
::Interfaces::

1: lo:  mtu 16436 qdisc noqueue
link/loopback 00:00:00:00:00:00 brd
00:00:00:00:00:00
inet 127.0.0.1/8 brd 127.255.255.255 scope host lo
2: dummy0:  mtu 1500 qdisc noop
link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
3: eth0:  mtu 1500 qdisc pfifo_fast qlen 100
link/ether 00:10:4b:00:64:c4 brd ff:ff:ff:ff:ff:ff
4: eth1:  mtu 1500 qdisc pfifo_fast qlen 100
link/ether 00:60:08:08:78:81 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.254/24 brd 192.168.1.255 scope
global eth1
5: ppp0:  mtu 1492 qdisc pfifo_fast qlen 3
link/ppp
inet 151.200.47.185 peer 10.1.32.1/32 scope global
ppp0

::Routes::

10.1.32.1 dev ppp0  proto kernel  scope link  src
151.200.47.185
192.168.1.0/24 dev eth1  proto kernel  scope link  src
192.168.1.254
default via 10.1.32.1 dev ppp0 

::Statistics::

1: lo:  mtu 16436 qdisc noqueue 
link/loopback 00:00:00:00:00:00 brd
00:00:00:00:00:00
RX: bytes  packets  errors  dropped overrun mcast
8184842115268   0   0   0   0
TX: bytes  packets  errors  dropped carrier
collsns
8184842115268   0   0   0   0
2: dummy0:  mtu 1500 qdisc noop
link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
RX: bytes  packets  errors  dropped overrun mcast
0  00   0   0   0
TX: bytes  packets  errors  dropped carrier
collsns
0  00   0   0   0
3: eth0:  mtu 1500 qdisc pfifo_fast qlen 100
link/ether 00:10:4b:00:64:c4 brd ff:ff:ff:ff:ff:ff
RX: bytes  packets  errors  dropped overrun mcast
2005329302 1816910  0   0   0   0 

TX: bytes  packets  errors  dropped carrier
collsns
146703239  1243293  0   0   0   70

4: eth1:  mtu 1500 qdisc pfifo_fast qlen 100
link/ether 00:60:08:08:78:81 brd ff:ff:ff:ff:ff:ff
RX: bytes  packets  errors  dropped overrun mcast
132329438  1023266  0   0   0   0
TX: bytes  packets  errors  dropped carrier
collsns
1971211362 1600843  0   0   0   159   

5: ppp0:  mtu 1492 qdisc pfifo_fast qlen 3
link/ppp 
RX: bytes  packets  errors  dropped overrun mcast
1958204569 1628681  0   0   0   0 

TX: bytes  packets  errors  dropped carrier
collsns
117379954  1055064  0   0   0   0 



::Masqueraded Connections::

tcp src=192.168.1.10 33651 dst=205.188.10.8 5190
--431992 sec. ESTABLISHED
tcp src=192.168.1.10 33653 dst=205.188.9.167 5190
--431977 sec. ESTABLISHED


::Other Connections::

tcp src=204.108.8.5 49488 dst=151.200.47.185 22
--59324 sec. ESTABLISHED
tcp src=192.168.1.10 35271 dst=192.168.1.254 22
--431858 sec. ESTABLISHED
tcp src=192.168.1.10 35275 dst=192.168.1.254 443
--431997 sec. ESTABLISHED

EXAMPLE OF A CONNECTION REPORT WHILE A FAILED PING IS
ONGOING:
icmp src=16 dst=208.185.127.167 dst=src=151.200.47.185
type=8 --1 sec. id=22583 [UNREPLIED]
src=208.185.127.167 dst=151.200.47.185 type=0 code=0
id=22583 use=1

::General System Info::

Uptime:  10:32pm  up 16 days, 16:34, load average:
0.59, 0.18, 0.05


Kernel:Linux firewall 2.4.18 #4 Sun Jun 9 09:46:15
CEST 2002 i486 unknown


Modules:
ip_nat_irc  2384   0 (unused)
ip_nat_ftp

Re: [leaf-user] Win2K DNS Problem

2003-01-04 Thread Gene Smith
Brad Fritz wrote:

On Sat, 04 Jan 2003 11:58:26 EST Kory Krofft wrote:



Brad: Output from tcpdump as well as an Ethereal dump
are at:
http:home.woh.rr.com/kkrofft/etherealout
http:home.woh.rr.com/kkrofft/tcpdump.txt


FYI: I see the tcpdump.txt but not etherealout when I click.




---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

leaf-user mailing list: [EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-user
SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html