Re: Internet Access Problem

2024-04-12 Thread Max Nikulin



On 11/04/2024 20:53, Stephen P. Molnar wrote:
I am running Bullseye and attempting to use QEMU/KVM virt-manager, on 
the computers on my LAN rather than Oracle VM VirtualBox.

[...]

However, when I pinged yahoo.com. I got the result:

Reply from 169.234.75.136: Destination host unreachable.


If the VM for some reason is configured with "user" network instead of 
vibr0 then it is expected:


https://wiki.qemu.org/Documentation/Networking

Note - if you are using the (default) SLiRP user networking, then ping
(ICMP) will not work, though TCP and UDP will. Don't try to use ping to
test your QEMU network configuration!


Regular user running VM does not have enough privileges to send ICMP 
packets.




Re: Internet Access Problem

2024-04-11 Thread Marco Moock
Am 11.04.2024 um 09:53:30 Uhr schrieb Stephen P. Molnar:

> I followed the How To (HowTo.txt, attached) without any warning or
> error messages. However, when I pinged yahoo.com. I got the result:
> 
> Reply from 169.234.75.136: Destination host unreachable.

You have to specify how your network is being attached to the VM. I
recommend a network bridge to your NIC, so the virtual PC is a normal
client in your network.

-- 
Gruß
Marco

Send unsolicited bulk mail to 1712822010mu...@cartoonies.org



Internet Access Problem

2024-04-11 Thread Stephen P. Molnar
I am running Bullseye and attempting to use QEMU/KVM virt-manager, on 
the computers on my LAN rather than Oracle VM VirtualBox.


I particularly would like to be able to run Windows 10 as there in one 
application that I need for my molecular modeling research that is not 
available for Linux.


I followed the How To (HowTo.txt, attached) without any warning or error 
messages. However, when I pinged yahoo.com. I got the result:


Reply from 169.234.75.136: Destination host unreachable.

It is my understanding the internet should be reachable from Windows 10 
from the default connection.


The default virt-manger xml file and the host i pa results are also 
attached.


I would appreciate any sort of insight as to what might have gone wrong.

Thanks in advance.

--
Stephen P. Molnar, Ph.D.
https://insilicochemistry.net
(614)312-7528 (c)
Skype:  smolnar1



  default
  8230a394-6e17-4ef9-8841-5b4a13812a38
  

  

  
  
  
  

  

  

How To Install Windows 10 on Ubuntu
KVM?
By: Saifudheen Sidheeq


Published: August 23, 2020 - Last updated: November 4, 2023


https://getlabsdone.com/install-windows-10-on-ubuntu-kvm/
 (base) comp@AbNormal:~$ ip a
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
   valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
   valid_lft forever preferred_lft forever
2: enp2s0:  mtu 1500 qdisc fq_codel state UP 
group default qlen 1000
link/ether bc:ee:7b:5e:83:36 brd ff:ff:ff:ff:ff:ff
inet 162.237.98.238/22 brd 162.237.99.255 scope global dynamic 
noprefixroute enp2s0
   valid_lft 547sec preferred_lft 547sec
inet6 2600:1700:4280:3690::3f7/128 scope global dynamic noprefixroute
   valid_lft 2583846sec preferred_lft 596646sec
inet6 2600:1700:4280:3690:beee:7bff:fe5e:8336/64 scope global dynamic 
mngtmpaddr noprefixroute
   valid_lft 3414sec preferred_lft 3414sec
inet6 fe80::beee:7bff:fe5e:8336/64 scope link noprefixroute
   valid_lft forever preferred_lft forever
3: virbr0:  mtu 1500 qdisc noqueue state 
DOWN group default qlen 1000
link/ether 52:54:00:c4:59:37 brd ff:ff:ff:ff:ff:ff
inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
   valid_lft forever preferred_lft forever
4: virbr1:  mtu 1500 qdisc noqueue state 
DOWN group default qlen 1000
link/ether 52:54:00:68:bf:76 brd ff:ff:ff:ff:ff:ff
inet 192.168.100.1/24 brd 192.168.100.255 scope global virbr1
   valid_lft forever preferred_lft forever
(base) comp@AbNormal:~$


Re: Internet access problem with ppp(oe)

2007-09-21 Thread Micaela Gallerini
2007/9/20, Tuomas Jouhten <[EMAIL PROTECTED]>:
>
> I'm quite green with debian and with linux, so that workaround was found 
> simply
> by an accident..
>
> The problem was evident right after Etch installation (netinst dvd-image).
> Network manager (an icon the side panel) notified that there was a network
> connection, and that there were updates available, but still the browsers
> couldn't access the web.
>
> "ps x | grep ppp" shows
>
>  3736 ?Ss 0:00 /usr/sbin/pppd call provider
>  4587 ?Ss 0:00 /usr/sbin/pppd call dsl-provider
>  5227 pts/1S+ 0:00 grep ppp
>
> Running etch, vdsl-modem, ppp confed with pppoeconf. Have two entries in
> /etc/ppp/peers/. (and don't know if both of them should be there)
>
> Also, Firestarter is running and showing eth0 (type is ethernet) and ppp0 
> (type
> is internet) and ppp1 (type is dialup).
>
>

hi,

  try to install the package

pppconfig

with aptitude if you have this package try to give the www-data
permiss at the user

regards,

heba


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Internet access problem with ppp(oe)

2007-09-20 Thread Tuomas Jouhten
Hi,

Problems with internet connection. Neither browsers nor apt cannot access
internet right after booting up to X. After booting up there's two
pppd-processes, which need to be killed, and then only after running
"pon dsl-provider" (prints "Plugin rp-pppoe.so loaded")
internet connection works. 

I'm quite green with debian and with linux, so that workaround was found simply
by an accident.. 

The problem was evident right after Etch installation (netinst dvd-image).
Network manager (an icon the side panel) notified that there was a network
connection, and that there were updates available, but still the browsers
couldn't access the web.  

"ps x | grep ppp" shows

 3736 ?Ss 0:00 /usr/sbin/pppd call provider
 4587 ?Ss 0:00 /usr/sbin/pppd call dsl-provider
 5227 pts/1S+ 0:00 grep ppp

Running etch, vdsl-modem, ppp confed with pppoeconf. Have two entries in
/etc/ppp/peers/. (and don't know if both of them should be there)

Also, Firestarter is running and showing eth0 (type is ethernet) and ppp0 (type
is internet) and ppp1 (type is dialup). 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: Internet access problem with Debian Sarge + BSNL Dataone

2006-01-22 Thread Andrew M.A. Cater
On Sun, Jan 22, 2006 at 05:49:34PM -0800, L.V.Gandhi wrote:
> On 1/22/06, K MS <[EMAIL PROTECTED]> wrote:
> > Hi,
> 
> >The DNS server addresses are worrying because the address reported
> >in the log as secondary is exactly what I supplied to pppoeconf as
> >the *primary* DNS address. The primary reported in the log output
> >doesn't ring a bell at all...
> 
> Primary or sec DNS, I tink shouldn't matter.
> 
> >After the first time I ran pon the file /etc/resolv.conf contained
> >the primary and the secondary nameserver addresses as per the log
> >above (218.248.255.145 & 61.1.96.69).
> >When these were edited to be 61.1.96.69 & 61.1.96.71 (the correct
> >values supplied by ISP), the log still showed the same output and
> >nameservers were the same (they get reset!).
> 
> DNS addresses are changed dynamically by default by ppp.
> 
> >Some other information...
> >   debian:~# route -n
> >   Destination Gateway Genmask Flags Metric RefUse
> > Iface
> >   192.168.1.0 0.0.0.0 255.255.255.0   U 0  00
> > eth0
> >   0.0.0.0 192.168.1.1 0.0.0.0 UG0  00
> > eth0
> >
> >debian:~# ping 218.248.255.145
> >PING 218.248.255.145 ( 218.248.255.145) 56(84) bytes of data.
> >   From 192.168.1.1 icmp_seq=1 Destination Net Unreachable
> >   From 192.168.1.1 icmp_seq=2 Destination Net Unreachable
> >   From 192.168.1.1 icmp_seq=3 Destination Net Unreachable
> >   From 192.168.1.1 icmp_seq=4 Destination Net Unreachable
> >   From 192.168.1.1 icmp_seq=5 Destination Net Unreachable
> >
> Normally your bsnl fellow would have configured for windows. As I have
> seen one connection in Chennai, the modem is also a router. Only that
> need to be configured. Once it is configured, you can use lines in
> /etc/network/interfaces as
> auto eth0
> iface eth0 inet dhcp
> that should connect. You can have /etc/resolv.conf with bsnl supplied DNS.
> To check your modem/router which is web server connect to http://192.168.1.1/
> and login. you can see info about router and search in google for details.
> --
If this is a broadband cable modem for ADSL or equivalent. As supplied,
it should have a setup disk. Look on there for any installation guide
for Windows for a start. If it is something like the Alcatels common
here in Europe, it will have telephone line in and USB out. Google for
(model number) and Linux and work from there. If you have something like the 
Linksys/Netgear modem/ethernet switch/wifi all in one box - they have an 
inbuilt web server. Point your browser at the web interface and go. 
Total time to setup for any OS about three minutes. If broadband with a dynamic 
IP for one PC, use dhclient on the PC to pick up info. 
A stanza in /etc/network/interfaces something like

auto eth0
iface eth0 inet dhcp

should do it.
> 
> L.V.Gandhi
> http://lvgandhi.tripod.com/
> linux user No.205042


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: Internet access problem with Debian Sarge + BSNL Dataone

2006-01-22 Thread L.V.Gandhi
On 1/22/06, K MS <[EMAIL PROTECTED]> wrote:
> Hi,

>Dec 23 21:57:23 localhost pppd[4727]: Plugin rp-pppoe.so loaded.
>Dec 23 21:57:23 localhost pppd[4728]: pppd 2.4.3 started by root, uid 0
>Dec 23 21:57:23 localhost pppd[4728]: PPP session is 7279
>Dec 23 21:57:23 localhost pppd[4728]: Using interface ppp0
>Dec 23 21:57:23 localhost pppd[4728]: Connect: ppp0 <--> eth0
>Dec 23 21:57:23 localhost pppd[4728]: Couldn't increase MTU to 1500
>Dec 23 21:57:23 localhost pppd[4728]: Couldn't increase MRU to 1500
>Dec 23 21:57:23 localhost pppd[4728]: Couldn't increase MTU to 1500
>Dec 23 21:57:23 localhost pppd[4728]: Couldn't increase MRU to 1500
>Dec 23 21:57:24 localhost pppd[4728]: CHAP authentication succeeded:
> Authentication success,Welcome!
>Dec 23 21:57:24 localhost pppd[4728]: peer from calling number
> 00:E0:FC:39:92:4A authorized
>Dec 23 21:57:24 localhost pppd[4728]: not replacing default route to eth0
> [192.168.1.1]
>Dec 23 21:57:24 localhost pppd[4728]: Cannot determine ethernet address
> for proxy ARP
>Dec 23 21:57:24 localhost pppd[4728]: local  IP address 59.92.133.88
>Dec 23 21:57:24 localhost pppd[4728]: remote IP address 59.92.128.1
>Dec 23 21:57:24 localhost pppd[4728]: primary   DNS address
> 218.248.255.145
>Dec 23 21:57:24 localhost pppd[4728]: secondary DNS address 61.1.96.69

above lines indicate you are connected.

>The DNS server addresses are worrying because the address reported
>in the log as secondary is exactly what I supplied to pppoeconf as
>the *primary* DNS address. The primary reported in the log output
>doesn't ring a bell at all...

Primary or sec DNS, I tink shouldn't matter.

>After the first time I ran pon the file /etc/resolv.conf contained
>the primary and the secondary nameserver addresses as per the log
>above (218.248.255.145 & 61.1.96.69).
>When these were edited to be 61.1.96.69 & 61.1.96.71 (the correct
>values supplied by ISP), the log still showed the same output and
>nameservers were the same (they get reset!).

DNS addresses are changed dynamically by default by ppp.

>Some other information...
>   debian:~# route -n
>   Destination Gateway Genmask Flags Metric RefUse
> Iface
>   192.168.1.0 0.0.0.0 255.255.255.0   U 0  00
> eth0
>   0.0.0.0 192.168.1.1 0.0.0.0 UG0  00
> eth0
>
>debian:~# ping 218.248.255.145
>PING 218.248.255.145 ( 218.248.255.145) 56(84) bytes of data.
>   From 192.168.1.1 icmp_seq=1 Destination Net Unreachable
>   From 192.168.1.1 icmp_seq=2 Destination Net Unreachable
>   From 192.168.1.1 icmp_seq=3 Destination Net Unreachable
>   From 192.168.1.1 icmp_seq=4 Destination Net Unreachable
>   From 192.168.1.1 icmp_seq=5 Destination Net Unreachable
>
Normally your bsnl fellow would have configured for windows. As I have
seen one connection in Chennai, the modem is also a router. Only that
need to be configured. Once it is configured, you can use lines in
/etc/network/interfaces as
auto eth0
iface eth0 inet dhcp
that should connect. You can have /etc/resolv.conf with bsnl supplied DNS.
To check your modem/router which is web server connect to http://192.168.1.1/
and login. you can see info about router and search in google for details.
--
L.V.Gandhi
http://lvgandhi.tripod.com/
linux user No.205042


Internet access problem with Debian Sarge + BSNL Dataone

2006-01-22 Thread K MS
Hi,
    Kindly help me get my first browsing experience in Debian linux.
I have tried various list-archives recommended by Google still have
not been able to get around fixing this.
    Email below is rather long. I have explained my installation
and shown the logs before asking my questions at the bottom.

  I have installed Debian GNU/Linux, Sarge 3.1r0a on my PC along
  with Kernel version 2.6 686.
  I also have the dataone broadband service from BSNL (in bangalore,
  INDIA).
  
  I logged in as root and started ADSL/pppoe configuration as root 
  (/usr/sbin/pppoeconf) and answered the questions. Entered user-name
  and password - but I didn't get a question for which I could enter
  the DNS server names in response..
  
  To clarify further, I did not additionally install rp/pppoe or any
  other software on top of the installation.
  
  eth0 contains a LAN card. This was detected during installation and the driver
  was automatically loaded. The ethernet connection is active and ifconfig on
  restart/startup is as follows:
  eth0  Link encap:Ethernet  HWaddr 00:05:5D:4B:1E:85
   
inet addr:192.168.1.34  Bcast:

192.168.1.255 
Mask:255.255.255.0
    inet6 addr: fe80::205:5dff:fe4b:1e85/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
    RX packets:140 errors:0 dropped:0 overruns:0 frame:0
    TX packets:175 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:11877 (11.5 KiB)  TX bytes:15003 (14.6 KiB)
    Interrupt:209 Base address:0xc400
  
  When I run pon and then plog I get the following output.
  
  plog output (copy-pasted from /var/log/syslog)
  
  Dec 23 21:57:23 localhost pppd[4727]: Plugin rp-pppoe.so loaded.
  Dec 23 21:57:23 localhost pppd[4728]: pppd 2.4.3 started by root, uid 0
  Dec 23 21:57:23 localhost pppd[4728]: PPP session is 7279
  Dec 23 21:57:23 localhost pppd[4728]: Using interface ppp0
  Dec 23 21:57:23 localhost pppd[4728]: Connect: ppp0 <--> eth0
  Dec 23 21:57:23 localhost pppd[4728]: Couldn't increase MTU to 1500
  Dec 23 21:57:23 localhost pppd[4728]: Couldn't increase MRU to 1500
  Dec 23 21:57:23 localhost pppd[4728]: Couldn't increase MTU to 1500
  Dec 23 21:57:23 localhost pppd[4728]: Couldn't increase MRU to 1500
  Dec 23 21:57:24 localhost pppd[4728]: CHAP authentication succeeded: Authentication success,Welcome!
  Dec 23 21:57:24 localhost pppd[4728]: peer from calling number 00:E0:FC:39:92:4A authorized
  Dec 23 21:57:24 localhost pppd[4728]: not replacing default route to eth0 [192.168.1.1]
  Dec 23 21:57:24 localhost pppd[4728]: Cannot determine ethernet address for proxy ARP
  Dec 23 21:57:24 localhost pppd[4728]: local  IP address 59.92.133.88
  Dec 23 21:57:24 localhost pppd[4728]: remote IP address 59.92.128.1
  Dec 23 21:57:24 localhost pppd[4728]: primary   DNS address 218.248.255.145
  Dec 23 21:57:24 localhost pppd[4728]: secondary DNS address 61.1.96.69
  
  The DNS server addresses are worrying because the address reported
  in the log as secondary is exactly what I supplied to pppoeconf as
  the *primary* DNS address. The primary reported in the log output 
  doesn't ring a bell at all...
  
  After the first time I ran pon the file /etc/resolv.conf contained 
  the primary and the secondary nameserver addresses as per the log 
  above (218.248.255.145 & 

61.1.96.69).
  When these were edited to be 61.1.96.69 & 

61.1.96.71 (the correct
  values supplied by ISP), the log still showed the same output and 
  nameservers were the same (they get reset!).
  
  Some other information...
 debian:~# route -n
 Destination
Gateway
Genmask Flags Metric
Ref    Use Iface
 192.168.1.0
0.0.0.0
255.255.255.0   U
0 
0    0 eth0
 0.0.0.0
192.168.1.1
0.0.0.0
UG    0 
0    0 eth0
  
  debian:~# ping 218.248.255.145


  PING 218.248.255.145 (

218.248.255.145) 56(84) bytes of data.

 From 192.168.1.1 icmp_seq=1 Destination Net Unreachable


 From 192.168.1.1 icmp_seq=2 Destination Net Unreachable


 From 192.168.1.1 icmp_seq=3 Destination Net Unreachable


 From 192.168.1.1 icmp_seq=4 Destination Net Unreachable


 From 192.168.1.1 icmp_seq=5 Destination Net Unreachable


  
  --- 218.248.255.145 ping statistics ---
  5 packets transmitted, 0 received, +5 errors, 100% packet loss, time 3999ms

Questions
Now the basic question is has it been able to connect ?! 
Although I don't see any error messages in the log, ping for any ip results in an 
error message: "net is unreachable" and I am not able to access the web via 
Epiphany / Konqueror.

If not, then how to correct this problem and verify if it has connected properly ?
Once pppoe connects is there something extra that needs to be done to access
the web from my desktop ?





Re: Internet access problem

2002-03-18 Thread Crispin Wellington
On Tue, 2002-03-19 at 11:07, Darren Walker wrote:
> 
> Hello Debian,
> 
> I have recently installed Debian onto
> an old P75 of mine and am using it as 
> an internet sharing server
> 
> I am using a modem connection
> and using firewalling with masquerading
> 
> I am also running exim and squid
> 
> the problem is that it connects
> and masquerades without any problems
> 
> clients can browse the internet and send emails
> but for no apparent reason
> HTTP access becomes unavailable after awhile
> it seems to occur after using email but not always
> 
> I can ping FQDN without problems i.e. www.yahoo.com
> but can not browse web sites
> 
> this is also the case from the server using lynx
> it hangs "waiting for response"
> 
> is there any clues as to the cause
> of this problems
> 
> I would appreciate any assistance

I take it by your email address that you are dialing into the iprimus
network in Australia. I had problems connecting linux to iprimus dialup
routers, and was informed by iprimus that the "do not support linux".
The problems I had were constantly breaking dialup connections and
problems establishing reasonably long lasting TCP connections (no RST or
FIN packets. The stream just stopped).

I would suggest turning on debugging on your PPP connection. Go
pppconfig and under your connection choose advanced, and then switch
debugging on.

>From the debug info in syslog I saw constant CCP negotiation errors and
problems (Compression Control Protocol). I fixed this by forcing off BSD
and deflate compression on the connection. Edit /etc/ppp/options and add
in these lines

bsdcomp 0
deflate 0
noccp 

restart ppp and make sure that the CCP errors no longer appear in your
ppp debug output. Although this removes the compression, it won't slow
your link to much as you think as the modems will still have their LAP-M
or whatever its called.

Basically when iprimus says "we don't support linux" they mean, "we
don't debug our dialup routers, if windows dials OK, then its OK,
right!"

Let us know how you go.

Kind Regards
Crispin Wellington



Internet access problem

2002-03-18 Thread Darren Walker

Hello Debian,

I have recently installed Debian onto
an old P75 of mine and am using it as 
an internet sharing server

I am using a modem connection
and using firewalling with masquerading

I am also running exim and squid

the problem is that it connects
and masquerades without any problems

clients can browse the internet and send emails
but for no apparent reason
HTTP access becomes unavailable after awhile
it seems to occur after using email but not always

I can ping FQDN without problems i.e. www.yahoo.com
but can not browse web sites

this is also the case from the server using lynx
it hangs "waiting for response"

is there any clues as to the cause
of this problems

I would appreciate any assistance

thank you

Darren Walker
mailto:[EMAIL PROTECTED]
http://home.iprimus.com.au/drwalker