From: Axel V. <xi...@pa...> - 2004-08-22 09:44:51
|
Hey I'm not new to linux, but I am new to this routing and firewall stuff, so the manual was a bit hard to understand for me :) I have a home LAN, router connected to the internet (getting its ip etc by dhcp) and to 2 subnets in our LAN. I'd like to create 1 subnet (192.168.0.x) through bridging. I tried this, by using the sample br0 and eth files and by adding a ROUTE entry in br0, and both subnets could access the router (192.168.0.1) but they couldn't ping eachother, nor did internet work :( I've also tried using 2 subnets (192.168.1.x and 192.168.0.x), they could ping eachother, but internet still didn't work (now with ROUTE entries in the eth1 and eth2 files, ROUTE="$ROUTE 192.168.0.0/255.255.255.0" for example) What am I doing wrong? Or better yet what should I do to get 1 'virtual' subnet on 192.168.0.x? (using static ip's for the boxes, there are only 6 of them so dhcp isn't necessary) What ROUTE entry should I use, and do I have to put this in the br0 file or in the ethx files? And if I use this bridge, should I use the default 2 nic firewall script with eth0 and br0, or the 3 nic with the three eth's? I'm sorry if this is a simple question, but I already tried a lot of combinations, and it takes a very long time rebooting this thing and testing it, so I can't try EVERY possible combination :) Thanks a lot, Axel |
From: Richard B. <Richard@Belcher.com> - 2004-08-22 13:25:44
|
Hi All, I've got my server configured as I wanted now. Thank you all, for the help you have given in getting me this far. But now I want to create a CD with the configuration combined. I followed the documentation as best as i could, I created a "new" and "ISO" directory on my Hard disc, and put the "etc" compressed file (the config file) in the "new" directory. Below is what I enter, when the Script runs.... I have a problem "Where to mount CD/ISO" option, I have no idea at all, or how to do this! # Default location of old ISO image or CD device. #INPUT=/dev/cdrom INPUT=./dev/cdroms/cdrom0 # Default ISO file to be created ISO=./var/data/ISO/bootcdnew.iso # Were to mount CD/ISO ??????????? MP="/mnt/devil" # Location (directory) of new files to add/replace: NEW=./var/data/new # Temporary location to hold all files from CD/ISO TEMP=./var/data/tmpfiles Hope some of you can help, Best regards Richard |
From: Heiko Z. <he...@zu...> - 2004-08-23 18:31:26
|
Hey, you don't need any bridging in your setup, simple TCP/IP routing will do. -- Regards Heiko Zuerker http://www.devil-linux.org |
From: Axel V. <xi...@pa...> - 2004-08-23 19:13:46
|
On Monday 23 August 2004 20:28, Heiko Zuerker wrote: > Hey, > > you don't need any bridging in your setup, simple TCP/IP routing will do. Hi, Ok, but as I already said in my initial mail, I tried this as well, and the boxes could ping eachother, but internet didn't work, probably because I messed up with the ROUTE variable. I gave eth0 (internet) no ROUTE entry, eth1 ROUTE="$ROUTE 192.168.0.0/255.255.255.0" and eth2 analogue to eth1. I tried some other combinations as well, but nothing worked :(. What should the ROUTE entries look like? Thanks, Axel |
From: Heiko Z. <he...@zu...> - 2004-08-23 19:51:22
|
Howdy, > On Monday 23 August 2004 20:28, Heiko Zuerker wrote: >> Hey, >> >> you don't need any bridging in your setup, simple TCP/IP routing will >> do. > > Hi, > > Ok, but as I already said in my initial mail, I tried this as well, and > the > boxes could ping eachother, but internet didn't work, probably because I > messed up with the ROUTE variable. I gave eth0 (internet) no ROUTE entry, > eth1 ROUTE="$ROUTE 192.168.0.0/255.255.255.0" and eth2 analogue to eth1. I > tried some other combinations as well, but nothing worked :(. What should > the > ROUTE entries look like? Can you send us your 3 ifcfg-files ? Did you setup the firewall script ? You need NAT in order to get the internet working. Use the sample firewall script we provide as a basis. -- Regards Heiko Zuerker http://www.devil-linux.org |
From: Axel V. <ax...@va...> - 2004-08-25 09:37:12
|
Hey I tried setting up devil linux with and without a router (with the ifcfg config files you can find below) and if I don't start the router as a service, boxes in the 192.168.0 and 192.168.1 subnet can ping eachother (but no internet) and if I do start the firewall, they can ping the router but not eachother (and the internet doesn't work either) The firewall is the default 3 nic script, with no modifications. ifcfg-eth0 ------------- DEVICE=eth0 ONBOOT=yes MODULE="ne2k-pci" DHCP=yes IP= NETMASK= BROADCAST="" ifcfg-eth1 ------------- DHCP=no ONBOOT=yes DEVICE=eth1 IP=192.168.0.1 MODULE=8139too NETMASK=255.255.255.0 BROADCAST=192.168.0.255 ROUTE="$ROUTE 192.168.0.0/255.255.255.0" ifcfg-eth2 ------------- DHCP=no ONBOOT=yes DEVICE=eth2 IP=192.168.1.1 MODULE=8139too NETMASK=255.255.255.0 BROADCAST=192.168.1.255 ROUTE="$ROUTE 192.168.1.0/255.255.255.0" On Monday 23 August 2004 21:49, Heiko Zuerker wrote: > Howdy, > > Can you send us your 3 ifcfg-files ? > > Did you setup the firewall script ? You need NAT in order to get the > internet working. Use the sample firewall script we provide as a basis. |
From: Heiko Z. <he...@zu...> - 2004-08-26 00:16:27
|
Axel Vandevenne wrote: >Hey > >I tried setting up devil linux with and without a router (with the ifcfg >config files you can find below) and if I don't start the router as a >service, boxes in the 192.168.0 and 192.168.1 subnet can ping eachother (but >no internet) and if I do start the firewall, they can ping the router but not >eachother (and the internet doesn't work either) > >The firewall is the default 3 nic script, with no modifications. > > Your setup is OK, you don't even need the ROUTE= statements, since the once you specified get assigned automatically. You also need to use the firewall script and modify it for your needs. Most likely it's currently configured so the 2 networks can't talk to eachother. Heiko |
From: Axel V. <xi...@pa...> - 2004-08-27 11:36:55
|
Hi I've modified the firewall 2 nic script, now using INT_DEV1 and INT_DEV2 on every place where there was a INT_DEV in the old script. However I still can't access the internet! I've also tried pinging google (both the url and the ip) with the router, but he sais the network is unreachable or something like that. (I also tried this with the firewall disabled) Is the router supposed to be able to access the net? An 'ifconfig' command tells me that interface should be up and running... Thanks, Axel Firewall script below: # Path to executables IPTABLES=/usr/sbin/iptables MODPROBE=/sbin/modprobe OUT_DEV=eth0 # Internet INT_DEV1=eth1 # Internal/protected network. (192.168.0.x) INT_DEV2=eth2 # Internal/protected network. (192.168.1.x) # Stop forwarding while setting up. echo "0" > /proc/sys/net/ipv4/ip_forward # Uncomment the following line to enable logging: # LOGGING="yes" # Optional Modules: ${MODPROBE} ip_conntrack_ftp ${MODPROBE} ip_nat_ftp ${MODPROBE} ip_conntrack_irc ${MODPROBE} ip_nat_irc #${MODPROBE} ip_owner # Only needed if we're going to log. [ -n "$LOGGING" ] && ${MODPROBE} ipt_LOG # Flush tables & setup Policy ${IPTABLES} -F # flush chains ${IPTABLES} -X # delete user chains ${IPTABLES} -Z # zero counters for t in `cat /proc/net/ip_tables_names` do ${IPTABLES} -F -t $t ${IPTABLES} -X -t $t ${IPTABLES} -Z -t $t done ${IPTABLES} -P INPUT DROP # Policy = DROP ${IPTABLES} -P OUTPUT DROP # Drop all packets that are ${IPTABLES} -P FORWARD DROP # not specifically accepted. # Local interface - do not delete! ${IPTABLES} -A INPUT -i lo -j ACCEPT ${IPTABLES} -A OUTPUT -o lo -j ACCEPT # We accept anything from the inside. ${IPTABLES} -A INPUT -i ${INT_DEV1} -j ACCEPT ${IPTABLES} -A OUTPUT -o ${INT_DEV1} -j ACCEPT ${IPTABLES} -A INPUT -i ${INT_DEV2} -j ACCEPT ${IPTABLES} -A OUTPUT -o ${INT_DEV2} -j ACCEPT # Allow our firewall to connect. ${IPTABLES} -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT ${IPTABLES} -A OUTPUT -m state --state NEW,ESTABLISHED,RELATED -j ACCEPT # Allow Ping and friends. ${IPTABLES} -A INPUT -p icmp -j ACCEPT ${IPTABLES} -A OUTPUT -p icmp -j ACCEPT # Fast reject for Ident to eliminate email delays. ${IPTABLES} -A INPUT -p TCP --dport 113 -i ${OUT_DEV} -j REJECT --reject-with tcp-reset # Masquerading (aka NAT, PAT, ...) ${IPTABLES} -t nat -A POSTROUTING -o ${OUT_DEV} -j MASQUERADE # Uncomment/modify the next 4 lines to forward a service to an internal IP. # SERVER_IP=192.168.1.1 # Internal IP of server. # PORT=22 # 22 = SSH. Change to 80 for web server, etc. # ${IPTABLES} -A PREROUTING -i ${OUT_DEV} -t nat -p TCP --dport $PORT -j DNAT --to ${SERVER_IP}:${PORT} # ${IPTABLES} -A FORWARD -p TCP -d ${SERVER_IP} --dport $PORT -i ${OUT_DEV} -o ${INT_DEV} -j ACCEPT # Uncomment/modify the next 2 lines to open a port on the internet to Devil Linux. # PORT=25 # 25 = SMTP. Change to the port you wish to open. # ${IPTABLES} -A INPUT -p tcp --dport $PORT -i ${OUT_DEV} -j ACCEPT # Block invalid connections from the internet. [ -n "$LOGGING" ] && \ ${IPTABLES} -A FORWARD -m state --state NEW,INVALID -i ${OUT_DEV} -j LOG --log-prefix "FORWARD INVALID: " ${IPTABLES} -A FORWARD -m state --state NEW,INVALID -i ${OUT_DEV} -j DROP # Allow connections to the internet from the internal network. ${IPTABLES} -A FORWARD -m state --state ESTABLISHED,RELATED -j ACCEPT ${IPTABLES} -A FORWARD -m state --state NEW -i ${INT_DEV1} -j ACCEPT ${IPTABLES} -A FORWARD -m state --state NEW -i ${INT_DEV2} -j ACCEPT # Prevent NetBIOS and Samba from leaking. ${IPTABLES} -t nat -A PREROUTING -p TCP --dport 135 -j DROP ${IPTABLES} -t nat -A PREROUTING -p UDP --dport 135 -j DROP ${IPTABLES} -t nat -A PREROUTING -p TCP --dport 137:139 -j DROP ${IPTABLES} -t nat -A PREROUTING -p UDP --dport 137:139 -j DROP ${IPTABLES} -t nat -A PREROUTING -p TCP --dport 445 -j DROP ${IPTABLES} -t nat -A PREROUTING -p UDP --dport 445 -j DROP # make interactive sesions a bit more interactive under load ${IPTABLES} -A PREROUTING -t mangle -p TCP --sport ssh -j TOS --set-tos Minimize-Delay ${IPTABLES} -A PREROUTING -t mangle -p TCP --sport ftp -j TOS --set-tos Minimize-Delay ${IPTABLES} -A PREROUTING -t mangle -p TCP --sport ftp-data -j TOS --set-tos Maximize-Throughput # Log invalid packets from DROP policy: if [ -n "$LOGGING" ] ; then ${IPTABLES} -A INPUT -d 255.255.255.255 -j DROP # do not log broadcasts ${IPTABLES} -A INPUT -d 224.0.0.0/8 -j DROP # do not log Microsoft multicasts ${IPTABLES} -A INPUT -m limit --limit 3/minute --limit-burst 3 -j LOG --log-prefix "INPUT policy: " ${IPTABLES} -A OUTPUT -m limit --limit 3/minute --limit-burst 3 -j LOG --log-prefix "OUTPUT policy: " ${IPTABLES} -A FORWARD -m limit --limit 3/minute --limit-burst 3 -j LOG --log-prefix "FORWARD policy: " fi # enable dynamic IP address following echo 7 > /proc/sys/net/ipv4/ip_dynaddr # stop some smurf attacks. echo 1 > /proc/sys/net/ipv4/icmp_echo_ignore_broadcasts # Don't accept source routed packets. echo "0" > /proc/sys/net/ipv4/conf/all/accept_source_route # Syncookies echo "1" > /proc/sys/net/ipv4/tcp_syncookies # Stop IP spoofing, for interface in /proc/sys/net/ipv4/conf/*/rp_filter; do echo "1" > $interface done # Stop ICMP redirect for interface in /proc/sys/net/ipv4/conf/*/accept_redirects; do echo "0" > ${interface} done # Enable bad error message protection. echo "1" > /proc/sys/net/ipv4/icmp_ignore_bogus_error_responses # Enabling IP forwarding. echo "1" > /proc/sys/net/ipv4/ip_forward #-------------------------------------------------------------------------------------------- On Thursday 26 August 2004 02:14, Heiko Zuerker wrote: > Axel Vandevenne wrote: > >Hey > > > >I tried setting up devil linux with and without a router (with the ifcfg > >config files you can find below) and if I don't start the router as a > >service, boxes in the 192.168.0 and 192.168.1 subnet can ping eachother > > (but no internet) and if I do start the firewall, they can ping the > > router but not eachother (and the internet doesn't work either) > > > >The firewall is the default 3 nic script, with no modifications. > > Your setup is OK, you don't even need the ROUTE= statements, since the > once you specified get assigned automatically. > You also need to use the firewall script and modify it for your needs. > Most likely it's currently configured so the 2 networks can't talk to > eachother. > > Heiko > > > ------------------------------------------------------- > SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media > 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 > Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. > http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 > _______________________________________________ > Devil-linux-discuss mailing list > Dev...@li... > https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss |
From: Heiko Z. <he...@zu...> - 2004-08-27 13:26:23
|
Axel Vandevenne wrote: >Hi > >I've modified the firewall 2 nic script, now using INT_DEV1 and INT_DEV2 on >every place where there was a INT_DEV in the old script. However I still >can't access the internet! >I've also tried pinging google (both the url and the ip) with the router, but >he sais the network is unreachable or something like that. (I also tried this >with the firewall disabled) Is the router supposed to be able to access the >net? An 'ifconfig' command tells me that interface should be up and >running... > > The Router should be able to access the Internet, but not the clients behind it. In order to get the clients working, you'll need NAT (or IP Masquerading), because the client use a private address space. Our firewall script 'should' take care of the NAT. Turn on the logging LOGGING="yes" and check if you see any blocked packets on console 10. Heiko |
From: Axel V. <xi...@pa...> - 2004-08-30 12:55:21
|
Hey With logging on nothing seems to happen on console 10 if you want to access the internet from another box. There are a lot of boot messages there, and the last 3 lines after booting are: <date and pc name>: kernel: eth2: no IPv6 routers present <date and pc name>: kernel: eth1: no IPv6 routers present <date and pc name>: kernel: eth0: no IPv6 routers present Does this mean anything? Is it an error or just a notice? I only need IPv4, and never said anything about IPv6... Then 10 minutes after booting (and trying to acces the internet with boxes in the lan) this line appeared: <date and pc name>: syslog-ng[523]: STATS: dropped 0 I assume this means that the firewall is configured correctly and that he didn't drop any of the packages? As I already said, the router itself is unable to ping google, maybe that's the problem, eth0 somehow doesn't work? On our current Freesco router everything works (but the thing crashes a lot so that's why I want to use Devil Linux) Axel > > The Router should be able to access the Internet, but not the clients > behind it. > In order to get the clients working, you'll need NAT (or IP > Masquerading), because the client use a private address space. Our > firewall script 'should' take care of the NAT. > > Turn on the logging > > LOGGING="yes" > > and check if you see any blocked packets on console 10. > > Heiko > |
From: Heiko Z. <he...@zu...> - 2004-08-31 00:46:37
|
Axel Vandevenne wrote: >Hey > >With logging on nothing seems to happen on console 10 if you want to access >the internet from another box. There are a lot of boot messages there, and >the last 3 lines after booting are: > ><date and pc name>: kernel: eth2: no IPv6 routers present ><date and pc name>: kernel: eth1: no IPv6 routers present ><date and pc name>: kernel: eth0: no IPv6 routers present > >Does this mean anything? Is it an error or just a notice? I only need IPv4, >and never said anything about IPv6... > > You can safely ignore those messages >Then 10 minutes after booting (and trying to acces the internet with boxes in >the lan) this line appeared: > ><date and pc name>: syslog-ng[523]: STATS: dropped 0 > > This is just the syslog daemon which tells you, that it is still running. >I assume this means that the firewall is configured correctly and that he >didn't drop any of the packages? > > No this has nothing todo with the firewall, just the syslog daemon. >As I already said, the router itself is unable to ping google, maybe that's >the problem, eth0 somehow doesn't work? > > Can you ping the IP address of google? ping 216.239.41.99 ping 216.239.41.104 You need first to concentrate on getting the internet connection running, then the routing to the subnets. >On our current Freesco router everything works (but the thing crashes a lot so >that's why I want to use Devil Linux) > > We should get that baby running... Let's do some more analyzing: Can you send us the output of: ifconfig -a route -n iptables -L -v -n cu Heiko |
From: Axel V. <xi...@pa...> - 2004-08-31 11:47:45
|
Hey I hope you can find my mistake in the information below :) Eth0 seems to be able to connect to my ISP since he received an IP through dhcp, but after that he's too lazy to make any further contact with the internet ;) Axel root@p133:~ # ping 216.239.41.99 connect: Network is unreachable root@p133:~ # ifconfig -a eth0 Link encap:Ethernet HWaddr 00:20:18:B9:2E:B5 inet addr:213.118.77.223 Bcast:213.118.77.255 Mask:255.255.255.0 inet6 addr: fe80::220:18ff:feb9:2eb5/64 Scope:Link UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1427 errors:0 dropped:0 overruns:0 frame:0 TX packets:7 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:90966 (88.8 Kb) TX bytes:1028 (1.0 Kb) Interrupt:11 Base address:0x6200 eth1 Link encap:Ethernet HWaddr 00:02:44:2D:80:C0 inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0 inet6 addr: fe80::202:44ff:fe2d:80c0/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1884 errors:0 dropped:0 overruns:0 frame:0 TX packets:925 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:125931 (122.9 Kb) TX bytes:88249 (86.1 Kb) Interrupt:15 Base address:0x6100 eth2 Link encap:Ethernet HWaddr 00:40:F4:42:E5:A5 inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::240:f4ff:fe42:e5a5/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:5 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:0 (0.0 b) TX bytes:378 (378.0 b) Interrupt:10 Base address:0x6400 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:4 errors:0 dropped:0 overruns:0 frame:0 TX packets:4 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:336 (336.0 b) TX bytes:336 (336.0 b) sit0 Link encap:IPv6-in-IPv4 NOARP MTU:1480 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) root@p133:~ # route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 213.118.77.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth2 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth2 192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1 192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1 root@p133:~ # iptables -L -v -n Chain INPUT (policy DROP 7 packets, 332 bytes) pkts bytes target prot opt in out source destination 4 336 ACCEPT all -- lo * 0.0.0.0/0 0.0.0.0/0 210 16622 ACCEPT all -- eth1 * 0.0.0.0/0 0.0.0.0/0 0 0 ACCEPT all -- eth2 * 0.0.0.0/0 0.0.0.0/0 0 0 ACCEPT all -- * * 0.0.0.0/0 0.0.0.0/0 state RELATED,ESTA BLISHED 0 0 ACCEPT icmp -- * * 0.0.0.0/0 0.0.0.0/0 0 0 REJECT tcp -- eth0 * 0.0.0.0/0 0.0.0.0/0 tcp dpt:113 reject-with tcp-reset Chain FORWARD (policy DROP 0 packets, 0 bytes) pkts bytes target prot opt in out source destination 0 0 DROP all -- eth0 * 0.0.0.0/0 0.0.0.0/0 state INVALID,NEW 0 0 ACCEPT all -- * * 0.0.0.0/0 0.0.0.0/0 state RELATED,ESTABLISHED 0 0 ACCEPT all -- eth1 * 0.0.0.0/0 0.0.0.0/0 state NEW 0 0 ACCEPT all -- eth2 * 0.0.0.0/0 0.0.0.0/0 state NEW Chain OUTPUT (policy DROP 0 packets, 0 bytes) pkts bytes target prot opt in out source destination 4 336 ACCEPT all -- * lo 0.0.0.0/0 0.0.0.0/0 1053 90233 ACCEPT all -- * eth1 0.0.0.0/0 0.0.0.0/0 0 0 ACCEPT all -- * eth2 0.0.0.0/0 0.0.0.0/0 0 0 ACCEPT all -- * * 0.0.0.0/0 0.0.0.0/0 state NEW,RELATED,ESTABLISHED 0 0 ACCEPT icmp -- * * 0.0.0.0/0 0.0.0.0/0 On Tuesday 31 August 2004 02:43, Heiko Zuerker wrote: > Axel Vandevenne wrote: > >Hey > > > >With logging on nothing seems to happen on console 10 if you want to > > access the internet from another box. There are a lot of boot messages > > there, and the last 3 lines after booting are: > > > ><date and pc name>: kernel: eth2: no IPv6 routers present > ><date and pc name>: kernel: eth1: no IPv6 routers present > ><date and pc name>: kernel: eth0: no IPv6 routers present > > > >Does this mean anything? Is it an error or just a notice? I only need > > IPv4, and never said anything about IPv6... > > You can safely ignore those messages > > >Then 10 minutes after booting (and trying to acces the internet with boxes > > in the lan) this line appeared: > > > ><date and pc name>: syslog-ng[523]: STATS: dropped 0 > > This is just the syslog daemon which tells you, that it is still running. > > >I assume this means that the firewall is configured correctly and that he > >didn't drop any of the packages? > > No this has nothing todo with the firewall, just the syslog daemon. > > >As I already said, the router itself is unable to ping google, maybe > > that's the problem, eth0 somehow doesn't work? > > Can you ping the IP address of google? > ping 216.239.41.99 > ping 216.239.41.104 > > You need first to concentrate on getting the internet connection > running, then the routing to the subnets. > > >On our current Freesco router everything works (but the thing crashes a > > lot so that's why I want to use Devil Linux) > > We should get that baby running... > > Let's do some more analyzing: > Can you send us the output of: > ifconfig -a > route -n > iptables -L -v -n > > cu > Heiko > > > ------------------------------------------------------- > This SF.Net email is sponsored by BEA Weblogic Workshop > FREE Java Enterprise J2EE developer tools! > Get your free copy of BEA WebLogic Workshop 8.1 today. > http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click > _______________________________________________ > Devil-linux-discuss mailing list > Dev...@li... > https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss |