This is a discussion on HELP my last chance to keep my job HELP within the Linux Networking forums, part of the Linux Forums category; I've posted here before and thanks to all for your help. my boss tells me that I have one ...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
I've posted here before and thanks to all for your help.
my boss tells me that I have one last chance to get this working or I must hit the want adds on Friday: so here we go::: the computer in question has a ppp connection (ip 203.88.230.11) to the internet and a eth0 connection (ip 203.88.230.129) to another two specialty devices (ip's 203.88.230.130 and next 230.88.230.131) I can ping from inside the computer in to A. the internet, B. both specialty devices. Form out side I can trace/ping to both the ppp connection and the eth0 connection. but I can't trace or ping to ether of the other ones. my routing table looks like this at present: Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 203.88.255.241 0.0.0.0 255.255.255.255 UH 40 0 0 ppp0 203.88.230.0 203.88.230.129 255.255.255.0 UG 40 0 0 eth0 203.88.230.0 203.88.230.11 255.255.255.0 UG 40 0 0 ppp0 203.88.230.0 0.0.0.0 255.255.255.0 U 40 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 40 0 0 lo 0.0.0.0 203.88.230.11 0.0.0.0 UG 40 0 0 ppp0 can any one tell me what "route add" line I can enter to at least get it running so I don't get fired, I can make it permanent once I get it working. Thank you in advance. Robert |
|
|||
|
"Grendell" <tarl@cyber.net.au> wrote in
news:OWAgb.140380$bo1.58470@news-server.bigpond.net.au: > I've posted here before and thanks to all for your help. > > my boss tells me that I have one last chance to get this working or I > must hit the want adds on Friday: > > so here we go::: > > the computer in question has a ppp connection (ip 203.88.230.11) to > the internet and a eth0 connection (ip 203.88.230.129) to another two > specialty devices (ip's 203.88.230.130 and next 230.88.230.131) > > I can ping from inside the computer in to A. the internet, B. both > specialty devices. > Form out side I can trace/ping to both the ppp connection and the eth0 > connection. > but I can't trace or ping to ether of the other ones. > > my routing table looks like this at present: > > Kernel IP routing table > Destination Gateway Genmask Flags MSS Window > irtt Iface > 203.88.255.241 0.0.0.0 255.255.255.255 UH 40 0 > 0 ppp0 > 203.88.230.0 203.88.230.129 255.255.255.0 UG 40 0 > 0 eth0 > 203.88.230.0 203.88.230.11 255.255.255.0 UG 40 0 > 0 ppp0 > 203.88.230.0 0.0.0.0 255.255.255.0 U 40 0 > 0 eth0 > 127.0.0.0 0.0.0.0 255.0.0.0 U 40 0 > 0 lo 0.0.0.0 203.88.230.11 0.0.0.0 UG 40 0 > 0 ppp0 > > can any one tell me what "route add" line I can enter to at least get > it running so I don't get fired, I can make it permanent once I get it > working. > > Thank you in advance. > > Robert > > > The first question I would have is, are the two 'specialty' devices supposed to have public IP address, or did you simply arbitrarily pick a couple of numbers for them? If they truely are assigned those two public IP addresses, where are the routers that serve those addresses? Does the upstream router send packes to 203.88.230.129, 203.88.230.130, and 203.88.230.131 down the same line as to 203.88.230.11? |
|
|||
|
"Mark Taylor" <mtaylorx@xlrim.com> wrote in message news:Xns940D712D4C981mtaylorxxlrimcom@66.170.196.2 49... > > The first question I would have is, are the two 'specialty' devices > supposed to have public IP address, or did you simply arbitrarily pick a > couple of numbers for them? Yes there are supposed to have public IP address, these where assigned by the ISP we connect thru >If they truely are assigned those two public > IP addresses, where are the routers that serve those addresses? Does the > upstream router send packes to 203.88.230.129, 203.88.230.130, and > 203.88.230.131 down the same line as to 203.88.230.11? again yes all are being routed to 203.88.230.11 by the ISP, this was the first thin I checked. The trouble is in our routeing table though I can't see it my self. Robert |
|
|||
|
On Tue, 07 Oct 2003 15:26:38 GMT, Grendell <tarl@cyber.net.au> wrote:
> I've posted here before and thanks to all for your help. > > my boss tells me that I have one last chance to get this working or I must > hit the want adds on Friday: > > so here we go::: > > the computer in question has a ppp connection (ip 203.88.230.11) to the > internet and a eth0 connection (ip 203.88.230.129) to another two specialty > devices (ip's 203.88.230.130 and next 230.88.230.131) > my routing table looks like this at present: > > Kernel IP routing table > Destination Gateway Genmask Flags Iface > 203.88.255.241 0.0.0.0 255.255.255.255 UH ppp0 > 203.88.230.0 203.88.230.129 255.255.255.0 UG eth0 > 203.88.230.0 203.88.230.11 255.255.255.0 UG ppp0 > 203.88.230.0 0.0.0.0 255.255.255.0 U eth0 > 127.0.0.0 0.0.0.0 255.0.0.0 U lo > 0.0.0.0 203.88.230.11 0.0.0.0 UG ppp0 My guess is that you didn't turn IP forwarding on. This should "work", even though it probably isn't right. Let's go through it. First, where did you get these addresses? I'm hoping you got them from an ISP called "Rivers Network" rather than just having made them up. Also, are they part of a block, or is this all there is? If they are part of a block, whoever gave them to you would have mentioned something about netmasks. Here's what you need to do: 1. Put a proper netmask on eth0. If you only have three addresses, and they are part of a block, the netmask is probably 255.255.255.248, which gives you 129-135 on eth0, network of 128 and broadcast of 136. That will change this entry: 203.88.230.0 203.88.230.129 255.255.255.0 eth0 To this: 203.88.230.128 203.88.230.129 255.255.255.248 eth0 However, if these addresses are "loose", not part of a block, then you might instead want to set up two host routes, one for 130 and one for 131, with 129 as the gateway. All would have a netmask of 255. That would give you: 203.88.230.130 203.88.230.129 255.255.255.255 eth0 203.88.230.131 203.88.230.129 255.255.255.255 eth0 Just doing a mask of 255.255.255.0 as you have done will probably "work" in this case, but is likely to make neighboring addresses unreachable. For instance, if someone else has 203.88.230.134 and you've got a mask of 255.255.255.0, you won't be able to talk to them because your router will assume that they are on your own network. Maybe you don't care. 2. Remove the entry that says 203.88.230.11 is the gateway for 203.88.230.0. It isn't, from the router's point of view. 3. Make 203.88.230.11 the default gateway for your router, which seems to already be the case. You might want to think about fixing the netmask on that interface as well. 4. Make 203.88.230.129 the default gateway on both of the other computers / devices / whatever. Make sure they have the correct netmasks and such. 5. Make sure IP forwarding is on. Most of the time it is off by default nowadays. "echo 1 > /proc/sys/net/ipv4/ip_forward". 6. Temporarily disable any firewall rules you or your distro maker have put in. Now you've got eth0 and ppp0 on different networks. You've got forwarding turned on. Your firewall is (temporarily) disabled. You should be all set. -- -| Bob Hauck -| To Whom You Are Speaking -| http://www.haucks.org/ |
|
|||
|
On Tue, 07 Oct 2003 15:26:38 GMT, Grendell <tarl@cyber.net.au> wrote:
> I've posted here before and thanks to all for your help. > > my boss tells me that I have one last chance to get this working or I must > hit the want adds on Friday: > > so here we go::: > > the computer in question has a ppp connection (ip 203.88.230.11) to the > internet and a eth0 connection (ip 203.88.230.129) to another two specialty > devices (ip's 203.88.230.130 and next 230.88.230.131) > > I can ping from inside the computer in to A. the internet, B. both specialty > devices. > Form out side I can trace/ping to both the ppp connection and the eth0 > connection. > but I can't trace or ping to ether of the other ones. > > my routing table looks like this at present: > > Kernel IP routing table > Destination Gateway Genmask Flags MSS Window irtt > Iface > 203.88.255.241 0.0.0.0 255.255.255.255 UH 40 0 0 > ppp0 > 203.88.230.0 203.88.230.129 255.255.255.0 UG 40 0 0 > eth0 > 203.88.230.0 203.88.230.11 255.255.255.0 UG 40 0 0 > ppp0 > 203.88.230.0 0.0.0.0 255.255.255.0 U 40 0 0 > eth0 > 127.0.0.0 0.0.0.0 255.0.0.0 U 40 0 0 lo > 0.0.0.0 203.88.230.11 0.0.0.0 UG 40 0 0 > ppp0 > > can any one tell me what "route add" line I can enter to at least get it > running so I don't get fired, I can make it permanent once I get it working. I think I answered this in another newsgroup or post (although, your post there may not have had as many details). Your routing is all mixed up. For one thing, your default gw loops back yourself. It's gateway should be remote ppp0 IP 203.88.255.241. You also loop all other 203.88.230.0/24 network traffic back to your own eth0 IP. Your network on eth0 should not have ANY gw specified (gw should be 0.0.0.0). Apparently you need to learn how routing for non-Windows systems is different from Windows routing. In Linux, a gw is either NOT specified for a local directly connected network/host (LAN route), or a local remote IP for any non-local network (WAN route that goes through another router, or internet route). It is very unlikely that you would ever use your own IP as gw (maybe for some special loopback network testing or simulation). This is my best guess of what your routing should look like, without knowing what your netmask should be for the extra IPs that Rivernet routes to you: Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 203.88.255.241 0.0.0.0 255.255.255.255 UH 40 0 0 ppp0 203.88.230.0 0.0.0.0 255.255.255.0 U 40 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 40 0 0 lo 0.0.0.0 203.88.255.241 0.0.0.0 UG 40 0 0 ppp0 Or if they ONLY route those other 2 IPs to your ppp0 IP instead of a network (no netmask): 203.88.255.241 0.0.0.0 255.255.255.255 UH 40 0 0 ppp0 203.88.230.130 0.0.0.0 255.255.255.255 H 40 0 0 eth0 203.88.230.131 0.0.0.0 255.255.255.255 H 40 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 40 0 0 lo 0.0.0.0 203.88.255.241 0.0.0.0 UG 40 0 0 ppp0 -- David Efflandt - All spam ignored http://www.de-srv.com/ http://www.autox.chicago.il.us/ http://www.berniesfloral.net/ http://cgi-help.virtualave.net/ http://hammer.prohosting.com/~cgi-wiz/ |
|
|||
|
"Grendell" <tarl@cyber.net.au> wrote in message news:OWAgb.140380$bo1.58470@news-server.bigpond.net.au... > I've posted here before and thanks to all for your help. > > my boss tells me that I have one last chance to get this working or I must > hit the want adds on Friday: > > so here we go::: > > the computer in question has a ppp connection (ip 203.88.230.11) to the > internet and a eth0 connection (ip 203.88.230.129) to another two specialty > devices (ip's 203.88.230.130 and next 230.88.230.131) > > I can ping from inside the computer in to A. the internet, B. both specialty > devices. > Form out side I can trace/ping to both the ppp connection and the eth0 > connection. > but I can't trace or ping to ether of the other ones. > > my routing table looks like this at present: > > Kernel IP routing table > Destination Gateway Genmask Flags MSS Window irtt > Iface > 203.88.255.241 0.0.0.0 255.255.255.255 UH 40 0 0 > ppp0 > 203.88.230.0 203.88.230.129 255.255.255.0 UG 40 0 0 > eth0 > 203.88.230.0 203.88.230.11 255.255.255.0 UG 40 0 0 > ppp0 > 203.88.230.0 0.0.0.0 255.255.255.0 U 40 0 0 > eth0 > 127.0.0.0 0.0.0.0 255.0.0.0 U 40 0 0 lo > 0.0.0.0 203.88.230.11 0.0.0.0 UG 40 0 0 > ppp0 > > can any one tell me what "route add" line I can enter to at least get it > running so I don't get fired, I can make it permanent once I get it working. You should always check that the kernel has been told to allow forwarding, check the firewalling doesnt have any rules that limit things to working with the ethernet ... If you leave the netmask's like this it can be made to work * You need set to set the pppd to proxy-arp the ppp links. because the ppp links have ip addresses in the same range as the ethernet, other computers on the ethernet assume them to be on the ethernet and send out arp requests ... which dont get answered. proxy arp tells your linux server to answer these requests with the fake ethernet address of the server. The linux server then routes the packets on. * You give up any hope of reaching any other 203.88.230.* addresses not on your Lan or PPP links. I assume this is ok. they may be your addresses, maybe other clients of the same ISP. If you change netmasks, you can subnet, make the LAN a subnet, put the ppp addresses onto a different subnet, and then you dont have to worry about proxy arp. But to change netmask you have to change the netmask on all systems on the ethernet., and it reduces the max number of hosts on your ethernet (unless you want to run a router and dual networks on the one lan ! which is doable but.. ) |