[leaf-user] wisp-dist ... Client cannot hear AP
I have set up an two wisp-dists ... one as AP and one As Client ( managed mode ). I double checked all the routes and subnets the AP shows active association of the client. The client shows association to the AP I run tcpdump -i netcs0 and can see the AP is hearing the client but the client is not hearing anything coming from the AP. Thus, no data can go across the link. I am using the teletronics 100mW cards on the 486 SBC. I tried the pigtale in the second slot ( farthest away from LED's ) and then the AP could not connect to anything. both the client and AP shows a radio association. But the client shows no traffic being received at all when I am sending pings to it from the AP. The AP can hear the arp requests and the pings from the client. I have tried wisp-dist builds 2312 and 2324. Am I missing something obvious here? Any suggestions? thanx --- 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] FTP and IP-NAT
HI people, I have a Dachstein router with EchoWall and SSH on it. I try connecting to a FTP server and get this message: error message: 501 you are on a LAN and the IP-NAT is not translating your IP address correctly I didn't have this problem before with this server, so i assume they changed something. What do I need to change in my router to prevent this problem? Thanks for any help. Joris Met vriendelijke groet, Joris Kempen St. Ursulahof 47 5995 CB Kessel email: [EMAIL PROTECTED] tel. nr.: 06 1257 4228 --- 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] Cisco Aironet PCI cards and wisp-dist
John van Oppen wrote about AW: [leaf-user] Cisco Aironet PCI cards and wisp-dist: I am using build 2290. I did not see anything on the URL below except a link to the main leaf site. Where would I obtain a development version? Sorry, I didn't type the link fully - http://www.hazard.maks.net/wisp-dist/downaloads . Download image 2341. This is a release candidate. Thanks John :) John van Oppen vanoppen.biz Internet hosting and security services +1 (650) 587 - 1867 PO Box 502 Mercer Island, WA 98040 -Ursprüngliche Nachricht- Von: Vladimir I. [mailto:[EMAIL PROTECTED]] Gesendet: Freitag, 20. September 2002 05:43 An: John van Oppen Cc: [EMAIL PROTECTED] Betreff: Re: [leaf-user] Cisco Aironet PCI cards and wisp-dist Hi, Please try the latest test image from http://www.hazard.maks.net/wisp-dist. John van Oppen wrote: All - I could not find this exact issue being addressed in the archives so I figured that someone subscribed to this list might know the answer. I have two computers with cisco aironet 350 PCI cards running wisp-dist and I am having trouble getting wisp-dist to recognize the cisco cards. It seems from the documentation that the aironet cards are supported but I can't find where to enable the module. My other wisp-dist box with a lucent card just recognized it on boot up. I am sure this is an obvious problem and any help getting the cisco cards running would be greatly appreciated. Thanks, John van Oppen www.vanoppen.biz Fast reliable internet hosting! --- This SF.NET email is sponsored by: AMD - Your access to the experts on Hammer Technology! Open Source Linux Developers, register now for the AMD Developer Symposium. Code: EX8664 http://www.developwithamd.com/developerlab 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 -- Best Regards, Vladimir Systems Engineer (RHCE) -- 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] [ leaf-Support Requests-606429 ] Problems whit SSH and FTP, using Bering
Support Requests item #606429, was opened at 2002-09-08 20:16 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=213751aid=606429group_id=13751 Category: Release/Branch: Bering Group: None Status: Open Priority: 5 Submitted By: Tom Harr Jakobsen (harjakob) Assigned to: Mike Noyes (mhnoyes) Summary: Problems whit SSH and FTP, using Bering Initial Comment: I have a router whith Bering, and now I try to get access to it throug SSH - but I do experience some problems -I can' t get through the Shorewall with FTP either - I follow the installation guide, and the Users guide, but it don't seem to work anyway - are ther any known issues around this? -- Comment By: Tom Harr Jakobsen (harjakob) Date: 2002-09-21 10:46 Message: Logged In: YES user_id=607432 thanx - that worked!!! -- Comment By: Matt Schalit (rogermatt) Date: 2002-09-20 19:17 Message: Logged In: YES user_id=144016 1. Check that sshd is running on the LEAF box, using the command ps from the command line. You should see something like 15392 root 4344 R/usr/sbin/sshd If sshd is not running, then type at the # prompt: # /usr/sbin/sshd If it returns to a command prompt with no messages, you're set. If it dies with an error like special user not found, read the docs that jnilo has in his sections for sshd. 2. vi /etc/shorewall/rules and add lines like these above the LAST LINE. # Accept DNS connections from the firewall to the network ACCEPT fw net tcp 53 ACCEPT fw net udp 53 # Accept SSH connections from the local network for administration ACCEPT loc fw tcp 22 # Accept DNS queries from local network to the firewall (dnscache/tinydns) ACCEPT loc fw tcp 53 ACCEPT loc fw udp 53 # Accept Web queries from local network to firewall (weblet) ACCEPT loc fw tcp 80 Either the process wasnt' running, or you were blocked. If you were blocked it would show up in your syslog. It should work now. Let us know so we can close this or get you some more help :) Matthew -- Comment By: Manfred Schuler (mschuler) Date: 2002-09-10 01:25 Message: Logged In: YES user_id=490757 It seems that sshd is not running. sshd is not enabled in inetd.conf and the file /etc/init.d/sshd contains this lines: #Comment out and edit /etc/inetd.conf to run as a stand alone server echo Secure Shell server via inetd: sshd exit 0 So sshd is not started. You have to decide, if you start sshd by inetd or by initscript. When started by inted, connecting to LEAF takes more time, because the session key must be generated by sshd before connecting. Starting by initscript consumes some memory, because sshd is always running, even when you are not logged in. You must either comment the echo and exit line in /etc/init.d/sshd or uncomment the #ssh line in /etc/inetd.conf. Manfred -- Comment By: Tom Harr Jakobsen (harjakob) Date: 2002-09-09 16:41 Message: Logged In: YES user_id=607432 I'm only trying to connect using ssh from a local machine on the network, using Putty...I only recive connection refused -- Comment By: Jacques Nilo (jnilo) Date: 2002-09-09 12:22 Message: Logged In: YES user_id=150195 Aren't you trying to ssh of ftp from the outside network by any chance ? If so you need to adjust Shorewall rules file and /etc/hosts.allow If not more info about the type of error you get would help... -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=213751aid=606429group_id=13751 --- 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] FTP and IP-NAT
Hi people, I talked with the admin of the ftp site. and he told me that port 864 is needed for IP NAT. Can I just open port 864? I have DachStein Echowall, how do I open this port 864. Any links maybe that tell me (in easy language:) what IP-NAT exactly is.. Thanks.. Met vriendelijke groet, Joris Kempen St. Ursulahof 47 5995 CB Kessel email: [EMAIL PROTECTED] tel. nr.: 06 1257 4228 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Joris Kempen Sent: Saturday, September 21, 2002 10:14 AM To: Leaf (E-mail) Subject: [leaf-user] FTP and IP-NAT HI people, I have a Dachstein router with EchoWall and SSH on it. I try connecting to a FTP server and get this message: error message: 501 you are on a LAN and the IP-NAT is not translating your IP address correctly I didn't have this problem before with this server, so i assume they changed something. What do I need to change in my router to prevent this problem? Thanks for any help. Joris Met vriendelijke groet, Joris Kempen St. Ursulahof 47 5995 CB Kessel email: [EMAIL PROTECTED] tel. nr.: 06 1257 4228 --- 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 --- 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] wisp-dist ... Client cannot hear AP
Looks like your PCMCIA controller needs special settings to make it work. Check if there are any interrupts for wireless card in /proc/interrupts. /etc/init.d/pcmcia already knows about some weird PCMCIA controllers, so try adding yours - search for the line which mentions Teletronics boards. [EMAIL PROTECTED] wrote: I have set up an two wisp-dists ... one as AP and one As Client ( managed mode ). I double checked all the routes and subnets the AP shows active association of the client. The client shows association to the AP I run tcpdump -i netcs0 and can see the AP is hearing the client but the client is not hearing anything coming from the AP. Thus, no data can go across the link. I am using the teletronics 100mW cards on the 486 SBC. I tried the pigtale in the second slot ( farthest away from LED's ) and then the AP could not connect to anything. both the client and AP shows a radio association. But the client shows no traffic being received at all when I am sending pings to it from the AP. The AP can hear the arp requests and the pings from the client. -- 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
Re: [leaf-user] VPN Static Routes
I have a Dachstein LRP with this routing table: Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 10.50.50.0 68.2.2.1255.255.255.0 UG0 0 0 ipsec0 192.168.38.00.0.0.0 255.255.255.0 U 0 0 0 eth1 68.2.2.00.0.0.0 255.255.255.0 U 0 0 0 eth0 68.2.2.00.0.0.0 255.255.252.0 U 0 0 0 ipsec0 0.0.0.0 68.2.2.10.0.0.0 UG0 0 0 eth0 The subnet 10.50.50.0/24 on the right-hand side of the IPSec tunnel has a hub router at 10.50.50.1 that has routes to the other VPN subnets. My '38 network is one of the spokes of a hub spoke topology. I'd like to add a single static route here (left-hand side, spoke end) and be able to reach the far-flung spoke networks via the hub router at 10.50.50.1 (e.g., those up-state wahoos over on the 192.168.4.0/24 spoke). So I tried: # route add -net 192.168.0.0 netmask 255.255.0.0 gw 10.50.50.1 SIOCADDRT: Network is unreachable Unfortunately, I cannot ping hosts in 10.50.50.0/24 from the LRP, although I can ping any host in 10.50.50.0/24 from another host in my '38 network. How might I be able to configure my spoke, and the other spokes, to use the hub router? Remember only traffic explicitly specified in the IPSec connections will be able to go through the ipsec tunnel. Since your IPSec tunnel is apparently between the 192.168.38.0/24 and 10.50.50.0/24 subnets, only traffic matching these IP's for source/destination will pass through the subnet-subnet IPSec tunnel. If you have additional subnets on the far side of the router, you will need to create additional connection descriptions for them, or suitably widen the [left|right]subnet declaration in your existing connection description. As is usual in networking, proper planning of subnet addressing can significantly reduce the complexity of your routing (and IPSec connection) configuration. More details are available in the FreeS/WAN Documentation: http://www.freeswan.org/freeswan_snaps/CURRENT-SNAP/doc/adv_config.html# otherconf I believe the tunnels are cheap example describes your problem exactly... NOTE: Link is from the current snapshot tree, since the release tree documentation seems to have gone walk-about. Actual docs from the Dachstein release of FreeS/WAN can be found here: http://leaf.sourceforge.net/devel/cstein/Packages/man/IPSec1.91/index.ht ml ...but the later docs are generally more complete and useful. Charles Steinkuehler http://lrp.steinkuehler.net http://c0wz.steinkuehler.net (lrp.c0wz.com mirror) --- 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 RC3: pptp connection fails with mschap-v2 authentication
Hello all, I have problems establishing a pptp connection between Bering RC3 poptop server and a Win2k client. I'm using the patched pppd 2.4.1 (pppd-pptp) as described in Bering installation guide (ppp-2.4.1-openssl-0.9.6-mppe-patch.gz;ppp-2.4.1-MSCHAPv2-fix.patch.gz). Trying to bring up the connection on Win2k with settings for MSCHAPv2 authentication produces error 741 (The local computer does not support the required data encryption type). On Bering pppd says: peer refused to authenticate: terminating link. If I let the client to authenticate without data encryption it uses CHAP MD5 the connection comes up and works. Here's my deamon.log enty for failed connection: Sep 20 20:47:29 firewall pptpd[20787]: MGR: Launching /usr/sbin/pptpctrl to handle client Sep 20 20:47:29 firewall pptpd[20787]: CTRL: local address = 192.168.1.240 Sep 20 20:47:29 firewall pptpd[20787]: CTRL: remote address = 192.168.1.240 Sep 20 20:47:29 firewall pptpd[20787]: CTRL: pppd speed = 115200 Sep 20 20:47:29 firewall pptpd[20787]: CTRL: pppd options file = /etc/ppp/pptpd-options Sep 20 20:47:29 firewall pptpd[20787]: CTRL: Client 62.134.116.133 control connection started Sep 20 20:47:29 firewall pptpd[20787]: CTRL: Received PPTP Control Message (type: 1) Sep 20 20:47:29 firewall pptpd[20787]: CTRL: Made a START CTRL CONN RPLY packet Sep 20 20:47:29 firewall pptpd[20787]: CTRL: I wrote 156 bytes to the client. Sep 20 20:47:29 firewall pptpd[20787]: CTRL: Sent packet to client Sep 20 20:47:29 firewall pptpd[20787]: CTRL: Received PPTP Control Message (type: 7) Sep 20 20:47:29 firewall pptpd[20787]: CTRL: Set parameters to 1525 maxbps, 64 window size Sep 20 20:47:29 firewall pptpd[20787]: CTRL: Made a OUT CALL RPLY packet Sep 20 20:47:29 firewall pptpd[20787]: CTRL: Starting call (launching pppd, opening GRE) Sep 20 20:47:29 firewall pptpd[20787]: CTRL: pty_fd = 5 Sep 20 20:47:29 firewall pptpd[20787]: CTRL: tty_fd = 6 Sep 20 20:47:29 firewall pptpd[20787]: CTRL: I wrote 32 bytes to the client. Sep 20 20:47:29 firewall pptpd[13294]: CTRL (PPPD Launcher): Connection speed = 115200 Sep 20 20:47:29 firewall pptpd[13294]: CTRL (PPPD Launcher): local address = 192.168.1.240 Sep 20 20:47:29 firewall pptpd[13294]: CTRL (PPPD Launcher): remote address = 192.168.1.240 Sep 20 20:47:29 firewall pppd[13294]: pppd 2.4.1 started by root, uid 0 Sep 20 20:47:29 firewall pppd[13294]: using channel 2 Sep 20 20:47:29 firewall pppd[13294]: Using interface ppp1 Sep 20 20:47:29 firewall pptpd[20787]: CTRL: Sent packet to client Sep 20 20:47:29 firewall pppd[13294]: Connect: ppp1 -- /dev/ttyp0 Sep 20 20:47:29 firewall pptpd[20787]: CTRL: Received PPTP Control Message (type: 15) Sep 20 20:47:29 firewall pptpd[20787]: CTRL: Got a SET LINK INFO packet with standard ACCMs Sep 20 20:47:29 firewall pptpd[20787]: GRE: Discarding duplicate packet Sep 20 20:47:31 firewall pppd[13294]: peer refused to authenticate: terminating link Sep 20 20:47:31 firewall pptpd[20787]: CTRL: Received PPTP Control Message (type: 15) Sep 20 20:47:31 firewall pptpd[20787]: CTRL: Ignored a SET LINK INFO packet with real ACCMs! Sep 20 20:47:31 firewall pptpd[20787]: CTRL: Received PPTP Control Message (type: 15) Sep 20 20:47:31 firewall pptpd[20787]: CTRL: Got a SET LINK INFO packet with standard ACCMs Sep 20 20:47:31 firewall pptpd[20787]: CTRL: Received PPTP Control Message (type: 12) Sep 20 20:47:31 firewall pptpd[20787]: CTRL: Made a CALL DISCONNECT RPLY packet Sep 20 20:47:31 firewall pptpd[20787]: CTRL: Received CALL CLR request (closing call) Sep 20 20:47:31 firewall pptpd[20787]: CTRL: I wrote 148 bytes to the client. Sep 20 20:47:31 firewall pptpd[20787]: CTRL: Sent packet to client Sep 20 20:47:31 firewall pppd[13294]: Modem hangup Sep 20 20:47:31 firewall pppd[13294]: Connection terminated. Sep 20 20:47:31 firewall pppd[13294]: Exit. Sep 20 20:47:31 firewall pptpd[20787]: CTRL: Received PPTP Control Message (type: 3) Sep 20 20:47:31 firewall pptpd[20787]: CTRL: Made a STOP CTRL CONN RPLY packet Sep 20 20:47:31 firewall pptpd[20787]: CTRL: Received STOP CTRL CONN request (disconnecting) Sep 20 20:47:31 firewall pptpd[20787]: CTRL: I wrote 16 bytes to the client. Sep 20 20:47:31 firewall pptpd[20787]: CTRL: Sent packet to client Sep 20 20:47:31 firewall pptpd[20787]: CTRL: Client 62.134.116.133 control connection finished Sep 20 20:47:31 firewall pptpd[20787]: CTRL: Exiting now Sep 20 20:47:31 firewall pptpd[1268]: MGR: Reaped child 20787 This is my ppptp.options file: lock multilink proxyarp auth asyncmap 0 require-chap require-mppe require-mppe-stateless -chap -chapms +chapms-v2 ipcp-accept-local ipcp-accept-remote lcp-echo-failure 30 lcp-echo-interval 5 deflate 0 mppe-128 mppe-stateless These are the entries in /etc/modules: # Modules needed for PPP connection slhc ppp_generic ppp_async ppp_deflate # Modules needed for PPP/PPPOE connection #slhc n_hdlc #ppp_generic ppp_synctty pppox pppoe # Modules needed for PPTP connection #slhc #ppp_generic #ppp_async
RE: [leaf-user] FTP and IP-NAT
This is a new one to me. I hope someone else will turn out to be familiar with it and post a simple solution, but I wouldn't count on it. (I waited awhile before replying, in this hope.) I am reasonably sure that IP-NAT is just a slightly more exact synonym for NAT. At least every reference I could find used it that way. I assume you know what the ordinary meaning of NAT is. I can't find any reference to the use of port 864 in connection with NAT or IP-NAT (or ftp). Just opening it is unlikely to help you much; something on your router or LAN will need either to send from that port or listen on it -- or maybe accept input *from* it; the advice you report getting is so sketchy that it is hard to guess. The admin's advice doesn't include telling you what his site uses the port for, and I can't find any indication that the use is anything established by any standard ... or at least nothing connected to NAT or ftp. (The only references to port 864 that I was able to track down are in RFC 768, where 864-UDP is associated with a service called Discard, and with connection to ypserv, which also runs on 864-UDP. You may need to find out what the site expects to receive or send from or to that port.) So ... if someone else jumps in here with an easy answer, that's terrific. If no one does ... then you may be the first one to run into a new problem that we (and Linux-NAT users generally) need to work out a solution for. In that case, the more information you can provide, the better. The other possibility is that this use of port 864 is some oddity specific to the particular ftp site. I've seen a few other cases recently where admins of ftp sites did something short-sighted that caused problems for connections from firewalled sites, and in such cases, there is really no sensible fix other than letting the admin know that it is his problem to fix, not yours. I'm sorry this reply isn't more helpful, and I do hope that someone else who recognizes the problem from your description will respond with more information. At 01:23 PM 9/21/02 +0200, Joris Kempen wrote: Hi people, I talked with the admin of the ftp site. and he told me that port 864 is needed for IP NAT. Can I just open port 864? I have DachStein Echowall, how do I open this port 864. Any links maybe that tell me (in easy language:) what IP-NAT exactly is.. Thanks.. Met vriendelijke groet, Joris Kempen St. Ursulahof 47 5995 CB Kessel email: [EMAIL PROTECTED] tel. nr.: 06 1257 4228 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Joris Kempen Sent: Saturday, September 21, 2002 10:14 AM To: Leaf (E-mail) Subject: [leaf-user] FTP and IP-NAT HI people, I have a Dachstein router with EchoWall and SSH on it. I try connecting to a FTP server and get this message: error message: 501 you are on a LAN and the IP-NAT is not translating your IP address correctly I didn't have this problem before with this server, so i assume they changed something. What do I need to change in my router to prevent this problem? -- ---Never tell me the odds! Ray Olszewski -- Han Solo Palo Alto, California, USA[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] Bewan drivers
Hi, I am upgrading to the latest version of the bewan adsl pci card drivers (http://www.bewan.com/bewan/drivers/bapst-0.3.4.tar.gz) I have setup up the debian/slink virtual uml and compiled the driver, but when I try and load the module I get # insmod unicorn_atm Using /lib/modules/unicorn_atm.o insmod: unresolved symbol do_BUG I did have some problems getting the compile to work, but eventually got it compiled against my redhat 2.4.18 kernel (it's the same as a deb 2.4.18 kernel, isn't it?) The last drivers I got, Jacques kindly compiled for me, but I was trying to cut down on his workload this time ;-) Does anyone have any ideas, or is there maybe something that needs to be added to the leaf/uml instructions specifically for compiling drivers for Bering. Do you just need the uml kernel running, root fs, uml utilities, kernel source and driver code. Thanks for any help. Dave --- 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] FTP and IP-NAT
On Saturday 21 September 2002 12:28, Ray Olszewski wrote: This is a new one to me. I hope someone else will turn out to be familiar with it and post a simple solution, but I wouldn't count on it. (I waited awhile before replying, in this hope.) I'll have to agree with Ray one this one. There is generally a higher port that ftp servers use for multiple traffic requests on the server side of the net (ie... port 1021 is common for Linux ftp server traffic). However you should not need to open anything on your firewall to RECEIVE a requested ftp file. In 2.2 LEAF boxes, udp traffic is not blocked, only tcp which would normally be request instead of a response. The 2.4/iptables LEAF firewalls use connection tracking, so if your client/firewall requested a ftp file it will remember and accept it. The only possible option I can think of an ISP using a different port would be some form of a proxy, which is not typical of any decent ISP that I am aware of. I would have to think that something very fishy is going on with your ISP. Is your ISP running NAT??? This could be the only reason for using a different port for NAT transversal. -- ~Lynn Avants aka Guitarlynn guitarlynn at users.sourceforge.net http://leaf.sourceforge.net If linux isn't the answer, you've probably got the wrong question! --- 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] HowTo set Date time
How To set Date Time - 3 questions I ) Is there a DateTime HowTo for leaf? II ) I've forgotten how to set the date, time timezone under leaf (bering) for the system, user, and the cpu's clock. Where are examples of the correct usage for the commands documented? Where are the caveats for timezones dachstein/bering particulars documented? III) rdate appears to be available, but most servers have depreciated it (are no longer accepting it) where might I find a list of servers that still accept rdate requests? thanks --- 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] wisp-dist ... Client cannot hear AP
I have determined it is specifically build (2324) that is giving me the problem. with build 2312 the AP mode worked. with build 2324 it did not ( I could not get any cards including a lucent silver card to connect to the AP ) I created an .img and burned to flash with the latest build 2341 and it is working as well. I checked the interrupts and found they were assigned irq 10. I don't know what was causing the problem yet ... On 21 Sep 2002 at 15:21, Vladimir I. wrote: Looks like your PCMCIA controller needs special settings to make it work. Check if there are any interrupts for wireless card in /proc/interrupts. /etc/init.d/pcmcia already knows about some weird PCMCIA controllers, so try adding yours - search for the line which mentions Teletronics boards. [EMAIL PROTECTED] wrote: I have set up an two wisp-dists ... one as AP and one As Client ( managed mode ). I double checked all the routes and subnets the AP shows active association of the client. The client shows association to the AP I run tcpdump -i netcs0 and can see the AP is hearing the client but the client is not hearing anything coming from the AP. Thus, no data can go across the link. I am using the teletronics 100mW cards on the 486 SBC. I tried the pigtale in the second slot ( farthest away from LED's ) and then the AP could not connect to anything. both the client and AP shows a radio association. But the client shows no traffic being received at all when I am sending pings to it from the AP. The AP can hear the arp requests and the pings from the client. --- 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] wisp-dist ... Client cannot hear AP
[EMAIL PROTECTED] wrote about Re: [leaf-user] wisp-dist ... Client cannot hear AP: I have determined it is specifically build (2324) that is giving me the problem. with build 2312 the AP mode worked. with build 2324 it did not ( I could not get any cards including a lucent silver card to connect to the AP ) Ah, ok. Some of the test builds were broken. Don't remember which ones exactly right now. I created an .img and burned to flash with the latest build 2341 and it is working as well. It's not latest anymore :-) New public release, build 2348, should be released on the LEAF's homepage very soon. -- 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
Re: [leaf-user] wisp-dist -- How do I do an upgrade using the upgrade option?
[EMAIL PROTECTED] wrote about [leaf-user] wisp-dist -- How do I do an upgrade using the upgrade option?: wisp-dist -- How do I do an upgrade using the upgrade option? I can't seem to locate any documentation on this. http://leaf.sourceforge.net/mod.php?mod=userpagemenu=90801page_id=28 It's in the bottom of the page. I will start working on proper documentation, not sure when I will finish though as I don't have much free time. -- 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] is ntpdate available for leaf
is ntpdate available in a .lrp for leaf dachstein/bering? --- 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] HowTo set Date time
On Sat, 21 Sep 2002 18:53:42 -0400 lbilyeu wrote: How To set Date Time - 3 questions I ) Is there a DateTime HowTo for leaf? Not sure if it has made it into formal documentation yet, but Jeff Newmiller was kind enough to write this document about setting the timezone: http://www.mail-archive.com/leaf-user@lists.sourceforge.net/msg09632.html II ) I've forgotten how to set the date, time timezone under leaf (bering) for the system, user, and the cpu's clock. Where are examples of the correct usage for the commands documented? Where are the caveats for timezones dachstein/bering particulars documented? There have been several postings about clock configuration and the busybox date command to the leaf-user list, including the one linked above. The archives might be your best source of information. The best search interface is currently at http://www.mail-archive.com/leaf-user@lists.sourceforge.net/ The busybox date command should (mostly) work like other versions, so man date might be helpful there. --Brad III) rdate appears to be available, but most servers have depreciated it (are no longer accepting it) where might I find a list of servers that still accept rdate requests? thanks --- 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] is ntpdate available for leaf
On Sat, 21 Sep 2002 19:39:37 -0400 lbilyeu wrote: is ntpdate available in a .lrp for leaf dachstein/bering? ntpclient from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/leaf/devel/helices/ should fit the bill and works under Dachstein and Bering. It includes an init.d startup script for running as a daemon, or ntpclient can be run on the command line or out of cron. --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] [ leaf-Support Requests-606429 ] Problems whit SSH and FTP, using Bering
Support Requests item #606429, was opened at 2002-09-08 13:16 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=213751aid=606429group_id=13751 Category: Release/Branch: Bering Group: None Status: Closed Priority: 5 Submitted By: Tom Harr Jakobsen (harjakob) Assigned to: Matt Schalit (rogermatt) Summary: Problems whit SSH and FTP, using Bering Initial Comment: I have a router whith Bering, and now I try to get access to it throug SSH - but I do experience some problems -I can' t get through the Shorewall with FTP either - I follow the installation guide, and the Users guide, but it don't seem to work anyway - are ther any known issues around this? -- Comment By: Matt Schalit (rogermatt) Date: 2002-09-21 17:26 Message: Logged In: YES user_id=144016 Roger that. Sorry if it took a while, but you can usually get more speedy help via the leaf-user mailing list. Enjoy, matt. -- Comment By: Tom Harr Jakobsen (harjakob) Date: 2002-09-21 03:46 Message: Logged In: YES user_id=607432 thanx - that worked!!! -- Comment By: Matt Schalit (rogermatt) Date: 2002-09-20 12:17 Message: Logged In: YES user_id=144016 1. Check that sshd is running on the LEAF box, using the command ps from the command line. You should see something like 15392 root 4344 R/usr/sbin/sshd If sshd is not running, then type at the # prompt: # /usr/sbin/sshd If it returns to a command prompt with no messages, you're set. If it dies with an error like special user not found, read the docs that jnilo has in his sections for sshd. 2. vi /etc/shorewall/rules and add lines like these above the LAST LINE. # Accept DNS connections from the firewall to the network ACCEPT fw net tcp 53 ACCEPT fw net udp 53 # Accept SSH connections from the local network for administration ACCEPT loc fw tcp 22 # Accept DNS queries from local network to the firewall (dnscache/tinydns) ACCEPT loc fw tcp 53 ACCEPT loc fw udp 53 # Accept Web queries from local network to firewall (weblet) ACCEPT loc fw tcp 80 Either the process wasnt' running, or you were blocked. If you were blocked it would show up in your syslog. It should work now. Let us know so we can close this or get you some more help :) Matthew -- Comment By: Manfred Schuler (mschuler) Date: 2002-09-09 18:25 Message: Logged In: YES user_id=490757 It seems that sshd is not running. sshd is not enabled in inetd.conf and the file /etc/init.d/sshd contains this lines: #Comment out and edit /etc/inetd.conf to run as a stand alone server echo Secure Shell server via inetd: sshd exit 0 So sshd is not started. You have to decide, if you start sshd by inetd or by initscript. When started by inted, connecting to LEAF takes more time, because the session key must be generated by sshd before connecting. Starting by initscript consumes some memory, because sshd is always running, even when you are not logged in. You must either comment the echo and exit line in /etc/init.d/sshd or uncomment the #ssh line in /etc/inetd.conf. Manfred -- Comment By: Tom Harr Jakobsen (harjakob) Date: 2002-09-09 09:41 Message: Logged In: YES user_id=607432 I'm only trying to connect using ssh from a local machine on the network, using Putty...I only recive connection refused -- Comment By: Jacques Nilo (jnilo) Date: 2002-09-09 05:22 Message: Logged In: YES user_id=150195 Aren't you trying to ssh of ftp from the outside network by any chance ? If so you need to adjust Shorewall rules file and /etc/hosts.allow If not more info about the type of error you get would help... -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=213751aid=606429group_id=13751 --- 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] Bewan drivers
Dave, On Sat, 21 Sep 2002 21:21:32 +0100 Dave wrote: Hi, I am upgrading to the latest version of the bewan adsl pci card drivers (http://www.bewan.com/bewan/drivers/bapst-0.3.4.tar.gz) I have setup up the debian/slink virtual uml and compiled the driver, but when I try and load the module I get Since these are kernel modules, I don't think you need to use slink to compile them. Only Dachstein and Bering userspace code needs to be compiled against glibc-2.0.7. Hopefully someone more knowledgeable will correct me if I have mis-spoken. # insmod unicorn_atm Using /lib/modules/unicorn_atm.o insmod: unresolved symbol do_BUG I did have some problems getting the compile to work, but eventually got it compiled against my redhat 2.4.18 kernel (it's the same as a deb 2.4.18 kernel, isn't it?) If you want the modules to work with Jacques' Bering kernel, you will need to follow the patching and compiling process he used to create that kernel. Then compile the modules against that kernel source tree. For RC3, there is some information about the kernel patches and their sequence at http://leaf.sourceforge.net/devel/jnilo/bering/rc3/patches/kernel/ I also posted a script I use to build Bering RC3 compatible kernels at http://fritzfam.com/brad/leaftmp/make_bering_kernel . The script has a fairly major bug; it doesn't apply the freeswan patch. Still, it might help get you started. Applying the freeswan patch *should* be as simple as cd freeswan-1.97; make oldgo KERNELSRC=patched Bering kernel src dir after running the script. Hope that helps. --Brad The last drivers I got, Jacques kindly compiled for me, but I was trying to cut down on his workload this time ;-) Does anyone have any ideas, or is there maybe something that needs to be added to the leaf/uml instructions specifically for compiling drivers for Bering. Do you just need the uml kernel running, root fs, uml utilities, kernel source and driver code. Thanks for any help. Dave --- 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] Bewan drivers
On 2002.09.21_20:44:29_+, Brad Fritz wrote: Since these are kernel modules, I don't think you need to use slink to compile them. Only Dachstein and Bering userspace code needs to be compiled against glibc-2.0.7. Hopefully someone more knowledgeable will correct me if I have mis-spoken. True. According to the LEAF Developer's Guide, anyone can compile kernel everywhere. Userspace programs have to be compiled on a development environment suitable for the target system. I also posted a script I use to build Bering RC3 compatible kernels at http://fritzfam.com/brad/leaftmp/make_bering_kernel . The script has a fairly major bug; it doesn't apply the freeswan patch. Still, it might help get you started. Applying the freeswan patch *should* be as simple as Yes, this is actually a very useful script. The feature should not be hard to fix. I have adapted it for my own use with slightly modifications. Oh yes, there is a wrong URL for freeswan, just omit the 'old' directory, since it is not there any longer. --Brad -- H. D. Lee --- 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
