RE: [leaf-user] Problems connecting to devices on eth0

2002-12-05 Thread Wheldon,M
Ray,

Thank you for your very quick response to the inconsistent information
posted to the list.
I've mailed this response to the list as well as yourself as the solution to
the problem may be of interest.

In the very first post I had the following set-up

Win95 Oxygen- win2k pro

I was able to ping win2k from win9x box but not vice versa.

In second post I had the following set-up

win9x Oxygen LRP

I was able to ping both LRP and win9x from oxygen box, however when I tried
pinging LRP from win9x it wouldn't work.

The solution to the problem was that I had the Cisco VPN v3.6 on the win9x
box and the win2k box with enable statefull firewall option turned on.

Turn it off and the configuration works.

Both machines work OK on my live network but in the test environment with
the Oxygen box doing the routing both failed.

Hope this helps someone else

Thanks yet again for such a quick response.

Cheers

Martin


-Original Message-
From: Ray Olszewski [mailto:[EMAIL PROTECTED]]
Sent: 02 December 2002 21:09
To: [EMAIL PROTECTED]
Subject: RE: [leaf-user] Problems connecting to devices on eth0


At 08:34 PM 12/2/02 +, Wheldon,M wrote:
Hi,

 Sorry about the lack of information in the previous post.
Hopefully
what follows will help.

Not a bit, I'm sorry to say. Because this is not the same configuration 
that you reported having trouble with.

This router (according to what you report) connects networks 192.168.0.0/24 
and 192.168.10.0/24 . And you report no symptoms of any trouble with it 
(for example, all the pings work just as they should).

Your earlier message reported a problem with a router that connected 
networks 192.168.1/0/24 and 10.18.0.0/24 . Associated with it was an 
undescribed unable to ping from one LAN to the other.

Please report the same details for the router that is having the problems 
as you reported here for the one that is (apparently) not having any 
problems. Or describe a symptom of the one you are giving us details about, 
if it is exhibiting problems. Or, if the problems relate somehow to the 
interaction between two routers, tell us all the details.


#uname -a
Linux myrouter 2.2.19brfw #5 Thu May 10 21:25:38 CDT 2001 i686 unknown

#ip addr show
1: lo: LOOPBACK,UP mtu 3924 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: eth0: BROADCAST,MULTICAST,UP mtu 1500 qdisc pfifo_fast qlen 100
 link/ether 52:54:00:e8:cc:46 brd ff:ff:ff:ff:ff:ff
 inet 192.168.10.254/24 brd 192.168.10.255 scope global eth0
3: eth1: BROADCAST,MULTICAST,UP mtu 1500 qdisc pfifo_fast qlen 100
 link/ether 00:50:bf:7e:c9:48 brd ff:ff:ff:ff:ff:ff
 inet 192.168.0.254/24 brd 192.168.0.255 scope global eth1

#ip route show
192.168.0.254 dev eth1  scope link
192.168.10.254 dev eth0  scope link
192.168.0.0/24 dev eth1  proto kernel  scope link  src 192.168.0.254
192.168.10.0/24 dev eth0  proto kernel  scope link  src 192.168.10.254
127.0.0.0/8 dev lo  scope link
default via 192.168.10.254 dev eth0

#lsmod
Module  Size  Used by
ext2   40800   2
rtl813912348   1
ne2k-pci4688   1
83906340   0 [ne2k-pci]

#ipchains -nvL
Chain input (policy ACCEPT: 83 packets, 7028 bytes):
Chain forward (policy ACCEPT: 8 packets, 480 bytes):
Chain output (policy ACCEPT: 131 packets, 10156 bytes):

#tail /var/log/messages
Dec  2 10:59:21 myrouter kernel: RAMDISK: Uncompressing root archive: done.
Dec  2 10:59:21 myrouter kernel: RAMDISK: Auto Filesystem - minix: 5461i
16384bk 176fdz(176) 1024zs 2147483647ms
Dec  2 10:59:21 myrouter kernel: VFS: Mounted root (minix filesystem).
Dec  2 10:59:21 myrouter kernel: RAMDISK: Extracting root archive: done.
Dec  2 10:59:21 myrouter kernel: ne2k-pci.c: v1.02 for Linux 2.2,
10/19/2000, D. Becker/P. Gortmaker,
http://www.scyld.com/network/ne2k-pci.html
Dec  2 10:59:21 myrouter kernel: ne2k-pci.c: PCI NE2000 clone 'RealTek
RTL-8029' at I/O 0xcc00, IRQ 9.
Dec  2 10:59:21 myrouter kernel: eth0: RealTek RTL-8029 found at 0xcc00,
IRQ
9, 52:54:00:E8:CC:46.
Dec  2 10:59:21 myrouter kernel: rtl8139.c:v1.07 5/6/99 Donald Becker
http://cesdis.gsfc.nasa.gov/linux/drivers/rtl8139.html
Dec  2 10:59:21 myrouter kernel: eth1: RealTek RTL8139 Fast Ethernet at
0xc800, IRQ 10, 00:50:bf:7e:c9:48.
Dec  2 10:59:21 myrouter kernel: Freeing unused kernel memory: 48k freed

192.168.0.26 is a windows 95 box
#ping -c 3 192.168.0.26
PING 192.168.0.26 (192.168.0.26): 56 data bytes
64 bytes from 192.168.0.26: icmp_seq=0 ttl=128 time=0.5 ms
64 bytes from 192.168.0.26: icmp_seq=1 ttl=128 time=0.4 ms
64 bytes from 192.168.0.26: icmp_seq=2 ttl=128 time=0.4 ms

--- 192.168.0.26 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 0.4/0.4/0.5 ms

192.168.10.1 is another lrp box
#ping -c 3 192.168.10.1
PING 192.168.10.1 (192.168.10.1): 56 data bytes
64 bytes from 

RE: [leaf-user] Unable to run linuxuml Virtual Router

2002-12-05 Thread Eric B Kiser
Hi Derek,

This usually happens because you are using an incompatible version of UML
Utilities. Here is the site to get the version you need:
http://user-mode-linux.sourceforge.net/dl-sf.html. The trick here is to find
the version that works. Try to choose the one that has the date code that is
closest to the date code for the kernel patch that you are using.

If you are using kernel 2.4.18-45 try using uml_utilities_20020729.tar.bz2.
If this does not work for you then it will be a matter of testing different
UML utilities until you find the one that works for you.

Best of luck and let us know how it turns out.
Regards,
Eric Kiser



-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Derek
Jennings
Sent: Wednesday, December 04, 2002 7:08 PM
To: [EMAIL PROTECTED]
Subject: [leaf-user] Unable to run linuxuml Virtual Router


Hi
It is probably me doing something idiotic, but I am having trouble running
Bering_1.0-stable_img_bering_1680.bin in the linuxuml-2.4.18-45 Virtual
environment.

I have followed Jacques Nilo's instructions, and can successfully create the
Bering_fs file system, but when I run my startuml script I get this output
in
my xterm.

early stuff SNIPPED

RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 2048 bind 2048)
Linux IP multicast router 0.06 plus PIM-SM
ip_conntrack version 2.0 (256 buckets, 2048 max) - 312 bytes per conntrack
ip_tables: (C) 2000-2002 Netfilter core team
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
Initializing software serial port version 1
mconsole (version 2) initialized on /home/leafuml/.uml/YEarYZ/mconsole
unable to open root_fs for validation
UML Audio Relay
Initializing stdio console driver
RAMDISK: Compressed image found at block 0
Freeing initrd memory: 401k freed
VFS: Mounted root (minix filesystem).
LINUXRC: Bering - Initrd - V1.0-stable
Mounting a 6M TMPFS filesystem...
LINUXRC: Could not mount the boot device. Can't install packages.
Kernel panic: Attempted to kill init!


My startuml script looks like :-
#!/bin/sh
./linuxuml-2.4.18-45 udb0=Bering_fs initrd=initrd.lrp root=/dev/ram0
init=/linuxrc \
 boot=/dev/udb0:minix PKGPATH=/dev/udb0 devfs=nomount
LRP=root,etc,local,log,modules,shorwall

Any suggestions would be welcome.

derek






---
This SF.net email is sponsored by: Microsoft Visual Studio.NET
comprehensive development tool, built to increase your
productivity. Try a free online hosted session at:
http://ads.sourceforge.net/cgi-bin/redirect.pl?micr0003en

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



---
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] WISP-Dist and Soekris

2002-12-05 Thread Vladimir I.
Hi All,

I just checked WISP-Dist on net4511/4522 and am happy to report
it works fine on both of the boards.

WISP-Dist is a Linux distribution targetted specifically for wireless 
routers with 8MB/16 MB RAM, heavily utilizes CramFS to save RAM and 
has nice menu-based configuration interface among other things. More 
info at 
http://www.leaf-project.org/mod.php?mod=userpagemenu=908page_id=27

--
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] Dachstein FreeS/WAN IPSec update re:bugtraq id 6011?

2002-12-05 Thread Duncan Napier
Hi,

I was wondering if Dachstein is still being  maintained, and if so 
whether there are any plans to update the IPSec components to something 
newer than FreeS/WAN 1.9.6? 

Essentially, the issue is that certain types of malformed IPSec packets 
can cause kernel panics in vulnerable versions (FreeS/WAN v. 1.9.6 and 
older):

http://online.securityfocus.com/bid/6011/info/

Regards,

Duncan.






---
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] Dachstein FreeS/WAN IPSec update re:bugtraq id 6011?

2002-12-05 Thread Charles Steinkuehler
Duncan Napier wrote:

Hi,

I was wondering if Dachstein is still being  maintained, and if so 
whether there are any plans to update the IPSec components to something 
newer than FreeS/WAN 1.9.6? 

Essentially, the issue is that certain types of malformed IPSec packets 
can cause kernel panics in vulnerable versions (FreeS/WAN v. 1.9.6 and 
older):

http://online.securityfocus.com/bid/6011/info/

I have not had time recently to do much in the way of maintainence on 
Dachstein, and while attempts at recruiting others to assist usually 
result in an initial flurry of activity, there never seems to be enough 
sustained effort to generate a new release.

If you are worried about the FreeS/WAN vunerabilities, you will have to 
update the ipsec packages for Dachstein yourself, or migrate to Bering, 
which includes a newer version of FreeS/WAN.

Details on how to build the kernel (with ipsec support), and 
modifications to the ipsec scripts required for Dachstein's limited 
shell environment are on my website (the readme file in the kernel 
source tarball, and the notes on my ipsec package page, respectively).

--
Charles Steinkuehler
[EMAIL PROTECTED]




---
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


Subject: [leaf-user] Unable to run linuxuml Virtual Router

2002-12-05 Thread Rogan Lynch
Yes Derek,

It was in fact something idiotic.

Fix your UML script to call Universal Block Devices..
ubd0 instead of udb...



---
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] Unable to run linuxuml Virtual Router -solved

2002-12-05 Thread Derek Jennings
Thanks  for the reply Eric
As expected it was just me being idiotic :(
I spent two days typing the boot device as udb0 when it should have been ubd0  Doh!

Fortunately the nice person who corrected me on the UserMode Linux list was gentle..


derek

- Original Message -
From: Eric B Kiser [EMAIL PROTECTED]
Date: Thu, 5 Dec 2002 10:47:12 -0500
To: [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: RE: [leaf-user] Unable to run linuxuml Virtual Router


 Hi Derek,
 
 This usually happens because you are using an incompatible version of UML
 Utilities. Here is the site to get the version you need:
 http://user-mode-linux.sourceforge.net/dl-sf.html. The trick here is to find
 the version that works. Try to choose the one that has the date code that is
 closest to the date code for the kernel patch that you are using.
 
 If you are using kernel 2.4.18-45 try using uml_utilities_20020729.tar.bz2.
 If this does not work for you then it will be a matter of testing different
 UML utilities until you find the one that works for you.
 
 Best of luck and let us know how it turns out.
 Regards,
 Eric Kiser
 
 
 
 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]]On Behalf Of Derek
 Jennings
 Sent: Wednesday, December 04, 2002 7:08 PM
 To: [EMAIL PROTECTED]
 Subject: [leaf-user] Unable to run linuxuml Virtual Router
 
 
 Hi
 It is probably me doing something idiotic, but I am having trouble running
 Bering_1.0-stable_img_bering_1680.bin in the linuxuml-2.4.18-45 Virtual
 environment.
 
 I have followed Jacques Nilo's instructions, and can successfully create the
 Bering_fs file system, but when I run my startuml script I get this output
 in
 my xterm.
 
 early stuff SNIPPED
 
 RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
 NET4: Linux TCP/IP 1.0 for NET4.0
 IP Protocols: ICMP, UDP, TCP, IGMP
 IP: routing cache hash table of 512 buckets, 4Kbytes
 TCP: Hash tables configured (established 2048 bind 2048)
 Linux IP multicast router 0.06 plus PIM-SM
 ip_conntrack version 2.0 (256 buckets, 2048 max) - 312 bytes per conntrack
 ip_tables: (C) 2000-2002 Netfilter core team
 NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
 Initializing software serial port version 1
 mconsole (version 2) initialized on /home/leafuml/.uml/YEarYZ/mconsole
 unable to open root_fs for validation
 UML Audio Relay
 Initializing stdio console driver
 RAMDISK: Compressed image found at block 0
 Freeing initrd memory: 401k freed
 VFS: Mounted root (minix filesystem).
 LINUXRC: Bering - Initrd - V1.0-stable
 Mounting a 6M TMPFS filesystem...
 LINUXRC: Could not mount the boot device. Can't install packages.
 Kernel panic: Attempted to kill init!
 
 
 My startuml script looks like :-
 #!/bin/sh
 ./linuxuml-2.4.18-45 udb0=Bering_fs initrd=initrd.lrp root=/dev/ram0
 init=/linuxrc \
  boot=/dev/udb0:minix PKGPATH=/dev/udb0 devfs=nomount
 LRP=root,etc,local,log,modules,shorwall
 
 Any suggestions would be welcome.
 
 derek
 
 
 
 
 
 
 ---
 This SF.net email is sponsored by: Microsoft Visual Studio.NET
 comprehensive development tool, built to increase your
 productivity. Try a free online hosted session at:
 http://ads.sourceforge.net/cgi-bin/redirect.pl?micr0003en
 
 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
 
 

   
-- 
___
Get your free email from http://mymail.operamail.com

Powered by Outblaze


---
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] Super-Freeswan and Bering user mode app compiler

2002-12-05 Thread Chad Carr
 Message: 6
 From: Mike North [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]
 Date: Thu, 05 Dec 2002 00:24:12 +0200
 Subject: [leaf-user] Super-Freeswan and Bering user mode app compiler
 
 
 Hi,
 
 I sent a question about compiling Super-Freeswan user mode
 application for Bering into Freeswan mailing list. Then I found
 this LEAF mailing list and I think that this is better place
 for the question.

Good job sending it here.  I am working on it.  I have attempted to
apply the alg patches and tried to compile them.  Same errors as
yourself.  I am currently trying to come up with a better solution to
the problem than hacking the code to make it compile (as we did with the
x509 patch), since the maintenance problem is forever.


-- 
---
Chad Carr [EMAIL PROTECTED]
---


---
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] PCI ADSL driver for Bering

2002-12-05 Thread Guy Ellis
Hi all,

For anyone who is interested I have compiled a PCI ADSL driver for Bering 
1.0. This driver is for the Pulsar PCI ADSL card and supports Bridged 
Ethernet, PPPoE and PPPoA.

You can download the driver from...

http://www.traverse.com.au/downloads/drivers/

Cheers,

 - Guy.
--
Guy Ellis
[EMAIL PROTECTED]

Traverse Technologies
ABN 98 078 657 324
652 Smith St.,
Clifton Hill, Victoria, 3068
AUSTRALIA
http://www.traverse.com.au
Tel (+613) 9486 7775
Fax (+613) 9482 7754
Mobile 0419 398 234
--



---
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