From: Lyubomir L. <ly...@ma...> - 2004-12-05 09:24:37
|
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:~ # |
From: Russell P. <rus...@ai...> - 2005-07-11 16:02:26
|
netstat -rn shows me: 85.133.20.0 0.0.0 255.255.255.128 eth0 85.133.20.0 0.0.0 255.255.255.128 eth1 10.0.0.1 0.0.0.0 255.255.255.0 eth2 0.0.0.0 85.133.20.1 0.0.0.0 eth0 Which is pretty wrong, as indeed - how does anything know to come back = through eth1? I tried subnetting it out (255.255.255.192) but couldn't make that happy = either. I also tried some static routes (in case the router wasn't happy with me = subnetting), but again no joy... -----Original Message----- From: dev...@li... on behalf of = Gordon Russell Sent: Mon 7/11/2005 4:36 PM To: dev...@li... Cc:=09 Subject: Re: [Devil-Linux-discuss] Routing what does netstat -rn tell you? you will have the same network on two interfaces (eth0, facing the=20 router, and eth1, facing the dmz). To which is the assigned network=20 (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 ------------------------------------------------------- This SF.Net email is sponsored by the 'Do More With Dual!' webinar = happening July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual core and dual graphics technology at this free one hour event hosted by = HP, AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar _______________________________________________ Devil-linux-discuss mailing list Dev...@li... https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss |
From: Russell P. <rus...@ai...> - 2005-07-11 16:08:59
|
Ooops. Bad typing ;) 85.133.20.0 0.0.0.0 255.255.255.128 eth0 85.133.20.0 0.0.0.0 255.255.255.128 eth1=20 -----Original Message----- From: Russell Packer on behalf of Russell Packer Sent: Mon 7/11/2005 5:02 PM To: dev...@li... Cc:=09 Subject: RE: [Devil-Linux-discuss] Routing netstat -rn shows me: 85.133.20.0 0.0.0 255.255.255.128 eth0 85.133.20.0 0.0.0 255.255.255.128 eth1 10.0.0.1 0.0.0.0 255.255.255.0 eth2 0.0.0.0 85.133.20.1 0.0.0.0 eth0 Which is pretty wrong, as indeed - how does anything know to come back = through eth1? I tried subnetting it out (255.255.255.192) but couldn't make that happy = either. I also tried some static routes (in case the router wasn't happy with me = subnetting), but again no joy... -----Original Message----- From: dev...@li... on behalf of = Gordon Russell Sent: Mon 7/11/2005 4:36 PM To: dev...@li... Cc:=09 Subject: Re: [Devil-Linux-discuss] Routing what does netstat -rn tell you? you will have the same network on two interfaces (eth0, facing the=20 router, and eth1, facing the dmz). To which is the assigned network=20 (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 ------------------------------------------------------- This SF.Net email is sponsored by the 'Do More With Dual!' webinar = happening July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual core and dual graphics technology at this free one hour event hosted by = HP, AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar _______________________________________________ Devil-linux-discuss mailing list Dev...@li... https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss |
From: Moray M. <mmc...@ox...> - 2005-07-11 16:37:07
|
We deal with this (tho glad to hear of a better way, because I thought = it very odd when setting it up!) by subnetting like this for eth0: 85.133.20.0/30 and then running virtual interfaces on eth1 (assuming class C for a = minute) as 85.133.20.4/30 85.133.20.8/29 85.133.20.16/28 85.133.20.32/27 85.133.20.64/26 85.133.20.128/25 Your DMZ address space is then 85.133.20.5-85.133.20.254, excepting = 85.133.20.7,85.133.20.8, 85.133.20.15, = 85.133.20.31,85.133.20.32,85.133.20.63,85.133.20.64,85.133.20.127. IPtables interface specifier is not sensitive to the virtual interfaces, = which means $IPTABLES -i eth0 -o eth1 still gets everything coming from = outside destined to the DMZ. If you don't care about using all the = address space, just using the last line would be easier. Then you tell the router to use static routing for each DMZ group you = set up, routing each through your eth0 IP address. Yours, Moray ------------------------------------------- Moray McConnachie IT Manager - mmc...@ox... Oxford Analytica - http://www.oxan.com -----Original Message----- From: dev...@li... [mailto:dev...@li...]On Behalf Of Russell Packer Sent: 11 July 2005 17:02 To: dev...@li... Subject: RE: [Devil-Linux-discuss] Routing netstat -rn shows me: 85.133.20.0 0.0.0 255.255.255.128 eth0 85.133.20.0 0.0.0 255.255.255.128 eth1 10.0.0.1 0.0.0.0 255.255.255.0 eth2 0.0.0.0 85.133.20.1 0.0.0.0 eth0 Which is pretty wrong, as indeed - how does anything know to come back = through eth1? I tried subnetting it out (255.255.255.192) but couldn't make that happy = either. I also tried some static routes (in case the router wasn't happy with me = subnetting), but again no joy... -----Original Message----- From: dev...@li... on behalf of = Gordon Russell Sent: Mon 7/11/2005 4:36 PM To: dev...@li... Cc:=09 Subject: Re: [Devil-Linux-discuss] Routing what does netstat -rn tell you? you will have the same network on two interfaces (eth0, facing the=20 router, and eth1, facing the dmz). To which is the assigned network=20 (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 ------------------------------------------------------- This SF.Net email is sponsored by the 'Do More With Dual!' webinar = happening July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual core and dual graphics technology at this free one hour event hosted by = HP, AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar _______________________________________________ Devil-linux-discuss mailing list Dev...@li... https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss |
From: Russell P. <rus...@ai...> - 2005-07-11 16:54:59
|
Hm. I figured I may have to do something like that - but I've never used = that sort of configuration before. I guess I'll have to have a try again = at the subnetting. I do seem to remember a long time ago using static routes and modifying = the arp tables (back on ipso/Firewall-1)... The router here is one of the ISP(BT) managed things, so slightly = reluctant to have to have any configuration changes made to that. -----Original Message----- From: dev...@li... on behalf of Moray = McConnachie Sent: Mon 7/11/2005 5:36 PM To: dev...@li... Cc:=09 Subject: RE: [Devil-Linux-discuss] Routing We deal with this (tho glad to hear of a better way, because I thought = it very odd when setting it up!) by subnetting like this for eth0: 85.133.20.0/30 and then running virtual interfaces on eth1 (assuming class C for a = minute) as 85.133.20.4/30 85.133.20.8/29 85.133.20.16/28 85.133.20.32/27 85.133.20.64/26 85.133.20.128/25 Your DMZ address space is then 85.133.20.5-85.133.20.254, excepting = 85.133.20.7,85.133.20.8, 85.133.20.15, = 85.133.20.31,85.133.20.32,85.133.20.63,85.133.20.64,85.133.20.127. IPtables interface specifier is not sensitive to the virtual interfaces, = which means $IPTABLES -i eth0 -o eth1 still gets everything coming from = outside destined to the DMZ. If you don't care about using all the = address space, just using the last line would be easier. Then you tell the router to use static routing for each DMZ group you = set up, routing each through your eth0 IP address. Yours, Moray ------------------------------------------- Moray McConnachie IT Manager - mmc...@ox... Oxford Analytica - http://www.oxan.com -----Original Message----- From: dev...@li... [mailto:dev...@li...]On Behalf Of Russell Packer Sent: 11 July 2005 17:02 To: dev...@li... Subject: RE: [Devil-Linux-discuss] Routing netstat -rn shows me: 85.133.20.0 0.0.0 255.255.255.128 eth0 85.133.20.0 0.0.0 255.255.255.128 eth1 10.0.0.1 0.0.0.0 255.255.255.0 eth2 0.0.0.0 85.133.20.1 0.0.0.0 eth0 Which is pretty wrong, as indeed - how does anything know to come back = through eth1? I tried subnetting it out (255.255.255.192) but couldn't make that happy = either. I also tried some static routes (in case the router wasn't happy with me = subnetting), but again no joy... -----Original Message----- From: dev...@li... on behalf of = Gordon Russell Sent: Mon 7/11/2005 4:36 PM To: dev...@li... Cc:=09 Subject: Re: [Devil-Linux-discuss] Routing what does netstat -rn tell you? you will have the same network on two interfaces (eth0, facing the=20 router, and eth1, facing the dmz). To which is the assigned network=20 (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 ------------------------------------------------------- This SF.Net email is sponsored by the 'Do More With Dual!' webinar = happening July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual core and dual graphics technology at this free one hour event hosted by = HP, AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar _______________________________________________ Devil-linux-discuss mailing list Dev...@li... https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss ------------------------------------------------------- This SF.Net email is sponsored by the 'Do More With Dual!' webinar = happening July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual core and dual graphics technology at this free one hour event hosted by = HP, AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar _______________________________________________ Devil-linux-discuss mailing list Dev...@li... https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss |
From: Gordon R. <ru...@cl...> - 2005-07-11 18:11:40
|
I have always created a DMZ by patching in a simple unmanaged switch between the router and the firewall. Otherwise, the router will have to know that your firewall is the gateway to your DMZ somehow, either with a routing rule added to the ISP's router or getting the DL firewall's eth0 to grab everything that the router sends to your 85.133.20.0/25 subnet. Im not sure of the easiest way to do the latter. gordon Russell Packer wrote: > Hm. I figured I may have to do something like that - but I've never used that sort of configuration before. I guess I'll have to have a try again at the subnetting. > > I do seem to remember a long time ago using static routes and modifying the arp tables (back on ipso/Firewall-1)... > > The router here is one of the ISP(BT) managed things, so slightly reluctant to have to have any configuration changes made to that. > > > -----Original Message----- > From: dev...@li... on behalf of Moray McConnachie > Sent: Mon 7/11/2005 5:36 PM > To: dev...@li... > Cc: > Subject: RE: [Devil-Linux-discuss] Routing > We deal with this (tho glad to hear of a better way, because I thought it very odd when setting it up!) by subnetting like this for eth0: > > 85.133.20.0/30 > > and then running virtual interfaces on eth1 (assuming class C for a minute) as > > 85.133.20.4/30 > 85.133.20.8/29 > 85.133.20.16/28 > 85.133.20.32/27 > 85.133.20.64/26 > 85.133.20.128/25 > > Your DMZ address space is then 85.133.20.5-85.133.20.254, excepting 85.133.20.7,85.133.20.8, 85.133.20.15, 85.133.20.31,85.133.20.32,85.133.20.63,85.133.20.64,85.133.20.127. > > IPtables interface specifier is not sensitive to the virtual interfaces, which means $IPTABLES -i eth0 -o eth1 still gets everything coming from outside destined to the DMZ. If you don't care about using all the address space, just using the last line would be easier. > > Then you tell the router to use static routing for each DMZ group you set up, routing each through your eth0 IP address. > > Yours, > Moray > > > ------------------------------------------- > Moray McConnachie > IT Manager - mmc...@ox... > Oxford Analytica - http://www.oxan.com > > -----Original Message----- > From: dev...@li... > [mailto:dev...@li...]On Behalf Of > Russell Packer > Sent: 11 July 2005 17:02 > To: dev...@li... > Subject: RE: [Devil-Linux-discuss] Routing > > > netstat -rn shows me: > > 85.133.20.0 0.0.0 255.255.255.128 eth0 > 85.133.20.0 0.0.0 255.255.255.128 eth1 > 10.0.0.1 0.0.0.0 255.255.255.0 eth2 > 0.0.0.0 85.133.20.1 0.0.0.0 eth0 > > Which is pretty wrong, as indeed - how does anything know to come back through eth1? > > I tried subnetting it out (255.255.255.192) but couldn't make that happy either. > > I also tried some static routes (in case the router wasn't happy with me subnetting), but again no joy... > > > -----Original Message----- > From: dev...@li... on behalf of Gordon Russell > Sent: Mon 7/11/2005 4:36 PM > To: dev...@li... > Cc: > Subject: Re: [Devil-Linux-discuss] Routing > 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 > > > ------------------------------------------------------- > This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening > July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual > core and dual graphics technology at this free one hour event hosted by HP, > AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar > _______________________________________________ > Devil-linux-discuss mailing list > Dev...@li... > https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening > July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual > core and dual graphics technology at this free one hour event hosted by HP, > AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar > _______________________________________________ > Devil-linux-discuss mailing list > Dev...@li... > https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss > > > |
From: Moray M. <mmc...@ox...> - 2006-07-28 08:31:48
|
Could it be firewalling issue? If so, please send the output of=20 =20 iptables -L =20 It could also be that whatever is routing at 192.128.11.6 is blocking traffic from 192.128.10.xx ? =20 This could explain why it works from your DL box, where ping traffic will originate from 192.168.11.1, and not from your LAN (which will originate from 192.168.10.xx unless you are doing any masquerading) =20 Yours, Moray =20 =20 ------------------------------------- Moray McConnachie IS Manager +44 1865 261 600 Oxford Analytica http://www.oxan.com <http://www.oxan.com/>=20 =20 ________________________________ From: dev...@li... [mailto:dev...@li...] On Behalf Of Ross Petrie Sent: 27 July 2006 14:41 To: dev...@li... Subject: [Devil-Linux-discuss] Routing Hopefully someone can help me with this query...... =20 I've got an old pc running devil linux. It has 2 nics, each connected to a different subnet. =20 eth0 - 192.128.10.12 eth1 - 192.128.11.1 =20 I have also added a static route - 192.168.0.0/255.255.255.0:192.128.11.6 =20 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. =20 >From my PC though, on the 192.128.10 subnet, I can ping 192.128.11.xx fine but not 192.168.0.xx. =20 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? =20 Any clues? =20 Thanks =20 Ross Petrie =20 IT Administrator CAN Offshore Ltd Hareness Road Altens Aberdeen AB12 3LE =20 ________________________________________________________________________ IMPORTANT - our "canoffshore.ltd.uk" address is scheduled for cancellation. Address books should be changed to use our "cangroup.net" address. Thank you for your cooperation. This transmission contains information which may be confidential and that may also be privileged. It is intended for the named addressee only. Unless you are the named addressee, or authorised to receive it on behalf of the addressee, you may not copy or use it, or disclose it to anyone else. If you have received this transmission in error please contact the sender. Thank you for your cooperation. This email has been scanned for all viruses by the MessageLabs SkyScan service. CAN also uses the MessageLabs spam filtering service. This should not affect routine messages but in rare cases a bona-fide message could be blocked. Please contact CAN if you experience any difficulties. ________________________________________________________________________ |
From: Ross P. <Ros...@ca...> - 2006-07-28 11:11:21
|
I=20couldn't=20get=20to=20a=20machine=20on=20the=20192.168.0=20subnet=20to= =20see=20if=20it=20could get=20back=20the=20other=20way. Basically,=20the=20deal=20is=20that=20we=20have=20borrowed=20a=20couple=20= Cisco=20routers=20to get=20the=20link=20up=20to=20another=20building=20working,=20I'm=20looking= =20at=20Devil=20Linux as=20a=20cheap=20alternative! From=20the=20DL=20box,=20I=20can=20ping=20192.128.10.1,=20192.128.11.2=20a= nd=20192.168.0.18, all=20valid=20machines=20on=20each=20respective=20subnet. From=20my=20PC,=20which=20is=20on=20the=20192.128.10=20subnet,=20I=20can=20= ping=20192.128.11.2 but=20get=20no=20reply=20from=20192.168.0.18. It's=20like=20the=20final=20step=20from=20the=20router=20to=20my=20pc=20is= n't=20working,=20yet=20I can=20ping=20my=20machine=20from=20the=20router.=20 -----Original=20Message----- From:=20d...@li... [mailto:dev...@li...]=20On=20Behalf=20= Of Dick=20Middleton Sent:=2027=20July=202006=2022:26 To:=20d...@li... Subject:=20Re:=20[Devil-Linux-discuss]=20Routing Ross=20Petrie=20wrote: >=20Hopefully=20someone=20can=20help=20me=20with=20this=20query...... >=20=20 >=20I've=20got=20an=20old=20pc=20running=20devil=20linux.=20It=20has=202=20= nics,=20each=20connected=20 >=20to=20a=20different=20subnet. >=20=20 >=20eth0=20-=20192.128.10.12 >=20eth1=20-=20192.128.11.1 >=20=20 >=20I=20have=20also=20added=20a=20static=20route=20-=20 >=20192.168.0.0/255.255.255.0:192.128.11.6 >=20=20 >=20Now,=20the=20linux=20server=20can=20reach=20everything,=20no=20problem= .=20Can=20ping=20 >=20192.128.10.xx,=20192.128.11.xx=20and=20192.168.0.xx=20without=20any=20= trouble. >=20=20 >=20=20From=20my=20PC=20though,=20on=20the=20192.128.10=20subnet,=20I=20ca= n=20ping=20192.128.11.xx >=20fine=20but=20not=20192.168.0.xx. >=20=20 >=20I=20have=20set=20a=20route=20on=20the=20lan=20firewall=20to=20route=20= 192.128.11=20and=20 >=20192.168.0=20traffic=20to=20the=20devil=20linux=20box,=20which=20it=20c= learly=20does=20before >=20I=20can=20reach=20the=20192.128.11=20subnet.=20Why=20would=20I=20be=20= unable=20to=20get=20to=20the 192.168.0=20subnet? I=20don't=20know=20-=20what's=20supposed=20to=20respond=20to=20the=20ping?= =20=20Does=20it=20know=20how to=20get=20back=20to=20the=20PC.=20=20Can=20you=20ping=20the=20PC=20from=20= whatever=20is=20on 192.168... Dick ------------------------------------------------------------------------ - Take=20Surveys.=20Earn=20Cash.=20Influence=20the=20Future=20of=20IT=20Join= SourceForge.net's=20Techsay=20panel=20and=20you'll=20get=20the=20chance=20= to=20share=20your opinions=20on=20IT=20&=20business=20topics=20through=20brief=20surveys=20-= -=20and=20earn=20cash http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3DD= EVDE V _______________________________________________ Devil-linux-discuss=20mailing=20list Dev...@li... https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss ________________________________________________________________________ This=20email=20has=20been=20scanned=20for=20all=20viruses=20by=20the=20Mes= sageLabs=20Email security=20system.=20For=20more=20information=20visit=20www.messagelabs.co= m ________________________________________________________________________ ________________________________________________________________________ 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-28 11:34:13
|
Ross Petrie wrote: > > It's like the final step from the router to my pc isn't working, yet I > can ping my machine from the router. The only other obvious thing to check is that ip_forward is set. echo 1 > /proc/sys/net/ipv4/ip_forward Dick |
From: Aaron <aa...@uw...> - 2006-07-29 18:32:02
|
Hi Ross There's a chance that the issue might actually be on the Cisco side o= f=20 things if you still have one somewhere in this equation. Cisco route= rs=20 have a command called "ip subnet zero" that must be there to let them= =20 route .0.X type CIDRs. I guess older Network hardware used to have= =20 issues with zero CIDRs. Depending on the type of Cisco hardware and = the=20 IOS revision, some of them have "no ip subnet zero" as the default, i= n=20 which case your traffic might make it there but then get discarded by= =20 the Cisco box. You may also want to get a hold of the folks controlling the 192.168.= 0.0=20 network to see what sort of routing rules are in place there as well. Aaron Ross Petrie wrote: > I couldn't get to a machine on the 192.168.0 subnet to see if it co= uld > get back the other way. >=20 > Basically, the deal is that we have borrowed a couple Cisco routers= to > get the link up to another building working, I'm looking at Devil L= inux > as a cheap alternative! >=20 > From the DL box, I can ping 192.128.10.1, 192.128.11.2 and 192.168.= 0.18, > all valid machines on each respective subnet. >=20 > From my PC, which is on the 192.128.10 subnet, I can ping 192.128.1= 1.2 > but get no reply from 192.168.0.18. >=20 > It's like the final step from the router to my pc isn't working, ye= t I > can ping my machine from the router.=20 >=20 > -----Original Message----- > From: dev...@li... > [mailto:dev...@li...] On Behal= f Of > Dick Middleton > Sent: 27 July 2006 22:26 > To: dev...@li... > Subject: Re: [Devil-Linux-discuss] Routing >=20 > Ross Petrie wrote: >> Hopefully someone can help me with this query...... >> =20 >> I've got an old pc running devil linux. It has 2 nics, each connec= ted=20 >> to a different subnet. >> =20 >> eth0 - 192.128.10.12 >> eth1 - 192.128.11.1 >> =20 >> I have also added a static route -=20 >> 192.168.0.0/255.255.255.0:192.128.11.6 >> =20 >> Now, the linux server can reach everything, no problem. Can ping= =20 >> 192.128.10.xx, 192.128.11.xx and 192.168.0.xx without any trouble. >> =20 >> From my PC though, on the 192.128.10 subnet, I can ping 192.128.1= 1.xx >=20 >> fine but not 192.168.0.xx. >> =20 >> I have set a route on the lan firewall to route 192.128.11 and= =20 >> 192.168.0 traffic to the devil linux box, which it clearly does be= fore >=20 >> I can reach the 192.128.11 subnet. Why would I be unable to get to= the > 192.168.0 subnet? >=20 > I don't know - what's supposed to respond to the ping? Does it kno= w how > to get back to the PC. Can you ping the PC from whatever is on > 192.168... >=20 > Dick >=20 > -------------------------------------------------------------------= ----- > - > Take Surveys. Earn Cash. Influence the Future of IT Join > SourceForge.net's Techsay panel and you'll get the chance to share = your > opinions on IT & business topics through brief surveys -- and earn = cash > http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&= CID=3DDEVDE > V > _______________________________________________ > Devil-linux-discuss mailing list > Dev...@li... > https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss >=20 > ___________________________________________________________________= _____ > This email has been scanned for all viruses by the MessageLabs Emai= l > security system. For more information visit www.messagelabs.com > ___________________________________________________________________= _____ >=20 > ___________________________________________________________________= _____ > IMPORTANT =96 our =93canoffshore.ltd.uk=94 address is scheduled for= cancellation. Address books should be changed to use our =93cangrou= p.net=94 address. Thank you for your cooperation. >=20 > This transmission contains information which may be confidential an= d that may also be privileged. It is intended for the named addresse= e only. Unless you are the named addressee, or authorised to receive= it on behalf of the addressee, you may not copy or use it, or disclo= se it to anyone else. If you have received this transmission in erro= r please contact the sender. Thank you for your cooperation. >=20 > This email has been scanned for all viruses by the MessageLabs SkyS= can service. CAN also uses the MessageLabs spam filtering service. = This should not affect routine messages but in rare cases a bona-fide= message could be blocked. Please contact CAN if you experience any = difficulties. > ___________________________________________________________________= _____ >=20 >=20 >=20 > -------------------------------------------------------------------= ----- >=20 > -------------------------------------------------------------------= ------ > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to s= hare your > opinions on IT & business topics through brief surveys -- and earn = cash > http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&= CID=3DDEVDEV >=20 >=20 > -------------------------------------------------------------------= ----- >=20 > _______________________________________________ > Devil-linux-discuss mailing list > Dev...@li... > https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss |
From: Ross P. <Ros...@ca...> - 2006-07-31 09:09:41
|
To=20give=20you=20some=20background, The=20LAN=20at=20our=20main=20office=20is=20the=20192.128.10=20subnet.=20W= e=20have=20installed=20a wireless=20link=20between=20our=20office=20and=20a=20temporary=20office=20= we=20have=20rented. The=20wireless=20access=20points=20which=20make=20up=20the=20link=20are=20= on=20the=20192.128.11 subnet=20with=20the=20LAN=20at=20the=20temporary=20office=20on=20the=20192= .168.0=20subnet. We=20currently=20have=20a=20Cisco=202600=20router=20sitting=20on=20our=20L= AN=20with=20IP's=20on the=20192.128.10=20and=20192.128.11=20subnets=20and=20another=20on=20the=20= 192.128.11=20and 192.168.0=20subnets.=20These=20Cisco=20boxes=20are=20only=20loaners,=20so=20= I'm=20trying=20to get=20DL=20up=20and=20running=20so=20that=20I=20don't=20have=20to=20spend=20= silly=20money=20buying the=20Cisco=20kit.=20I=20think=20that=20the=20routers=20are=20configured=20= with=20IGRP,=20so=20I guess=20I=20would=20have=20to=20replace=20both=20machines=20at=20the=20sam= e=20time? -----Original=20Message----- From:=20d...@li... [mailto:dev...@li...]=20On=20Behalf=20= Of Aaron Sent:=2029=20July=202006=2016:13 To:=20d...@li... Subject:=20Re:=20[Devil-Linux-discuss]=20Routing Hi=20Ross There's=20a=20chance=20that=20the=20issue=20might=20actually=20be=20on=20t= he=20Cisco=20side=20of things=20if=20you=20still=20have=20one=20somewhere=20in=20this=20equation.= =20=20Cisco=20routers have=20a=20command=20called=20"ip=20subnet=20zero"=20that=20must=20be=20th= ere=20to=20let=20them route=20.0.X=20type=20CIDRs.=20=20I=20guess=20older=20Network=20hardware=20= used=20to=20have issues=20with=20zero=20CIDRs.=20=20Depending=20on=20the=20type=20of=20Cisc= o=20hardware=20and=20the IOS=20revision,=20some=20of=20them=20have=20"no=20ip=20subnet=20zero"=20as= =20the=20default,=20in which=20case=20your=20traffic=20might=20make=20it=20there=20but=20then=20g= et=20discarded=20by the=20Cisco=20box. You=20may=20also=20want=20to=20get=20a=20hold=20of=20the=20folks=20control= ling=20the=20192.168.0.0 network=20to=20see=20what=20sort=20of=20routing=20rules=20are=20in=20place= =20there=20as=20well. Aaron Ross=20Petrie=20wrote: >=20I=20couldn't=20get=20to=20a=20machine=20on=20the=20192.168.0=20subnet=20= to=20see=20if=20it=20could >=20get=20back=20the=20other=20way. >=20 >=20Basically,=20the=20deal=20is=20that=20we=20have=20borrowed=20a=20coupl= e=20Cisco=20routers=20to >=20get=20the=20link=20up=20to=20another=20building=20working,=20I'm=20loo= king=20at=20Devil=20 >=20Linux=20as=20a=20cheap=20alternative! >=20 >=20From=20the=20DL=20box,=20I=20can=20ping=20192.128.10.1,=20192.128.11.2= =20and=20 >=20192.168.0.18,=20all=20valid=20machines=20on=20each=20respective=20subn= et. >=20 >=20From=20my=20PC,=20which=20is=20on=20the=20192.128.10=20subnet,=20I=20c= an=20ping=20192.128.11.2 >=20but=20get=20no=20reply=20from=20192.168.0.18. >=20 >=20It's=20like=20the=20final=20step=20from=20the=20router=20to=20my=20pc=20= isn't=20working,=20yet=20I >=20can=20ping=20my=20machine=20from=20the=20router. >=20 >=20-----Original=20Message----- >=20From:=20d...@li... >=20[mailto:dev...@li...]=20On=20Beha= lf=20 >=20Of=20Dick=20Middleton >=20Sent:=2027=20July=202006=2022:26 >=20To:=20d...@li... >=20Subject:=20Re:=20[Devil-Linux-discuss]=20Routing >=20 >=20Ross=20Petrie=20wrote: >>=20Hopefully=20someone=20can=20help=20me=20with=20this=20query...... >>=20=20 >>=20I've=20got=20an=20old=20pc=20running=20devil=20linux.=20It=20has=202=20= nics,=20each=20connected >>=20to=20a=20different=20subnet. >>=20=20 >>=20eth0=20-=20192.128.10.12 >>=20eth1=20-=20192.128.11.1 >>=20=20 >>=20I=20have=20also=20added=20a=20static=20route=20- >>=20192.168.0.0/255.255.255.0:192.128.11.6 >>=20=20 >>=20Now,=20the=20linux=20server=20can=20reach=20everything,=20no=20proble= m.=20Can=20ping=20 >>=20192.128.10.xx,=20192.128.11.xx=20and=20192.168.0.xx=20without=20any=20= trouble. >>=20=20 >>=20=20From=20my=20PC=20though,=20on=20the=20192.128.10=20subnet,=20I=20c= an=20ping=20 >>=20192.128.11.xx >=20 >>=20fine=20but=20not=20192.168.0.xx. >>=20=20 >>=20I=20have=20set=20a=20route=20on=20the=20lan=20firewall=20to=20route=20= 192.128.11=20and=20 >>=20192.168.0=20traffic=20to=20the=20devil=20linux=20box,=20which=20it=20= clearly=20does=20 >>=20before >=20 >>=20I=20can=20reach=20the=20192.128.11=20subnet.=20Why=20would=20I=20be=20= unable=20to=20get=20to=20 >>=20the >=20192.168.0=20subnet? >=20 >=20I=20don't=20know=20-=20what's=20supposed=20to=20respond=20to=20the=20p= ing?=20=20Does=20it=20know=20 >=20how=20to=20get=20back=20to=20the=20PC.=20=20Can=20you=20ping=20the=20P= C=20from=20whatever=20is=20on=20 >=20192.168... >=20 >=20Dick >=20 >=20----------------------------------------------------------------------= >=20-- >=20- >=20Take=20Surveys.=20Earn=20Cash.=20Influence=20the=20Future=20of=20IT=20= Join=20 >=20SourceForge.net's=20Techsay=20panel=20and=20you'll=20get=20the=20chanc= e=20to=20share=20 >=20your=20opinions=20on=20IT=20&=20business=20topics=20through=20brief=20= surveys=20--=20and=20 >=20earn=20cash=20 >=20http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID= =3DDEV >=20DE >=20V >=20_______________________________________________ >=20Devil-linux-discuss=20mailing=20list >=20D...@li... >=20https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss >=20 >=20______________________________________________________________________= >=20__=20This=20email=20has=20been=20scanned=20for=20all=20viruses=20by=20= the=20MessageLabs=20 >=20Email=20security=20system.=20For=20more=20information=20visit=20www.me= ssagelabs.com=20 >=20______________________________________________________________________= >=20__ >=20 >=20______________________________________________________________________= >=20__=20IMPORTANT=20-=20our=20"canoffshore.ltd.uk"=20address=20is=20sched= uled=20for=20 >=20cancellation.=20=20Address=20books=20should=20be=20changed=20to=20use=20= our "cangroup.net"=20address.=20=20Thank=20you=20for=20your=20cooperation. >=20 >=20This=20transmission=20contains=20information=20which=20may=20be=20conf= idential=20and that=20may=20also=20be=20privileged.=20=20It=20is=20intended=20for=20the=20= named=20addressee only.=20=20Unless=20you=20are=20the=20named=20addressee,=20or=20authorised= =20to=20receive=20it on=20behalf=20of=20the=20addressee,=20you=20may=20not=20copy=20or=20use=20= it,=20or=20disclose=20it to=20anyone=20else.=20=20If=20you=20have=20received=20this=20transmission=20= in=20error=20please contact=20the=20sender.=20=20Thank=20you=20for=20your=20cooperation. >=20 >=20This=20email=20has=20been=20scanned=20for=20all=20viruses=20by=20the=20= MessageLabs=20SkyScan service.=20=20CAN=20also=20uses=20the=20MessageLabs=20spam=20filtering=20s= ervice.=20=20This should=20not=20affect=20routine=20messages=20but=20in=20rare=20cases=20a=20= bona-fide=20message could=20be=20blocked.=20=20Please=20contact=20CAN=20if=20you=20experience=20= any difficulties. >=20______________________________________________________________________= >=20__ >=20 >=20 >=20 >=20----------------------------------------------------------------------= >=20-- >=20 >=20----------------------------------------------------------------------= >=20---=20Take=20Surveys.=20Earn=20Cash.=20Influence=20the=20Future=20of=20= IT=20Join=20 >=20SourceForge.net's=20Techsay=20panel=20and=20you'll=20get=20the=20chanc= e=20to=20share=20 >=20your=20opinions=20on=20IT=20&=20business=20topics=20through=20brief=20= surveys=20--=20and=20 >=20earn=20cash=20 >=20http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID= =3DDEV >=20DEV >=20 >=20 >=20----------------------------------------------------------------------= >=20-- >=20 >=20_______________________________________________ >=20Devil-linux-discuss=20mailing=20list >=20D...@li... >=20https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss ------------------------------------------------------------------------ - Take=20Surveys.=20Earn=20Cash.=20Influence=20the=20Future=20of=20IT=20Join= SourceForge.net's=20Techsay=20panel=20and=20you'll=20get=20the=20chance=20= to=20share=20your opinions=20on=20IT=20&=20business=20topics=20through=20brief=20surveys=20-= -=20and=20earn=20cash http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3DD= EVDE V _______________________________________________ Devil-linux-discuss=20mailing=20list Dev...@li... https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss ________________________________________________________________________ This=20email=20has=20been=20scanned=20for=20all=20viruses=20by=20the=20Mes= sageLabs=20Email security=20system.=20For=20more=20information=20visit=20www.messagelabs.co= m ________________________________________________________________________ ________________________________________________________________________ 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: Devil-Linux <dev...@js...> - 2006-07-31 09:53:38
|
Hi, It could be a simple matter of 192.168.0.18 not knowing where your 192.128.10 net is either that has the wrong default route or that you have to add a specific rout or that its router dont know that it should ask your router. I beleive that IGRP is patented by CISCO so I doubt tha you can announce it VIA zebra/quagga but dont know, you might be able to talk RIP or IGP or something tho.. but I would go static atleast for testing. /Jacob ----- Original Message ----- From: "Ross Petrie" <Ros...@ca...> To: <dev...@li...> Sent: Monday, July 31, 2006 11:06 AM Subject: Re: [Devil-Linux-discuss] Routing To give you some background, The LAN at our main office is the 192.128.10 subnet. We have installed a wireless link between our office and a temporary office we have rented. The wireless access points which make up the link are on the 192.128.11 subnet with the LAN at the temporary office on the 192.168.0 subnet. We currently have a Cisco 2600 router sitting on our LAN with IP's on the 192.128.10 and 192.128.11 subnets and another on the 192.128.11 and 192.168.0 subnets. These Cisco boxes are only loaners, so I'm trying to get DL up and running so that I don't have to spend silly money buying the Cisco kit. I think that the routers are configured with IGRP, so I guess I would have to replace both machines at the same time? -----Original Message----- From: dev...@li... [mailto:dev...@li...] On Behalf Of Aaron Sent: 29 July 2006 16:13 To: dev...@li... Subject: Re: [Devil-Linux-discuss] Routing Hi Ross There's a chance that the issue might actually be on the Cisco side of things if you still have one somewhere in this equation. Cisco routers have a command called "ip subnet zero" that must be there to let them route .0.X type CIDRs. I guess older Network hardware used to have issues with zero CIDRs. Depending on the type of Cisco hardware and the IOS revision, some of them have "no ip subnet zero" as the default, in which case your traffic might make it there but then get discarded by the Cisco box. You may also want to get a hold of the folks controlling the 192.168.0.0 network to see what sort of routing rules are in place there as well. Aaron Ross Petrie wrote: > I couldn't get to a machine on the 192.168.0 subnet to see if it could > get back the other way. > > Basically, the deal is that we have borrowed a couple Cisco routers to > get the link up to another building working, I'm looking at Devil > Linux as a cheap alternative! > > From the DL box, I can ping 192.128.10.1, 192.128.11.2 and > 192.168.0.18, all valid machines on each respective subnet. > > From my PC, which is on the 192.128.10 subnet, I can ping 192.128.11.2 > but get no reply from 192.168.0.18. > > It's like the final step from the router to my pc isn't working, yet I > can ping my machine from the router. > > -----Original Message----- > From: dev...@li... > [mailto:dev...@li...] On Behalf > Of Dick Middleton > Sent: 27 July 2006 22:26 > To: dev...@li... > Subject: Re: [Devil-Linux-discuss] Routing > > 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 > > ---------------------------------------------------------------------- > -- > - > Take Surveys. Earn Cash. Influence the Future of IT Join > SourceForge.net's Techsay panel and you'll get the chance to share > your opinions on IT & business topics through brief surveys -- and > earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEV > DE > V > _______________________________________________ > Devil-linux-discuss mailing list > Dev...@li... > https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss > > ______________________________________________________________________ > __ This email has been scanned for all viruses by the MessageLabs > Email security system. For more information visit www.messagelabs.com > ______________________________________________________________________ > __ > > ______________________________________________________________________ > __ IMPORTANT - our "canoffshore.ltd.uk" address is scheduled for > cancellation. Address books should be changed to use our "cangroup.net" address. Thank you for your cooperation. > > This transmission contains information which may be confidential and that may also be privileged. It is intended for the named addressee only. Unless you are the named addressee, or authorised to receive it on behalf of the addressee, you may not copy or use it, or disclose it to anyone else. If you have received this transmission in error please contact the sender. Thank you for your cooperation. > > This email has been scanned for all viruses by the MessageLabs SkyScan service. CAN also uses the MessageLabs spam filtering service. This should not affect routine messages but in rare cases a bona-fide message could be blocked. Please contact CAN if you experience any difficulties. > ______________________________________________________________________ > __ > > > > ---------------------------------------------------------------------- > -- > > ---------------------------------------------------------------------- > --- Take Surveys. Earn Cash. Influence the Future of IT Join > SourceForge.net's Techsay panel and you'll get the chance to share > your opinions on IT & business topics through brief surveys -- and > earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEV > DEV > > > ---------------------------------------------------------------------- > -- > > _______________________________________________ > Devil-linux-discuss mailing list > Dev...@li... > https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss ------------------------------------------------------------------------ - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDE V _______________________________________________ Devil-linux-discuss mailing list Dev...@li... https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss ________________________________________________________________________ This email has been scanned for all viruses by the MessageLabs Email security system. For more information visit www.messagelabs.com ________________________________________________________________________ ________________________________________________________________________ IMPORTANT - our "canoffshore.ltd.uk" address is scheduled for cancellation. Address books should be changed to use our "cangroup.net" address. Thank you for your cooperation. This transmission contains information which may be confidential and that may also be privileged. It is intended for the named addressee only. Unless you are the named addressee, or authorised to receive it on behalf of the addressee, you may not copy or use it, or disclose it to anyone else. If you have received this transmission in error please contact the sender. Thank you for your cooperation. This email has been scanned for all viruses by the MessageLabs SkyScan service. CAN also uses the MessageLabs spam filtering service. This should not affect routine messages but in rare cases a bona-fide message could be blocked. Please contact CAN if you experience any difficulties. ________________________________________________________________________ -------------------------------------------------------------------------------- > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share > your > opinions on IT & business topics through brief surveys -- and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV -------------------------------------------------------------------------------- > _______________________________________________ > Devil-linux-discuss mailing list > Dev...@li... > https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss > |
From: Aaron <aa...@uw...> - 2006-07-31 10:25:58
|
Agreed - IGRP is proprietary to Cisco. For a small Network such as that, use static routes. Static routes override dynamic routing in Cisco's IOS, so if you add the appropriate static routes on the destination side, you should see some results. --Aaron Devil-Linux wrote: > Hi, > > It could be a simple matter of 192.168.0.18 not knowing where your > 192.128.10 net is > either that has the wrong default route or that you have to add a specific > rout or that > its router dont know that it should ask your router. > > I beleive that IGRP is patented by CISCO so I doubt tha you can announce it > VIA > zebra/quagga but dont know, you might be able to talk RIP or IGP or > something tho.. > but I would go static atleast for testing. > > /Jacob > > ----- Original Message ----- > From: "Ross Petrie" <Ros...@ca...> > To: <dev...@li...> > Sent: Monday, July 31, 2006 11:06 AM > Subject: Re: [Devil-Linux-discuss] Routing > > > To give you some background, > > The LAN at our main office is the 192.128.10 subnet. We have installed a > wireless link between our office and a temporary office we have rented. > The wireless access points which make up the link are on the 192.128.11 > subnet with the LAN at the temporary office on the 192.168.0 subnet. > > We currently have a Cisco 2600 router sitting on our LAN with IP's on > the 192.128.10 and 192.128.11 subnets and another on the 192.128.11 and > 192.168.0 subnets. These Cisco boxes are only loaners, so I'm trying to > get DL up and running so that I don't have to spend silly money buying > the Cisco kit. I think that the routers are configured with IGRP, so I > guess I would have to replace both machines at the same time? > > -----Original Message----- > From: dev...@li... > [mailto:dev...@li...] On Behalf Of > Aaron > Sent: 29 July 2006 16:13 > To: dev...@li... > Subject: Re: [Devil-Linux-discuss] Routing > > Hi Ross > > There's a chance that the issue might actually be on the Cisco side of > things if you still have one somewhere in this equation. Cisco routers > have a command called "ip subnet zero" that must be there to let them > route .0.X type CIDRs. I guess older Network hardware used to have > issues with zero CIDRs. Depending on the type of Cisco hardware and the > IOS revision, some of them have "no ip subnet zero" as the default, in > which case your traffic might make it there but then get discarded by > the Cisco box. > > You may also want to get a hold of the folks controlling the 192.168.0.0 > network to see what sort of routing rules are in place there as well. > > Aaron > > Ross Petrie wrote: >> I couldn't get to a machine on the 192.168.0 subnet to see if it could > >> get back the other way. >> >> Basically, the deal is that we have borrowed a couple Cisco routers to > >> get the link up to another building working, I'm looking at Devil >> Linux as a cheap alternative! >> >> From the DL box, I can ping 192.128.10.1, 192.128.11.2 and >> 192.168.0.18, all valid machines on each respective subnet. >> >> From my PC, which is on the 192.128.10 subnet, I can ping 192.128.11.2 > >> but get no reply from 192.168.0.18. >> >> It's like the final step from the router to my pc isn't working, yet I > >> can ping my machine from the router. >> >> -----Original Message----- >> From: dev...@li... >> [mailto:dev...@li...] On Behalf >> Of Dick Middleton >> Sent: 27 July 2006 22:26 >> To: dev...@li... >> Subject: Re: [Devil-Linux-discuss] Routing >> >> 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 >> >> ---------------------------------------------------------------------- >> -- >> - >> Take Surveys. Earn Cash. Influence the Future of IT Join >> SourceForge.net's Techsay panel and you'll get the chance to share >> your opinions on IT & business topics through brief surveys -- and >> earn cash >> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEV >> DE >> V >> _______________________________________________ >> Devil-linux-discuss mailing list >> Dev...@li... >> https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss >> >> ______________________________________________________________________ >> __ This email has been scanned for all viruses by the MessageLabs >> Email security system. For more information visit www.messagelabs.com >> ______________________________________________________________________ >> __ >> >> ______________________________________________________________________ >> __ IMPORTANT - our "canoffshore.ltd.uk" address is scheduled for >> cancellation. Address books should be changed to use our > "cangroup.net" address. Thank you for your cooperation. >> This transmission contains information which may be confidential and > that may also be privileged. It is intended for the named addressee > only. Unless you are the named addressee, or authorised to receive it > on behalf of the addressee, you may not copy or use it, or disclose it > to anyone else. If you have received this transmission in error please > contact the sender. Thank you for your cooperation. >> This email has been scanned for all viruses by the MessageLabs SkyScan > service. CAN also uses the MessageLabs spam filtering service. This > should not affect routine messages but in rare cases a bona-fide message > could be blocked. Please contact CAN if you experience any > difficulties. >> ______________________________________________________________________ >> __ >> >> >> >> ---------------------------------------------------------------------- >> -- >> >> ---------------------------------------------------------------------- >> --- Take Surveys. Earn Cash. Influence the Future of IT Join >> SourceForge.net's Techsay panel and you'll get the chance to share >> your opinions on IT & business topics through brief surveys -- and >> earn cash >> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEV >> DEV >> >> >> ---------------------------------------------------------------------- >> -- >> >> _______________________________________________ >> Devil-linux-discuss mailing list >> Dev...@li... >> https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss > > > > ------------------------------------------------------------------------ > - > Take Surveys. Earn Cash. Influence the Future of IT Join > SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys -- and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDE > V > _______________________________________________ > Devil-linux-discuss mailing list > Dev...@li... > https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss > > ________________________________________________________________________ > This email has been scanned for all viruses by the MessageLabs Email > security system. For more information visit www.messagelabs.com > ________________________________________________________________________ > > ________________________________________________________________________ > IMPORTANT - our "canoffshore.ltd.uk" address is scheduled for cancellation. > Address books should be changed to use our "cangroup.net" address. Thank > you for your cooperation. > > This transmission contains information which may be confidential and that > may also be privileged. It is intended for the named addressee only. > Unless you are the named addressee, or authorised to receive it on behalf of > the addressee, you may not copy or use it, or disclose it to anyone else. > If you have received this transmission in error please contact the sender. > Thank you for your cooperation. > > This email has been scanned for all viruses by the MessageLabs SkyScan > service. CAN also uses the MessageLabs spam filtering service. This should > not affect routine messages but in rare cases a bona-fide message could be > blocked. Please contact CAN if you experience any difficulties. > ________________________________________________________________________ > > > > > -------------------------------------------------------------------------------- > > >> ------------------------------------------------------------------------- >> Take Surveys. Earn Cash. Influence the Future of IT >> Join SourceForge.net's Techsay panel and you'll get the chance to share >> your >> opinions on IT & business topics through brief surveys -- and earn cash >> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > > > -------------------------------------------------------------------------------- > > >> _______________________________________________ >> Devil-linux-discuss mailing list >> Dev...@li... >> https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss >> > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys -- and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Devil-linux-discuss mailing list > Dev...@li... > https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss |
From: Ross P. <Ros...@ca...> - 2006-08-01 09:09:18
|
Thanks=20to=20all,=20I=20now=20have=20it=20working! Hopefully=20I'll=20get=20to=20keep=20the=20couple=20grand=20that=20they=20= were=20going=20to spend=20on=20the=20Cisco=20gear? Thanks=20a=20lot Ross=20 -----Original=20Message----- From:=20d...@li... [mailto:dev...@li...]=20On=20Behalf=20= Of Aaron Sent:=2031=20July=202006=2011:27 To:=20d...@li... Subject:=20Re:=20[Devil-Linux-discuss]=20Routing Agreed=20-=20IGRP=20is=20proprietary=20to=20Cisco.=20=20For=20a=20small=20= Network=20such=20as that,=20use=20static=20routes.=20=20Static=20routes=20override=20dynamic=20= routing=20in Cisco's=20IOS,=20so=20if=20you=20add=20the=20appropriate=20static=20routes= =20on=20the destination=20side,=20you=20should=20see=20some=20results. --Aaron Devil-Linux=20wrote: >=20Hi, >=20 >=20It=20could=20be=20a=20simple=20matter=20of=20192.168.0.18=20not=20know= ing=20where=20your=20 >=20192.128.10=20net=20is=20either=20that=20has=20the=20wrong=20default=20= route=20or=20that=20you=20 >=20have=20to=20add=20a=20specific=20rout=20or=20that=20its=20router=20don= t=20know=20that=20it=20 >=20should=20ask=20your=20router. >=20 >=20I=20beleive=20that=20IGRP=20is=20patented=20by=20CISCO=20so=20I=20doub= t=20tha=20you=20can=20 >=20announce=20it=20VIA=20zebra/quagga=20but=20dont=20know,=20you=20might=20= be=20able=20to=20talk=20 >=20RIP=20or=20IGP=20or=20something=20tho.. >=20but=20I=20would=20go=20static=20atleast=20for=20testing. >=20 >=20/Jacob >=20 >=20-----=20Original=20Message=20----- >=20From:=20"Ross=20Petrie"=20<Ros...@ca...> >=20To:=20<dev...@li...> >=20Sent:=20Monday,=20July=2031,=202006=2011:06=20AM >=20Subject:=20Re:=20[Devil-Linux-discuss]=20Routing >=20 >=20 >=20To=20give=20you=20some=20background, >=20 >=20The=20LAN=20at=20our=20main=20office=20is=20the=20192.128.10=20subnet.= =20We=20have=20installed >=20a=20wireless=20link=20between=20our=20office=20and=20a=20temporary=20o= ffice=20we=20have rented. >=20The=20wireless=20access=20points=20which=20make=20up=20the=20link=20ar= e=20on=20the=20 >=20192.128.11=20subnet=20with=20the=20LAN=20at=20the=20temporary=20office= =20on=20the 192.168.0=20subnet. >=20 >=20We=20currently=20have=20a=20Cisco=202600=20router=20sitting=20on=20our= =20LAN=20with=20IP's=20on=20 >=20the=20192.128.10=20and=20192.128.11=20subnets=20and=20another=20on=20t= he=20192.128.11=20 >=20and=20192.168.0=20subnets.=20These=20Cisco=20boxes=20are=20only=20loan= ers,=20so=20I'm=20 >=20trying=20to=20get=20DL=20up=20and=20running=20so=20that=20I=20don't=20= have=20to=20spend=20silly=20 >=20money=20buying=20the=20Cisco=20kit.=20I=20think=20that=20the=20routers= =20are=20configured=20 >=20with=20IGRP,=20so=20I=20guess=20I=20would=20have=20to=20replace=20both= =20machines=20at=20the same=20time? >=20 >=20-----Original=20Message----- >=20From:=20d...@li... >=20[mailto:dev...@li...]=20On=20Beha= lf=20 >=20Of=20Aaron >=20Sent:=2029=20July=202006=2016:13 >=20To:=20d...@li... >=20Subject:=20Re:=20[Devil-Linux-discuss]=20Routing >=20 >=20Hi=20Ross >=20 >=20There's=20a=20chance=20that=20the=20issue=20might=20actually=20be=20on= =20the=20Cisco=20side=20of >=20things=20if=20you=20still=20have=20one=20somewhere=20in=20this=20equat= ion.=20=20Cisco=20 >=20routers=20have=20a=20command=20called=20"ip=20subnet=20zero"=20that=20= must=20be=20there=20to=20 >=20let=20them=20route=20.0.X=20type=20CIDRs.=20=20I=20guess=20older=20Net= work=20hardware=20used=20 >=20to=20have=20issues=20with=20zero=20CIDRs.=20=20Depending=20on=20the=20= type=20of=20Cisco=20 >=20hardware=20and=20the=20IOS=20revision,=20some=20of=20them=20have=20"no= =20ip=20subnet=20zero"=20 >=20as=20the=20default,=20in=20which=20case=20your=20traffic=20might=20mak= e=20it=20there=20but=20 >=20then=20get=20discarded=20by=20the=20Cisco=20box. >=20 >=20You=20may=20also=20want=20to=20get=20a=20hold=20of=20the=20folks=20con= trolling=20the=20 >=20192.168.0.0=20network=20to=20see=20what=20sort=20of=20routing=20rules=20= are=20in=20place there=20as=20well. >=20 >=20Aaron >=20 >=20Ross=20Petrie=20wrote: >>=20I=20couldn't=20get=20to=20a=20machine=20on=20the=20192.168.0=20subnet= =20to=20see=20if=20it=20 >>=20could >=20 >>=20get=20back=20the=20other=20way. >> >>=20Basically,=20the=20deal=20is=20that=20we=20have=20borrowed=20a=20coup= le=20Cisco=20routers=20 >>=20to >=20 >>=20get=20the=20link=20up=20to=20another=20building=20working,=20I'm=20lo= oking=20at=20Devil=20 >>=20Linux=20as=20a=20cheap=20alternative! >> >>=20From=20the=20DL=20box,=20I=20can=20ping=20192.128.10.1,=20192.128.11.= 2=20and=20 >>=20192.168.0.18,=20all=20valid=20machines=20on=20each=20respective=20sub= net. >> >>=20From=20my=20PC,=20which=20is=20on=20the=20192.128.10=20subnet,=20I=20= can=20ping=20 >>=20192.128.11.2 >=20 >>=20but=20get=20no=20reply=20from=20192.168.0.18. >> >>=20It's=20like=20the=20final=20step=20from=20the=20router=20to=20my=20pc= =20isn't=20working,=20yet=20 >>=20I >=20 >>=20can=20ping=20my=20machine=20from=20the=20router. >> >>=20-----Original=20Message----- >>=20From:=20d...@li... >>=20[mailto:dev...@li...]=20On=20Beh= alf=20 >>=20Of=20Dick=20Middleton >>=20Sent:=2027=20July=202006=2022:26 >>=20To:=20d...@li... >>=20Subject:=20Re:=20[Devil-Linux-discuss]=20Routing >> >>=20Ross=20Petrie=20wrote: >>>=20Hopefully=20someone=20can=20help=20me=20with=20this=20query...... >>> >>>=20I've=20got=20an=20old=20pc=20running=20devil=20linux.=20It=20has=202= =20nics,=20each=20 >>>=20connected >=20 >>>=20to=20a=20different=20subnet. >>> >>>=20eth0=20-=20192.128.10.12 >>>=20eth1=20-=20192.128.11.1 >>> >>>=20I=20have=20also=20added=20a=20static=20route=20- >>>=20192.168.0.0/255.255.255.0:192.128.11.6 >>> >>>=20Now,=20the=20linux=20server=20can=20reach=20everything,=20no=20probl= em.=20Can=20ping=20 >>>=20192.128.10.xx,=20192.128.11.xx=20and=20192.168.0.xx=20without=20any=20= trouble. >>> >>>=20=20From=20my=20PC=20though,=20on=20the=20192.128.10=20subnet,=20I=20= can=20ping=20 >>>=20192.128.11.xx=20fine=20but=20not=20192.168.0.xx. >>> >>>=20I=20have=20set=20a=20route=20on=20the=20lan=20firewall=20to=20route=20= 192.128.11=20and=20 >>>=20192.168.0=20traffic=20to=20the=20devil=20linux=20box,=20which=20it=20= clearly=20does=20 >>>=20before=20I=20can=20reach=20the=20192.128.11=20subnet.=20Why=20would=20= I=20be=20unable=20to=20 >>>=20get=20to=20the >>=20192.168.0=20subnet? >> >>=20I=20don't=20know=20-=20what's=20supposed=20to=20respond=20to=20the=20= ping?=20=20Does=20it=20know=20 >>=20how=20to=20get=20back=20to=20the=20PC.=20=20Can=20you=20ping=20the=20= PC=20from=20whatever=20is=20on=20 >>=20192.168... >> >>=20Dick >> >>=20---------------------------------------------------------------------= >>=20- >>=20-- >>=20- >>=20Take=20Surveys.=20Earn=20Cash.=20Influence=20the=20Future=20of=20IT=20= Join=20 >>=20SourceForge.net's=20Techsay=20panel=20and=20you'll=20get=20the=20chan= ce=20to=20share=20 >>=20your=20opinions=20on=20IT=20&=20business=20topics=20through=20brief=20= surveys=20--=20and=20 >>=20earn=20cash=20 >>=20http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CI= D=3DDE >>=20V >>=20DE >>=20V >>=20_______________________________________________ >>=20Devil-linux-discuss=20mailing=20list >>=20D...@li... >>=20https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss >> >>=20_____________________________________________________________________= >>=20_=20__=20This=20email=20has=20been=20scanned=20for=20all=20viruses=20= by=20the=20MessageLabs=20 >>=20Email=20security=20system.=20For=20more=20information=20visit=20www.m= essagelabs.com >>=20_____________________________________________________________________= >>=20_ >>=20__ >> >>=20_____________________________________________________________________= >>=20_=20__=20IMPORTANT=20-=20our=20"canoffshore.ltd.uk"=20address=20is=20= scheduled=20for=20 >>=20cancellation.=20=20Address=20books=20should=20be=20changed=20to=20use= =20our >=20"cangroup.net"=20address.=20=20Thank=20you=20for=20your=20cooperation.= >>=20This=20transmission=20contains=20information=20which=20may=20be=20con= fidential=20and >=20that=20may=20also=20be=20privileged.=20=20It=20is=20intended=20for=20t= he=20named=20addressee=20 >=20only.=20=20Unless=20you=20are=20the=20named=20addressee,=20or=20author= ised=20to=20receive=20it >=20on=20behalf=20of=20the=20addressee,=20you=20may=20not=20copy=20or=20us= e=20it,=20or=20disclose=20it >=20to=20anyone=20else.=20=20If=20you=20have=20received=20this=20transmiss= ion=20in=20error=20 >=20please=20contact=20the=20sender.=20=20Thank=20you=20for=20your=20coope= ration. >>=20This=20email=20has=20been=20scanned=20for=20all=20viruses=20by=20the=20= MessageLabs=20 >>=20SkyScan >=20service.=20=20CAN=20also=20uses=20the=20MessageLabs=20spam=20filtering= =20service.=20=20This=20 >=20should=20not=20affect=20routine=20messages=20but=20in=20rare=20cases=20= a=20bona-fide=20 >=20message=20could=20be=20blocked.=20=20Please=20contact=20CAN=20if=20you= =20experience=20any=20 >=20difficulties. >>=20_____________________________________________________________________= >>=20_ >>=20__ >> >> >> >>=20---------------------------------------------------------------------= >>=20- >>=20-- >> >>=20---------------------------------------------------------------------= >>=20- >>=20---=20Take=20Surveys.=20Earn=20Cash.=20Influence=20the=20Future=20of=20= IT=20Join=20 >>=20SourceForge.net's=20Techsay=20panel=20and=20you'll=20get=20the=20chan= ce=20to=20share=20 >>=20your=20opinions=20on=20IT=20&=20business=20topics=20through=20brief=20= surveys=20--=20and=20 >>=20earn=20cash=20 >>=20http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CI= D=3DDE >>=20V >>=20DEV >> >> >>=20---------------------------------------------------------------------= >>=20- >>=20-- >> >>=20_______________________________________________ >>=20Devil-linux-discuss=20mailing=20list >>=20D...@li... >>=20https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss >=20 >=20 >=20 >=20----------------------------------------------------------------------= >=20-- >=20- >=20Take=20Surveys.=20Earn=20Cash.=20Influence=20the=20Future=20of=20IT=20= Join=20 >=20SourceForge.net's=20Techsay=20panel=20and=20you'll=20get=20the=20chanc= e=20to=20share=20 >=20your=20opinions=20on=20IT=20&=20business=20topics=20through=20brief=20= surveys=20--=20and=20 >=20earn=20cash=20 >=20http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID= =3DDEV >=20DE >=20V >=20_______________________________________________ >=20Devil-linux-discuss=20mailing=20list >=20D...@li... >=20https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss >=20 >=20______________________________________________________________________= >=20__=20This=20email=20has=20been=20scanned=20for=20all=20viruses=20by=20= the=20MessageLabs=20 >=20Email=20security=20system.=20For=20more=20information=20visit=20www.me= ssagelabs.com=20 >=20______________________________________________________________________= >=20__ >=20 >=20______________________________________________________________________= >=20__=20IMPORTANT=20-=20our=20"canoffshore.ltd.uk"=20address=20is=20sched= uled=20for=20 >=20cancellation. >=20Address=20books=20should=20be=20changed=20to=20use=20our=20"cangroup.n= et"=20address.=20=20 >=20Thank=20you=20for=20your=20cooperation. >=20 >=20This=20transmission=20contains=20information=20which=20may=20be=20conf= idential=20and=20 >=20that=20may=20also=20be=20privileged.=20=20It=20is=20intended=20for=20t= he=20named=20addressee only. >=20Unless=20you=20are=20the=20named=20addressee,=20or=20authorised=20to=20= receive=20it=20on=20 >=20behalf=20of=20the=20addressee,=20you=20may=20not=20copy=20or=20use=20i= t,=20or=20disclose=20it=20to anyone=20else. >=20If=20you=20have=20received=20this=20transmission=20in=20error=20please= =20contact=20the sender.=20 >=20Thank=20you=20for=20your=20cooperation. >=20 >=20This=20email=20has=20been=20scanned=20for=20all=20viruses=20by=20the=20= MessageLabs=20SkyScan >=20service.=20=20CAN=20also=20uses=20the=20MessageLabs=20spam=20filtering= =20service.=20=20This=20 >=20should=20not=20affect=20routine=20messages=20but=20in=20rare=20cases=20= a=20bona-fide=20 >=20message=20could=20be=20blocked.=20=20Please=20contact=20CAN=20if=20you= =20experience=20any difficulties. >=20______________________________________________________________________= >=20__ >=20 >=20 >=20 >=20 >=20----------------------------------------------------------------------= >=20---------- >=20 >=20 >>=20---------------------------------------------------------------------= >>=20----=20Take=20Surveys.=20Earn=20Cash.=20Influence=20the=20Future=20of= =20IT=20Join=20 >>=20SourceForge.net's=20Techsay=20panel=20and=20you'll=20get=20the=20chan= ce=20to=20share=20 >>=20your=20opinions=20on=20IT=20&=20business=20topics=20through=20brief=20= surveys=20--=20and=20 >>=20earn=20cash=20 >>=20http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CI= D=3DDE >>=20VDEV >=20 >=20 >=20----------------------------------------------------------------------= >=20---------- >=20 >=20 >>=20_______________________________________________ >>=20Devil-linux-discuss=20mailing=20list >>=20D...@li... >>=20https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss >> >=20 >=20 >=20----------------------------------------------------------------------= >=20---=20Take=20Surveys.=20Earn=20Cash.=20Influence=20the=20Future=20of=20= IT=20Join=20 >=20SourceForge.net's=20Techsay=20panel=20and=20you'll=20get=20the=20chanc= e=20to=20share=20 >=20your=20opinions=20on=20IT=20&=20business=20topics=20through=20brief=20= surveys=20--=20and=20 >=20earn=20cash=20 >=20http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID= =3DDEV >=20DEV=20_______________________________________________ >=20Devil-linux-discuss=20mailing=20list >=20D...@li... >=20https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss ------------------------------------------------------------------------ - Take=20Surveys.=20Earn=20Cash.=20Influence=20the=20Future=20of=20IT=20Join= SourceForge.net's=20Techsay=20panel=20and=20you'll=20get=20the=20chance=20= to=20share=20your opinions=20on=20IT=20&=20business=20topics=20through=20brief=20surveys=20-= -=20and=20earn=20cash http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3DD= EVDE V _______________________________________________ Devil-linux-discuss=20mailing=20list Dev...@li... https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss ________________________________________________________________________ This=20email=20has=20been=20scanned=20for=20all=20viruses=20by=20the=20Mes= sageLabs=20Email security=20system.=20For=20more=20information=20visit=20www.messagelabs.co= m ________________________________________________________________________ ________________________________________________________________________ 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: Heiko Z. <he...@zu...> - 2006-08-01 13:18:51
|
On Tue, August 1, 2006 04:05, Ross Petrie wrote: > Thanks to all, I now have it working! > > > Hopefully I'll get to keep the couple grand that they were going to > spend on the Cisco gear? http://www.devil-linux.org/sitetools/donatedl.php ;-) -- Regards Heiko Zuerker http://www.devil-linux.org |
From: Brian H. <nautix@u.washington.edu> - 2004-12-06 07:00:12
|
Ah! I believe we have found the trouble! Today, Lyubomir Louisov was quoted as saying: > 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. So addresses work, but names do not. The problems lies in name-to-address resolution. > > /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 I would guess that /etc/resolv.conf.sv is a saved older version of your /etc/resolv.conf file. It would appear that 192.168.0.1 (which is your Devil Linux box) is not running a name server or is not answering queries from your Linux workstation. I would further guess that your W2K AS and WXP systems do not list the Devil Linux box as a name server and that the other nameservers (212.116.158.x) are also invalid. You can confirm this by the following command (under Linux): dig @192.168.0.1 www.yahoo.com which I expect to fail. Next try: dig @212.116.158.130 www.yahoo.com and: dig @212.116.158.133 www.yahoo.com You may find that those work. If they do, delete the line referring to 192.168.0.1 from /etc/resolv.conf. If they do not, you must find an appropriate name server to use. Determine which one(s) your W2K and WXP systems are using. (Hint: run 'ipconfig /all'.) Under Linux, ensure that they are listed as the nameservers in /etc/resolv.conf. Another possibillity is that your Linux workstation configurations (not Devil Linux) are blocking UDP port 53 (name service) so your queries are not getting out to their servers. Let us know if this resolves (pun intended) the problem or if it sheds any new light on the matter. -- 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." -- Newt Gingrich |