SuSE can't chew gum & walk
(1)I have kppp set up w/DNS addresses for my ISP, along w/phone# and other parameters. It works fine. (2)As long as I have eth0 set up for dhcp & have my ISP's DNS addresses in the lookup list, ppp0 continues to work just fine. (3)If I have eth0 set up for the local network using dhcp & the lookup set for my network (192.168.0.1) it doesn't work, whether or not ppp0 is active. (4)If I have eth0 set up for the local network using a static 192.168.0.10 & the lookup set for 192.168.0.1 eth0 works just fine w/the LAN & ppp0 will connect, but there is absolutely no modem throughput. The hub lights flash when I attempt to access the internet, and 'ip forwarding' is turned off. Now-then, I like SuSE just fine in lots of respects but the fact that it won't do what M$ Windoze does readily is beyond my comprehension. I can only believe that there must be *something* I'm missing, but I cannot figure out what! Any help really appreciated!! ...CH
måndag 23 februari 2004 21:05 skrev C Hamel:
(1)I have kppp set up w/DNS addresses for my ISP, along w/phone# and other parameters. It works fine.
all you need.
(2)As long as I have eth0 set up for dhcp & have my ISP's DNS addresses in the lookup list, ppp0 continues to work just fine.
What lookup list?
(3)If I have eth0 set up for the local network using dhcp & the lookup set for my network (192.168.0.1) it doesn't work, whether or not ppp0 is active.
Do you mean DNS lookup? You don't setup your DNS to point to your own box, unless you've setup a DNS server on it. You have it remain as your ISP's in all other cases.
(4)If I have eth0 set up for the local network using a static 192.168.0.10 & the lookup set for 192.168.0.1 eth0 works just fine w/the LAN & ppp0 will connect, but there is absolutely no modem throughput. The hub lights flash when I attempt to access the internet, and 'ip forwarding' is turned off.
Lookup setup for 192.168.0.1 eth0? now it sounds like you're talking about the routing table, your not supposed to edit that one by hand. Setting up Linux to work with a network and a dialup is easy as pie. You first, use YaST to configure the network interface and you leave the Gateway address empty, as well as the DNS unless you have a DNS server of your own. Then, you configure the kppp for a dialup according to your ISP's specifications and both will work just fine. If you want your box, to allow other computers on your box to connection through yours to the internet via your dial up ... you use YaST to setup SuSE firewall2 and you specify eth0 as the internal, and ppp0 as the external device.
On Mon, 2004-02-23 at 12:05, C Hamel wrote:
(1)I have kppp set up w/DNS addresses for my ISP, along w/phone# and other parameters. It works fine.
(2)As long as I have eth0 set up for dhcp & have my ISP's DNS addresses in the lookup list, ppp0 continues to work just fine.
(3)If I have eth0 set up for the local network using dhcp & the lookup set for my network (192.168.0.1) it doesn't work, whether or not ppp0 is active.
(4)If I have eth0 set up for the local network using a static 192.168.0.10 & the lookup set for 192.168.0.1 eth0 works just fine w/the LAN & ppp0 will connect, but there is absolutely no modem throughput. The hub lights flash when I attempt to access the internet, and 'ip forwarding' is turned off.
Now-then, I like SuSE just fine in lots of respects but the fact that it won't do what M$ Windoze does readily is beyond my comprehension. I can only believe that there must be *something* I'm missing, but I cannot figure out what!
Any help really appreciated!! ...CH
Think you might want to setting up SuSEFirewall2, not only does it protect your box, but it also does masquerading, worked well for me. Set external device as ppp0 and internal as eth0. By the way, throwing MS into your e-mail may have adverse affect (I ignored it...). Matt
On Monday 23 February 2004 14:44, Matthew Johnson wrote: <SNIP>
Think you might want to setting up SuSEFirewall2, not only does it protect your box, but it also does masquerading, worked well for me. Set external device as ppp0 and internal as eth0.
By the way, throwing MS into your e-mail may have adverse affect (I ignored it...).
Thanks for the reply. :-) Well... I am not on Linux because I 'hate' anyone... I'm on it because it does the job. What it doesn't do, I have to use a competing system. It's no moe complicated than that. <G> Regards... ...CH
* C Hamel (vgm2@sc2000.net) [040223 13:30]:
On Monday 23 February 2004 14:44, Matthew Johnson wrote: <SNIP>
Think you might want to setting up SuSEFirewall2, not only does it protect your box, but it also does masquerading, worked well for me. Set external device as ppp0 and internal as eth0.
By the way, throwing MS into your e-mail may have adverse affect (I ignored it...).
Thanks for the reply. :-)
Well... I am not on Linux because I 'hate' anyone... I'm on it because it does the job. What it doesn't do, I have to use a competing system. It's no moe complicated than that. <G>
Fair enough. But you are on a Linux mailing list so mentioning Microsoft doesn't do .. and getting a cold shoulder for bring up Microsoft without just asking how to do the job you want to do is in bad taste. A few years ago Linux people were so hungry to get people into the fold that those comments made them jump. Today that strategy doesn't work. -- Linux User #147972 ---===--- mailto:ben@whack.org -- "There is no need to teach that stars can fall out of the sky and land on a flat Earth in order to defend religious faith."
C Hamel wrote:
(1)I have kppp set up w/DNS addresses for my ISP, along w/phone# and other parameters. It works fine.
(2)As long as I have eth0 set up for dhcp & have my ISP's DNS addresses in the lookup list, ppp0 continues to work just fine.
(3)If I have eth0 set up for the local network using dhcp & the lookup set for my network (192.168.0.1) it doesn't work, whether or not ppp0 is active.
(4)If I have eth0 set up for the local network using a static 192.168.0.10 & the lookup set for 192.168.0.1 eth0 works just fine w/the LAN & ppp0 will connect, but there is absolutely no modem throughput. The hub lights flash when I attempt to access the internet, and 'ip forwarding' is turned off.
Now-then, I like SuSE just fine in lots of respects but the fact that it won't do what M$ Windoze does readily is beyond my comprehension. I can only believe that there must be *something* I'm missing, but I cannot figure out what!
Try turning off eth0, while using kppp.
On Monday 23 February 2004 14:29, Örn Hansen wrote: <SNIP>
Setting up Linux to work with a network and a dialup is easy as pie. You first, use YaST to configure the network interface and you leave the Gateway address empty, as well as the DNS unless you have a DNS server of your own. Then, you configure the kppp for a dialup according to your ISP's specifications and both will work just fine. If you want your box, to allow other computers on your box to connection through yours to the internet via your dial up ... you use YaST to setup SuSE firewall2 and you specify eth0 as the internal, and ppp0 as the external device.
That is what I was attempting to explain. I did exactly as you stated above --several times-- and each time I can get the modem to connect but there is absolutely no throughput until I put the IP addresses in the 'Host name & name server configuration' list. Then, and *only* then, I get modem throughput ...but then the network is dead. Ditto, if I change the dhcp to static address in 'Network Address Setup'... whether or not I have any IP addresses in the 'Host name...' list. Sorry if I am not completely articulate. I have had no problems setting up networking in the past, though I was not yet using SuSE, either. Now that I am, I cannot get the apparently mutually-dependent eth0 & ppp0 to operate independently. Even the 'ipconfig' output shows this: eth0 Link encap:Ethernet HWaddr 00:0D:9D:89:9C:47 inet addr:192.168.0.10 Bcast:192.168.0.255 Mask:255.255.255.0 inet6 addr: fe80::20d:9dff:fe89:9c47/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:297 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:0 (0.0 b) TX bytes:112074 (109.4 Kb) Interrupt:10 Base address:0x2000 ppp0 Link encap:Point-to-Point Protocol inet addr:204.250.144.61 P-t-P:205.247.108.66 Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1 RX packets:6 errors:0 dropped:0 overruns:0 frame:0 TX packets:6 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:3 RX bytes:71 (71.0 b) TX bytes:77 (77.0 b)
On Monday 23 February 2004 17:41, James Knott wrote: <SNIP>
Now-then, I like SuSE just fine in lots of respects but the fact that it won't do what M$ Windoze does readily is beyond my comprehension. I can only believe that there must be *something* I'm missing, but I cannot figure out what!
Try turning off eth0, while using kppp.
I have tried that, and when I eliminate eth0 the kppp connection is broken. It will log on, but there is absolutely no modem throughput past that: no e-mail, no web, no realplayer streams, nothing. ...CH
C Hamel wrote:
absolutely no throughput until I put the IP addresses in the 'Host name & name server configuration' list. Then, and *only* then, I get modem throughput ...but then the network is dead. Ditto, if I change the dhcp to static address in 'Network Address Setup'... whether or not I have any IP addresses in the 'Host name...' list.
Here are some things I think would help me and maybe others understand the problem. Provide these at a time when you think everything is set up the best you've been able to achieve. -the contents of /etc/resolv.conf -output of 'ip route' -output of 'ip addr' Additionally: -with your ISP's nameservers in place, external DNS lookups will fail when ppp0 is down -if you don't have a DHCP server on your local LAN, you'll need a static IP on eth0 -eth0 and ppp0 should be totally independent with respect to IP addresses; eth0 should be static and ppp0 should be DHCP. -you'd want a route for 192.168.0.0 to be eth0 -you'd want a default route to be ppp0 via the gateway that you get via DHCP from your ISP HTH, Brett
On Monday 23 February 2004 15:50, Ben Rosenberg wrote: <SNIP>
Well... I am not on Linux because I 'hate' anyone... I'm on it because it does the job. What it doesn't do, I have to use a competing system. It's no moe complicated than that. <G>
Fair enough. But you are on a Linux mailing list so mentioning Microsoft doesn't do .. and getting a cold shoulder for bring up Microsoft without just asking how to do the job you want to do is in bad taste. A few years ago Linux people were so hungry to get people into the fold that those comments made them jump. Today that strategy doesn't work.
As you say, fair enough. I'm just grateful for any help.
On Monday 23 February 2004 19:17, Brett Russ wrote: <SNIP>
Here are some things I think would help me and maybe others understand the problem. Provide these at a time when you think everything is set up the best you've been able to achieve.
-the contents of /etc/resolv.conf -output of 'ip route' -output of 'ip addr'
Additionally: -with your ISP's nameservers in place, external DNS lookups will fail when ppp0 is down -if you don't have a DHCP server on your local LAN, you'll need a static IP on eth0 -eth0 and ppp0 should be totally independent with respect to IP addresses; eth0 should be static and ppp0 should be DHCP. -you'd want a route for 192.168.0.0 to be eth0 -you'd want a default route to be ppp0 via the gateway that you get via DHCP from your ISP
Many thanks. I shall work on this and attempt to generate what you have suggested. ...CH
tisdag 24 februari 2004 01:27 skrev C Hamel:
That is what I was attempting to explain. I did exactly as you stated above --several times-- and each time I can get the modem to connect but there is absolutely no throughput until I put the IP addresses in the 'Host name & name server configuration' list. Then, and *only* then, I get modem throughput ...but then the network is dead. Ditto, if I change the dhcp to static address in 'Network Address Setup'... whether or not I have any IP addresses in the 'Host name...' list.
First, to see what's causing this... find some nice IP address, that's located on the internet and write it down. Then use kppp to dial up your ISP, and send one ping to that IP address. $ ping -c 1 <IP> You should get an echo reply. The problem, is most likely related to that DNS doesn't get updated after kppp has started. Check to see if kppp is SUID, that is it must be running as root. Don't you get a message, first time you start kppp telling you this? I do.
Sorry if I am not completely articulate. I have had no problems setting up networking in the past, though I was not yet using SuSE, either. Now that I am, I cannot get the apparently mutually-dependent eth0 & ppp0 to operate independently. Even the 'ipconfig' output shows this:
eth0 Link encap:Ethernet HWaddr 00:0D:9D:89:9C:47 inet addr:192.168.0.10 Bcast:192.168.0.255 Mask:255.255.255.0 inet6 addr: fe80::20d:9dff:fe89:9c47/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:297 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:0 (0.0 b) TX bytes:112074 (109.4 Kb) Interrupt:10 Base address:0x2000
ppp0 Link encap:Point-to-Point Protocol inet addr:204.250.144.61 P-t-P:205.247.108.66 Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1 RX packets:6 errors:0 dropped:0 overruns:0 frame:0 TX packets:6 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:3 RX bytes:71 (71.0 b) TX bytes:77 (77.0 b)
On Monday 23 February 2004 19:17, Brett Russ wrote:
Here are some things I think would help me and maybe others understand the problem. Provide these at a time when you think everything is set up the best you've been able to achieve.
-the contents of /etc/resolv.conf -output of 'ip route' -output of 'ip addr'
Additionally: -with your ISP's nameservers in place, external DNS lookups will fail when ppp0 is down -if you don't have a DHCP server on your local LAN, you'll need a static IP on eth0 -eth0 and ppp0 should be totally independent with respect to IP addresses; eth0 should be static and ppp0 should be DHCP. -you'd want a route for 192.168.0.0 to be eth0 -you'd want a default route to be ppp0 via the gateway that you get via DHCP from your ISP
Okay... here it all is, below my signature. I could use some help on this,
for certain.
...CH
======================
settings prior to any changes
linux:~ # ip route
205.247.108.66 dev ppp0 proto kernel scope link src 204.250.144.59
default via 205.247.108.66 dev ppp0
linux:~ # ip addr
1: lo:
On Monday 23 February 2004 20:41, Örn Hansen wrote:
tisdag 24 februari 2004 01:27 skrev C Hamel:
That is what I was attempting to explain. I did exactly as you stated above --several times-- and each time I can get the modem to connect but there is absolutely no throughput until I put the IP addresses in the 'Host name & name server configuration' list. Then, and *only* then, I get modem throughput ...but then the network is dead. Ditto, if I change the dhcp to static address in 'Network Address Setup'... whether or not I have any IP addresses in the 'Host name...' list.
First, to see what's causing this... find some nice IP address, that's located on the internet and write it down. Then use kppp to dial up your ISP, and send one ping to that IP address. I have set up kppp for my ISP w/the information supplied by said ISP.
$ ping -c 1 <IP>
You should get an echo reply.
No problem pinging and otherwise e-mailing, surfing, listening to streaming audio ...the works.
The problem, is most likely related to that DNS doesn't get updated after kppp has started. Check to see if kppp is SUID, that is it must be running as root. Don't you get a message, first time you start kppp telling you this? I do.
I did, as well, until I listed pppd in the permissions.local file giving permissions to the user. Since I did that, I've not seen that over many uses & reboots (I certainly wish they'd get ACPI working :-\). Many thanks to the user on this list who pointed me to that file. :-) ...CH
tisdag 24 februari 2004 05:13 skrev C Hamel:
3: eth0:
mtu 1500 qdisc pfifo_fast qlen 100 link/ether 00:0d:9d:89:9c:47 brd ff:ff:ff:ff:ff:ff inet6 fe80::20d:9dff:fe89:9c47/64 scope link
This doesn't look right ... notice there is no inet address.
14: ppp0:
mtu 1500 qdisc pfifo_fast qlen 3 link/ppp inet 204.250.144.59 peer 205.247.108.66/32 scope global ppp0 A. Connection established w/kppp & streaming audio started (all settings in kppp were ISP-specific & correct) B. I set the eth0 IP address to 192.168.0.10 C. All ip addresses were removed from 'Host name/name server config' D. Gateway for eth0 set to 192.168.0.0 192.168.0.0 is a network address, unless you have a gateway to the internet via eth0, you should leave it empty.
E. Finalized settings, audio stream continues w/o a problem F. Set up firewall w/ppp0 (external) & eth0 (internal); all other settings default G. Pinging on LAN impossible
Pinging on lan IS possible, but only with an inet6 address ... it doesn't have an inet4 address (see above).
H. Shut down fireall I. Pinging between machines possible but no smbfs connection possible
linux:~ # ifdown eth0 linux:~ # ifup eth0 ERROR: Error while excuting: Command 'ip route replace to default via 192.168.0.0' returned: RTNETLINK answers: Invalid argument Configuration line: default 192.168.0.0 - -
Remove the gateway address for eth0
linux:~ # ip route 205.247.108.66 dev ppp0 proto kernel scope link src 204.250.144.5 192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.10 default via 205.247.108.66 dev ppp0
Looks good.
3: eth0:
mtu 1500 qdisc pfifo_fast qlen 100 link/ether 00:0d:9d:89:9c:47 brd ff:ff:ff:ff:ff:ff inet 192.168.0.10/24 brd 192.168.0.255 scope global eth0 inet6 fe80::20d:9dff:fe89:9c47/64 scope link Now it's ok.
resolv.conf contents: domain local
This is what I was referring to, DNS is not being updated ... *this* is your sole problem.
J. Shut down audio stream/restarted stream: 'server not found' K. Closed/restarted ppp0 L. Audio stream not possible: 'server not found' M. Set eth0 IP to dhcp N. Set 'Host name/name server config' to 205.247.104.20 & 205.247.104.21 (ISP-specific IP addresses furnished by ISP) O. Set 'Gateway' to null P. Finalized settings Q. Started audio stream without difficulty.
resolv.conf contents: domain local nameserver 205.247.104.20 nameserver 205.247.104.20
Ok, since you have a dialup *this* is the wrong place to be doing this. You have a place in kppp to do it, that's where you are supposed to edit the DNS addressess for the dialup connection, and then setup kppp to be SUID so it can change the /etc/resolv.conf file. Without it being able to edit it when it makes the connection, you won't get dns lookups. If you don't want to change kppp run priveleges, you can always just make a copy of a "working /etc/resolv.conf" file and copy it into place, when connection has been made.
tisdag 24 februari 2004 05:13 skrev C Hamel:
14: ppp0:
mtu 1500 qdisc pfifo_fast qlen 3 link/ppp inet 204.250.144.59 peer 205.247.108.66/32 scope global ppp0 A. Connection established w/kppp & streaming audio started (all settings in kppp were ISP-specific & correct) B. I set the eth0 IP address to 192.168.0.10 C. All ip addresses were removed from 'Host name/name server config' D. Gateway for eth0 set to 192.168.0.0 E. Finalized settings, audio stream continues w/o a problem F. Set up firewall w/ppp0 (external) & eth0 (internal); all other settings default You need to clear the marker for "Protect from internal network". Obviously, you'd want your internal network to be trusted, right?
On Mon, 2004-02-23 at 11:05, C Hamel wrote:
(1)I have kppp set up w/DNS addresses for my ISP, along w/phone# and other parameters. It works fine.
(2)As long as I have eth0 set up for dhcp & have my ISP's DNS addresses in the lookup list, ppp0 continues to work just fine.
(3)If I have eth0 set up for the local network using dhcp & the lookup set for my network (192.168.0.1) it doesn't work, whether or not ppp0 is active.
(4)If I have eth0 set up for the local network using a static 192.168.0.10 & the lookup set for 192.168.0.1 eth0 works just fine w/the LAN & ppp0 will connect, but there is absolutely no modem throughput. The hub lights flash when I attempt to access the internet, and 'ip forwarding' is turned off.
Now-then, I like SuSE just fine in lots of respects but the fact that it won't do what M$ Windoze does readily is beyond my comprehension. I can only believe that there must be *something* I'm missing, but I cannot figure out what!
Any help really appreciated!! ...CH
Start with changing your subject to something appropriate. Dee
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday 24 February 2004 12:30 am, W.D.McKinney wrote:
On Mon, 2004-02-23 at 11:05, C Hamel wrote:
(1)I have kppp set up w/DNS addresses for my ISP, along w/phone# and other parameters. It works fine.
(2)As long as I have eth0 set up for dhcp & have my ISP's DNS addresses in the lookup list, ppp0 continues to work just fine.
(3)If I have eth0 set up for the local network using dhcp & the lookup set for my network (192.168.0.1) it doesn't work, whether or not ppp0 is active.
(4)If I have eth0 set up for the local network using a static 192.168.0.10 & the lookup set for 192.168.0.1 eth0 works just fine w/the LAN & ppp0 will connect, but there is absolutely no modem throughput. The hub lights flash when I attempt to access the internet, and 'ip forwarding' is turned off.
Now-then, I like SuSE just fine in lots of respects but the fact that it won't do what M$ Windoze does readily is beyond my comprehension. I can only believe that there must be *something* I'm missing, but I cannot figure out what!
Any help really appreciated!! ...CH
Start with changing your subject to something appropriate.
Dee
I've been avoiding posting to this thread up till now. Actually, this sounds like the old blow away the resolve.conf every time you make a connection. I forget the details, but some slick wizard over in Nürnberg had written a script that... Man! That thing had me going for days trying to figure out what was up. STH -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQFAOvd1H2SF0i7rrGwRAnksAJ9++IN19Pe2X63qwKOl/6C2NiOK7ACfdlMT DbSw6BZVnQQXOLT7FLD+F7I= =xbJS -----END PGP SIGNATURE-----
participants (8)
-
Ben Rosenberg
-
Brett Russ
-
C Hamel
-
James Knott
-
Matthew Johnson
-
Steven T. Hatton
-
W.D.McKinney
-
Örn Hansen