|
From: Renato D. <ren...@uo...> - 2001-09-10 14:16:47
|
Hi,
My system is almost there... The cards are configured, routing is =
enable, and I can ping local and web hosts.
But how my local machines must be configured to web-access ?
DL gateway is configured and, in the stations, I have configure the =
default gateway [the local DL address] and DNS.
What is wrong here ?
PS: As you could see I don't have any experience with Linux. So if =
you want to make a guide to DL install using the point of view of =
someone coming from "windows" I can do something...
Thank's
Renato Denardo =20
ICQ/uin 4631042 M.=B7.B.=B7.
eMail: ren...@uo...
|
|
From: scty L. <sct...@ya...> - 2004-08-31 19:29:56
|
Hello all, When you have routing selected in the services menu, what application does it start? Thanks all __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com |
|
From: Peter F. <pe...@em...> - 2004-09-01 11:04:22
|
I will reiterate Heiko's opinion... it would be nice to know your name. On Tue, 2004-08-31 at 15:14, scty Library wrote: > Hello all, > > When you have routing selected in the services menu, > what application does it start? NONE. If you are looking for something like Zebra...you have to do it yourself. Selecting "Routing" simply sets the flag that allows linux to behave as a router and pass packets from one interface to another. Peter |
|
From: scty L. <sct...@ya...> - 2004-09-01 14:01:49
|
Peter, I am starting to understand a little bit. From what I got so far routing sets the variable in the kernel to except routing tables and the firewall.rules set up the tables. Am I close? Dominic --- Peter Frischknecht <pe...@em...> wrote: > I will reiterate Heiko's opinion... > it would be nice to know your name. > > On Tue, 2004-08-31 at 15:14, scty Library wrote: > > Hello all, > > > > When you have routing selected in the services > menu, > > what application does it start? > NONE. > If you are looking for something like Zebra...you > have to do it > yourself. > > Selecting "Routing" simply sets the flag that allows > linux to behave as > a router and pass packets from one interface to > another. > > Peter > > > ------------------------------------------------------- > 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 > __________________________________ Do you Yahoo!? Yahoo! Mail is new and improved - Check it out! http://promotions.yahoo.com/new_mail |
|
From: Bruce S. <bw...@ar...> - 2004-09-01 14:46:42
|
> I am starting to understand a little bit. From what I > got so far routing sets the variable in the kernel to > except routing tables and the firewall.rules set up > the tables. > Am I close? Pretty much. Starting routing enables the kernel to forward packets from one network interface to another. Starting firewall runs the firewall scripts which enables the iptables rules, and also starts routing (in the default scripts anyway). So, technically it's not necessary to start routing, if routing is enabled in the firewall script. But in practice, I believe most people turn on both options in a firewall machine. - BS > > > When you have routing selected in the services > > menu, > > > what application does it start? > > NONE. > > If you are looking for something like Zebra...you > > have to do it > > yourself. > > > > Selecting "Routing" simply sets the flag that allows > > linux to behave as > > a router and pass packets from one interface to > > another. > > > > Peter |
|
From: <alo...@ma...> - 2004-11-30 20:11:49
|
I have a problem with the routing. At home i have 3 pcs: 1.Devil-Linux 1.2.1 -->Router only 2.Linux suse 9.2; slax 4.2; knoppix 3.3 3.Windows XP Proffesional; 2000 Advanced Server Windows get its ip from the DHCP server from the router and have internet access. But Linux cant access it. one week ago i was routing my internet traffic with win XP with Internet Conection Sharing and it worked on the both windows and linux no matter wich version or distro it is. Any ideas, suggestions? ----------------------------- =C2=F1=E8=F7=EA=EE =E5 =EF=EE-=E1=FA=F0=E7=EE =E8 =F1=E8=E3=F3=F0=ED=EE =F1 =C1=D2=CA ADSL! www.telecom.bg |
|
From: Brian H. <nautix@u.washington.edu> - 2004-11-30 21:20:58
|
Let's start with the basics. Is the suse/slax/knoppix box getting an IP address from DHCP? (Run=20 "ifconfig eth0".) If so, can it ping the DL box? (Run "ping xx.xx.xx.xx", substituting the= =20 LAN address of the router.) If so, does it have a default route? (Run "netstat -rn" and look for a=20 line that begins "0.0.0.0".) Get back on that info and we'll go from there. --b Today, ????? ?????? was quoted as saying: > I have a problem with the routing. > At home i have 3 pcs: > 1.Devil-Linux 1.2.1 -->Router only > 2.Linux suse 9.2; slax 4.2; knoppix 3.3 > 3.Windows XP Proffesional; 2000 Advanced Server > > Windows get its ip from the DHCP server from the router > and have internet access. > But Linux cant access it. > > one week ago i was routing my internet traffic with win XP > with Internet Conection Sharing and it worked > on the both windows and linux no matter > wich version or distro it is. > > Any ideas, suggestions? > > > > ----------------------------- > > =C2=F1=E8=F7=EA=EE =E5 =EF=EE-=E1=FA=F0=E7=EE =E8 =F1=E8=E3=F3=F0=ED=EE = =F1 > =C1=D2=CA ADSL! www.telecom.bg > > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://productguide.itmanagersjournal.com/ > _______________________________________________ > Devil-linux-discuss mailing list > Dev...@li... > https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss > -- Brian Haney, Software Engineer & UNIX Systems Administrator University of Washington, Dept of Biostatistics "Perseverance is the hard work you do after you get tired of doing the hard work you already did." =09=09=09=09=09-- Newt Gingrich |
|
From: Lyubomir L. <ly...@ma...> - 2004-12-16 20:07:33
|
I cant browse internet trough linux:Suse 9.2, Slax 4.2, Knoppix 3.3
but i can trough Windows 2000Advanced Server and XP Professional
Trough linux in shell i can ping any ip address, but cant browse internet
pages
and cant connect even to my msn and icq accounts.
this is from Slax 4.2:
Slax 4.2
root@slax:~# ifconfig
eth0 Link encap:Ethernet HWaddr 00:01:02:0E:9C:CA
inet addr:192.168.0.18 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3 errors:0 dropped:0 overruns:0 frame:0
TX packets:3 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:746 (746.0 b) TX bytes:1240 (1.2 Kb)
Interrupt:11 Base address:0xa000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 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@slax:~#
root@slax:~# ping 192.168.0.1
PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=0.417 ms
64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=0.404 ms
64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=0.378 ms
64 bytes from 192.168.0.1: icmp_seq=4 ttl=64 time=0.348 ms
--- 192.168.0.1 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3013ms
rtt min/avg/max/mdev = 0.348/0.386/0.417/0.035 ms
root@slax:~#
root@slax:~# netstat -rn
Kernel IP routing table
Destination Gateway Genmask Flags MSS Windowirtt Iface
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 192.168.0.1 0.0.0.0 UG 0 0 0 eth0
root@slax:~#
/etc/resolv.conf
nameserver 192.168.0.1
nameserver 212.116.158.130
nameserver 212.116.158.133
search Evil-Devil
And for what is this file?:
/etc/resolv.conf.sv
nameserver 192.168.0.1
search mshome.net
And this is from my router Devil-Linux 1.2.1:
Devil-linux
root@Devil:~ # netstat -rn
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt
Iface
255.255.255.255 0.0.0.0 255.255.255.255 UH 0 0 0
eth1
83.148.80.128 0.0.0.0 255.255.255.128 U 0 0 0
eth0
192.168.0.0 0.0.0.0 255.255.0.0 U 0 0 0
eth1
0.0.0.0 83.148.80.193 0.0.0.0 UG 0 0 0
eth0
root@Devil:~ #
root@Devil:~ # iptables -nvL
Chain INPUT (policy DROP 458 packets, 33279 bytes)
pkts bytes target prot opt in out source
destination
8 971 ACCEPT all -- lo * 0.0.0.0/0
0.0.0.0/0
1574 100K ACCEPT all -- eth1 * 0.0.0.0/0
0.0.0.0/0
1393 1695K ACCEPT all -- * * 0.0.0.0/0
0.0.0.0/0 state RELATED,ESTABLISHED
5 164 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
155K 127M ACCEPT all -- * * 0.0.0.0/0
0.0.0.0/0 state RELATED,ESTABLISHED
1862 94745 ACCEPT all -- eth1 * 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
8 971 ACCEPT all -- * lo 0.0.0.0/0
0.0.0.0/0
1223 152K ACCEPT all -- * eth1 0.0.0.0/0
0.0.0.0/0
1208 70408 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
root@Devil:~ #
iptables -nvL -t nat
Chain PREROUTING (policy ACCEPT 2233 packets, 127K bytes)
pkts bytes target prot opt in out source
destination
0 0 DROP tcp -- * * 0.0.0.0/0
0.0.0.0/0 tcp dpt:135
0 0 DROP udp -- * * 0.0.0.0/0
0.0.0.0/0 udp dpt:135
0 0 DROP tcp -- * * 0.0.0.0/0
0.0.0.0/0 tcp dpts:137:139
5694 722K DROP udp -- * * 0.0.0.0/0
0.0.0.0/0 udp dpts:137:139
0 0 DROP tcp -- * * 0.0.0.0/0
0.0.0.0/0 tcp dpt:445
0 0 DROP udp -- * * 0.0.0.0/0
0.0.0.0/0 udp dpt:445
Chain POSTROUTING (policy ACCEPT 17 packets, 1189 bytes)
pkts bytes target prot opt in out source
destination
1609 81839 MASQUERADE all -- * eth0 0.0.0.0/0
0.0.0.0/0
Chain OUTPUT (policy ACCEPT 67 packets, 4459 bytes)
pkts bytes target prot opt in out source
destination
root@Devil:~ #
This is from SLAX 4.2:
root@slax:~# dig @212.116.158.130 http://www.yahoo.com
; <<>> DiG 9.3.0 <<>> @212.116.158.130 http://www.yahoo.com
;; global options: printcmd
;; connection timed out; no servers could be reached
root@slax:~#
root@slax:~# iptables -nvL
Chain INPUT (policy ACCEPT 325 packets, 37997 bytes)
pkts bytes target prot opt in out sourcedestination
Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out sourcedestination
Chain OUTPUT (policy ACCEPT 503 packets, 38066 bytes)
pkts bytes target prot opt in out sourcedestination
69 4284 ACCEPT udp -- * * 0.0.0.0/00.0.0.0/0
udp dpt:53
root@slax:~#
|
|
From: Heiko Z. <he...@zu...> - 2004-12-16 20:45:50
|
Hey, isn't this an old post??? > > > This is from SLAX 4.2: > > > root@slax:~# dig @212.116.158.130 http://www.yahoo.com This won't work, the http:// is not part of the host name. The correct command is: dig @212.116.158.130 www.yahoo.com Run this command first on the router, to make sure he can resolve the address. -- Regards Heiko Zuerker http://www.devil-linux.org |
|
From: Russell P. <rus...@ai...> - 2005-07-11 15:20:00
|
Hi,
I'm just switching networks and setting up my new Devil Linux firewall =
box, but my brain is having an off day and can't sort the routing out.
I've got a network, 85.133.20.0/25
I've got a router - 85.133.20.1
I have 3 NICS in the Devil Linux box -
eth0 85.133.20.2 (to the 'net)
eth1 85.133.20.3 ('dmz')
eth2 10.0.0.1 (natted internal net)
What should I have in my ifcfg-ethx files so that everything works "in =
the normal way" (eg. natted stuff can access the 'net, the dmz can =
access the net and have the net access it).
I've got $ROUTE DEFAULT/0:85.133.20.1 at the end of my ifcfg-eth0, and =
this seems to do the trick for the Devil box itself and the natted =
internal network. However, the DMZ can't access the net?
I thought maybe I'd made a silly iptables error, but I flushed (-F) and =
set everything to accept for testing (-P OUTPUT ACCEPT, etc).
I'm missing something really basic, I just know it O_o
Any help / hints much appreciated!
|
|
From: Gordon R. <ru...@cl...> - 2005-07-11 15:39:11
|
what does netstat -rn tell you? you will have the same network on two interfaces (eth0, facing the router, and eth1, facing the dmz). To which is the assigned network (85.133.20.0) attached in the routing tables on the DL box? do you need to further netmask it to split it between the two interfaces? gordon |
|
From: Ross P. <Ros...@ca...> - 2006-07-27 14:10:51
|
Hopefully=20someone=20can=20help=20me=20with=20this=20query...... =20 I've=20got=20an=20old=20pc=20running=20devil=20linux.=20It=20has=202=20nic= s,=20each=20connected=20to a=20different=20subnet. =20 eth0=20-=20192.128.10.12 eth1=20-=20192.128.11.1 =20 I=20have=20also=20added=20a=20static=20route=20- 192.168.0.0/255.255.255.0:192.128.11.6 =20 Now,=20the=20linux=20server=20can=20reach=20everything,=20no=20problem.=20= Can=20ping 192.128.10.xx,=20192.128.11.xx=20and=20192.168.0.xx=20without=20any=20trou= ble. =20 From=20my=20PC=20though,=20on=20the=20192.128.10=20subnet,=20I=20can=20pin= g=20192.128.11.xx fine=20but=20not=20192.168.0.xx. =20 I=20have=20set=20a=20route=20on=20the=20lan=20firewall=20to=20route=20192.= 128.11=20and=20192.168.0 traffic=20to=20the=20devil=20linux=20box,=20which=20it=20clearly=20does=20= before=20I=20can=20reach the=20192.128.11=20subnet.=20Why=20would=20I=20be=20unable=20to=20get=20to= =20the=20192.168.0 subnet? =20 Any=20clues? =20 Thanks =20 Ross=20Petrie =20 IT=20Administrator CAN=20Offshore=20Ltd Hareness=20Road Altens Aberdeen AB12=203LE =20 ________________________________________________________________________ IMPORTANT=20=96=20our=20=93canoffshore.ltd.uk=94=20address=20is=20schedule= d=20for=20cancellation.=20=20Address=20books=20should=20be=20changed=20to=20= use=20our=20=93cangroup.net=94=20address.=20=20Thank=20you=20for=20your=20= cooperation. This=20transmission=20contains=20information=20which=20may=20be=20confiden= tial=20and=20that=20may=20also=20be=20privileged.=20=20It=20is=20intended=20= for=20the=20named=20addressee=20only.=20=20Unless=20you=20are=20the=20name= d=20addressee,=20or=20authorised=20to=20receive=20it=20on=20behalf=20of=20= the=20addressee,=20you=20may=20not=20copy=20or=20use=20it,=20or=20disclose= =20it=20to=20anyone=20else.=20=20If=20you=20have=20received=20this=20trans= mission=20in=20error=20please=20contact=20the=20sender.=20=20Thank=20you=20= for=20your=20cooperation. This=20email=20has=20been=20scanned=20for=20all=20viruses=20by=20the=20Mes= sageLabs=20SkyScan=20service.=20=20CAN=20also=20uses=20the=20MessageLabs=20= spam=20filtering=20service.=20=20This=20should=20not=20affect=20routine=20= messages=20but=20in=20rare=20cases=20a=20bona-fide=20message=20could=20be=20= blocked.=20=20Please=20contact=20CAN=20if=20you=20experience=20any=20diffi= culties. ________________________________________________________________________ |
|
From: Dick M. <di...@li...> - 2006-07-27 21:26:12
|
Ross Petrie wrote: > Hopefully someone can help me with this query...... > > I've got an old pc running devil linux. It has 2 nics, each connected to > a different subnet. > > eth0 - 192.128.10.12 > eth1 - 192.128.11.1 > > I have also added a static route - 192.168.0.0/255.255.255.0:192.128.11.6 > > Now, the linux server can reach everything, no problem. Can ping > 192.128.10.xx, 192.128.11.xx and 192.168.0.xx without any trouble. > > From my PC though, on the 192.128.10 subnet, I can ping 192.128.11.xx > fine but not 192.168.0.xx. > > I have set a route on the lan firewall to route 192.128.11 and 192.168.0 > traffic to the devil linux box, which it clearly does before I can reach > the 192.128.11 subnet. Why would I be unable to get to the 192.168.0 subnet? I don't know - what's supposed to respond to the ping? Does it know how to get back to the PC. Can you ping the PC from whatever is on 192.168... Dick |
|
From: Heiko Z. <hz...@pr...> - 2001-09-10 14:30:58
|
Renato Denardo wrote: > My system is almost there... The cards are configured, routing is > enable, and I can ping local and web hosts. > > But how my local machines must be configured to web-access ? You only have to set the Default Gateway & DNS Server on the Clients as you did it. > DL gateway is configured and, in the stations, I have configure the > default gateway [the local DL address] and DNS. > > What is wrong here ? You need Masquerading or SNAT. Look in this posting http://www.devil-linux.org/cgi-bin/ikonboard/topic.cgi?forum=1&topic=7 There you can find some links describing this stuff. I hope that I'm able in the near future (weeks, months?...), to upgrade my System to a 2.4 Kernel, then I can publish some sample script. > PS: As you could see I don't have any experience with Linux. So if > you want to make a guide to DL install using the point of view of > someone coming from "windows" I can do something... That would be very good! Just write down what problems you had and how you solved them. This could be the beginning of the DL FAQ. -- cu Heiko http://www.devil-linux.org |