Sponsored Content
Full Discussion: Modem sharing
Top Forums UNIX for Dummies Questions & Answers Modem sharing Post 32428 by WIntellect on Monday 25th of November 2002 04:25:20 PM
Old 11-25-2002
Having done this on my FreeBSD server - and home LAN, the principles are:

(1) Your SCO server must be made a gateway; this requires NAT (Network Address Translation) so that it can forward unknown packets to the ISP it's connected to.

(2) The PCs on the LAN will then need to have the server IP address configured as their "default gateway/router"; and the ISP's DNS IP address(es) configured too.

Hope this helps!
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Modem on HP-UX 10.20

Hi everyone I am having some real difficulties getting a dial in modem to work on one of my HP boxes. It's a mux modem on port 7 which I have set up at 9600 baud. I can dial in, the handshakes are completed, but then it returns incoherent characters on the emulation screen. I think my dial in... (1 Reply)
Discussion started by: alwayslearningunix
1 Replies

2. UNIX for Advanced & Expert Users

Modem

I've spent enough time trying to put on work Lucent Winmodem in my armada M300 (compaq laptop) I use Mandrake 8.0 but as soon as i get connected and prompmts appears modem shutsdown. Does any one had a similar situation, solved it? cheers (2 Replies)
Discussion started by: alex blanco
2 Replies

3. UNIX for Dummies Questions & Answers

Modem problem: "Sorry, modem is busy"

Hi! I have a little prob with dialing up to the internet... When I try connect, it says "Sorry, modem is busy"... Specs: Laptop 56K modem Slackware 8.0 Kernel 2.4.5 Cheers;) (4 Replies)
Discussion started by: satan404
4 Replies

4. UNIX for Dummies Questions & Answers

Modem

Pleaseee... Helpppp.... !!! I am using SCO Open Server 5.05. Recently, i have upgraded the system which means transfer all apps and data to the new system. Everything work well except one thing. On my old system i have an external modem which to dial out. Now that i use the same modem on... (4 Replies)
Discussion started by: jackpotp
4 Replies

5. UNIX for Dummies Questions & Answers

modem

I have got Suse 8.0 by using a modem (US Robotics 56K Faxmodem Ext). During connection i got the error 16. I tried it under RedHat and Mandrake too.....same problem. What can i do ? Thanx...a lot... Logfile: SuSE Meta pppd (smpppd), Version 0.73 on zuhause. wwwoffle not is running ... (1 Reply)
Discussion started by: Pennywize
1 Replies

6. UNIX for Dummies Questions & Answers

Modem - Test /dev/modem

Ok. I tried following the directions from some of the other threads, but I've hit a road block. I have red hat 7.3 and I installed the hcf package: hcfpcimodem-0.99lnxtbeta03042700k2.4.18_3-1rh.i386.rpm It installed ok, no errors, but I still can't get linux to find my modem. I've tried... (2 Replies)
Discussion started by: lawadm1
2 Replies

7. HP-UX

Modem issue in HP-UX

Hi, I'v got a Hayes modem which is connected to my HP-UX 10.20 Server by the Mux. I tried to connect to the modem using cu command in unix but all in vain. How will i know my modem is in working state. I configured the modem using sam and i think the setting are correct. Can anybody help... (1 Reply)
Discussion started by: Hanwant
1 Replies

8. Solaris

Is the cable you are using a null modem cable or a modem cable

Hi all, Is there any difference between a null modem cable or a modem cable ? i assume that a null modem cable is a normal cable that i used from cpu serial ports to a modem for dialup. please correct if i am wrong, thks (2 Replies)
Discussion started by: waterbear
2 Replies

9. IP Networking

sharing of IP address for load sharing avoiding virtual server & redirection machine

I have RedHat 9.0 installed on three of my servers (PIII - 233MHz) and want that they share a common IP address so that any request made reaches each of the servers. Can anyone suggest how should I setup my LAN. I'm new to networking in Linux so please elaborate and would be thankful for a timely... (2 Replies)
Discussion started by: Rakesh Ranjan
2 Replies

10. Solaris

Modem

hi folks, i am looking for a analog modem to use it with a solaris9 sparc mashine. as far as i know, solaris communicates with the modem using AT-commands. so do i need a special modem for solaris or just a modem? i am open for everything. PCI-modem, seriell modem, usb modem. what are you using? i... (1 Reply)
Discussion started by: pressy
1 Replies
SHOREWALL6-PROVIDER(5)						  [FIXME: manual]					    SHOREWALL6-PROVIDER(5)

NAME
providers - Shorewall6 Providers file SYNOPSIS
/etc/shorewall6/providers DESCRIPTION
This file is used to define additional routing tables. You will want to define an additional table if: o You have connections to more than one ISP or multiple connections to the same ISP o You run Squid as a transparent proxy on a host other than the firewall. o You have other requirements for policy routing. Each entry in the file defines a single routing table. If you wish to omit a column entry but want to include an entry in the next column, use "-" for the omitted entry. The columns in the file are as follows. NAME - name The provider name. Must be a valid shell variable name. The names 'local', 'main', 'default' and 'unspec' are reserved and may not be used as provider names. NUMBER - number The provider number -- a number between 1 and 15. Each provider must be assigned a unique value. MARK (Optional) - value A FWMARK value used in your shorewall6-tcrules(5)[1] file to direct packets to this provider. If HIGH_ROUTE_MARKS=Yes in shorewall6.conf(5)[2], then the value must be a multiple of 256 between 256 and 65280 or their hexadecimal equivalents (0x0100 and 0xff00 with the low-order byte of the value being zero). Otherwise, the value must be between 1 and 255. Each provider must be assigned a unique mark value. This column may be omitted if you don't use packet marking to direct connections to a particular provider. DUPLICATE - routing-table-name The name of an existing table to duplicate to create this routing table. May be main or the name of a previously listed provider. You may select only certain entries from the table to copy by using the COPY column below. INTERFACE - interface The name of the network interface to the provider. Must be listed in shorewall6-interfaces(5)[3]. GATEWAY - {-|address|detect} The IP address of the provider's gateway router. You can enter "detect" here and Shorewall6 will attempt to detect the gateway automatically. For PPP devices, you may omit this column. OPTIONS (Optional) - [-|option[,option]...] A comma-separated list selected from the following. The order of the options is not significant but the list may contain no embedded whitespace. balance Added in Shorewall 4.4.25. Causes a default route to this provider's gateway to be added to the main routing table (USE_DEFAULT_RT=No) or to the balance routing table (USE_DEFAULT_RT=Yes). At most one provider can specify this option. fallback Added in Shorewall 4.4.25. Causes a default route to this provider's gateway to be added to the default routing table.At most one provider can specify this option. track If specified, inbound connections on this interface are to be tracked so that responses may be routed back out this same interface. You want to specify track if internet hosts will be connecting to local servers through this provider. Beginning with Shorewall 4.4.3, track defaults to the setting of the TRACK_PROVIDERS option in shorewall6.conf[4] (5). If you set TRACK_PROVIDERS=Yes and want to override that setting for an individual provider, then specify notrack (see below). loose Shorewall6 normally adds a routing rule for each IP address on an interface which forces traffic whose source is that IP address to be sent using the routing table for that interface. Setting loose prevents creation of such rules on this interface. notrack Added in Shorewall 4.4.3. When specified, turns off track. optional (deprecated for use with providers that do not share an interface) If the interface named in the INTERFACE column is not up and configured with an IPv4 address then ignore this provider. If not specified, the value of the optional option for the INTERFACE in shorewall6-interfaces(5)[3] is assumed. Use of that option is preferred to this one, unless an address is provider in the INTERFACE column. src=source-address Specifies the source address to use when routing to this provider and none is known (the local client has bound to the 0 address). May not be specified when an address is given in the INTERFACE column. If this option is not used, Shorewall6 substitutes the primary IP address on the interface named in the INTERFACE column. mtu=number Specifies the MTU when forwarding through this provider. If not given, the MTU of the interface named in the INTERFACE column is assumed. tproxy Added in Shorewall 4.5.4. Used for supporting the TPROXY action in shorewall-tcrules(5). See http://www.shorewall.net/Shorewall_Squid_Usage.html. When specified, the MARK, DUPLICATE and GATEWAY columns should be empty, INTERFACE should be set to 'lo' and tproxy should be the only OPTION. Only one tproxy provider is allowed. COPY - [{none|interface[,interface]...}] A comma-separated list of other interfaces on your firewall. Wildcards specified using an asterisk ("*") are permitted (e.g., tun* ). Usually used only when DUPLICATE is main. Only copy routes through INTERFACE and through interfaces listed here. If you only wish to copy routes through INTERFACE, enter none in this column. EXAMPLES
Example 1: You run squid in your DMZ on IP address 2002:ce7c:92b4:1::2. Your DMZ interface is eth2 #NAME NUMBER MARK DUPLICATE INTERFACE GATEWAY OPTIONS Squid 1 1 - eth2 2002:ce7c:92b4:1::2 - Example 2: eth0 connects to ISP 1. The ISP's gateway router has IP address 2001:ce7c:92b4:1::2. eth1 connects to ISP 2. The ISP's gateway router has IP address 2001:d64c:83c9:12::8b. eth2 connects to a local network. #NAME NUMBER MARK DUPLICATE INTERFACE GATEWAY OPTIONS COPY ISP1 1 1 main eth0 2001:ce7c:92b4:1::2 track eth2 ISP2 2 2 main eth1 2001:d64c:83c9:12::8b track eth2 FILES
/etc/shorewall6/providers SEE ALSO
http://shorewall.net/MultiISP.html http://shorewall.net/configuration_file_basics.htm#Pairs shorewall6(8), shorewall6-accounting(5), shorewall6-actions(5), shorewall6-blacklist(5), shorewall6-hosts(5), shorewall6-interfaces(5), shorewall6-maclist(5), shoewall6-netmap(5),shorewall6-params(5), shorewall6-policy(5), shorewall6-rtrules(5), shorewall6-routestopped(5), shorewall6-rules(5), shorewall6.conf(5), shorewall6-secmarks(5), shorewall6-tcclasses(5), shorewall6-tcdevices(5), shorewall6-tcrules(5), shorewall6-tos(5), shorewall6-tunnels(5), shorewall6-zones(5) NOTES
1. shorewall6-tcrules(5) http://www.shorewall.net/manpages6/shorewall6-tcrules.html 2. shorewall6.conf(5) http://www.shorewall.net/manpages6/shorewall6.conf.html 3. shorewall6-interfaces(5) http://www.shorewall.net/manpages6/shorewall6-interfaces.html 4. shorewall6.conf http://www.shorewall.net/manpages6/shorwewall6.conf.html [FIXME: source] 06/28/2012 SHOREWALL6-PROVIDER(5)
All times are GMT -4. The time now is 02:00 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy