networking / shared static internet connection

Posts: 16
i have Mepis 6.0 installed on computer with two nic cards. one is for the internet ( dsl ) the other is for Home network that is plugged into a Linksys 16 port switch.
i have two other puters and two printers. from MY computer i can ping the server but from the server i cant ping mine?? i can even ping one one my printers.
I dont know anything about networking but have exhausted my resourses in reading and now am more confused than when i started.
the server has a static ip that i want to share with the other machines. i had done this with Gentoo but am having a time with it in Mepis.PLEASE if anyone can help let me know. right now for me and my wife to share the internet one has to be offline and my web pages are none existant untill i get it up and running.
-------------------------------------------------------------------------------
root@1[~]# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 * 255.255.255.0 U 0 0 0 eth0
192.168.0.0 * 255.255.255.0 U 0 0 0 eth1
207.70.159.0 * 255.255.255.0 U 0 0 0 eth0
default etex-adsl254.et 0.0.0.0 UG 0 0 0 eth0
---------------------------------------------------------------------------------
root@1[~]# ifconfig
eth0 Link encap:Ethernet HWaddr 00:12:17:57:E0:19
inet addr:207.70.159.71 Bcast:192.168.0.254 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:578983 errors:0 dropped:0 overruns:0 frame:0
TX packets:365873 errors:97 dropped:0 overruns:0 carrier:97
collisions:0 txqueuelen:1000
RX bytes:843152042 (804.0 MiB) TX bytes:29015526 (27.6 MiB)
Interrupt:185 Base address:0xe100
eth1 Link encap:Ethernet HWaddr 00:02:E3:17:5C:31
inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:6024 errors:0 dropped:0 overruns:0 frame:0
TX packets:146805 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1197996 (1.1 MiB) TX bytes:6730164 (6.4 MiB)
Interrupt:193 Base address:0x2000
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:127813 errors:0 dropped:0 overruns:0 frame:0
TX packets:127813 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:10114341 (9.6 MiB) TX bytes:10114341 (9.6 MiB)
---------------------------------------------------------------------------------
# /etc/hosts.allow: list of hosts that are allowed to access the system.
# See the manual pages hosts_access(5), hosts_options(5)
# and /usr/doc/netbase/portmapper.txt.gz
#
# Example: ALL: LOCAL @some_netgroup
# ALL: .foobar.edu EXCEPT terminalserver.foobar.edu
#
# If you're going to protect the portmapper use the name "portmap" for the
# daemon name. Remember that you can only use the keyword "ALL" and IP
# addresses (NOT host or domain names) for the portmapper. See portmap(
# and /usr/doc/netbase/portmapper.txt.gz for further information.
#
-----------------------------------------------------------------------------
# /etc/inetd.conf: see inetd(
for further informations.
#
# Internet server configuration database
#
#
# Lines starting with "#:LABEL:" or "#
# be changed unless you know what you are doing!
#
# If you want to disable an entry so it isn't touched during
# package updates just comment it out with a single '#' character.
#
# Packages should modify this file by using update-inetd(
#
#
#
#:INTERNAL: Internal services
#echo stream tcp nowait root internal
#echo dgram udp wait root internal
#chargen stream tcp nowait root internal
#chargen dgram udp wait root internal
#discard stream tcp nowait root internal
#discard dgram udp wait root internal
#daytime stream tcp nowait root internal
#daytime dgram udp wait root internal
#time stream tcp nowait root internal
#time dgram udp wait root internal
#:STANDARD: These are standard services.
#:BSD: Shell, login, exec and talk are BSD protocols.
#:MAIL: Mail, news and uucp services.
#:INFO: Info services
#:BOOT: Tftp service is provided primarily for booting. Most sites
# run this only on machines acting as "boot servers."
#:RPC: RPC based services
#:HAM-RADIO: amateur-radio services
#:OTHER: Other services
#
printer stream tcp nowait lp /usr/lib/cups/daemon/cups-lpd cups-lpd
vboxd stream tcp nowait root /usr/sbin/tcpd /usr/sbin/vboxd
===========================================================================
Im sending some of the stuff you might need if you need anything else PLEASE let me know. THANKS for you SUPPORT
Terry

My static ip is
Posts: 16
My static ip is 207.70.159.71 from my ip provider and the gateway is from my provider also 207.70.159.254. thats why any sugguestions?
ip 207.70.159.71
gw 207.70.159.254

Does your router only have a single ethernet port?
Posts: 959
If it does, may I suggest replacing it with a multi-port your single port router and all of the other computers. That way, the router will take care of all local addresses.
In the meantime, edit your /etc/samba/smb.conf as I have specified above and your mepis machine should allow traffic from the 207 address. Leave it to your router to take care of the firewalling. If you suspect an intrusion attempt, then that is beyond my scope.
I've got to get to work now, it's early monday morning here right now.
Mike P
-------------------
Life may not be the party we thought, but while we're here, we may as well dance.
Break M$'s shackles from your feet and free yourself with Mepis

thanks
Posts: 16
No i have a modem single port that i pulg into my nic card, then out of the second card plug into a switch ( 16 port Linksys Switch ) that all other stuff on the network plugs into. all is hard wired and nothing is wireless.
My static ip is 207.70.159.71 mask 255.255.255.0 gw 207.70.159.254 that is how i get on the net.
===============================================
root@1[~]# lspci
0000:00:00.0 Host bridge: VIA Technologies, Inc. K8M800 Host Bridge
0000:00:00.1 Host bridge: VIA Technologies, Inc. K8M800 Host Bridge
0000:00:00.2 Host bridge: VIA Technologies, Inc. K8M800 Host Bridge
0000:00:00.3 Host bridge: VIA Technologies, Inc. K8M800 Host Bridge
0000:00:00.4 Host bridge: VIA Technologies, Inc. K8M800 Host Bridge
0000:00:00.7 Host bridge: VIA Technologies, Inc. K8M800 Host Bridge
0000:00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI bridge [K8T800/K8T890 South]
0000:00:08.0 VGA compatible controller: ATI Technologies Inc Rage XL (rev 65)
0000:00:09.0 Ethernet controller: Linksys NC100 Network Everywhere Fast Ethernet 10/100 (rev 11)
0000:00:0a.0 Ethernet controller: National Semiconductor Corporation DP83815 (MacPhyter) Ethernet Controller
0000:00:0f.0 RAID bus controller: VIA Technologies, Inc. VIA VT6420 SATA RAID Controller (rev 80)
0000:00:0f.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
0000:00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
0000:00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
0000:00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
0000:00:10.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
0000:00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 86)
0000:00:11.0 ISA bridge: VIA Technologies, Inc. VT8237 ISA bridge [KT600/K8T800/K8T890 South]
0000:00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 60)
0000:00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
0000:00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
0000:00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
0000:00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
0000:01:00.0 VGA compatible controller: VIA Technologies, Inc. S3 Unichrome Pro VGA Adapter (rev 01)
============================================
i cant use a router on my ip provider, only this modem....
Good luck at work today. Thanks Again

I think what's being
Posts: 1634
I think what's being implicitly said is this:
Put a hardwired router between the modem and the rest of the network.
DSL --> DSL MODEM --> Router --> Switch (if needed) --> All Computers
The router can be configured to have a public IP address of 207.70.159.71 with a subnet mask of 255.255.255.0, talking to a gateway at 207.70.159.254. You'll also have to add the DNS addresses to the router configs.
That kind of setup is a bit more scalable and resilient, and a lot less hassle (or so it would seem) than what you're dealing with now.
My occupation?
Well, computer geek-stuff, mostly. I could tell you all about it; but, then I would have to delete you.

They isp said there isint a
Posts: 16
They isp said there isint a router that can be used on the service. i even have went down to a local computer supply that knows about there system. Seems that the dsl that im on is really a lan......??? this is getting way over my head now. i like Mepis and have used it for over 2 years on my personal pc but never as a server. I want to use it but i must say if i cant get it up and going pretty soon i will have to revert back to Gentoo. which takes 3 days to install. So please help!!!!!
Thanks in advance

Quote:They isp said there
Posts: 1634
They isp said there isint a router that can be used on the service.
My first reaction was that they would be the first I've heard of, with that kind of limitation on their system; and you're setting-up a router on the Linux-based system anyway; but, knowing that I've heard of stranger things in the past, I went-ahead and called the ETEX Tel-Coop tech support line.
They assure me that you will have no problem using the firmware router I pointed you toward, as long as you configure the router with the information you've already given us, and set up all your computers to use DHCP to obtain an IP address from the router itself.
They mentioned that they would be more than happy to help with configuring a router to function correctly with their modem, if you give 'em a call during business hours: 1-800-421-0731.
The guy I spoke with seemed to be very familiar with the Linksys router model line, which is a big plus, as compared to the DSL tech support folks in our neck of the woods. It certainly beats feeling like you're shooting in the dark.
My occupation?
Well, computer geek-stuff, mostly. I could tell you all about it; but, then I would have to delete you.

WOW!!!!!!!!!!!!!!it must
Posts: 16
WOW!!!!!!!!!!!!!!
it must seem that you have to get ahold of the right person!! Today im on my way to get this router!!! Thanks a BUNCH!! Lets hope this works. Im at my wits end here. I myself even talked to the people at Etex... owell im off to get a router and try to set this up .
AGAIN THANKS!!!!!!
I will update ya.
O btw they just told me that they dont support Linux........
so i hope you can help me set this up when i get it .

Quote:...you have to get
Posts: 1634
...you have to get ahold of the right person...
That's the general rule in talking with tech-support/help desk types. I usually ask for the Level 3 tech who uses Slackware, before even going into any description of the problem--because if I could solve it myself, I wouldn't be calling them.
I usually get good service out of our DSL folks because of it.
...btw they just told me that they dont support Linux
{laughing} Neither does VerizonOnLine, and we've been using their DSL for something like 4 years now. When we first signed-up for DSL with them, they didn't support routers either, if you can believe that.
Over that 4 (or so) year time-frame, we've had 4 instances where I've had to call:
Once because they had a screwed-up router interface five hops from us, once because they screwed-up our residential move order, twice to confirm that they had an outage associated with our local CO.
Not once was the fact that we run Linux germane to the situation at hand.
The thing to keep in mind is this:
They support getting DSL tone to your modem, and making sure that your modem can talk with the DSLAM at their office. Beyond that, they really don't support much else.
The only involvement they should have with any OS you might be using, would be a familiarity with the tools that you would use to do a bit of networking diagnostics from your end, when you are on the phone with you.
If they don't know the Linux tool set, they can't help you, and that seems to be the majority case. It's just easier for them to say that don't support Linux, as if it's your fault; instead of their fault for not knowing the tools available to your OS environment.
My occupation?
Well, computer geek-stuff, mostly. I could tell you all about it; but, then I would have to delete you.

Router
Posts: 16
Ok router up and running!!!!!!!!!!!!!!!!!
everything online now. i just have to fugure out how to get to my web pages or let others get to the web pages....lol
I thank you so much for the advice! Doing the modem-router-switch-pc's, printers...ect works great and was VERY easy to set up with the browser interface! and at Wally World was very cheap. Now just to learn how to let it see my Apache and Gallery stuff.
Again Thanks

The easy part is a definite
Posts: 1634
The easy part is a definite plus, as well as the added SPI/NAT firewall features.
If you're running a server on the inside, you should be able to port forward to that machine without a problem.
If you ever happen to bump into Shawn, of ETEX, tell him that I said, "Thanks!"
My occupation?
Well, computer geek-stuff, mostly. I could tell you all about it; but, then I would have to delete you.
I might be wrong, but this may help
Posts: 959
It appears that somewhere along the line, you are either using a non-standard ip address or you have one automatically assigned that is a non standard address.
inet addr:207.70.159.71 Bcast:192.168.0.254 Mask:255.255.255.0
The output from ifconfig shows your eth0 has an address of 207.70.159.71 and that you're using a broadcast address of 192.168.0.254, which probably comes directly from your router.
While this may work in terms of traffic flowing out, if you want to enable access to your mepis box from other computers in the network, you'll need to edit your /etc/samba/smb.conf and add 207.70.159. to the hosts allow = line.
Now a word of caution. If this non-standard address is being automatically assigned and it moves outside of the range of the first 3 blocks of numbers, the same thing will happen again. Why do you use this range and why have an ip address that is totally different to your broadcast address?
Mike P
--------------------
Life may not be the party we thought, but while we're here, we may as well dance.
Break M$'s shackles from your feet and free yourself with Mepis