Re: Kvm Bridge Network Problem

[Geert Stappers]

On Tue, May 07, 2024 at 02:17:05AM +0100, Gareth Evans wrote:
> On Tue 07/05/2024 at 01:51, Gareth Evans wrote:
> 
> I did miss a step.  
> 
> > Start VM, check DHCP address assigned
> 
> should be
> 
> > Edit the VM NIC settings and choose your routed network connection from the 
> > "Network Source" dropdown. Apply changes.
> 
> > Start VM, check DHCP address assigned
> 
> I actually deleted other vibrX devices and networks before starting, but I 
> don't think that matters.
> 
> G

For the sake of the archive: Place _all_ steps in one email.
Preferable in reply to the original posting.
 

Groeten
Geert Stappers
-- 
Silence is hard to parse

Re: Kvm Bridge Network Problem

[Gareth Evans]

On Tue 07/05/2024 at 01:51, Gareth Evans  wrote:

I did miss a step.  

> Start VM, check DHCP address assigned

should be

> Edit the VM NIC settings and choose your routed network connection from the 
> "Network Source" dropdown. Apply changes.

> Start VM, check DHCP address assigned

I actually deleted other vibrX devices and networks before starting, but I 
don't think that matters.

G

Re: Kvm Bridge Network Problem

[Gareth Evans]

On host:

$ ip a|grep wl
3: wlp1s0:  mtu 1500 qdisc noqueue state UP 
group default qlen 1000
inet 192.168.1.100/24 ...

Using:

virt-manager > Edit > Connection Details > Virtual Networks > Add network 

Mode: Routed
Network: 192.168.200.0/24
Accept default DHCP range
Forward to: physical device
Device: wlp1s0 [this is my physical wifi card]

Then:

$ sudo sysctl -w net.ipv4.ip_forward=1

Then check:

$ ip link

6: virbr0:  mtu 1500 qdisc noqueue state UP 
mode DEFAULT group default qlen 1000
link/ether 52:54:00:54:ed:48 brd ff:ff:ff:ff:ff:ff
7: vnet0:  mtu 1500 qdisc noqueue master 
virbr0 state UNKNOWN mode DEFAULT group default qlen 1000
link/ether fe:54:00:9b:a7:8e brd ff:ff:ff:ff:ff:ff

Start VM, check DHCP address assigned

On VM guest:

$ ip a|grep enp
2: enp1s0:  mtu 1500 qdisc fq_codel state UP 
group default qlen 1000
inet 192.168.200.151/24 ...

At this point (with firewalls temporarily off) I was able to ssh to and from 
host and VM guest using their respective IP addresses.

After adding a static route on my wireless router:

192.168.200.0/24 via 192.168.1.100  (to paraphrase the web form)

I installed apache2 on the VM guest and was able to access

http://192.168.200.151

from my phone over wifi, and websites on the host from the VM guest.

Firewalld actived on host with ssh and https services allowed - ssh and web 
browsing worked as before.

No nf/iptables jiggery-pokery, but static route on router required.

Perhaps not the most efficient solution, but I try to avoid too many firewall 
rules because they make my head spin :)

Don't think I've omitted any steps.

Does that help?

Best wishes,
Gareth

Re: Kvm Bridge Network Problem

[Gareth Evans]

On Sun 05/05/2024 at 07:53, Gareth Evans  wrote:

> That might suggest NAT is still operative for the VM.

Ah, I hadn't seen Geert's reply, which I think is closer to the mark :)

This gives a routing-based approach:

https://www.linux-kvm.org/page/Networking

This creates an isolated network between host and guest, which without routing 
presumably is additional to the default network, and the (Ubuntu-based) netplan 
stuff needs substituting with /e/n/i adjustments:

https://www.nodinrogers.com/post/2022-01-06-enabling-kvm-host-to-vm-communcation/

All of which I have yet to test but have been meaning to look into this again.

HTH

Re: Kvm Bridge Network Problem

[Gareth Evans]

On Sat 04/05/2024 at 21:26, Stephen P. Molnar  wrote:
> ... 
> I have managed to follow the 
> instructions in:
>
> https://www.cyberciti.biz/faq/how-to-add-network-bridge-with-nmcli-networkmanager-on-linux/
>  
> ...
> I was able to use the LAN 
> printer and the 40" TV , but could not access the Host.

Hi Stephen,

That might suggest NAT is still operative for the VM.

Did you do the "optional" part of the tutorial in your link too, re KVM network 
config?

What is the output of

# nmcli con show

# nmcli device

# virsh net-list --all

# virsh net-dumpxml yourNetworkName

I don't have a network cable to hand to test this at the moment (wifi NIC 
bridging is complex if possible with KVM [1] and apples and oranges and all 
that) but will do later if your problem is not solved.

I think the presence of enp2s0 in /e/n/i (which your attachment seems to be) 
prevents NM from managing it, but if I'm wrong about that, could it be getting 
an address (static or otherwise) from NM?

Gareth

[1] https://hacktivate.it/posts/kvm-bridge-wireless/

Re: Kvm Bridge Network Problem, VM accessing the host

[Geert Stappers]

On Sat, May 04, 2024 at 04:26:07PM -0400, Stephen P. Molnar wrote:
> I am running Bookworm on my main platform. After quite a bit of googling and
> many errors and much head scratching I have managed to follow the
> instructions in:
> 
> https://www.cyberciti.biz/faq/how-to-add-network-bridge-with-nmcli-networkmanager-on-linux/
> .
> 
> I have currently implicated this on a Windows 10 client. However, there
> still remains a problem. After the first restart of the Windows client the
> internet was accessible. However, a problem arose after I successfully
> installed br0 (copy attached). I was able to use the LAN printer and the 40"
> TV , but could not access the Host.

Ah, the VM guest can not access the host.
(I changed 'Subject: Re: Kvm Bridge Network Problem'
into 'Subject: Re: Kvm Bridge Network Problem, VM accessing the host')

 
> I'm sure that I have missed something, but I don't know what.

Network switches only forward packets.

 
> Guidance to a solution to the problem would be appreciated.

I have been where O.P. is, the challenge^Wproblem is real.
 

> # This file describes the network interfaces available on your system
> # and how to activate them. For more information, see interfaces(5).
> 
> source /etc/network/interfaces.d/*
> 
> # The loopback network interface
> auto lo
> iface lo inet loopback
> 
> # Specify that the physical interface that should be connected to the bridge
> # should be configured manually, to avoid conflicts with NetworkManager
> iface enp2s0 inet manual
> 
> #Primary network interface with bridge
> auto br0
> iface br0 inet static
> address 162.237.98.238
> broadcast 162.237.98.255
> netmask 255.255.255.0
> gateway 162.237.98.1
> bridge_ports enp2s0
> bridge_stp off
> bridge_waitport 0
> bridge fd 0


That brigde configuration looks good, even might be good.

The thing is that host and VM are at the same interface of the network
switch. And network switches only forward packets. It is a "physical
law" in computer networking. Hopefully brings this email thread
the jargon name of the "problem".


If direct connection between host and the VM guest is important,
then add such connection and take the costs it brings.


Groeten
Geert Stappers
-- 
Silence is hard to parse

Kvm Bridge Network Problem

[Stephen P. Molnar]

I am running Bookworm on my main platform. After quite a bit of googling 
and many errors and much head scratching I have managed to follow the 
instructions in:


https://www.cyberciti.biz/faq/how-to-add-network-bridge-with-nmcli-networkmanager-on-linux/ 
.


I have currently implicated this on a Windows 10 client. However, there 
still remains a problem. After the first restart of the Windows client 
the internet was accessible. However, a problem arose after I 
successfully installed br0 (copy attached). I was able to use the LAN 
printer and the 40" TV , but could not access the Host.


I'm sure that I have missed something, but I don't know what.

Guidance to a solution to the problem would be appreciated.

Thanks in advance,

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

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

# Specify that the physical interface that should be connected to the bridge
# should be configured manually, to avoid conflicts with NetworkManager
iface enp2s0 inet manual

#Primary network interface with bridge
auto br0
iface br0 inet static
address 162.237.98.238
broadcast 162.237.98.255
netmask 255.255.255.0
gateway 162.237.98.1
bridge_ports enp2s0
bridge_stp off
bridge_waitport 0
bridge fd 0

Re: Network Problem: Redirection

[Gremlin]

On 2/4/24 09:03, Marco Moock wrote:

Am 04.02.2024 um 07:12:50 Uhr schrieb Gremlin:


I also slay all the mDNS non sense.


mDNS works fine if the host names are properly set and no other way of
setting the addresses (Unicast DNS, /etc/hosts) is being used.



It is not needed if the network is setup correctly with DNS.

Re: Network Problem: Redirection

[Marco Moock]

Am 04.02.2024 um 07:12:50 Uhr schrieb Gremlin:

> I also slay all the mDNS non sense.

mDNS works fine if the host names are properly set and no other way of
setting the addresses (Unicast DNS, /etc/hosts) is being used.

-- 
kind regards
Marco

Spam und Werbung bitte an ichschickerekl...@cartoonies.org

Re: Network Problem: Redirection

[Gremlin]

On 2/4/24 02:39, Marco Moock wrote:

Am 02.02.2024 um 17:12:06 Uhr schrieb Gremlin:


On 2/2/24 16:28, Greg Wooledge wrote:

On Fri, Feb 02, 2024 at 02:03:46PM -0700, Charles Curley wrote:

root@hawk:~# host samba
samba.localdomain is an alias for hawk.localdomain.
hawk.localdomain has address 192.168.100.6


host(1) looks in DNS only.  It doesn't do the standard name
resolution that applications do.
   


host gremlin
gremlin.home.arpa has address 192.168.1.4
gremlin.home.arpa has IPv6 address fe80::a940:6c49:a620:4c09


You have to check from where the other IP address comes.



What other IP addresses.

His "problem" could have been resolved by properly setting up a DNS 
server. I also slay all the mDNS non sense.


# /etc/nsswitch.conf
#
# Example configuration of GNU Name Service Switch functionality.
# If you have the `glibc-doc-reference' and `info' packages installed, try:
# `info libc "Name Service Switch"' for information about this file.

passwd: files
group:  files
shadow: files
gshadow:files

hosts:  files  dns
networks:   files

protocols:  db files
services:   db files
ethers: db files
rpc:db files

netgroup:   nis

Re: Network Problem: Redirection

[hw]

On Fri, 2024-02-02 at 16:47 -0700, Charles Curley wrote:
> On Fri, 2 Feb 2024 15:52:41 -0700
> Charles Curley  wrote:
> 
> > But I don't think that will solve the routing problem.
> 
> Well, I was wrong. That did solve the routing problems.
> 
> I moved the apt-proxy line for the VMs' benefit into a VM's /etc/hosts
> and took it out of hawk's /etc/hosts. samba is now an alias in the
> virtual zone, so I don't need that line at all.
> 
> Thanks, Greg, for spotting that. Sometimes I'm dense. It took me a
> while to realize what you were getting at.
> 

This is not a routing problem in the first place.

If you have a DNS server configured that can resolve for you LAN(s)
(like you should), you don't need to (and should not) change anything
in /etc/hosts.  When you specify different addresses for the same host
at arbitrary places, you're likely to create confusion, especially
when you're using addresses that are supposed to have the same
meaning.  If you need to specify different names for the same host,
use CNAME records.  If you need to specify different addresses for the
same host, use different host names (at least I don't have a better
idea for that).

If you have vlans in use, make sure the addresses in the networks do
not overlap.  Otherwise your networks may not be as virtual as you
think, vlans or not, and you may create something that looks like a
routing problem.  If you're not using vlans and want virtual netwoks,
it's probably a very good idea to use vlans (and to use routing if
desirable and necessary).

Re: Network Problem: Redirection

[Marco Moock]

Am 02.02.2024 um 17:12:06 Uhr schrieb Gremlin:

> On 2/2/24 16:28, Greg Wooledge wrote:
> > On Fri, Feb 02, 2024 at 02:03:46PM -0700, Charles Curley wrote:  
> >> root@hawk:~# host samba
> >> samba.localdomain is an alias for hawk.localdomain.
> >> hawk.localdomain has address 192.168.100.6  
> > 
> > host(1) looks in DNS only.  It doesn't do the standard name
> > resolution that applications do.
> >   
> 
> host gremlin
> gremlin.home.arpa has address 192.168.1.4
> gremlin.home.arpa has IPv6 address fe80::a940:6c49:a620:4c09

You have to check from where the other IP address comes.

-- 
Gruß
Marco

Spam und Werbung bitte an ichschickerekl...@cartoonies.org

Re: Network Problem: Redirection

[Charles Curley]

On Fri, 2 Feb 2024 15:52:41 -0700
Charles Curley  wrote:

> But I don't think that will solve the routing problem.

Well, I was wrong. That did solve the routing problems.

I moved the apt-proxy line for the VMs' benefit into a VM's /etc/hosts
and took it out of hawk's /etc/hosts. samba is now an alias in the
virtual zone, so I don't need that line at all.

Thanks, Greg, for spotting that. Sometimes I'm dense. It took me a
while to realize what you were getting at.

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

Re: Network Problem: Redirection

[Charles Curley]

On Fri, 2 Feb 2024 16:52:48 -0500
Greg Wooledge  wrote:

> Well, we don't know what's "right" or "wrong" on your networks.  These
> are private (non-routable) addresses with no meaning to anyone but you
> and your fellow network denizens.

Agree.

> 
> If you need different name resolution depending on whether you're
> running on the host vs. running on the guest, then I would imagine
> there is some well-known way to define that.  Perhaps a different
> hosts file that's only used by guests?  I don't know virtualization
> stuff well.

Yup. I took a quick and dirty route to solve a problem, and it leaked
over into another area. Sigh. The solution I took depends on the fact
that the libvirtual stuff uses dnsmasq for DNS and DHCP. And dnsmasq
reads the host machine's hosts file. Nice. But, as you pointed out, so
does the host machine's DNS lookup stuff. Sigh.

Possibly the solution to this problem is to see if I can take it out of
hosts, add it to dnsmasq directly, and finagle dnsmasq to only be
visible to the virtual machines.

But I don't think that will solve the routing problem.

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

Re: Network Problem: Redirection

[Gremlin]

On 2/2/24 16:28, Greg Wooledge wrote:

On Fri, Feb 02, 2024 at 02:03:46PM -0700, Charles Curley wrote:

root@hawk:~# host samba
samba.localdomain is an alias for hawk.localdomain.
hawk.localdomain has address 192.168.100.6


host(1) looks in DNS only.  It doesn't do the standard name resolution
that applications do.



host gremlin
gremlin.home.arpa has address 192.168.1.4
gremlin.home.arpa has IPv6 address fe80::a940:6c49:a620:4c09

Re: Network Problem: Redirection

[Greg Wooledge]

> > > # For the benefit of virtual machines.
> > > 192.168.100.12 apt-proxy
> > > 192.168.122.1 samba samba.localdomain  
> > 
> > And that's where it came from (/etc/hosts).  If this IP address is
> > wrong, then it shouldn't be in here.
> 
> Gnrrr. It's right for the virtual network (192.168.122.0). But
> shouldn't that work even if it isn't the "right" address?

Well, we don't know what's "right" or "wrong" on your networks.  These
are private (non-routable) addresses with no meaning to anyone but you
and your fellow network denizens.

If you need different name resolution depending on whether you're
running on the host vs. running on the guest, then I would imagine there
is some well-known way to define that.  Perhaps a different hosts file
that's only used by guests?  I don't know virtualization stuff well.

Re: Network Problem: Redirection

[Charles Curley]

On Fri, 2 Feb 2024 22:10:19 +0100
Marco Moock  wrote:

> Sorry for the first post.
> Your problem is located in the name resolution.
> 
> Show /etc/nsswitch.conf

I have not touched this.

root@hawk:~# cat /etc/nsswitch.conf 
# /etc/nsswitch.conf
#
# Example configuration of GNU Name Service Switch functionality.
# If you have the `glibc-doc-reference' and `info' packages installed, try:
# `info libc "Name Service Switch"' for information about this file.

passwd: files systemd
group:  files systemd
shadow: files
gshadow:files

hosts:  files mdns4_minimal [NOTFOUND=return] dns mymachines
networks:   files

protocols:  db files
services:   db files
ethers: db files
rpc:db files

netgroup:   nis
root@hawk:~# 


-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

Re: Network Problem: Redirection

[Charles Curley]

On Fri, 2 Feb 2024 16:28:06 -0500
Greg Wooledge  wrote:

> > However, when I try to ping samba by host name:
> > 
> > root@hawk:~# ping samba
> > PING samba (192.168.122.1) 56(84) bytes of data.  
> 
> Note that this is a *different* IP address.

Good catch, thank you.

> 
> > # For the benefit of virtual machines.
> > 192.168.100.12 apt-proxy
> > 192.168.122.1 samba samba.localdomain  
> 
> And that's where it came from (/etc/hosts).  If this IP address is
> wrong, then it shouldn't be in here.

Gnrrr. It's right for the virtual network (192.168.122.0). But
shouldn't that work even if it isn't the "right" address?

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

Re: Network Problem: Redirection

[Greg Wooledge]

On Fri, Feb 02, 2024 at 02:03:46PM -0700, Charles Curley wrote:
> root@hawk:~# host samba
> samba.localdomain is an alias for hawk.localdomain.
> hawk.localdomain has address 192.168.100.6

host(1) looks in DNS only.  It doesn't do the standard name resolution
that applications do.

> root@hawk:~# ping 192.168.100.6
> PING 192.168.100.6 (192.168.100.6) 56(84) bytes of data.
> 64 bytes from 192.168.100.6: icmp_seq=1 ttl=64 time=0.083 ms

> However, when I try to ping samba by host name:
> 
> root@hawk:~# ping samba
> PING samba (192.168.122.1) 56(84) bytes of data.

Note that this is a *different* IP address.

> # For the benefit of virtual machines.
> 192.168.100.12 apt-proxy
> 192.168.122.1 samba samba.localdomain

And that's where it came from (/etc/hosts).  If this IP address is
wrong, then it shouldn't be in here.

Re: Network Problem: Redirection

[Marco Moock]

Am 02.02.2024 um 14:03:46 Uhr schrieb Charles Curley:

> root@hawk:~# host samba
> samba.localdomain is an alias for hawk.localdomain.
> hawk.localdomain has address 192.168.100.6


> root@hawk:~# ping samba
> PING samba (192.168.122.1) 56(84) bytes of data.


Sorry for the first post.
Your problem is located in the name resolution.

Show /etc/nsswitch.conf


-- 
kind regards
Marco

Spam und Werbung bitte an ichschickerekl...@cartoonies.org

Re: Network Problem: Redirection

[Marco Moock]

Am 02.02.2024 um 14:03:46 Uhr schrieb Charles Curley:

> From apt-proxy (192.168.100.12): icmp_seq=2 Redirect Host(New
> nexthop: hawk.localdomain (192.168.100.6))

Check the routing table on apt-proxy.
ICMP redirect happens if you have 2 routers on the same ethernet link
and the router you try to contact know a better route to the
destination.
Although, both routes need to point to the same direction.

-- 
Gruß
Marco

Spam und Werbung bitte an ichschickerekl...@cartoonies.org

Network Problem: Redirection

[Charles Curley]

I have an interesting network problem. I have a samba service on hawk. I
have an alias for it in DNS:

root@hawk:~# host samba
samba.localdomain is an alias for hawk.localdomain.
hawk.localdomain has address 192.168.100.6
root@hawk:~# host hawk
hawk.localdomain has address 192.168.100.6
root@hawk:~# 

I can ping by IP address just fine:

root@hawk:~# ping 192.168.100.6
PING 192.168.100.6 (192.168.100.6) 56(84) bytes of data.
64 bytes from 192.168.100.6: icmp_seq=1 ttl=64 time=0.083 ms
64 bytes from 192.168.100.6: icmp_seq=2 ttl=64 time=0.034 ms
64 bytes from 192.168.100.6: icmp_seq=3 ttl=64 time=0.044 ms
64 bytes from 192.168.100.6: icmp_seq=4 ttl=64 time=0.052 ms
64 bytes from 192.168.100.6: icmp_seq=5 ttl=64 time=0.063 ms

--- 192.168.100.6 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4101ms
rtt min/avg/max/mdev = 0.034/0.055/0.083/0.016 ms
root@hawk:~# 

However, when I try to ping samba by host name:

root@hawk:~# ping samba
PING samba (192.168.122.1) 56(84) bytes of data.
From apt-proxy (192.168.100.12): icmp_seq=2 Redirect Host(New nexthop: 
hawk.localdomain (192.168.100.6))
From apt-proxy (192.168.100.12): icmp_seq=3 Redirect Host(New nexthop: 
hawk.localdomain (192.168.100.6))
From apt-proxy (192.168.100.12): icmp_seq=4 Redirect Host(New nexthop: 
hawk.localdomain (192.168.100.6))
From apt-proxy (192.168.100.12): icmp_seq=5 Redirect Host(New nexthop: 
hawk.localdomain (192.168.100.6))

--- samba ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 4019ms

root@hawk:~# host apt-proxy
apt-proxy.localdomain is an alias for issola.localdomain.
issola.localdomain has address 192.168.100.12
root@hawk:~# 

192.168.100.12 is my router. apt-roxy is defined in /etc/hosts:

root@hawk:~# cat /etc/hosts
127.0.0.1   localhost
127.0.1.1   hawk.localdomainhawk

# The following lines are desirable for IPv6 capable hosts
::1 localhost ip6-localhost ip6-loopback
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters

# For the benefit of virtual machines.
192.168.100.12 apt-proxy
192.168.122.1 samba samba.localdomain
root@hawk:~# 

There is an apt-cacher-ng running on issola, 192.168.100.12. That
apt-proxy entry is for the benefit of virtual machines on hawk.

This mis-routing prevents the samba clients on hawk from mounting if I
use the host name. Other machines have no problems with the share.
However, as soon as I change hawk's fstab entry to the loopback
address, samba on hawk is fine.

Using the IP address works, but I'd rather use an alias in case some
time in the future I move the samba service to another machine; all I
need do is change the alias.

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

Re: network problem (fwd)

[David]

On Thu, 7 Oct 2021 at 12:53, Lee  wrote:
> On 10/6/21, David  wrote:

> > But others here are vastly more knowledgeable than I am about
> > networks, so additions or corrections are welcome, as always :)

> It's Classless Inter-domain Routing (CIDR) now and network masks are
> no longer supported [1].  If you take a look at RFC-950 [2], there is
> no requirement that the network and sub-network bits of an address be
> contiguous.  252.252.252.252 was a perfectly valid mask and yields the
> same number of host bits (8) as a 255.255.255.0 mask does.
>
> Then along came CIDR and dis-contiguous network/subnet bits were prohibited.

Ahhh, that's interesting, I didn't know about that aspect.

Thank you for taking the time to explain clearly, with links.
I really appreciate it!

Re: network problem (fwd)

[Lee]

On 10/6/21, David  wrote:
> On Thu, 7 Oct 2021 at 10:53,  wrote:
>> On Wednesday, October 06, 2021 11:15:11 AM Brian wrote:
>> > On Wed 06 Oct 2021 at 14:09:23 +0200, Pierre Frenkiel wrote:
>>
>> > >netmask 255.255.255.0
>> > >gateway 192.168.1.1
>> >
>> > Just in passing: The line with netmask 255.255.255.0 can be deleted.
>> > It is a deprecated option, as is broadcast. See #912220.
>>
>> Does that mean 255.255.255.0 is the default netmask?
>
> The netmask has to be specified *somewhere*. My understanding
> is that either CIDR or 'netmask' is required to do that. Read
> about CIDR here:
> https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing#CIDR_notation
>
> But others here are vastly more knowledgeable than I am about
> networks, so additions or corrections are welcome, as always :)

It's Classless Inter-domain Routing (CIDR) now and network masks are
no longer supported [1].  If you take a look at RFC-950 [2], there is
no requirement that the network and sub-network bits of an address be
contiguous.  252.252.252.252 was a perfectly valid mask and yields the
same number of host bits (8) as a 255.255.255.0 mask does.

Then along came CIDR and dis-contiguous network/subnet bits were prohibited.

Lee


[1]  Specifically, _bitmasks_ are no longer supported. "network masks"
are now just another way of specifying the first however many bits of
an address that make up the network portion of an address - eg. /24
and 255.255.255.0 both specify the first 24 bits of an address

[2]  https://datatracker.ietf.org/doc/html/rfc950#page-15

   3.  A Class C Network Case (illustrating non-contiguous subnet bits)

  For this case, assume that the requesting host is on class C
  network 192.1.127.0, has address 192.1.127.19, that there is a
  gateway at 192.1.127.50, and that on network an 3-bit subnet field
  is in use (01011000), that is, the address mask is 255.255.255.88.

Re: network problem (fwd)

[David Wright]

On Wed 06 Oct 2021 at 14:09:23 (+0200), Pierre Frenkiel wrote:
> please note that the main problem is
>   "why the /etc/network/interfaces" is not used?"

> I have the following problem on my laptop.
> my /etc/network/interfaces file contains:
>auto enp0s1
>iface enp0s1  inet static
>address 192.168.1.10
>netmask 255.255.255.0
>gateway 192.168.1.1
> 
>but after boot, ifconfig gives
> 
>address 192.168.0.163
>netmask 255.255.255.0
>gateway 192.168.1.1
> 
>Then, networking works i.e. I can reach Internet, but of course
>not my desktop and other devices 192.168.1.xx
> 
>I looked on the entire disk to find where this address 192.168.0.163
>is hidden, but I was unable to find it !
> 
>rather strange, isn't it?

One possibility might be that you've somehow got yourself connected to
the WAN side of your router, rather that the LAN side.
I think you should login to your router and see what the address of
the Internet Port is.
I seem to remember that happening to someone here with one of those
"captive" or ISP-managed modem/routers.
It's one reason why we run three routers at home: one that Cox rent,
the real one (mine), and one with a broken WAN port that we use as
a switch and wireless repeater.

Cheers,
David.

Re: network problem (fwd)

[David]

On Thu, 7 Oct 2021 at 10:53,  wrote:
> On Wednesday, October 06, 2021 11:15:11 AM Brian wrote:
> > On Wed 06 Oct 2021 at 14:09:23 +0200, Pierre Frenkiel wrote:
>
> > >netmask 255.255.255.0
> > >gateway 192.168.1.1
> >
> > Just in passing: The line with netmask 255.255.255.0 can be deleted.
> > It is a deprecated option, as is broadcast. See #912220.
>
> Does that mean 255.255.255.0 is the default netmask?

The netmask has to be specified *somewhere*. My understanding
is that either CIDR or 'netmask' is required to do that. Read
about CIDR here:
https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing#CIDR_notation

But others here are vastly more knowledgeable than I am about
networks, so additions or corrections are welcome, as always :)

Re: network problem (fwd)

[rhkramer]

On Wednesday, October 06, 2021 11:15:11 AM Brian wrote:
> On Wed 06 Oct 2021 at 14:09:23 +0200, Pierre Frenkiel wrote:

> >netmask 255.255.255.0
> >gateway 192.168.1.1
> 
> Just in passing: The line with netmask 255.255.255.0 can be deleted.
> It is a deprecated option, as is broadcast. See #912220.

Does that mean 255.255.255.0 is the default netmask?

Re: network problem (fwd)

[David]

On Wed, 6 Oct 2021 at 23:09, Pierre Frenkiel  wrote:
>
> please note that the main problem is
>"why the /etc/network/interfaces" is not used?"

Ok. Noted.

Several knowledgeable and helpful people have already
made an effort trying to help you answer exactly this.
You can find those efforts in the 4 links labelled "Follow-Ups"
at the bottom of this web page:
https://lists.debian.org/debian-user/2021/10/msg00244.html

If you do not engage with those efforts then it really is a
puzzle to understand what kind of help you expect when
you write to this list.

Should we conclude that you prefer to solve this without
our assistance?

If that is the case, you could do the following:

First, learn what DHCP is.

Second, learn what all the commands (that others
have suggested in the links above) do, and how to
understand their outputs.

Third, use those commands to answer the question yourself.

If that is not the case, then perhaps you could explain
what kind of help you do expect when you ask a question
here.

Re: network problem (fwd)

[Brian]

On Wed 06 Oct 2021 at 16:40:55 +0100, Thomas Pircher wrote:

> Brian wrote:
> > Just in passing: The line with netmask 255.255.255.0 can be deleted.
> > It is a deprecated option, as is broadcast. See #912220.
> 
> Crikey, it is indeed deprecated. Just removing the line will probably
> not be a good idea. I guess it can be deleted only when the address line
> contains the netmask in CIDR notation:
> > >address 192.168.1.10/24

That looks to be the situation, according to examples in interfaces(5).
Mind you

  address 192.168.7.40

works for me. Don't ask me why. It is easy enough to rectify.

-- 
Brian.

Re: network problem (fwd)

[Thomas Pircher]

Brian wrote:

Just in passing: The line with netmask 255.255.255.0 can be deleted.
It is a deprecated option, as is broadcast. See #912220.


Crikey, it is indeed deprecated. Just removing the line will probably
not be a good idea. I guess it can be deleted only when the address line
contains the netmask in CIDR notation:

   address 192.168.1.10/24


Thomas

Re: network problem (fwd)

[Brian]

On Wed 06 Oct 2021 at 14:09:23 +0200, Pierre Frenkiel wrote:

[...]

> I have the following problem on my laptop.
> my /etc/network/interfaces file contains:
>auto enp0s1
>iface enp0s1  inet static
>address 192.168.1.10
>netmask 255.255.255.0
>gateway 192.168.1.1

Just in passing: The line with netmask 255.255.255.0 can be deleted.
It is a deprecated option, as is broadcast. See #912220.

-- 
Brian.

Re: network problem (fwd)

[Greg Wooledge]

On Wed, Oct 06, 2021 at 02:09:23PM +0200, Pierre Frenkiel wrote:
> please note that the main problem is
>   "why the /etc/network/interfaces" is not used?"

Please show us the information you've been asked to show, by multiple
people:

ip addr
ip route

network problem (fwd)

[Pierre Frenkiel]

please note that the main problem is
  "why the /etc/network/interfaces" is not used?"

best regards,
--
Pierre Frenkiel--- Begin Message ---


hi,
I have the following problem on my laptop.
my /etc/network/interfaces file contains:
   auto enp0s1
   iface enp0s1  inet static
   address 192.168.1.10
   netmask 255.255.255.0
   gateway 192.168.1.1

   but after boot, ifconfig gives

   address 192.168.0.163
   netmask 255.255.255.0
   gateway 192.168.1.1

   Then, networking works i.e. I can reach Internet, but of course
   not my desktop and other devices 192.168.1.xx

   I looked on the entire disk to find where this address 192.168.0.163
   is hidden, but I was unable to find it !

   rather strange, isn't it?

best regards,
--
Pierre Frenkiel
--- End Message ---

Re: network problem

[Reco]

Hi.

On Tue, Oct 05, 2021 at 10:00:45PM +0200, Pierre Frenkiel wrote:
> hi,
> I have the following problem on my laptop.
> my /etc/network/interfaces file contains:
>auto enp0s1
>iface enp0s1  inet static
>address 192.168.1.10
>netmask 255.255.255.0
>gateway 192.168.1.1

That's probably Ok.


>but after boot, ifconfig gives
> 
>address 192.168.0.163
>netmask 255.255.255.0
>gateway 192.168.1.1

And that is not.

First, ifconfig is not able to show you IP routing, so please be more
specific at how exactly you've got this result.
Second, it's impossible to have a working default gateway that's outside
the subnet you're having, and it's exactly what you have here.

>Then, networking works i.e. I can reach Internet, but of course
>not my desktop and other devices 192.168.1.xx

Third, the whole purpose of default gateway is to let you communicate
with host that are outside your subnet.


>rather strange, isn't it?

dpkg -l 'ifupdown*'
dpkg -l 'network*'

Reco

Re: network problem

[ghe2001]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256



‐‐‐ Original Message ‐‐‐
On Tuesday, October 5, 2021 2:00 PM, Pierre Frenkiel 
 wrote:

> hi,
> I have the following problem on my laptop.
> my /etc/network/interfaces file contains:
> auto enp0s1
> iface enp0s1 inet static
> address 192.168.1.10
> netmask 255.255.255.0
> gateway 192.168.1.1
>
> but after boot, ifconfig gives
>
> address 192.168.0.163
> netmask 255.255.255.0
> gateway 192.168.1.1
>
> Then, networking works i.e. I can reach Internet, but of course
> not my desktop and other devices 192.168.1.xx
>
> I looked on the entire disk to find where this address 192.168.0.163
> is hidden, but I was unable to find it !
>
> rather strange, isn't it?

Most peculiar indeed.

Does the interface always get the same address?

Have you tried setting the IP with ifconfig -- after the box is up with the bad 
IP address?

Is there anything in /etc/init.d that might be doing it?

Have you looked at dmesg?  (That 163's gotta be somewhere.)

Have you looked at what's in /etc/network/interfaces.d?  (There's nothing in 
mine, but ifup works as expected here.)

Have you tried Webmin?  (I know, I know, but it works.)

Have you tried pinging the two addresses?  (Not likely, but something's bent 
somewhere.)

A workaround: change the netmask everywhere on your LAN to 255.255.0.0 and let 
the address be whatever systemd wants to assign to it :-)

--
Glenn English
-BEGIN PGP SIGNATURE-
Version: ProtonMail

wsBzBAEBCAAGBQJhXL2SACEJEJ/XhjGCrIwyFiEELKJzD0JScCVjQA2Xn9eG
MYKsjDLdhwgAwp4apR3uGebYU5bOx+qQbh8iGDFa+sPxMzqdzYa0bVBcoaUE
hzxPw1+pAe3vEfD/VYYrm5GGC4aUHILqH7SffpMMbWEZtSaL5ghKC8EGZhlk
wcP0d7p3paPNvKpCHMOUkxDQOd04Cqu+gudkeiQasqAPBqnTzLpk0sEBIsj9
EMeA/RCivsIGt+VvNQPaR2+surTnubOx95pwT/SmFT1at6awcbiYYNjUU08T
rnOdSAA1A7/X5UED1Mo5R+6k/DT3DqKzkK1jmwY1IKt24iBLH4wn/2md6j8w
WpbLDjn/U9Gb+rpNqdEhLkVwMgLrxFRkyKkH+gJangN7JyExoT6RbQ==
=Ze8U
-END PGP SIGNATURE-

Re: network problem

[Greg Wooledge]

On Tue, Oct 05, 2021 at 10:00:45PM +0200, Pierre Frenkiel wrote:
> hi,
> I have the following problem on my laptop.
> my /etc/network/interfaces file contains:
>auto enp0s1
>iface enp0s1  inet static
>address 192.168.1.10
>netmask 255.255.255.0
>gateway 192.168.1.1
> 
>but after boot, ifconfig gives
> 
>address 192.168.0.163
>netmask 255.255.255.0
>gateway 192.168.1.1

There is a *lot* to unpack here.  I'm not sure where to start.

Let's start here: that is *not* the output of "ifconfig" on Debian.
The ifconfig command, which is not installed by default, but is available
in an optional package, does not produce output that looks anything
like that.

Most particularly, it does not show any information about routing.  So
that "gateway" line that you claim it shows... that didn't come from
ifconfig, not even if you reformatted the hell out of it.

That leaves us to guess what you actually did, what the actual output
of ifconfig is, and why you're misleading us.

Now, let's assume for the sake of argument that you actually ran several
different commands, collated their output together in your head, and
rewrote it into this format.  Let's even assume that you did not make
any typos during this entire procedure.

This still leaves us with some questions.

1) What is the actual name of your network interface?

   The stanza in /etc/network/interface will only apply if the
   interface's name is enp0s1.  If it's not, then something else (perhaps
   network-manager) will take over and configure the interface.

The 192.168.0.163 address might have come from DHCP.  A fallback
configuration, like the one used by N-M, might be "run a DHCP client
and see if that works".

>Then, networking works i.e. I can reach Internet, but of course
>not my desktop and other devices 192.168.1.xx

2) What is your full routing table?  "ip route" under modern era tools,
   or "route -n" under the legacy tools.

It's not clear to me how you have working Internet access if your default
route is an address (192.168.1.1) that isn't on your subnet (192.168.0.0/24).

At the very least, you would need a route that leads you to the 192.168.0
network.  Perhaps you have one.  But you didn't show it.

Then, if for some reason you really *do* have a 192.168.0 address,
and a route to the 192.168.1 network, and a default gateway of 192.168.1.1,
and if all of this actually works, then... where did this routing table
get configured?

It's a mystery for sure.

You might want to look for log files that indicate what's happening.  They
could be in /var/log/ or you might need to use journalctl.

Meanwhile, use "ip addr" and "ip route" to see what your actual network
configuration is.  Don't reformat it.  Don't omit pieces of it.  Don't
mash the two together.

Re: network problem

[Dan Ritter]

Pierre Frenkiel wrote: 
> hi,
> I have the following problem on my laptop.
> my /etc/network/interfaces file contains:
>auto enp0s1
>iface enp0s1  inet static
>address 192.168.1.10
>netmask 255.255.255.0
>gateway 192.168.1.1
> 
>but after boot, ifconfig gives
> 
>address 192.168.0.163
>netmask 255.255.255.0
>gateway 192.168.1.1
> 
>Then, networking works i.e. I can reach Internet, but of course
>not my desktop and other devices 192.168.1.xx
> 
>I looked on the entire disk to find where this address 192.168.0.163
>is hidden, but I was unable to find it !
> 
>rather strange, isn't it?

First, let's see if you have the right interface.

ip link show |grep enp0s1

if that doesn't show you a line of config, you are specifying
the wrong interface.

ip link show

will show all of them to you.

Second, let's see if something else is doing the configuration:

grep -C1 ifupdown /etc/NetworkManager

(you want this to show managed=false)

ls /etc/systemd/network/

(you would like this to be empty)


Let us know what you find out.

-dsr-

network problem

[Pierre Frenkiel]

hi,
I have the following problem on my laptop.
my /etc/network/interfaces file contains:
   auto enp0s1
   iface enp0s1  inet static
   address 192.168.1.10
   netmask 255.255.255.0
   gateway 192.168.1.1

   but after boot, ifconfig gives

   address 192.168.0.163
   netmask 255.255.255.0
   gateway 192.168.1.1

   Then, networking works i.e. I can reach Internet, but of course
   not my desktop and other devices 192.168.1.xx

   I looked on the entire disk to find where this address 192.168.0.163
   is hidden, but I was unable to find it !

   rather strange, isn't it?

best regards,
--
Pierre Frenkiel

Re: Strange Network Problem

[David Christensen]

On 09/02/2018 03:22 PM, mick crane wrote:

On 2018-09-02 19:39, David Christensen wrote:

On 09/02/2018 05:48 AM, mick crane wrote:

On 2018-09-02 13:16, Stephen P. Molnar wrote:


The Firewall Passthrough is set to Allocation Mode set to 'Passthrough
with the Passthrough Mode set to 'DHCPS-dynamic '.

It's my intention to change the Allocation Mode to 'Off', as soon as I
talk to AT Tech Support to make sure that doesn't mess things up.


I'm not quite understanding how one PC is going straight through the 
router to the ISP's network whereas you have other PCs with private 
addresses.


In my case as I understand it the ISP's router redirects from its 
external network to internal private.
PC with say 2 NICS one to the router and one to a switch whereby 
connect the local machines using PC with 2 NICS as gateway doing 
DHCP, firewall and all that.


mick



https://en.wikipedia.org/wiki/Firewall_pinhole

https://en.wikipedia.org/wiki/DMZ_(computing)

https://en.wikipedia.org/wiki/DMZ_(computing)#DMZ_host


The OP appears to have the third option enabled on his gateway.


the ISP router maybe has NAT ( that's what it's called isn't it ) on 
some of the ports that things with the private 192.168 block connect to 
but seems to have a DMZ on one of the ports.

I dunno

mick


https://en.wikipedia.org/wiki/Dynamic_Host_Configuration_Protocol

https://en.wikipedia.org/wiki/Network_address_translation


Internet gateways typically provide DHCP and NAT/IP masquerading to 
hosts on a private network (e.g. 192.168.1.0/24).  DMZ hosts are treated 
specially.



David

Re: Strange Network Problem

[mick crane]

On 2018-09-02 19:39, David Christensen wrote:

On 09/02/2018 05:48 AM, mick crane wrote:

On 2018-09-02 13:16, Stephen P. Molnar wrote:

The Firewall Passthrough is set to Allocation Mode set to 
'Passthrough

with the Passthrough Mode set to 'DHCPS-dynamic '.

It's my intention to change the Allocation Mode to 'Off', as soon as 
I

talk to AT Tech Support to make sure that doesn't mess things up.


I'm not quite understanding how one PC is going straight through the 
router to the ISP's network whereas you have other PCs with private 
addresses.


In my case as I understand it the ISP's router redirects from its 
external network to internal private.
PC with say 2 NICS one to the router and one to a switch whereby 
connect the local machines using PC with 2 NICS as gateway doing DHCP, 
firewall and all that.


mick



https://en.wikipedia.org/wiki/Firewall_pinhole

https://en.wikipedia.org/wiki/DMZ_(computing)

https://en.wikipedia.org/wiki/DMZ_(computing)#DMZ_host


The OP appears to have the third option enabled on his gateway.


the ISP router maybe has NAT ( that's what it's called isn't it ) on 
some of the ports that things with the private 192.168 block connect to 
but seems to have a DMZ on one of the ports.

I dunno

mick


--
Key ID4BFEBB31

Re: Strange Network Problem

[David Christensen]

On 09/02/2018 05:48 AM, mick crane wrote:

On 2018-09-02 13:16, Stephen P. Molnar wrote:


The Firewall Passthrough is set to Allocation Mode set to 'Passthrough
with the Passthrough Mode set to 'DHCPS-dynamic '.

It's my intention to change the Allocation Mode to 'Off', as soon as I
talk to AT Tech Support to make sure that doesn't mess things up.


I'm not quite understanding how one PC is going straight through the 
router to the ISP's network whereas you have other PCs with private 
addresses.


In my case as I understand it the ISP's router redirects from its 
external network to internal private.
PC with say 2 NICS one to the router and one to a switch whereby connect 
the local machines using PC with 2 NICS as gateway doing DHCP, firewall 
and all that.


mick



https://en.wikipedia.org/wiki/Firewall_pinhole

https://en.wikipedia.org/wiki/DMZ_(computing)

https://en.wikipedia.org/wiki/DMZ_(computing)#DMZ_host


The OP appears to have the third option enabled on his gateway.


David

Re: Strange Network Problem

[mick crane]

On 2018-09-02 13:16, Stephen P. Molnar wrote:


The Firewall Passthrough is set to Allocation Mode set to 'Passthrough
with the Passthrough Mode set to 'DHCPS-dynamic '.

It's my intention to change the Allocation Mode to 'Off', as soon as I
talk to AT Tech Support to make sure that doesn't mess things up.


I'm not quite understanding how one PC is going straight through the 
router to the ISP's network whereas you have other PCs with private 
addresses.


In my case as I understand it the ISP's router redirects from its 
external network to internal private.
PC with say 2 NICS one to the router and one to a switch whereby connect 
the local machines using PC with 2 NICS as gateway doing DHCP, firewall 
and all that.


mick




--
Key ID4BFEBB31

Re: Strange Network Problem

[Stephen P. Molnar]

On 09/02/2018 01:37 AM, David Christensen wrote:

On 09/01/2018 04:05 AM, Stephen P. Molnar wrote:



On 08/31/2018 10:41 PM, David Christensen wrote:

On 08/31/2018 12:50 PM, Stephen P. Molnar wrote:

I am running Debian Stretch on my Linux platform.

I have noticed low internet traffic when I have not been doing 
anything outside of my LAN.  This has made me a tad suspicious.


Now:

root@AbNormal:/home/comp# ifconfig
enp2s0: flags=4163 mtu 1500
 inet 162.237.98.238  netmask 255.255.252.0 broadcast 
162.237.99.255

 ether bc:ee:7b:5e:83:36  txqueuelen 1000 (Ethernet)
 RX packets 796401  bytes 529829454 (505.2 MiB)
 RX errors 0  dropped 0  overruns 0  frame 0
 TX packets 236054  bytes 22520861 (21.4 MiB)
 TX errors 0  dropped 0 overruns 0  carrier 0 collisions 0

lo: flags=73  mtu 65536
 inet 127.0.0.1  netmask 255.0.0.0
 loop  txqueuelen 1  (Local Loopback)
 RX packets 399  bytes 42360 (41.3 KiB)
 RX errors 0  dropped 0  overruns 0  frame 0
 TX packets 399  bytes 42360 (41.3 KiB)
 TX errors 0  dropped 0 overruns 0  carrier 0 collisions 0


It turns out that this ISP, 162.237.98.238 is my ISP, AT here in 
Columbus, Ohio.


The other four nodes on my LAn all have IP's starting with 
192.168.1 - which is what it's supposed to be.


Just what is going on here? I don't have a clue.

I dop have firewalls implemented on both the modem and the computers.

Any insights will be much appreciated.

Thanks in advance.



Running nslookup(1):

2018-08-31 18:53:21 dpchrist@vstretch ~
$ nslookup 162.237.98.238
Server:192.168.5.1
Address:192.168.5.1#53

Non-authoritative answer:
238.98.237.162.in-addr.arpaname = 
162-237-98-238.lightspeed.clmboh.sbcglobal.net.


Authoritative answers can be found from:


Running host(1):

2018-08-31 18:58:15 dpchrist@vstretch ~
$ host 162.237.98.238
238.98.237.162.in-addr.arpa domain name pointer 
162-237-98-238.lightspeed.clmboh.sbcglobal.net.



162.237.98.238 appears to be a valid IPv4 public Internet address.


You should have a device provided by your Internet service provider 
(ISP) between their wiring (e.g. telephone service) and your wiring 
(e.g. Ethernet local area network/LAN).  What is the make and model 
of the ISP device?  Please provide a URL to the product support page.



What are the "other four nodes"?


How is everything interconnected?


David



Thanks for your reply.

ISO device is an Arris BGE210-700 Broadband Gateway Release 1.0 from 
AT (http://www.arris.com/Search/?q=Arris+BGE210-700+Broadband+Gateway)


Wired Connections:  2 Desktops,  printer and VOIP telephone

Wireless Connections:  Laptop and two Android Smartphones

root@AbNormal:/home/comp# nslookup
 > nslookup -a
Server:192.168.1.254
Address:192.168.1.254#53

Non-authoritative answer:
Name:nslookup
Address: 198.105.244.130
Name:nslookup
Address: 104.239.207.44
 >
 > host
Server:192.168.1.254
Address:192.168.1.254#53

Non-authoritative answer:
*** Can't find host: No answer
 >



It appears that your ISP gateway device is configured to pass through 
it's Internet address (and all incoming packets) to the computer in 
question.  This is a feature that allows a server behind the gateway 
to be visible on the Internet.



Enabling or disabling gateway features is a matter of browsing to the 
gateway's IP address (192.168.1.254?) and operatingthe web control panel.



I have a Pace Plc Model 5268AC, also through AT  The relevant 
control panel page for putting a server on the Internet would seem to 
be Settings -> Firewall -> Applications, Pinholes and DMZ.  I would 
pick a computer and then select "Allow all applications (DMZplus 
mode)" to turn the feature on.  The feature is currently off, so I 
don't know how I would turn it off.



If you can't figure out the control panel for your gateway, contact 
your ISP.



David



Thanks for your reply.

The Firewall Passthrough is set to Allocation Mode set to 'Passthrough 
with the Passthrough Mode set to 'DHCPS-dynamic '.


It's my intention to change the Allocation Mode to 'Off', as soon as I 
talk to AT Tech Support to make sure that doesn't mess things up.


--
Stephen P. Molnar, Ph.D.
Consultant
www.molecular-modeling.net
(614)312-7528 (c)
Skype: smolnar1

Re: Strange Network Problem

[David Christensen]

On 09/01/2018 04:05 AM, Stephen P. Molnar wrote:



On 08/31/2018 10:41 PM, David Christensen wrote:

On 08/31/2018 12:50 PM, Stephen P. Molnar wrote:

I am running Debian Stretch on my Linux platform.

I have noticed low internet traffic when I have not been doing 
anything outside of my LAN.  This has made me a tad suspicious.


Now:

root@AbNormal:/home/comp# ifconfig
enp2s0: flags=4163  mtu 1500
 inet 162.237.98.238  netmask 255.255.252.0  broadcast 
162.237.99.255

 ether bc:ee:7b:5e:83:36  txqueuelen 1000  (Ethernet)
 RX packets 796401  bytes 529829454 (505.2 MiB)
 RX errors 0  dropped 0  overruns 0  frame 0
 TX packets 236054  bytes 22520861 (21.4 MiB)
 TX errors 0  dropped 0 overruns 0  carrier 0 collisions 0

lo: flags=73  mtu 65536
 inet 127.0.0.1  netmask 255.0.0.0
 loop  txqueuelen 1  (Local Loopback)
 RX packets 399  bytes 42360 (41.3 KiB)
 RX errors 0  dropped 0  overruns 0  frame 0
 TX packets 399  bytes 42360 (41.3 KiB)
 TX errors 0  dropped 0 overruns 0  carrier 0 collisions 0


It turns out that this ISP, 162.237.98.238 is my ISP, AT here in 
Columbus, Ohio.


The other four nodes on my LAn all have IP's starting with 192.168.1 
- which is what it's supposed to be.


Just what is going on here? I don't have a clue.

I dop have firewalls implemented on both the modem and the computers.

Any insights will be much appreciated.

Thanks in advance.



Running nslookup(1):

    2018-08-31 18:53:21 dpchrist@vstretch ~
    $ nslookup 162.237.98.238
    Server:    192.168.5.1
    Address:    192.168.5.1#53

    Non-authoritative answer:
    238.98.237.162.in-addr.arpa    name = 
162-237-98-238.lightspeed.clmboh.sbcglobal.net.


    Authoritative answers can be found from:


Running host(1):

    2018-08-31 18:58:15 dpchrist@vstretch ~
    $ host 162.237.98.238
    238.98.237.162.in-addr.arpa domain name pointer 
162-237-98-238.lightspeed.clmboh.sbcglobal.net.



162.237.98.238 appears to be a valid IPv4 public Internet address.


You should have a device provided by your Internet service provider 
(ISP) between their wiring (e.g. telephone service) and your wiring 
(e.g. Ethernet local area network/LAN).  What is the make and model of 
the ISP device?  Please provide a URL to the product support page.



What are the "other four nodes"?


How is everything interconnected?


David



Thanks for your reply.

ISO device is an Arris BGE210-700 Broadband Gateway Release 1.0 from 
AT (http://www.arris.com/Search/?q=Arris+BGE210-700+Broadband+Gateway)


Wired Connections:  2 Desktops,  printer and VOIP telephone

Wireless Connections:  Laptop and two Android Smartphones

root@AbNormal:/home/comp# nslookup
 > nslookup -a
Server:    192.168.1.254
Address:    192.168.1.254#53

Non-authoritative answer:
Name:    nslookup
Address: 198.105.244.130
Name:    nslookup
Address: 104.239.207.44
 >
 > host
Server:    192.168.1.254
Address:    192.168.1.254#53

Non-authoritative answer:
*** Can't find host: No answer
 >



It appears that your ISP gateway device is configured to pass through 
it's Internet address (and all incoming packets) to the computer in 
question.  This is a feature that allows a server behind the gateway to 
be visible on the Internet.



Enabling or disabling gateway features is a matter of browsing to the 
gateway's IP address (192.168.1.254?) and operatingthe web control panel.



I have a Pace Plc Model 5268AC, also through AT  The relevant control 
panel page for putting a server on the Internet would seem to be 
Settings -> Firewall -> Applications, Pinholes and DMZ.  I would pick a 
computer and then select "Allow all applications (DMZplus mode)" to turn 
the feature on.  The feature is currently off, so I don't know how I 
would turn it off.



If you can't figure out the control panel for your gateway, contact your 
ISP.



David

Re: Strange Network Problem

[rhkramer]

On Saturday, September 01, 2018 11:59:27 AM Stephen P. Molnar wrote:
> On 09/01/2018 08:26 AM, rhkra...@gmail.com wrote:
> > On Saturday, September 01, 2018 07:05:55 AM Stephen P. Molnar wrote:
> >> On 08/31/2018 10:41 PM, David Christensen wrote:
> >>> On 08/31/2018 12:50 PM, Stephen P. Molnar wrote:
>  I am running Debian Stretch on my Linux platform.
>  
>  I have noticed low internet traffic when I have not been doing
>  anything outside of my LAN.  This has made me a tad suspicious.
> >> 
> >> Wired Connections:  2 Desktops,  printer and VOIP telephone
> >> 
> >> Wireless Connections:  Laptop and two Android Smartphones
> > 
> > Out of curiosity, who is your VOIP service provider?
> > 
> > I use ObiHai, and find that it exchanges traffic with its "server"
> > continuously.
> > 
> > I've not recently attempted to check how much, and don't remember any
> > figures, but it wouldn't surprise me if that accounts for some, most,
> > all of the traffic you report.
> > 
> > And, maybe Android smartphones do something similar, especially if they
> > are setup for VOIP or some similar service.
> 
> AT

Hmm, Ok, I don't have any experience with AT VOIP, but, I still suspect that 
is the source of at least some of the traffic you notice when you are not doing 
anything outside your LAN.

Re: Strange Network Problem

[Stephen P. Molnar]

On 09/01/2018 08:26 AM, rhkra...@gmail.com wrote:

On Saturday, September 01, 2018 07:05:55 AM Stephen P. Molnar wrote:

On 08/31/2018 10:41 PM, David Christensen wrote:

On 08/31/2018 12:50 PM, Stephen P. Molnar wrote:

I am running Debian Stretch on my Linux platform.

I have noticed low internet traffic when I have not been doing
anything outside of my LAN.  This has made me a tad suspicious.


Wired Connections:  2 Desktops,  printer and VOIP telephone

Wireless Connections:  Laptop and two Android Smartphones

Out of curiosity, who is your VOIP service provider?

I use ObiHai, and find that it exchanges traffic with its "server" continuously.

I've not recently attempted to check how much, and don't remember any figures,
but it wouldn't surprise me if that accounts for some, most, all of the traffic
you report.

And, maybe Android smartphones do something similar, especially if they are
setup for VOIP or some similar service.



AT

--
Stephen P. Molnar, Ph.D.
Consultant
www.molecular-modeling.net
(614)312-7528 (c)
Skype: smolnar1

Re: Strange Network Problem

[rhkramer]

On Saturday, September 01, 2018 07:05:55 AM Stephen P. Molnar wrote:
> On 08/31/2018 10:41 PM, David Christensen wrote:
> > On 08/31/2018 12:50 PM, Stephen P. Molnar wrote:
> >> I am running Debian Stretch on my Linux platform.
> >> 
> >> I have noticed low internet traffic when I have not been doing
> >> anything outside of my LAN.  This has made me a tad suspicious.
> >> 

> Wired Connections:  2 Desktops,  printer and VOIP telephone
> 
> Wireless Connections:  Laptop and two Android Smartphones

Out of curiosity, who is your VOIP service provider?

I use ObiHai, and find that it exchanges traffic with its "server" continuously.

I've not recently attempted to check how much, and don't remember any figures, 
but it wouldn't surprise me if that accounts for some, most, all of the traffic 
you report.

And, maybe Android smartphones do something similar, especially if they are 
setup for VOIP or some similar service.

Re: Strange Network Problem

[Stephen P. Molnar]

On 08/31/2018 10:41 PM, David Christensen wrote:

On 08/31/2018 12:50 PM, Stephen P. Molnar wrote:

I am running Debian Stretch on my Linux platform.

I have noticed low internet traffic when I have not been doing 
anything outside of my LAN.  This has made me a tad suspicious.


Now:

root@AbNormal:/home/comp# ifconfig
enp2s0: flags=4163  mtu 1500
 inet 162.237.98.238  netmask 255.255.252.0  broadcast 
162.237.99.255

 ether bc:ee:7b:5e:83:36  txqueuelen 1000  (Ethernet)
 RX packets 796401  bytes 529829454 (505.2 MiB)
 RX errors 0  dropped 0  overruns 0  frame 0
 TX packets 236054  bytes 22520861 (21.4 MiB)
 TX errors 0  dropped 0 overruns 0  carrier 0 collisions 0

lo: flags=73  mtu 65536
 inet 127.0.0.1  netmask 255.0.0.0
 loop  txqueuelen 1  (Local Loopback)
 RX packets 399  bytes 42360 (41.3 KiB)
 RX errors 0  dropped 0  overruns 0  frame 0
 TX packets 399  bytes 42360 (41.3 KiB)
 TX errors 0  dropped 0 overruns 0  carrier 0 collisions 0


It turns out that this ISP, 162.237.98.238 is my ISP, AT here in 
Columbus, Ohio.


The other four nodes on my LAn all have IP's starting with 192.168.1 
- which is what it's supposed to be.


Just what is going on here? I don't have a clue.

I dop have firewalls implemented on both the modem and the computers.

Any insights will be much appreciated.

Thanks in advance.



Running nslookup(1):

2018-08-31 18:53:21 dpchrist@vstretch ~
$ nslookup 162.237.98.238
Server:192.168.5.1
Address:192.168.5.1#53

Non-authoritative answer:
238.98.237.162.in-addr.arpaname = 
162-237-98-238.lightspeed.clmboh.sbcglobal.net.


Authoritative answers can be found from:


Running host(1):

2018-08-31 18:58:15 dpchrist@vstretch ~
$ host 162.237.98.238
238.98.237.162.in-addr.arpa domain name pointer 
162-237-98-238.lightspeed.clmboh.sbcglobal.net.



162.237.98.238 appears to be a valid IPv4 public Internet address.


You should have a device provided by your Internet service provider 
(ISP) between their wiring (e.g. telephone service) and your wiring 
(e.g. Ethernet local area network/LAN).  What is the make and model of 
the ISP device?  Please provide a URL to the product support page.



What are the "other four nodes"?


How is everything interconnected?


David



Thanks for your reply.

ISO device is an Arris BGE210-700 Broadband Gateway Release 1.0 from 
AT (http://www.arris.com/Search/?q=Arris+BGE210-700+Broadband+Gateway)


Wired Connections:  2 Desktops,  printer and VOIP telephone

Wireless Connections:  Laptop and two Android Smartphones

root@AbNormal:/home/comp# nslookup
> nslookup -a
Server:192.168.1.254
Address:192.168.1.254#53

Non-authoritative answer:
Name:nslookup
Address: 198.105.244.130
Name:nslookup
Address: 104.239.207.44
>
> host
Server:192.168.1.254
Address:192.168.1.254#53

Non-authoritative answer:
*** Can't find host: No answer
>

--
Stephen P. Molnar, Ph.D.
Consultant
www.molecular-modeling.net
(614)312-7528 (c)
Skype: smolnar1

Re: Strange Network Problem

[mick crane]

On 2018-08-31 20:50, Stephen P. Molnar wrote:

I am running Debian Stretch on my Linux platform.

I have noticed low internet traffic when I have not been doing
anything outside of my LAN.  This has made me a tad suspicious.

Now:

root@AbNormal:/home/comp# ifconfig
enp2s0: flags=4163  mtu 1500
inet 162.237.98.238  netmask 255.255.252.0  broadcast 
162.237.99.255

ether bc:ee:7b:5e:83:36  txqueuelen 1000  (Ethernet)
RX packets 796401  bytes 529829454 (505.2 MiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 236054  bytes 22520861 (21.4 MiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73  mtu 65536
inet 127.0.0.1  netmask 255.0.0.0
loop  txqueuelen 1  (Local Loopback)
RX packets 399  bytes 42360 (41.3 KiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 399  bytes 42360 (41.3 KiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0


It turns out that this ISP, 162.237.98.238 is my ISP, AT here in
Columbus, Ohio.

The other four nodes on my LAn all have IP's starting with 192.168.1 -
which is what it's supposed to be.

Just what is going on here? I don't have a clue.

I dop have firewalls implemented on both the modem and the computers.

Any insights will be much appreciated.

Thanks in advance.


well ifconfig should report the internal private address of its NIC but 
seems to be showing the external address range of the router. Could this 
be anything to do with the router being in bridge mode which is 
something I'm not entirely clear about.


mick


--
Key ID4BFEBB31

Re: Strange Network Problem

[David Christensen]

On 08/31/2018 12:50 PM, Stephen P. Molnar wrote:

I am running Debian Stretch on my Linux platform.

I have noticed low internet traffic when I have not been doing anything 
outside of my LAN.  This has made me a tad suspicious.


Now:

root@AbNormal:/home/comp# ifconfig
enp2s0: flags=4163  mtu 1500
     inet 162.237.98.238  netmask 255.255.252.0  broadcast 
162.237.99.255

     ether bc:ee:7b:5e:83:36  txqueuelen 1000  (Ethernet)
     RX packets 796401  bytes 529829454 (505.2 MiB)
     RX errors 0  dropped 0  overruns 0  frame 0
     TX packets 236054  bytes 22520861 (21.4 MiB)
     TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73  mtu 65536
     inet 127.0.0.1  netmask 255.0.0.0
     loop  txqueuelen 1  (Local Loopback)
     RX packets 399  bytes 42360 (41.3 KiB)
     RX errors 0  dropped 0  overruns 0  frame 0
     TX packets 399  bytes 42360 (41.3 KiB)
     TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0


It turns out that this ISP, 162.237.98.238 is my ISP, AT here in 
Columbus, Ohio.


The other four nodes on my LAn all have IP's starting with 192.168.1 - 
which is what it's supposed to be.


Just what is going on here? I don't have a clue.

I dop have firewalls implemented on both the modem and the computers.

Any insights will be much appreciated.

Thanks in advance.



Running nslookup(1):

2018-08-31 18:53:21 dpchrist@vstretch ~
$ nslookup 162.237.98.238
Server: 192.168.5.1
Address:192.168.5.1#53

Non-authoritative answer:
238.98.237.162.in-addr.arpa	name = 
162-237-98-238.lightspeed.clmboh.sbcglobal.net.


Authoritative answers can be found from:


Running host(1):

2018-08-31 18:58:15 dpchrist@vstretch ~
$ host 162.237.98.238
238.98.237.162.in-addr.arpa domain name pointer 
162-237-98-238.lightspeed.clmboh.sbcglobal.net.



162.237.98.238 appears to be a valid IPv4 public Internet address.


You should have a device provided by your Internet service provider 
(ISP) between their wiring (e.g. telephone service) and your wiring 
(e.g. Ethernet local area network/LAN).  What is the make and model of 
the ISP device?  Please provide a URL to the product support page.



What are the "other four nodes"?


How is everything interconnected?


David

Re: Strange Network Problem

[Dan Purgert]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Stephen P. Molnar wrote:
> I am running Debian Stretch on my Linux platform.
>
> I have noticed low internet traffic when I have not been doing
> anything outside of my LAN.  This has made me a tad suspicious.
>
>
> It turns out that this ISP, 162.237.98.238 is my ISP, AT here in 
> Columbus, Ohio.

Is this pc perhaps set up to be in the dmz?


-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEBcqaUD8uEzVNxUrujhHd8xJ5ooEFAluJst4ACgkQjhHd8xJ5
ooFfegf/UD2Fcat+GG27VWk8w9FdCDmrNwWLHX0jHXa6/0HNQYVKRBYK6x2CXvtk
98XaXDbKAp/cPrMquK9az0po9bC/M97/Ou+/ul1CiTeL9qKN065x+LuLGkEC5Ow/
f4hhqhVCzawQi4A5NcqF14asM2S3FcDQGfSpPIsP1RsA8cSO6ZykQfyLR+s0cs6K
mVfhE/1/+OdJms4Fa2tbRzgP2O7nnvKTrnZjLVTSkhVsaonL7K7USpH8bQ6jYW+N
t/o6kd4R3LLT/cpw0c6oX7835MRT4SPpmBFCbQfRxSjW4UMxpo6yZav6NwQhNEbN
owdR+fRHrLkYanSaKz4k8m3tesLgJQ==
=DK7D
-END PGP SIGNATURE-

-- 
|_|O|_| Registered Linux user #585947
|_|_|O| Github: https://github.com/dpurgert
|O|O|O| PGP: 05CA 9A50 3F2E 1335 4DC5  4AEE 8E11 DDF3 1279 A281

Strange Network Problem

[Stephen P. Molnar]

I am running Debian Stretch on my Linux platform.

I have noticed low internet traffic when I have not been doing anything 
outside of my LAN.  This has made me a tad suspicious.


Now:

root@AbNormal:/home/comp# ifconfig
enp2s0: flags=4163  mtu 1500
inet 162.237.98.238  netmask 255.255.252.0  broadcast 
162.237.99.255

ether bc:ee:7b:5e:83:36  txqueuelen 1000  (Ethernet)
RX packets 796401  bytes 529829454 (505.2 MiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 236054  bytes 22520861 (21.4 MiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73  mtu 65536
inet 127.0.0.1  netmask 255.0.0.0
loop  txqueuelen 1  (Local Loopback)
RX packets 399  bytes 42360 (41.3 KiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 399  bytes 42360 (41.3 KiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0


It turns out that this ISP, 162.237.98.238 is my ISP, AT here in 
Columbus, Ohio.


The other four nodes on my LAn all have IP's starting with 192.168.1 - 
which is what it's supposed to be.


Just what is going on here? I don't have a clue.

I dop have firewalls implemented on both the modem and the computers.

Any insights will be much appreciated.

Thanks in advance.

--
Stephen P. Molnar, Ph.D.
Consultant
www.molecular-modeling.net
(614)312-7528 (c)
Skype: smolnar1

Re: dhclient or network problem

[Dominique Dumont]

On Monday, 10 July 2017 11:28:12 CEST Franz Angeli wrote:
> for example interface name eno52 (tg3, Broadcom Limited NetXtreme
> BCM5719 Gigabit Ethernet PCIe (rev 01) :

I had a similar issue due to a missing firmware. I think it was on a broadcom 
card.

Please check the kernel logs (journalctl -k) and check the logs mentioning 
your card.

HTH

-- 
 https://github.com/dod38fr/   -o- http://search.cpan.org/~ddumont/
http://ddumont.wordpress.com/  -o-   irc: dod at irc.debian.org

Re: dhclient or network problem

[Mark Fletcher]

On Mon, Jul 10, 2017 at 12:55:53PM +0200, Dejan Jocic wrote:
> On 10-07-17, Franz Angeli wrote:
> > Hi,
> > 
> > i have a problem with dhclient:
> > 
> > for example interface name eno52 (tg3, Broadcom Limited NetXtreme
> > BCM5719 Gigabit Ethernet PCIe (rev 01) :
> > 
> > root@:~# dhclient eno52 -v
> > Internet Systems Consortium DHCP Client 4.3.5
> > Copyright 2004-2016 Internet Systems Consortium.
> > All rights reserved.
> > For info, please visit https://www.isc.org/software/dhcp/
> > 
> > Listening on LPF/eno52/3c:a8:2a:e7:87:bf
> > Sending on   LPF/eno52/3c:a8:2a:e7:87:bf
> > Sending on   Socket/fallback
> > DHCPDISCOVER on eno52 to 255.255.255.255 port 67 interval 4
> > DHCPDISCOVER on eno52 to 255.255.255.255 port 67 interval 10
> > DHCPDISCOVER on eno52 to 255.255.255.255 port 67 interval 7
> > DHCPDISCOVER on eno52 to 255.255.255.255 port 67 interval 9
> > DHCPDISCOVER on eno52 to 255.255.255.255 port 67 interval 15
> > DHCPDISCOVER on eno52 to 255.255.255.255 port 67 interval 16
> > No DHCPOFFERS received.
> > No working leases in persistent database - sleeping.
> > 
> > tcpdump during dhclient doesn't show anything?!?
> > 
> > root@*:~# tcpdump -i eno52
> > tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
> > listening on eno52, link-type EN10MB (Ethernet), capture size 262144 bytes
> > 
> > 
> > root@***:~# ip addr show eno52
> > 9: eno52:  mtu 1500 qdisc mq state
> > DOWN group default qlen 1000
> > link/ether 3c:a8:2a:e7:87:bf brd ff:ff:ff:ff:ff:ff
> > 
> > 
> > if i use the same ethernet cable on my laptop all works fine...
> 
> Don't you think that you have enough of a clue there :P That eno52 is,
> as you can see ethernet card, of course it will work when you connect it
> with ethernet cable. If you want it to work with wifi, that is another
> story. What is your wifi card, do you have something starting with w in
> the output of ip addr show? What is the output of the lspci -v | grep -i
> -A6 net?
> > 

Uh, no mate, I don't think that is what the OP meant. I suspect the 
laptop is a different computer. And telling us the cable works in his 
laptop is designed to head off suggestions the cable might be at fault.

He never mentiond WiFi anywhere.

Mark

Re: Debain 9 dhclient or network problem

[Brian]

On Tue 11 Jul 2017 at 09:24:01 +0200, Dejan Jocic wrote:
 
> You are doing lspci as root, so with A10 it does not get to the kernel
> driver and module part. Can you see what is there by using A15 instead?

If the driver turns out to be tg3 then firmware from nonfree is required.

-- 
Brian.

Re: Debain 9 dhclient or network problem

[Franz Angeli]

nothing usefull...

one strange thing is that during debian installation all works fine
because i use net-install with a iso.




2017-07-11 9:27 GMT+02:00 Johann Spies :
> On 11 July 2017 at 08:29, Franz Angeli  wrote:
>
>> i tried every other interface butt it's the same
>>
>> i tried also to disable interface renaming but doesn't work.
>
> What information do you get from /var/log/messages, /var/log/syslog
> and dmesg about your interfaces?
>
> Regards
> Johann
>

Re: Debain 9 dhclient or network problem

[Johann Spies]

On 11 July 2017 at 08:29, Franz Angeli  wrote:

> i tried every other interface butt it's the same
>
> i tried also to disable interface renaming but doesn't work.

What information do you get from /var/log/messages, /var/log/syslog
and dmesg about your interfaces?

Regards
Johann

Re: Debain 9 dhclient or network problem

[Dejan Jocic]

On 11-07-17, Franz Angeli wrote:
> Hi,
> 
> i have a problem with dhclient:
> 
> for example interface name eno52 (tg3, Broadcom Limited NetXtreme
> BCM5719 Gigabit Ethernet PCIe (rev 01) :
> 
> root@:~# dhclient eno52 -v
> Internet Systems Consortium DHCP Client 4.3.5
> Copyright 2004-2016 Internet Systems Consortium.
> All rights reserved.
> For info, please visit https://www.isc.org/software/dhcp/
> 
> Listening on LPF/eno52/3c:a8:2a:e7:87:bf
> Sending on   LPF/eno52/3c:a8:2a:e7:87:bf
> Sending on   Socket/fallback
> DHCPDISCOVER on eno52 to 255.255.255.255 port 67 interval 4
> DHCPDISCOVER on eno52 to 255.255.255.255 port 67 interval 10
> DHCPDISCOVER on eno52 to 255.255.255.255 port 67 interval 7
> DHCPDISCOVER on eno52 to 255.255.255.255 port 67 interval 9
> DHCPDISCOVER on eno52 to 255.255.255.255 port 67 interval 15
> DHCPDISCOVER on eno52 to 255.255.255.255 port 67 interval 16
> No DHCPOFFERS received.
> No working leases in persistent database - sleeping.
> 
> tcpdump during dhclient doesn't show anything?!?
> 
> root@*:~# tcpdump -i eno52
> tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
> listening on eno52, link-type EN10MB (Ethernet), capture size 262144 bytes
> 
> 
> root@***:~# ip addr show eno52
> 9: eno52:  mtu 1500 qdisc mq state
> DOWN group default qlen 1000
> link/ether 3c:a8:2a:e7:87:bf brd ff:ff:ff:ff:ff:ff
> 
> interface eno52 seems to be disconnected but cable is plugged and
> working (i tried with other pc)
> 
> obviously ethernet cable is connected...
> Debian 8 works fine with this hw
> Debian 9 doesn't work
> 
> Server is ProLiant DL380 Gen9 (719064-B21)
> 
> root@***:~# lspci -v | grep -A10 Ethernet
> 02:00.0 Ethernet controller: Broadcom Limited NetXtreme BCM5719
> Gigabit Ethernet PCIe (rev 01)
> Subsystem: Hewlett-Packard Company Ethernet 1Gb 4-port 331i Adapter
> Flags: bus master, fast devsel, latency 0, IRQ 16, NUMA node 0
> Memory at 92c9 (64-bit, prefetchable) [size=64K]
> Memory at 92ca (64-bit, prefetchable) [size=64K]
> Memory at 92cb (64-bit, prefetchable) [size=64K]
> [virtual] Expansion ROM at 9310 [disabled] [size=256K]
> Capabilities: [48] Power Management version 3
> Capabilities: [50] Vital Product Data
> Capabilities: [58] MSI: Enable- Count=1/8 Maskable- 64bit+
> Capabilities: [a0] MSI-X: Enable+ Count=17 Masked-
> Capabilities: [ac] Express Endpoint, MSI 00
> --
> 02:00.1 Ethernet controller: Broadcom Limited NetXtreme BCM5719
> Gigabit Ethernet PCIe (rev 01)
> Subsystem: Hewlett-Packard Company Ethernet 1Gb 4-port 331i Adapter
> Flags: bus master, fast devsel, latency 0, IRQ 17, NUMA node 0
> Memory at 92c6 (64-bit, prefetchable) [size=64K]
> Memory at 92c7 (64-bit, prefetchable) [size=64K]
> Memory at 92c8 (64-bit, prefetchable) [size=64K]
> [virtual] Expansion ROM at 9314 [disabled] [size=256K]
> Capabilities: [48] Power Management version 3
> Capabilities: [50] Vital Product Data
> Capabilities: [58] MSI: Enable- Count=1/8 Maskable- 64bit+
> Capabilities: [a0] MSI-X: Enable- Count=17 Masked-
> Capabilities: [ac] Express Endpoint, MSI 00
> --
> 02:00.2 Ethernet controller: Broadcom Limited NetXtreme BCM5719
> Gigabit Ethernet PCIe (rev 01)
> Subsystem: Hewlett-Packard Company Ethernet 1Gb 4-port 331i Adapter
> Flags: bus master, fast devsel, latency 0, IRQ 16, NUMA node 0
> Memory at 92c3 (64-bit, prefetchable) [size=64K]
> Memory at 92c4 (64-bit, prefetchable) [size=64K]
> Memory at 92c5 (64-bit, prefetchable) [size=64K]
> [virtual] Expansion ROM at 9318 [disabled] [size=256K]
> Capabilities: [48] Power Management version 3
> Capabilities: [50] Vital Product Data
> Capabilities: [58] MSI: Enable- Count=1/8 Maskable- 64bit+
> Capabilities: [a0] MSI-X: Enable- Count=17 Masked-
> Capabilities: [ac] Express Endpoint, MSI 00
> --
> 02:00.3 Ethernet controller: Broadcom Limited NetXtreme BCM5719
> Gigabit Ethernet PCIe (rev 01)
> Subsystem: Hewlett-Packard Company Ethernet 1Gb 4-port 331i Adapter
> Flags: bus master, fast devsel, latency 0, IRQ 17, NUMA node 0
> Memory at 92c0 (64-bit, prefetchable) [size=64K]
> Memory at 92c1 (64-bit, prefetchable) [size=64K]
> Memory at 92c2 (64-bit, prefetchable) [size=64K]
> [virtual] Expansion ROM at 931c [disabled] [size=256K]
> Capabilities: [48] Power Management version 3
> Capabilities: [50] Vital Product Data
> Capabilities: [58] MSI: Enable- Count=1/8 Maskable- 64bit+
> Capabilities: [a0] MSI-X: Enable- Count=17 Masked-
> Capabilities: [ac] Express Endpoint, MSI 00
> --
> 04:00.0 Ethernet controller: Broadcom Limited NetXtreme BCM5719
> Gigabit Ethernet PCIe (rev 01)
> Subsystem: Hewlett-Packard Company Ethernet 1Gb 4-port 331FLR Adapter
> Flags: bus master, fast devsel, latency 0, IRQ 16, NUMA node 0
> Memory at 92b9 (64-bit, prefetchable) [size=64K]
> Memory at 92ba (64-bit, prefetchable) [size=64K]
> Memory at 92bb (64-bit, prefetchable) 

Re: Debain 9 dhclient or network problem

[Franz Angeli]

Hi,

i tried every other interface butt it's the same

i tried also to disable interface renaming but doesn't work.

2017-07-11 8:02 GMT+02:00 Johann Spies :
> On 11 July 2017 at 07:48, Franz Angeli  wrote:
>> Hi,
>>
>> i have a problem with dhclient:
>>
>> for example interface name eno52 (tg3, Broadcom Limited NetXtreme
>> BCM5719 Gigabit Ethernet PCIe (rev 01) :
>>
>> root@:~# dhclient eno52 -v
>> Internet Systems Consortium DHCP Client 4.3.5
>> Copyright 2004-2016 Internet Systems Consortium.
>> All rights reserved.
>> For info, please visit https://www.isc.org/software/dhcp/
>>
> ...
>> if i use the same ethernet cable on my laptop all works fine... (DHCP
>> lease and so on)
>
> My first guess would be that the order of the network interfaces
> differ between Debian 8 and 9 and that you should try the cable on the
> other interfaces.
>
> In the past (many years ago) it was a known problem that eth0 on the
> new system used for another interface.  I don't know whether this is
> still the case. It had been some time that I had to build a server.
>
> Regards
> Johann
> --
> Because experiencing your loyal love is better than life itself,
> my lips will praise you.  (Psalm 63:3)
>

Re: Debain 9 dhclient or network problem

[Johann Spies]

On 11 July 2017 at 07:48, Franz Angeli  wrote:
> Hi,
>
> i have a problem with dhclient:
>
> for example interface name eno52 (tg3, Broadcom Limited NetXtreme
> BCM5719 Gigabit Ethernet PCIe (rev 01) :
>
> root@:~# dhclient eno52 -v
> Internet Systems Consortium DHCP Client 4.3.5
> Copyright 2004-2016 Internet Systems Consortium.
> All rights reserved.
> For info, please visit https://www.isc.org/software/dhcp/
>
...
> if i use the same ethernet cable on my laptop all works fine... (DHCP
> lease and so on)

My first guess would be that the order of the network interfaces
differ between Debian 8 and 9 and that you should try the cable on the
other interfaces.

In the past (many years ago) it was a known problem that eth0 on the
new system used for another interface.  I don't know whether this is
still the case. It had been some time that I had to build a server.

Regards
Johann
-- 
Because experiencing your loyal love is better than life itself,
my lips will praise you.  (Psalm 63:3)

Debain 9 dhclient or network problem

[Franz Angeli]

Hi,

i have a problem with dhclient:

for example interface name eno52 (tg3, Broadcom Limited NetXtreme
BCM5719 Gigabit Ethernet PCIe (rev 01) :

root@:~# dhclient eno52 -v
Internet Systems Consortium DHCP Client 4.3.5
Copyright 2004-2016 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/eno52/3c:a8:2a:e7:87:bf
Sending on   LPF/eno52/3c:a8:2a:e7:87:bf
Sending on   Socket/fallback
DHCPDISCOVER on eno52 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on eno52 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on eno52 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on eno52 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on eno52 to 255.255.255.255 port 67 interval 15
DHCPDISCOVER on eno52 to 255.255.255.255 port 67 interval 16
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

tcpdump during dhclient doesn't show anything?!?

root@*:~# tcpdump -i eno52
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eno52, link-type EN10MB (Ethernet), capture size 262144 bytes


root@***:~# ip addr show eno52
9: eno52:  mtu 1500 qdisc mq state
DOWN group default qlen 1000
link/ether 3c:a8:2a:e7:87:bf brd ff:ff:ff:ff:ff:ff

interface eno52 seems to be disconnected but cable is plugged and
working (i tried with other pc)

obviously ethernet cable is connected...
Debian 8 works fine with this hw
Debian 9 doesn't work

Server is ProLiant DL380 Gen9 (719064-B21)

root@***:~# lspci -v | grep -A10 Ethernet
02:00.0 Ethernet controller: Broadcom Limited NetXtreme BCM5719
Gigabit Ethernet PCIe (rev 01)
Subsystem: Hewlett-Packard Company Ethernet 1Gb 4-port 331i Adapter
Flags: bus master, fast devsel, latency 0, IRQ 16, NUMA node 0
Memory at 92c9 (64-bit, prefetchable) [size=64K]
Memory at 92ca (64-bit, prefetchable) [size=64K]
Memory at 92cb (64-bit, prefetchable) [size=64K]
[virtual] Expansion ROM at 9310 [disabled] [size=256K]
Capabilities: [48] Power Management version 3
Capabilities: [50] Vital Product Data
Capabilities: [58] MSI: Enable- Count=1/8 Maskable- 64bit+
Capabilities: [a0] MSI-X: Enable+ Count=17 Masked-
Capabilities: [ac] Express Endpoint, MSI 00
--
02:00.1 Ethernet controller: Broadcom Limited NetXtreme BCM5719
Gigabit Ethernet PCIe (rev 01)
Subsystem: Hewlett-Packard Company Ethernet 1Gb 4-port 331i Adapter
Flags: bus master, fast devsel, latency 0, IRQ 17, NUMA node 0
Memory at 92c6 (64-bit, prefetchable) [size=64K]
Memory at 92c7 (64-bit, prefetchable) [size=64K]
Memory at 92c8 (64-bit, prefetchable) [size=64K]
[virtual] Expansion ROM at 9314 [disabled] [size=256K]
Capabilities: [48] Power Management version 3
Capabilities: [50] Vital Product Data
Capabilities: [58] MSI: Enable- Count=1/8 Maskable- 64bit+
Capabilities: [a0] MSI-X: Enable- Count=17 Masked-
Capabilities: [ac] Express Endpoint, MSI 00
--
02:00.2 Ethernet controller: Broadcom Limited NetXtreme BCM5719
Gigabit Ethernet PCIe (rev 01)
Subsystem: Hewlett-Packard Company Ethernet 1Gb 4-port 331i Adapter
Flags: bus master, fast devsel, latency 0, IRQ 16, NUMA node 0
Memory at 92c3 (64-bit, prefetchable) [size=64K]
Memory at 92c4 (64-bit, prefetchable) [size=64K]
Memory at 92c5 (64-bit, prefetchable) [size=64K]
[virtual] Expansion ROM at 9318 [disabled] [size=256K]
Capabilities: [48] Power Management version 3
Capabilities: [50] Vital Product Data
Capabilities: [58] MSI: Enable- Count=1/8 Maskable- 64bit+
Capabilities: [a0] MSI-X: Enable- Count=17 Masked-
Capabilities: [ac] Express Endpoint, MSI 00
--
02:00.3 Ethernet controller: Broadcom Limited NetXtreme BCM5719
Gigabit Ethernet PCIe (rev 01)
Subsystem: Hewlett-Packard Company Ethernet 1Gb 4-port 331i Adapter
Flags: bus master, fast devsel, latency 0, IRQ 17, NUMA node 0
Memory at 92c0 (64-bit, prefetchable) [size=64K]
Memory at 92c1 (64-bit, prefetchable) [size=64K]
Memory at 92c2 (64-bit, prefetchable) [size=64K]
[virtual] Expansion ROM at 931c [disabled] [size=256K]
Capabilities: [48] Power Management version 3
Capabilities: [50] Vital Product Data
Capabilities: [58] MSI: Enable- Count=1/8 Maskable- 64bit+
Capabilities: [a0] MSI-X: Enable- Count=17 Masked-
Capabilities: [ac] Express Endpoint, MSI 00
--
04:00.0 Ethernet controller: Broadcom Limited NetXtreme BCM5719
Gigabit Ethernet PCIe (rev 01)
Subsystem: Hewlett-Packard Company Ethernet 1Gb 4-port 331FLR Adapter
Flags: bus master, fast devsel, latency 0, IRQ 16, NUMA node 0
Memory at 92b9 (64-bit, prefetchable) [size=64K]
Memory at 92ba (64-bit, prefetchable) [size=64K]
Memory at 92bb (64-bit, prefetchable) [size=64K]
[virtual] Expansion ROM at 9300 [disabled] [size=256K]
Capabilities: [48] Power Management version 3
Capabilities: [50] Vital Product Data
Capabilities: [58] MSI: Enable- Count=1/8 Maskable- 64bit+
Capabilities: [a0] MSI-X: Enable- Count=17 

Re: dhclient or network problem

[Dejan Jocic]

On 10-07-17, Franz Angeli wrote:
> Hi,
> 
> i have a problem with dhclient:
> 
> for example interface name eno52 (tg3, Broadcom Limited NetXtreme
> BCM5719 Gigabit Ethernet PCIe (rev 01) :
> 
> root@:~# dhclient eno52 -v
> Internet Systems Consortium DHCP Client 4.3.5
> Copyright 2004-2016 Internet Systems Consortium.
> All rights reserved.
> For info, please visit https://www.isc.org/software/dhcp/
> 
> Listening on LPF/eno52/3c:a8:2a:e7:87:bf
> Sending on   LPF/eno52/3c:a8:2a:e7:87:bf
> Sending on   Socket/fallback
> DHCPDISCOVER on eno52 to 255.255.255.255 port 67 interval 4
> DHCPDISCOVER on eno52 to 255.255.255.255 port 67 interval 10
> DHCPDISCOVER on eno52 to 255.255.255.255 port 67 interval 7
> DHCPDISCOVER on eno52 to 255.255.255.255 port 67 interval 9
> DHCPDISCOVER on eno52 to 255.255.255.255 port 67 interval 15
> DHCPDISCOVER on eno52 to 255.255.255.255 port 67 interval 16
> No DHCPOFFERS received.
> No working leases in persistent database - sleeping.
> 
> tcpdump during dhclient doesn't show anything?!?
> 
> root@*:~# tcpdump -i eno52
> tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
> listening on eno52, link-type EN10MB (Ethernet), capture size 262144 bytes
> 
> 
> root@***:~# ip addr show eno52
> 9: eno52:  mtu 1500 qdisc mq state
> DOWN group default qlen 1000
> link/ether 3c:a8:2a:e7:87:bf brd ff:ff:ff:ff:ff:ff
> 
> 
> if i use the same ethernet cable on my laptop all works fine...

Don't you think that you have enough of a clue there :P That eno52 is,
as you can see ethernet card, of course it will work when you connect it
with ethernet cable. If you want it to work with wifi, that is another
story. What is your wifi card, do you have something starting with w in
the output of ip addr show? What is the output of the lspci -v | grep -i
-A6 net?
> 
> i don't know if is a module problem...or?
> 
> Can you help me?
> 
> BR
> 

dhclient or network problem

[Franz Angeli]

Hi,

i have a problem with dhclient:

for example interface name eno52 (tg3, Broadcom Limited NetXtreme
BCM5719 Gigabit Ethernet PCIe (rev 01) :

root@:~# dhclient eno52 -v
Internet Systems Consortium DHCP Client 4.3.5
Copyright 2004-2016 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/eno52/3c:a8:2a:e7:87:bf
Sending on   LPF/eno52/3c:a8:2a:e7:87:bf
Sending on   Socket/fallback
DHCPDISCOVER on eno52 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on eno52 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on eno52 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on eno52 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on eno52 to 255.255.255.255 port 67 interval 15
DHCPDISCOVER on eno52 to 255.255.255.255 port 67 interval 16
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

tcpdump during dhclient doesn't show anything?!?

root@*:~# tcpdump -i eno52
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eno52, link-type EN10MB (Ethernet), capture size 262144 bytes


root@***:~# ip addr show eno52
9: eno52:  mtu 1500 qdisc mq state
DOWN group default qlen 1000
link/ether 3c:a8:2a:e7:87:bf brd ff:ff:ff:ff:ff:ff


if i use the same ethernet cable on my laptop all works fine...

i don't know if is a module problem...or?

Can you help me?

BR

Re: Got that network problem solved, now a new one

[cbannister]

[Please don't top post]

On Wed, May 18, 2016 at 11:09:02PM +, John L. Ries wrote:
> I guess my first question would be why the script below has anything to do
> with /opt.  I don't see a change of directory to anything under that
> directory and I would assume this is running in some directory you own.
> 
> 
> System directory permissions are sometimes changed during software updates;
> annoying, but true.  I sometimes have to change permissions on /usr/local/src
> for that reason.

That would seem like a serious bug, the package manager doesn't touch the local
tree. I'm guessing it was a 3rd party application which you compiled/installed 
which of course the package manager has no control over.

-- 
The media's the most powerful entity on earth. 
They have the power to make the innocent guilty 
and to make the guilty innocent, and that's power.
 -- Malcolm X

Re: Got that network problem solved, now a new one

[Gene Heskett]

On Thursday 19 May 2016 05:48:19 Gene Heskett wrote:

[...]

> > What I'd do
> >
> > Consider making a subdirectory of /opt dedicated to whatever you
> > are doing with these scripts and setting its ownership to gene
> > (start as restricted as possible with that and widen as necessary,
> > e.g. to make parts of it readable to www-data via the group as your
> > scripts seem to do already.
> >
That has now been done, and all that stuff moved to the subdir, with a 
softlink from the main dir to the latest version, and it seems to work.
ownership and perms on the subdir make it mine.

Thanks for the idea Tomas, works a treat.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 

Re: Got that network problem solved, now a new one

[Bob Bernstein]

On Thu, 19 May 2016, Lisi Reisz wrote:


Doesn't being old _suck_?


Word dat.

--
Man is essentially a dreamer, wakened sometimes for a
moment by some peculiarly obtrusive element in the
outer world, but lapsing again quickly into the happy
somnolence of imagination.
Russell

Re: Got that network problem solved, now a new one

[Gene Heskett]

On Thursday 19 May 2016 12:24:38 Dan Purgert wrote:

> Gene Heskett wrote:
> > On Thursday 19 May 2016 09:04:54 Lisi Reisz wrote:
> >> [snip]
> >> Will reply to Gene off-list as well in order to send a screenshot.
> >> But no, it is still not working.  Tried in Chromium and Firefox.
> >>
> >> Lisi
> >
> > For those following along, I had apache2 listening on port 6309, and
> > the router was miss-set to port 80.  Ooops.  PEBBAK?  Access.log is
> > now now showing some activity.
>
> Yep, looks like it's up now.

Thanks Dan.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 

Re: Got that network problem solved, now a new one

[Dan Purgert]

Gene Heskett wrote:
> On Thursday 19 May 2016 09:04:54 Lisi Reisz wrote:
>> [snip]
>> Will reply to Gene off-list as well in order to send a screenshot. 
>> But no, it is still not working.  Tried in Chromium and Firefox.
>>
>> Lisi
>
> For those following along, I had apache2 listening on port 6309, and the 
> router was miss-set to port 80.  Ooops.  PEBBAK?  Access.log is now now 
> showing some activity.

Yep, looks like it's up now.
-- 
Registered Linux user #585947
Github: https://github.com/dpurgert

Re: Got that network problem solved, now a new one

[Gene Heskett]

On Thursday 19 May 2016 09:30:21 Lisi Reisz wrote:

> On Thursday 19 May 2016 12:25:41 Gene Heskett wrote:
> > > cramps, took big B-12, should kick in shortly.
>
A 2500mg. I have a 250mg in my daily pilltainer, but overdid it a bit 
yesterday, so that wasn't enough.  The Metformin we take for the 
diabetes flushes it out, so you need to put it back in, in wholesale 
amounts.

> Didn't know that one!  (B12)
>
> Doesn't being old _suck_?

Yessum, about 10 EE-33 tor. :)

For the uninitiated, thats equal to about halfway to Alpha-Centari.  
There are mornings when its simply not worth the effort to gnaw thru the 
straps and get up to recycle yesterdays coffee.  But we do anyway.

> Lisi


Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 

Re: Got that network problem solved, now a new one

[Gene Heskett]

On Thursday 19 May 2016 09:04:54 Lisi Reisz wrote:

> On Thursday 19 May 2016 12:25:41 Gene Heskett wrote:
> > On Thursday 19 May 2016 05:56:49 Lisi Reisz wrote:
> > > On Thursday 19 May 2016 10:48:19 Gene Heskett wrote:
> > > > Yes, its the link in the sig.
> > >
> > > Which has been unreachable all morning from here. :-( (Morning by
> > > BST=UTC+1)
> > >
> > > Lisi
> >
> > Thats Lisi, I'll check that out when I wake up again.  Bad night,
> > leg cramps, took big B-12, should kick in shortly.
> >
> > Looking at port forwarding rule, protocol is html, incoming address
> > is blank, source port is 6309, fwd is to this machines address on
> > port 80. Enabled, so it should Just Work(TM).  But I reset it, then
> > restored my config again.  I checked the dns, and it resolves
> > correctly.
> >
> > Let me know if it still doesn't work.
> >
> > Cheers, Gene Heskett
>
> Will reply to Gene off-list as well in order to send a screenshot. 
> But no, it is still not working.  Tried in Chromium and Firefox.
>
> Lisi

For those following along, I had apache2 listening on port 6309, and the 
router was miss-set to port 80.  Ooops.  PEBBAK?  Access.log is now now 
showing some activity.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 

Re: Got that network problem solved, now a new one

[Lisi Reisz]

On Thursday 19 May 2016 12:25:41 Gene Heskett wrote:
>
> > cramps, took big B-12, should kick in shortly.

Didn't know that one!  (B12)

Doesn't being old _suck_?

Lisi

Re: Got that network problem solved, now a new one

[Lisi Reisz]

On Thursday 19 May 2016 12:25:41 Gene Heskett wrote:
> On Thursday 19 May 2016 05:56:49 Lisi Reisz wrote:
> > On Thursday 19 May 2016 10:48:19 Gene Heskett wrote:
> > > Yes, its the link in the sig.
> >
> > Which has been unreachable all morning from here. :-( (Morning by
> > BST=UTC+1)
> >
> > Lisi
>
> Thats Lisi, I'll check that out when I wake up again.  Bad night, leg
> cramps, took big B-12, should kick in shortly.
>
> Looking at port forwarding rule, protocol is html, incoming address is
> blank, source port is 6309, fwd is to this machines address on port 80.
> Enabled, so it should Just Work(TM).  But I reset it, then restored my
> config again.  I checked the dns, and it resolves correctly.
>
> Let me know if it still doesn't work.
>
> Cheers, Gene Heskett

Will reply to Gene off-list as well in order to send a screenshot.  But no, it 
is still not working.  Tried in Chromium and Firefox.

Lisi

Re: Got that network problem solved, now a new one

[Gene Heskett]

On Thursday 19 May 2016 05:56:49 Lisi Reisz wrote:

> On Thursday 19 May 2016 10:48:19 Gene Heskett wrote:
> > Yes, its the link in the sig.
>
> Which has been unreachable all morning from here. :-( (Morning by
> BST=UTC+1)
>
> Lisi

Thats Lisi, I'll check that out when I wake up again.  Bad night, leg 
cramps, took big B-12, should kick in shortly.

Looking at port forwarding rule, protocol is html, incoming address is 
blank, source port is 6309, fwd is to this machines address on port 80.  
Enabled, so it should Just Work(TM).  But I reset it, then restored my 
config again.  I checked the dns, and it resolves correctly.

Let me know if it still doesn't work.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 

Re: Got that network problem solved, now a new one

[Lisi Reisz]

On Thursday 19 May 2016 10:48:19 Gene Heskett wrote:
> Yes, its the link in the sig.

Which has been unreachable all morning from here. :-( (Morning by BST=UTC+1)

Lisi

Re: Got that network problem solved, now a new one

[Gene Heskett]

On Thursday 19 May 2016 04:14:55 to...@tuxteam.de wrote:

> On Wed, May 18, 2016 at 10:45:12PM -0500, David Wright wrote:
> > I feel I've been warned off commenting here in case I come across as
> > a pontificating know-it-all who's insisting that you do everything
> > in "My Way" [...]
>
> ;-)
>
> Yes, I totally agree with David's analysis here. The problem is
> the "mv", and the root is in /opt's permissions. Since the script
> didn't change, /opt must have been writable by gene in the past,
> and not in the present.

Apparently true, but it ran just fine, on this install, back on Mar 18, 
2016.

> Opt's permissions (04755) are "correct", by default /opt shouldn't
> be world writable. You might "fix" your problem by making it so,
> but you should know the other side of the deal (is this a public
> Web server?

Yes, its the link in the sig.

> What if someone hijacks the Apache -- or one of its 
> underling CGI scripts and starts scribbling over /opt? Things like
> that).

That apache2 is running bare bones, I don't use any cgi stuff at all.

I changed it to 0777 long enough to be run, then put it back to 0755.

> What I'd do
>
> Consider making a subdirectory of /opt dedicated to whatever you
> are doing with these scripts and setting its ownership to gene
> (start as restricted as possible with that and widen as necessary,
> e.g. to make parts of it readable to www-data via the group as your
> scripts seem to do already.
>
> regards
> -- tomás

That sounds doable, when I wake again.  Thanks Tomas.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 

Re: Got that network problem solved, now a new one

[tomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Wed, May 18, 2016 at 10:45:12PM -0500, David Wright wrote:
> I feel I've been warned off commenting here in case I come across as a
> pontificating know-it-all who's insisting that you do everything in
> "My Way" [...]

;-)

Yes, I totally agree with David's analysis here. The problem is
the "mv", and the root is in /opt's permissions. Since the script
didn't change, /opt must have been writable by gene in the past,
and not in the present.

Opt's permissions (04755) are "correct", by default /opt shouldn't
be world writable. You might "fix" your problem by making it so,
but you should know the other side of the deal (is this a public
Web server? What if someone hijacks the Apache -- or one of its
underling CGI scripts and starts scribbling over /opt? Things like
that).

What I'd do

Consider making a subdirectory of /opt dedicated to whatever you
are doing with these scripts and setting its ownership to gene
(start as restricted as possible with that and widen as necessary,
e.g. to make parts of it readable to www-data via the group as your
scripts seem to do already.

regards
- -- tomás
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlc9df8ACgkQBcgs9XrR2ka7SQCeJJfj2UGgaMfzHEZ4IH8utE33
KmIAnj1+IXCJuPBiVMHvirRqNDJytD+4
=Q2vv
-END PGP SIGNATURE-

Re: Got that network problem solved, now a new one

[David Wright]

I feel I've been warned off commenting here in case I come across as a
pontificating know-it-all who's insisting that you do everything in
"My Way". Well, if there are any opinions here about how things
*should* be done, they're nothing to do with me, but just taken from
the FHS (2015-03-19). It uses "must" in the same way that RFCs and
STDs do. Feel free to disagree with any of the observations I make.

On Wed 18 May 2016 at 19:10:10 (-0400), Gene Heskett wrote:
> On Wednesday 18 May 2016 17:42:59 Gene Heskett wrote:
> 
> > Greetings all;
> >
> > I am, because my web page serves as a backup site for the os and some
> > tools for use with the now 30 year old trs-80 color computers, have a
> > script IP can run that pulls fresh copies of the sources for this code
> > using hg, then builds fresh copies and makes it all available on my
> > web page.
> >
> > Unfortunately that script, running as me, suddenly has no write
> > permissions to do what it does.  This has been working for several
> > years.
> >
> > This is the script:
> > 
> > #!/bin/bash
> > # since I'm always forgetting who I am
> > if [ `whoami` != 'gene' ]; then
> > echo
> > echo "!! Warning !!!"
> > echo "this script needs to be run by user gene"
> > echo
> > echo
> > exit 1
> > fi
> > mv lwtools lwtools-$(date +%Y-%m-%d-%H-%M)

So, assuming you are and were in /opt, you must in the past have had write
permission as user gene to execute a mv.

> > hg clone http://lwtools.projects.l-w.ca/hg/ lwtools
> > cd lwtools
> > make
> > sudo make install

So presumably "gene" is not an alias for "root", ie $UID != 0 or you
wouldn't have bothered to sudo.

> > cd ..
> > echo
> > echo
> > echo "lwtools has been built, next is toolshed"
> > echo
> > echo
> > chown -R gene:www-data lwtools # make visible to the web

Someone pointed out that you could only do this as root.
I don't think this is true. As long as the files were owned by gene,
and gene is in both the old and new groups involved, then there's
no permission problem with changing the group ownership.

> > [ script repeats the same sort of stuff twice more ]

> > ==
> > and its now being denied at the first mv operation. /opt of course is
> > owned by root:root but that hasn't changed in 18 years of running
> > linux. This script has been running flawlessly about once a month
> > since July 2013 when I wrote it.
> >
> > So what was changed to prevent the common user from using /opt as
> > himself? cd'd to /opt, I can't even "touch ajunkfile".  Grr.  Me,
> > goes in search of my LART.

Well that would suggest you are used to having world write permission
in /opt; very unusual.

> > Better yet, how can I fix it? /opt permissions are 40755,

...which is "correct".

> and I'm
> > assuming a chmod 0777 as root would fix it temporarily, but thats one
> > hell of a kludge.  I'd much rather find where the rules to this game
> > are and get them fixed.

Is it possible that you had the same idea three years ago?

> > Thanks all.
> >
> > Cheers, Gene Heskett
> 
> I did the above, and fixed my script with line ending && so it would bail 
> out at the error point,

I don't quite follow you here (the reference to &&), but I assume
you've just set /opt to world-writeable and then run the script.

> and got two of the 3 of them rebuilt, then 
> switched /opt back to 0755 perms.

...which perhaps you didn't remember to do three years ago.

So what changed it back to 755? Well, there are less than obvious ways
like extracting files from a tar archive. That's caught people out in
the past.

It's highly unusual to have /opt world-writable. You, as admin, are
expected to make do with /opt/{bin,doc,include,info,lib,man}/ if
you create them. It's conceivable that an archive might contain,
say:
opt/
opt/lwtools/
opt/lwtools/...
with more conventional directory metadata.

(I couldn't follow the posts about bugs in the shell. What sort of bug
specifically are we, sorry, they, talking about?)

Cheers,
David.

Re: Got that network problem solved, now a new one

[John L. Ries]

You should probably check the permissions on /opt and make sure they haven’t 
changed and that you still have permission to operate on the files in question. 
 You may not have changed anything, but things may have changed nevertheless, 
for whatever reason.

--|
John L. Ries  |
Salford Systems   |
Phone: (619)543-8880 x107 |
or (435)867-8885  |
--|



On May 18, 2016, at 7:41 PM, Gene Heskett 
<ghesk...@shentel.net<mailto:ghesk...@shentel.net>> wrote:

On Wednesday 18 May 2016 19:09:02 John L. Ries wrote:

I guess my first question would be why the script below has anything
to do with /opt.  I don't see a change of directory to anything under
that directory and I would assume this is running in some directory
you own.

Nope, this script, and the directories it mv's around, all live in the
root of /opt, and I've been running it that way since 2013.  This is
just one of the reasons that I go buy a fresh drive for each new
install, so I can copy all this history from install to install, usually
with mc.

System directory permissions are sometimes changed during software
updates; annoying, but true.  I sometimes have to change permissions
on /usr/local/src for that reason.

Good point, although I haven't built anything there, or in /src/src  in
yonks, it all gets built in ~/src, no suprises that way.


I don't know about your system, but on most, chown can only be run by
root.

Depends, in this case I own the files as they were just generated by me.
And ISTR I am a member of group www-data. Just checked, yes.


I don't see any bash specific syntax in your script, so you might try
running it under a different Bourne compatible shell (perhaps ash,
dash, or ksh) to see if it works there.  This will hopefully rule out
the possibility of a bash bug.


John L. Ries
Salford Systems
Phone: (619)543-8880 x107
or (435)867-8885

From: Logan Erbst <lo...@iccamnetworking.us<mailto:lo...@iccamnetworking.us>>
Sent: Wednesday, May 18, 2016 5:34 PM
To: debian-user@lists.debian.org<mailto:debian-user@lists.debian.org>
Subject: Re: Got that network problem solved, now a new one

This seems to me that it may be a bug in the version of bash that is
running on the system, but I could be very wrong.

To address that:
gene@coyote:/$ ls -l `locate bin/bash`
-rwxr-xr-x 1 root root 941252 Sep 25  2014 /bin/bash
-rwxr-xr-x 1 root root   6966 Sep 25  2014 /usr/bin/bashbug
gene@coyote:/$ file /bin/bash
/bin/bash: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV),
dynamically linked, interpreter /lib/ld-linux.so.2, for GNU/Linux
2.6.26, BuildID[sha1]=1fd3c09266e0feec964431a11fbf7f1132acdb44, stripped

But this script has been run successfully several times since the date on
that /bin/bash.

But the kernel running now is:
gene@coyote:/$ uname -r
3.16.0-0.bpo.4-amd64

This is a 32 bit system for 2 reasons, most annoying being that the 64
bit kernels have horrible interrupt latency so linuxcnc will not even
launch, and while it will run with the 32 bit rtai patched kernels,
there no PAE in those patches so I am a gigabyte or more into swap in 48
hours uptime.  With this amd64 kernel, its sees all the memory and takes
weeks to get 200 megs into swap.  And this kernel runs the simulated
linuxcnc just fine so I can sit, hack out a thousand lines of gcode and
exercise it cutting virtual air from a nice comfy office chair.  Quite
important when I've 2 collapsed disks in my back.

So I'm still bumfuzzled as to why it should suddenly fail.  Its worked
for 3+ years.

Does anyone think Dash might be worth a shot?

Thanks, to both of you.

On 5/18/2016 4:42 PM, Gene Heskett wrote:

Greetings all;

I am, because my web page serves as a backup site for the os and some
tools for use with the now 30 year old trs-80 color computers, have a
script IP can run that pulls fresh copies of the sources for this code
using hg, then builds fresh copies and makes it all available on my
web page.

Unfortunately that script, running as me, suddenly has no write
permissions to do what it does.  This has been working for several
years.

This is the script:

#!/bin/bash
# since I'm always forgetting who I am
if [ `whoami` != 'gene' ]; then
   echo
   echo "!! Warning !!!"
   echo "this script needs to be run by user gene"
   echo
   echo
   exit 1
fi
mv lwtools lwtools-$(date +%Y-%m-%d-%H-%M)
hg clone http://lwtools.projects.l-w.ca/hg/ lwtools
cd lwtools
make
sudo make install
cd ..
echo
echo
echo "lwtools has been built, next is toolshed"
echo
echo
chown -R gene:www-data lwtools # make visible to the web
mv toolshed toolshed-$(date +%Y-%m-%d-%H-%M)
hg clone http://hg.code.sf.net/p/toolshed/code toolshed
cd toolshed
make -C build/unix
sudo make install
cd hdbdos
make
cd ../..
chown -R gene:www-data toolshed

Re: Got that network problem solved, now a new one

[Gene Heskett]

On Wednesday 18 May 2016 19:09:02 John L. Ries wrote:

> I guess my first question would be why the script below has anything
> to do with /opt.  I don't see a change of directory to anything under
> that directory and I would assume this is running in some directory
> you own.

Nope, this script, and the directories it mv's around, all live in the 
root of /opt, and I've been running it that way since 2013.  This is 
just one of the reasons that I go buy a fresh drive for each new 
install, so I can copy all this history from install to install, usually 
with mc.

> System directory permissions are sometimes changed during software
> updates; annoying, but true.  I sometimes have to change permissions
> on /usr/local/src for that reason.

Good point, although I haven't built anything there, or in /src/src  in 
yonks, it all gets built in ~/src, no suprises that way.
>
>
> I don't know about your system, but on most, chown can only be run by
> root.

Depends, in this case I own the files as they were just generated by me.  
And ISTR I am a member of group www-data. Just checked, yes.

>
> I don't see any bash specific syntax in your script, so you might try
> running it under a different Bourne compatible shell (perhaps ash,
> dash, or ksh) to see if it works there.  This will hopefully rule out
> the possibility of a bash bug.
>
>
> John L. Ries
> Salford Systems
> Phone: (619)543-8880 x107
> or (435)867-8885
> 
> From: Logan Erbst <lo...@iccamnetworking.us>
> Sent: Wednesday, May 18, 2016 5:34 PM
> To: debian-user@lists.debian.org
> Subject: Re: Got that network problem solved, now a new one
>
> This seems to me that it may be a bug in the version of bash that is
> running on the system, but I could be very wrong.
>
To address that:
gene@coyote:/$ ls -l `locate bin/bash`
-rwxr-xr-x 1 root root 941252 Sep 25  2014 /bin/bash
-rwxr-xr-x 1 root root   6966 Sep 25  2014 /usr/bin/bashbug
gene@coyote:/$ file /bin/bash
/bin/bash: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), 
dynamically linked, interpreter /lib/ld-linux.so.2, for GNU/Linux 
2.6.26, BuildID[sha1]=1fd3c09266e0feec964431a11fbf7f1132acdb44, stripped

But this script has been run successfully several times since the date on 
that /bin/bash.

But the kernel running now is:
gene@coyote:/$ uname -r
3.16.0-0.bpo.4-amd64

This is a 32 bit system for 2 reasons, most annoying being that the 64 
bit kernels have horrible interrupt latency so linuxcnc will not even 
launch, and while it will run with the 32 bit rtai patched kernels, 
there no PAE in those patches so I am a gigabyte or more into swap in 48 
hours uptime.  With this amd64 kernel, its sees all the memory and takes 
weeks to get 200 megs into swap.  And this kernel runs the simulated 
linuxcnc just fine so I can sit, hack out a thousand lines of gcode and 
exercise it cutting virtual air from a nice comfy office chair.  Quite 
important when I've 2 collapsed disks in my back.

So I'm still bumfuzzled as to why it should suddenly fail.  Its worked 
for 3+ years.

Does anyone think Dash might be worth a shot?

Thanks, to both of you.

> On 5/18/2016 4:42 PM, Gene Heskett wrote:
>
> Greetings all;
>
> I am, because my web page serves as a backup site for the os and some
> tools for use with the now 30 year old trs-80 color computers, have a
> script IP can run that pulls fresh copies of the sources for this code
> using hg, then builds fresh copies and makes it all available on my
> web page.
>
> Unfortunately that script, running as me, suddenly has no write
> permissions to do what it does.  This has been working for several
> years.
>
> This is the script:
> 
> #!/bin/bash
> # since I'm always forgetting who I am
> if [ `whoami` != 'gene' ]; then
> echo
> echo "!! Warning !!!"
> echo "this script needs to be run by user gene"
> echo
> echo
> exit 1
> fi
> mv lwtools lwtools-$(date +%Y-%m-%d-%H-%M)
> hg clone http://lwtools.projects.l-w.ca/hg/ lwtools
> cd lwtools
> make
> sudo make install
> cd ..
> echo
> echo
> echo "lwtools has been built, next is toolshed"
> echo
> echo
> chown -R gene:www-data lwtools # make visible to the web
> mv toolshed toolshed-$(date +%Y-%m-%d-%H-%M)
> hg clone http://hg.code.sf.net/p/toolshed/code toolshed
> cd toolshed
> make -C build/unix
> sudo make install
> cd hdbdos
> make
> cd ../..
> chown -R gene:www-data toolshed
> echo
> echo
> echo "toolshed has been built and installed, next is nitros9"
> echo
> echo
> mv nitros9 nitros9-$(date +%Y-%m-%d-%H-%M)
> hg clone http://hg.code.sf.net/p

Re: Got that network problem solved, now a new one

[Gene Heskett]

On Wednesday 18 May 2016 17:42:59 Gene Heskett wrote:

> Greetings all;
>
> I am, because my web page serves as a backup site for the os and some
> tools for use with the now 30 year old trs-80 color computers, have a
> script IP can run that pulls fresh copies of the sources for this code
> using hg, then builds fresh copies and makes it all available on my
> web page.
>
> Unfortunately that script, running as me, suddenly has no write
> permissions to do what it does.  This has been working for several
> years.
>
> This is the script:
> 
> #!/bin/bash
> # since I'm always forgetting who I am
> if [ `whoami` != 'gene' ]; then
>   echo
>   echo "!! Warning !!!"
>   echo "this script needs to be run by user gene"
>   echo
>   echo
>   exit 1
> fi
> mv lwtools lwtools-$(date +%Y-%m-%d-%H-%M)
> hg clone http://lwtools.projects.l-w.ca/hg/ lwtools
> cd lwtools
> make
> sudo make install
> cd ..
> echo
> echo
> echo "lwtools has been built, next is toolshed"
> echo
> echo
> chown -R gene:www-data lwtools # make visible to the web
> mv toolshed toolshed-$(date +%Y-%m-%d-%H-%M)
> hg clone http://hg.code.sf.net/p/toolshed/code toolshed
> cd toolshed
> make -C build/unix
> sudo make install
> cd hdbdos
> make
> cd ../..
> chown -R gene:www-data toolshed
> echo
> echo
> echo "toolshed has been built and installed, next is nitros9"
> echo
> echo
> mv nitros9 nitros9-$(date +%Y-%m-%d-%H-%M)
> hg clone http://hg.code.sf.net/p/nitros9/code nitros9
> cd nitros9
> export NITROS9DIR=$PWD
> hgpull;hgupdate
> mkdir dsks # this step is temporarily needed
> make dsk
> make dskcopy
> cd ..
> chown -R gene:www-data nitros9
> echo
> echo "nitros9 has been refreshed"
> echo "this completes the build of lwtools, toolshed, and nitros9"
> ==
> and its now being denied at the first mv operation. /opt of course is
> owned by root:root but that hasn't changed in 18 years of running
> linux. This script has been running flawlessly about once a month
> since July 2013 when I wrote it.
>
> So what was changed to prevent the common user from using /opt as
> himself? cd'd to /opt, I can't even "touch ajunkfile".  Grr.  Me,
> goes in search of my LART.
>
> Better yet, how can I fix it? /opt permissions are 40755, and I'm
> assuming a chmod 0777 as root would fix it temporarily, but thats one
> hell of a kludge.  I'd much rather find where the rules to this game
> are and get them fixed.
>
> Thanks all.
>
> Cheers, Gene Heskett

I did the above, and fixed my script with line ending && so it would bail 
out at the error point, and got two of the 3 of them rebuilt, then 
switched /opt back to 0755 perms.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 

Re: Got that network problem solved, now a new one

[John L. Ries]

I guess my first question would be why the script below has anything to do with 
/opt.  I don't see a change of directory to anything under that directory and I 
would assume this is running in some directory you own.


System directory permissions are sometimes changed during software updates; 
annoying, but true.  I sometimes have to change permissions on /usr/local/src 
for that reason.


I don't know about your system, but on most, chown can only be run by root.


I don't see any bash specific syntax in your script, so you might try running 
it under a different Bourne compatible shell (perhaps ash, dash, or ksh) to see 
if it works there.  This will hopefully rule out the possibility of a bash bug.


John L. Ries
Salford Systems
Phone: (619)543-8880 x107
or (435)867-8885

From: Logan Erbst <lo...@iccamnetworking.us>
Sent: Wednesday, May 18, 2016 5:34 PM
To: debian-user@lists.debian.org
Subject: Re: Got that network problem solved, now a new one

This seems to me that it may be a bug in the version of bash that is running on 
the system, but I could be very wrong.

On 5/18/2016 4:42 PM, Gene Heskett wrote:

Greetings all;

I am, because my web page serves as a backup site for the os and some
tools for use with the now 30 year old trs-80 color computers, have a
script IP can run that pulls fresh copies of the sources for this code
using hg, then builds fresh copies and makes it all available on my web
page.

Unfortunately that script, running as me, suddenly has no write
permissions to do what it does.  This has been working for several
years.

This is the script:

#!/bin/bash
# since I'm always forgetting who I am
if [ `whoami` != 'gene' ]; then
echo
echo "!! Warning !!!"
echo "this script needs to be run by user gene"
echo
echo
exit 1
fi
mv lwtools lwtools-$(date +%Y-%m-%d-%H-%M)
hg clone http://lwtools.projects.l-w.ca/hg/ lwtools
cd lwtools
make
sudo make install
cd ..
echo
echo
echo "lwtools has been built, next is toolshed"
echo
echo
chown -R gene:www-data lwtools # make visible to the web
mv toolshed toolshed-$(date +%Y-%m-%d-%H-%M)
hg clone http://hg.code.sf.net/p/toolshed/code toolshed
cd toolshed
make -C build/unix
sudo make install
cd hdbdos
make
cd ../..
chown -R gene:www-data toolshed
echo
echo
echo "toolshed has been built and installed, next is nitros9"
echo
echo
mv nitros9 nitros9-$(date +%Y-%m-%d-%H-%M)
hg clone http://hg.code.sf.net/p/nitros9/code nitros9
cd nitros9
export NITROS9DIR=$PWD
hgpull;hgupdate
mkdir dsks # this step is temporarily needed
make dsk
make dskcopy
cd ..
chown -R gene:www-data nitros9
echo
echo "nitros9 has been refreshed"
echo "this completes the build of lwtools, toolshed, and nitros9"
==
and its now being denied at the first mv operation. /opt of course is
owned by root:root but that hasn't changed in 18 years of running linux.
This script has been running flawlessly about once a month since July
2013 when I wrote it.

So what was changed to prevent the common user from using /opt as
himself? cd'd to /opt, I can't even "touch ajunkfile".  Grr.  Me,
goes in search of my LART.

Better yet, how can I fix it? /opt permissions are 40755, and I'm
assuming a chmod 0777 as root would fix it temporarily, but thats one
hell of a kludge.  I'd much rather find where the rules to this game are
and get them fixed.

Thanks all.

Cheers, Gene Heskett



--
Logan Erbst
Member Free Software Foundation

Re: Got that network problem solved, now a new one

[Logan Erbst]

This seems to me that it may be a bug in the version of bash that is
running on the system, but I could be very wrong.

On 5/18/2016 4:42 PM, Gene Heskett wrote:
> Greetings all;
>
> I am, because my web page serves as a backup site for the os and some 
> tools for use with the now 30 year old trs-80 color computers, have a 
> script IP can run that pulls fresh copies of the sources for this code 
> using hg, then builds fresh copies and makes it all available on my web 
> page.
>
> Unfortunately that script, running as me, suddenly has no write 
> permissions to do what it does.  This has been working for several 
> years.
>
> This is the script:
> 
> #!/bin/bash
> # since I'm always forgetting who I am
> if [ `whoami` != 'gene' ]; then
>   echo
>   echo "!! Warning !!!"
>   echo "this script needs to be run by user gene"
>   echo
>   echo
>   exit 1
> fi
> mv lwtools lwtools-$(date +%Y-%m-%d-%H-%M)
> hg clone http://lwtools.projects.l-w.ca/hg/ lwtools
> cd lwtools
> make
> sudo make install
> cd ..
> echo
> echo
> echo "lwtools has been built, next is toolshed"
> echo
> echo
> chown -R gene:www-data lwtools # make visible to the web
> mv toolshed toolshed-$(date +%Y-%m-%d-%H-%M)
> hg clone http://hg.code.sf.net/p/toolshed/code toolshed
> cd toolshed
> make -C build/unix
> sudo make install
> cd hdbdos
> make
> cd ../..
> chown -R gene:www-data toolshed
> echo
> echo
> echo "toolshed has been built and installed, next is nitros9"
> echo
> echo
> mv nitros9 nitros9-$(date +%Y-%m-%d-%H-%M)
> hg clone http://hg.code.sf.net/p/nitros9/code nitros9
> cd nitros9
> export NITROS9DIR=$PWD
> hgpull;hgupdate
> mkdir dsks # this step is temporarily needed
> make dsk
> make dskcopy
> cd ..
> chown -R gene:www-data nitros9
> echo
> echo "nitros9 has been refreshed"
> echo "this completes the build of lwtools, toolshed, and nitros9"
> ==
> and its now being denied at the first mv operation. /opt of course is 
> owned by root:root but that hasn't changed in 18 years of running linux.
> This script has been running flawlessly about once a month since July 
> 2013 when I wrote it.
>
> So what was changed to prevent the common user from using /opt as 
> himself? cd'd to /opt, I can't even "touch ajunkfile".  Grr.  Me, 
> goes in search of my LART.
>
> Better yet, how can I fix it? /opt permissions are 40755, and I'm 
> assuming a chmod 0777 as root would fix it temporarily, but thats one 
> hell of a kludge.  I'd much rather find where the rules to this game are 
> and get them fixed.
>
> Thanks all.
>
> Cheers, Gene Heskett

-- 
Logan Erbst
Member Free Software Foundation



signature.asc
Description: OpenPGP digital signature

Got that network problem solved, now a new one

[Gene Heskett]

Greetings all;

I am, because my web page serves as a backup site for the os and some 
tools for use with the now 30 year old trs-80 color computers, have a 
script IP can run that pulls fresh copies of the sources for this code 
using hg, then builds fresh copies and makes it all available on my web 
page.

Unfortunately that script, running as me, suddenly has no write 
permissions to do what it does.  This has been working for several 
years.

This is the script:

#!/bin/bash
# since I'm always forgetting who I am
if [ `whoami` != 'gene' ]; then
echo
echo "!! Warning !!!"
echo "this script needs to be run by user gene"
echo
echo
exit 1
fi
mv lwtools lwtools-$(date +%Y-%m-%d-%H-%M)
hg clone http://lwtools.projects.l-w.ca/hg/ lwtools
cd lwtools
make
sudo make install
cd ..
echo
echo
echo "lwtools has been built, next is toolshed"
echo
echo
chown -R gene:www-data lwtools # make visible to the web
mv toolshed toolshed-$(date +%Y-%m-%d-%H-%M)
hg clone http://hg.code.sf.net/p/toolshed/code toolshed
cd toolshed
make -C build/unix
sudo make install
cd hdbdos
make
cd ../..
chown -R gene:www-data toolshed
echo
echo
echo "toolshed has been built and installed, next is nitros9"
echo
echo
mv nitros9 nitros9-$(date +%Y-%m-%d-%H-%M)
hg clone http://hg.code.sf.net/p/nitros9/code nitros9
cd nitros9
export NITROS9DIR=$PWD
hgpull;hgupdate
mkdir dsks # this step is temporarily needed
make dsk
make dskcopy
cd ..
chown -R gene:www-data nitros9
echo
echo "nitros9 has been refreshed"
echo "this completes the build of lwtools, toolshed, and nitros9"
==
and its now being denied at the first mv operation. /opt of course is 
owned by root:root but that hasn't changed in 18 years of running linux.
This script has been running flawlessly about once a month since July 
2013 when I wrote it.

So what was changed to prevent the common user from using /opt as 
himself? cd'd to /opt, I can't even "touch ajunkfile".  Grr.  Me, 
goes in search of my LART.

Better yet, how can I fix it? /opt permissions are 40755, and I'm 
assuming a chmod 0777 as root would fix it temporarily, but thats one 
hell of a kludge.  I'd much rather find where the rules to this game are 
and get them fixed.

Thanks all.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 

Re: Network Problem

[Johann Spies]

On 28 April 2016 at 18:23, NightC Core  wrote:

>
> The card works in 32 but not under debian 64, when looking around on
> google I find many similar cases to mine.
> https://www.google.com/search?q=debian%208%20marvell%2088E8056=j
> Nightcore
>
>
I see here(
http://www.linuxquestions.org/questions/linux-networking-3/how-to-configure-marvell-yukon-88e8055-pci-e-gigabit-ethernet-on-debian-910638/)
that this card use the sky2 module.

Did you try
sudo modprobe sky2  ?

Regards
Johann

Re: Network Problem

[NightC Core]

Hello,
Thank you for your reply.
What makes me say this is his because I install debian on 8 pc in 32
everything worked, and during installation in 64 unable to configure the
network ... or after installation!
If I specify my nationnalité is to avoid the problems linked to language.
If I need 64 debian is to use Java in 64.
The card works in 32 but not under debian 64, when looking around on google
I find many similar cases to mine.
https://www.google.com/search?q=debian%208%20marvell%2088E8056=j
Nightcore

2016-04-28 10:16 GMT+02:00 Nicolas George :

> Le decadi 10 floréal, an CCXXIV, NightC Core a écrit :
> > I am a French user
>
> I fail to see how your nationality is relevant to the issue, but no matter.
>
> >and I have a big problem, I created a debian server on
> > an old pc except that I need 64bit debian and my network card is a
> Marvell
> > 88E8056 is that it only works in 32?
>
> What makes you say that? A quick look in the logs of the kernel shows that
> this card is supported natively on all relevant architectures since long
> ago (~may 2007).
>
> Regards,
>
> --
>   Nicolas George
>

Re: Network Problem

[Nicolas George]

Le decadi 10 floréal, an CCXXIV, NightC Core a écrit :
> I am a French user

I fail to see how your nationality is relevant to the issue, but no matter.

>and I have a big problem, I created a debian server on
> an old pc except that I need 64bit debian and my network card is a Marvell
> 88E8056 is that it only works in 32?

What makes you say that? A quick look in the logs of the kernel shows that
this card is supported natively on all relevant architectures since long
ago (~may 2007).

Regards,

-- 
  Nicolas George


signature.asc
Description: Digital signature

Re: Network Problem

[Henning Follmann]

On Thu, Apr 28, 2016 at 01:16:05AM +0200, NightC Core wrote:
> Hello,
> I am a French user and I have a big problem, I created a debian server on
> an old pc except that I need 64bit debian and my network card is a Marvell
> 88E8056 is that it only works in 32? Can not you do a 64 with the driver or
> other packages or the 32 used to operate the network card? Please.
> Nightcore


Why do you need 64bit?

-H

-- 
Henning Follmann   | hfollm...@itcfollmann.com

Network Problem

[NightC Core]

Hello,
I am a French user and I have a big problem, I created a debian server on
an old pc except that I need 64bit debian and my network card is a Marvell
88E8056 is that it only works in 32? Can not you do a 64 with the driver or
other packages or the 32 used to operate the network card? Please.
Nightcore

[Solved] Strange network problem with Xen 4.0 on stable

[François TOURDE]

Hi.

For the archives:

Le 15883ième jour après Epoch,
François TOURDE écrivait:

 Hi list.

 I'm using Xen (long time ago), and I've a strange problem with one of
 the DomU. It's the only DomU with this behaviour. It doesn't reply to
 ping and can't have access to the net.

 In detail:

[...]

 Packets seems to be forwarded from Dom0 to DomU, but not from DomU to Dom0:

[...]

 Routes are:

 Dom0:
 root@srv04:~# ip route
 88.191.222.127 dev vif115.0  scope link  src 88.191.108.41 
 88.191.223.138 dev vif114.0  scope link  src 88.191.108.41 
 88.191.229.230 dev vif113.0  scope link  src 88.191.108.41 
 88.191.226.108 dev vif116.0  scope link  src 88.191.108.41 
 88.191.108.0/24 dev eth0  proto kernel  scope link  src 88.191.108.41 
 88.191.110.0/24 dev eth1  proto kernel  scope link  src 88.191.110.41 
 default via 88.191.110.1 dev eth1 
 default via 88.191.108.1 dev eth0 

Even with accept_source_routing on all concerned interfaces, the
vif114.0 packets that should be sent to outside network are routed by
eth1, not the receiving interface eth0.

Disabling eth1 (not yet used) solves the problem.


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87bo6q9y7n@tourde.org

Strange network problem with Xen 4.0 on stable

[François TOURDE]

Hi list.

I'm using Xen (long time ago), and I've a strange problem with one of
the DomU. It's the only DomU with this behaviour. It doesn't reply to
ping and can't have access to the net.

In detail:

Dom0 Debian stable:
  Linux srv04 2.6.32-5-xen-amd64 #1 SMP Fri May 10 11:48:05 UTC 2013 x86_64 
GNU/Linux

Working DomU:
  Linux wiki 2.6.32-5-amd64 #1 SMP Fri May 10 08:43:19 UTC 2013 x86_64 GNU/Linux

Not working DomU:
  Linux rh42g1 2.6.32-5-amd64 #1 SMP Fri May 10 11:48:05 UTC 2013 x86_64 
GNU/Linux

Packets seems to be forwarded from Dom0 to DomU, but not from DomU to Dom0:

(srv04=Dom0, Xternal NIC=eth0)

root@srv04:~# tcpdump -n -i eth0  src 88.191.223.138 or dst 88.191.223.138
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes
10:21:51.437722 IP 62.147.184.98  88.191.223.138: ICMP echo request, id 1448, 
seq 1, length 64
10:21:52.445622 IP 62.147.184.98  88.191.223.138: ICMP echo request, id 1448, 
seq 2, length 64
10:21:53.454046 IP 62.147.184.98  88.191.223.138: ICMP echo request, id 1448, 
seq 3, length 64

But packets from DomU to Dom0 seems to be sent to Dom0:

root@srv04:~# tcpdump -n -i vif114.0  src 88.191.223.138 or dst 88.191.223.138
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on vif114.0, link-type EN10MB (Ethernet), capture size 65535 bytes
10:22:13.224780 IP 62.147.184.98  88.191.223.138: ICMP echo request, id 1459, 
seq 1, length 64
10:22:13.224866 IP 88.191.223.138  62.147.184.98: ICMP echo reply, id 1459, 
seq 1, length 64
10:22:14.224020 IP 62.147.184.98  88.191.223.138: ICMP echo request, id 1459, 
seq 2, length 64
10:22:14.224114 IP 88.191.223.138  62.147.184.98: ICMP echo reply, id 1459, 
seq 2, length 64
10:22:18.223371 ARP, Request who-has 88.191.223.138 tell 88.191.108.41, length 
28
10:22:18.223467 ARP, Reply 88.191.223.138 is-at 00:16:3e:6b:9e:3c, length 28

Routes are:

Dom0:
root@srv04:~# ip route
88.191.222.127 dev vif115.0  scope link  src 88.191.108.41 
88.191.223.138 dev vif114.0  scope link  src 88.191.108.41 
88.191.229.230 dev vif113.0  scope link  src 88.191.108.41 
88.191.226.108 dev vif116.0  scope link  src 88.191.108.41 
88.191.108.0/24 dev eth0  proto kernel  scope link  src 88.191.108.41 
88.191.110.0/24 dev eth1  proto kernel  scope link  src 88.191.110.41 
default via 88.191.110.1 dev eth1 
default via 88.191.108.1 dev eth0 

Working DomU:
88.191.229.0/24 dev eth0  proto kernel  scope link  src 88.191.229.230 
default dev eth0  scope link 

Not working DomU:
88.191.223.0/24 dev eth0  proto kernel  scope link  src 88.191.223.138 
default dev eth0  scope link 

Any ideas are welcome


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87li5warkj@tourde.org

Re: Odd Network Problem

[Klaus Doering]

On 20/05/13 23:08, george cox wrote:






 - Original Message -

 From: Klaus Doering

 Sent: 05/20/13 04:27 PM

 To: debian-user@lists.debian.org

 Subject: Re: Odd Network Problem

 On 20/05/13 15:19, george cox wrote:

  I think the one thing I would  want to know about my original problem
   is in the squeeze version of gnome's network-manager, left-clicking
   on its notification area icon would, show several options one of
   which is auto eth0, this seemed to reliably attach my laptop's
   ethernet port to the default network of the printer-server.

 I'm pretty certain that the auto eth0 issue is a red herring: it's
 only an automatically generated name for your default wired
 connection, and although I haven't dug very deeply, the discussion in
 [1] would indicate that the change to Wired connection was made to
 make the naming more user friendly.

 [1] 
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/386900




 I can understand the motivation of the poster in [1], there often
 are a lot of techy details in using linux that can trip newbies up,
 but I hate to see details covered up. Then the system becomes a black
 box. In an ideal system, the gory details would be hidden, but could
 be revealed if the user felt like taking control. But clicking on
 auto eth0 must have done something to the interface because until I
 did that I couldn't get connected.

All the technical details are still there, in (right click) --
Connection Information and in Edit Connections. If you really wanted
the label auto eth0 back, just edit the connection and rename it. The
magic lies in the automatically connect to this network when it is
available (General tab), and in selecting the necessary IP setting
(most likely IPv4, DHCP).

---

After a factory reset of your print server, it cannot connect to your
wifi, and thus it cannot acquire an IP address via DHCP, and thus it
cannot pass-through DHCP request from other clients connected to the
4-port switch. Now, if your new laptop's Wired Connection is set up
as above, then the connection cannot be made since there is no DHCP
server available at that point. Hence my suggestion to manually set
the IP, and even go through the command line to make it more
obvious. Under those circumstances there is not much magic left, and
you have to bring down and back up the interface manually (the ifdown
eth0 -- ifup eth0 cycle in my last post).

It would still be easier to connect both, the laptop and one of the
four ethernet ports of the print server, to your router --- under the
assumption that the router is using the same subnet (192.168.0.x), has
at least two ethernet port available, and acts as the DHCP server. In
that case, your laptop will automatically connect, acquire an IP
address, and you can now access 192.168.0.102 without any further
stress.


HTH
Klaus


[2] http://kbserver.netgear.com/pdf/wgps606_user_manual.pdf



--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/519b272d.1070...@gmail.com

Re: Odd Network Problem

[Lisi Reisz]

On Monday 20 May 2013 00:15:30 george cox wrote:
 I don't know why it wasn't quoted, I'm just hitting re
  ply in the email providers web interface. Not sure what you mean by no
 air. I'll see what this email looks like when I send this one, maybe it was
 just a fluke.

Yes, some providers do that.  And my email to you has been rammed up all 
together.  It is obviously a problem with your email provider. :-(

By “air” I mean gaps, as between paragraphs.  I find text all crammed up very 
difficult to read - indeed I had difficulty unscrambling your reply to me in 
order to acknowledge it.

Which email provider's web interface is this?  It seems even  more than 
usually unfriendly. :-(  And most of them are fairly uncooperative.  E.g. 
Gmail's habit of breaking up threads is a pain.

Lisi


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201305200947.19562.lisi.re...@gmail.com

Re: Odd Network Problem

[george cox]

- Original Message -
From: Lisi Reisz
Sent: 05/20/13 04:47 AM
To: debian-user@lists.debian.org
Subject: Re: Odd Network Problem

On Monday 20 May 2013 00:15:30 george cox wrote:  I don't know why it wasn't 
quoted, I'm just hitting re  ply in the email providers web interface. Not 
sure what you mean by no  air. I'll see what this email looks like when I send 
this one, maybe it was  just a fluke. Yes, some providers do that. And my 
email to you has been rammed up all together. It is obviously a problem with 
your email provider. :-( By “air” I mean gaps, as between paragraphs. I find 
text all crammed up very difficult to read - indeed I had difficulty 
unscrambling your reply to me in order to acknowledge it. Which email 
provider's web interface is this? It seems even more than usually unfriendly. 
:-( And most of them are fairly uncooperative. E.g. Gmail's habit of breaking 
up threads is a pain. Lisi The provider is mail.com, which is free as is free 
beer, and perhaps not a good quality beer either. The problem was that quoting 
isn't done as text, when I trimmed my reply to Klaus I destroyed all of
  the quoting. I didn't see that at the time because all that does on the 
screen is remove a very faint line on the side.

I think the one thing I would want to know about my original problem is in the 
squeeze version of gnome's network-manager, left-clicking on its notification 
area icon would, show several options one of which is auto eth0, this seemed 
to reliably attach my laptop's ethernet port to the default network of the 
printer-server. I am curious what auto eth0 does because neither the 
print-server nor my laptop has a dhcp-server, and neither item was connected to 
any other network. The print-server must have some magic going on in order to 
bridge equipment plugged into it to the wireless network (once the wireless 
part is configured at least), but the manual clearly says when the unit is 
reset if it can't find a dhcp server it will use the default ip. I've checked 
that neither laptop has a dhcp server installed.

The second is simply using ifconfig eth0 192.168.0.22 (the .22 I randomly 
chose, the print-server defaults to using .102) worked on the laptop with 
squeeze installed, but didn't with the one with wheezy.

Thanks.

Re: Odd Network Problem

[Klaus Doering]

On 20/05/13 15:19, george cox wrote:


I think the one thing I would  want to know about my original problem

 is in the squeeze version of gnome's network-manager, left-clicking
 on its notification area icon would, show several options one of
 which is auto eth0, this seemed to reliably attach my laptop's
 ethernet port to the default network of the printer-server.

I'm pretty certain that the auto eth0 issue is a red herring: it's
only an automatically generated name for your default wired
connection, and although I have't dug very deeply, the discussion in
[1] would indicate that the change to Wired connection was made to
make the naming more user friendly.


(...) but the manual clearly  says when the

 unit is reset if it can't find a dhcp server it will use the default
 ip. (...) the print-server defaults to using .102  (...)


I'd guess that the different results that you see with the old and the
new laptop reflect two not exactly identical procedures. Could you try
the following sequence:

-- reset the printserver so that it falls back to it's default IP
setting (192.168.0.102 ?)

-- edit your /etc/network/interfaces file to include a static eth0
definition, something like this:

auto eth0
iface eth0 inet static
address 192.168.0.22
gateway 192.168.0.1
network 192.168.0.0
netmask 255.255.255.0

-- then cycle the interface with
   ifdown eth0
ifup eth0

-- check with ifconfig eth0 that the interface has the correct
   address, and that it is shown as UP

-- try and connect

-- if you now unplug the cable and plug it back in, I believe you'd
   have to repeat the ifdown ifup cycle

What make / model print server do you have?


Klaus

[1] https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/386900


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/519a8743.4080...@bigfoot.com

Re: Odd Network Problem

[george cox]

- Original Message -
From: Klaus Doering
Sent: 05/20/13 04:27 PM
To: debian-user@lists.debian.org
Subject: Re: Odd Network Problem

On 20/05/13 15:19, george cox wrote:  I think the one thing I would want to 
know about my original problem  is in the squeeze version of gnome's 
network-manager, left-clicking  on its notification area icon would, show 
several options one of  which is auto eth0, this seemed to reliably attach 
my laptop's  ethernet port to the default network of the printer-server. I'm 
pretty certain that the auto eth0 issue is a red herring: it's only an 
automatically generated name for your default wired connection, and although I 
have't dug very deeply, the discussion in [1] would indicate that the change to 
Wired connection was made to make the naming more user friendly.  (...) but 
the manual clearly says when the  unit is reset if it can't find a dhcp server 
it will use the default  ip. (...) the print-server defaults to using .102 
(...) I'd guess that the different results that you see with the old and the 
new laptop reflect two not exactly identical procedures. Could you t
 ry the following sequence: -- reset the printserver so that it falls back to 
it's default IP setting (192.168.0.102 ?) -- edit your /etc/network/interfaces 
file to include a static eth0 definition, something like this: auto eth0 iface 
eth0 inet static address 192.168.0.22 gateway 192.168.0.1 network 192.168.0.0 
netmask 255.255.255.0 -- then cycle the interface with ifdown eth0 ifup eth0 -- 
check with ifconfig eth0 that the interface has the correct address, and that 
it is shown as UP -- try and connect -- if you now unplug the cable and plug it 
back in, I believe you'd have to repeat the ifdown ifup cycle What make / model 
print server do you have? Klaus [1] 
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/386900 I can 
understand the motivation of the poster in [1], there often are a lot of techy 
details in using linux that can trip newbies up, but I hate to see details 
covered up. Then the system becomes a black box. In an ideal system, the gory 
details would 
 be hidden, but could be revealed if the user felt like taking control. But 
clicking on auto eth0 must have done something to the interface because until 
I did that I couldn't get connected.

The print-server is a netgear WPGS606. I had a wireless access point made by 
them as well and I had to use that auto eth0 before I could even ping the 
thing. I forget what model the access-point was, it broke six or seven months 
ago and I chucked it.

I'll try reseting it and let you know what happens. Thanks for the help.

Odd Network Problem

[george cox]

I have a piece of equipment that when conntected to my cablebox/TV allows me to 
view my home TV on any computer from anywhere on the internet. This device only 
has a hardwired internet connection so I use a wireless print-server (it has a 
4 ethernet ports that it bridges to the wireless) to connect the device to my 
home wireless network. Friday I changed my internet provider, and needed to 
reconfigure the print-server to use the new wireless network.

The problem was I could not get my laptop to connect to the printer-server (via 
a hardwired cable). I tried letting my laptop auto configure, I tried setting 
the address manually (ifconfig). None of this worked I could not get connected 
to the print-server. I turned off the wireless network on my laptop so the 
hardwired ethernet was the only NIC available. When plugging in the ethernet 
cable, the network manager would grid away for 3 or 4 minutes but the 
connection would always fail.

I bought a my laptop last week and installed wheezy on it. I still have the old 
one and have not updated, so it still runs squeeze. I pulled out my old laptop, 
plugged-in the ethernet cable to the print-server and entered the same ifconfig 
commands to set the IP address manually and viola, I could connect to the 
print-server and modified its settings with no problem.

Any idea why one laptop worked while the other didn't.

As a side note, in the network manager on the old laptop with squeeze, if you 
left-clicked one of the options listed there is auto eth0, this doesn't seem 
to exist on the network manager on the new wheezy laptop. Is there an 
equivalent function in the wheezy version of the GUI? I have used auto eth0 
several times to connect to various hardwired equipment and it comes in handy. 
Does anyone know exactly what auto eth0 does to the ethernet port?

Thanks.

Re: Odd Network Problem

[Klaus Doering]

On 19/05/13 13:30, george cox wrote:
I have a piece of equipment that when conntected to my cablebox/TV 
allows me to view my home TV on any computer from anywhere on the 
internet. This device only has a hardwired internet connection so I 
use a wireless print-server (it has a 4 ethernet ports that it bridges 
to the wireless) to connect the device to my home wireless network. 
Friday I changed my internet provider, and needed to reconfigure the 
print-server to use the new wireless network.


The problem was I could not get my laptop to connect to the 
printer-server (via a hardwired cable). I tried letting my laptop auto 
configure, I tried setting the address manually (ifconfig). None of 
this worked I could not get connected to the print-server. I turned 
off the wireless network on my laptop so the hardwired ethernet was 
the only NIC available. When plugging in the ethernet cable, the 
network manager would grid away for 3 or 4 minutes but the connection 
would always fail.


I bought a my laptop last week and installed wheezy on it. I still 
have the old one and have not updated, so it still runs squeeze. I 
pulled out my old laptop, plugged-in the ethernet cable to the 
print-server and entered the same ifconfig commands to set the IP 
address manually and viola, I could connect to the print-server and 
modified its settings with no problem.


Any idea why one laptop worked while the other didn't.

As a side note, in the network manager on the old laptop with squeeze, 
if you left-clicked one of the options listed there is auto eth0, 
this doesn't seem to exist on the network manager on the new wheezy 
laptop. Is there an equivalent function in the wheezy version of the 
GUI? I have used auto eth0 several times to connect to various 
hardwired equipment and it comes in handy. Does anyone know exactly 
what auto eth0 does to the ethernet port?


Thanks.


George

This could still be a network config issue. An easy way around might
be to connect (wired) both, the print server and the new laptop, to your
router (assuming that the router also acts as the dhcp server, and that both
clients are configured to get their ip address through dhcp). In the
router's  log you can then see the connected devices and their
respective IP addresses. Can you connect from laptop to print server now?

Klaus


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/5198d2de.3040...@gmail.com

Re: Odd Network Problem

[george cox]

This could still be a network config issue. An easy way around might be to 
connect (wired) both, the print server and the new laptop, to your router 
(assuming that the router also acts as the dhcp server, and that both clients 
are configured to get their ip address through dhcp). In the router's log you 
can then see the connected devices and their respective IP addresses. Can you 
connect from laptop to print server now? Klaus I don't think that can work. The 
print-server doesn't have the ability to connect it to the router through a 
wired port, it just has the wireless. The ethernet ports are only used to 
bridge other non-wireless equipment through the printer-server to whatever 
wireless network the printer-server is configured to use. The rub is the only 
way to configure what wireless network the print-server uses is to put a 
computer on one of those ethernet ports, hold the reset button on the 
print-server resetting it to factory defaults, then configure the wireless via 
a 
 web-page generated by the print-server. What seems weird to me, is using 
ifconfig command to set an IP worked on the squeeze laptop, but didn't on the 
wheezy laptop. Both systems seem to take the ip and the output of running 
ifconfig -a looked the same on both. It was just that on one box I could 
connect to the print-servers webpage and the other I couldn't. On both I took 
care to disconnect from all other networks, so I wasn't a routing issue.

Re: Odd Network Problem

[Lisi Reisz]

On Sunday 19 May 2013 16:43:31 george cox wrote:
 This could still be a network config issue. An easy way around might be to
 connect (wired) both, the print server and the new laptop, to your router
 (assuming that the router also acts as the dhcp server, and that both
 clients are configured to get their ip address through dhcp). In the
 router's log you can then see the connected devices and their respective IP
 addresses. Can you connect from laptop to print server now? Klaus I don't
 think that can work. The print-server doesn't have the ability to connect
 it to the router through a wired port, it just has the wireless. The
 ethernet ports are only used to bridge other non-wireless equipment through
 the printer-server to whatever wireless network the printer-server is
 configured to use. The rub is the only way to configure what wireless
 network the print-server uses is to put a computer on one of those ethernet
 ports, hold the reset button on the print-server resetting it to factory
 defaults, then configure the wireless via a web-page generated by the
 print-server. What seems weird to me, is using ifconfig command to set an
 IP worked on the squeeze laptop, but didn't on the wheezy laptop. Both
 systems seem to take the ip and the output of running ifconfig -a looked
 the same on both. It was just that on one box I could connect to the
 print-servers webpage and the other I couldn't. On both I took care to
 disconnect from all other networks, so I wasn't a routing issue.

I am interested in your problem and might even be able to help, but I cannot 
cope with this.  You have not quoted what you are replying to, and there is 
no air here at all.  I could, of course, reformat it, but I would still not 
have the quotation.

You will of course get help from those who are not bothered by such things. 
But you might get more answers if you made yourself more accessible.

Lisi


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201305191712.54992.lisi.re...@gmail.com

Re: Odd Network Problem

[george cox]

On Sunday 19 May 2013 16:43:31 george cox wrote:  This could still be a 
network config issue. An easy way around might be to  connect (wired) both, 
the print server and the new laptop, to your router  (assuming that the router 
also acts as the dhcp server, and that both  clients are configured to get 
their ip address through dhcp). In the  router's log you can then see the 
connected devices and their respective IP  addresses. Can you connect from 
laptop to print server now? Klaus I don't  think that can work. The 
print-server doesn't have the ability to connect  it to the router through a 
wired port, it just has the wireless. The  ethernet ports are only used to 
bridge other non-wireless equipment through  the printer-server to whatever 
wireless network the printer-server is  configured to use. The rub is the only 
way to configure what wireless  network the print-server uses is to put a 
computer on one of those ethernet  ports, hold the reset button on the print-
 server resetting it to factory  defaults, then configure the wireless via a 
web-page generated by the  print-server. What seems weird to me, is using 
ifconfig command to set an  IP worked on the squeeze laptop, but didn't on the 
wheezy laptop. Both  systems seem to take the ip and the output of running 
ifconfig -a looked  the same on both. It was just that on one box I could 
connect to the  print-servers webpage and the other I couldn't. On both I took 
care to  disconnect from all other networks, so I wasn't a routing issue. I am 
interested in your problem and might even be able to help, but I cannot cope 
with this. You have not quoted what you are replying to, and there is no air 
here at all. I could, of course, reformat it, but I would still not have the 
quotation. You will of course get help from those who are not bothered by such 
things. But you might get more answers if you made yourself more accessible. 
Lisi I don't know why it wasn't quoted, I'm just hitting re
 ply in the email providers web interface. Not sure what you mean by no air. 
I'll see what this email looks like when I send this one, maybe it was just a 
fluke.