Networking issues with Haswell-based Linux increase Courvoisier consumption

[chalsall]

Originally Posted by ewmayer

ping: unknown host 172.16.x.1

No change in LEDs during this.

The result of "ping 172.16.1.1"?

[ewmayer]

Originally Posted by chalsall

The result of "ping 172.16.1.1"?

PING 172.16.1.1 (172.16.1.1) 56(84) bytes of data.
[rapidly alternating ._ ascii char-field here, until I ^Ced it]
--- 172.16.1.1 ping statistics ---
24387 packets transmitted, 24387 packets received, 0% packet loss, time 7970ms
[added packet-stats-foo snipped]

[paulunderwood]

On the Debian Haswell box using the menus try going into: system-->preferences-->Network Connections
highlight the "wired connection"
click on the "edit" button
choose the ipv4 tab
make sure the address is 192.168.1.102
and the mask is 255.255.255.0
click on "apply"

On the MacBook:

ping 192.168.1.102

Also can make sure the MacBook is on the same subnet i.e 255.255.255.0 and that its address is 192.168.1.x where x is not the same as the Haswell or any router you have connected by the cables

[chalsall]

Originally Posted by ewmayer

PING 172.16.1.1 (172.16.1.1) 56(84) bytes of data.
[rapidly alternating ._ ascii char-field here, until I ^Ced it]
--- 172.16.1.1 ping statistics ---
24387 packets transmitted, 24387 packets received, 0% packet loss, time 7970ms
[added packet-stats-foo snipped]

Be happy...

You've just "made friends" with 172.16.1.1.

[ewmayer]

Originally Posted by paulunderwood

On the Debian Haswell box using the menus try going into: system-->preferences-->Network Connections
highlight the "wired connection"
click on the "edit" button
choose the ipv4 tab
make sure the address is 192.168.1.102
and the mask is 255.255.255.0
click on "apply"

Don't I wish - this was setup as a barebones access-via-network-ssh-only system, no GUI. I am interfacing in term mode via LCD right now.

On the MacBook:

ping 192.168.1.102

Also can make sure the MacBook is on the same subnet i.e 255.255.255.0 and that it's address is 192.168.1.x where x is not the same as the Haswell or any router you have connected by the cables

Macbook is ....101, and has always been on that 255.255.255.0 subnet since I first set things up last December. That ping is precisely what I tried after making the eth0-no-rename changes.

Still don't understand why ifconfig is showing the 172-address, not the 192-one I have in my interfaces file. {Maybe you explained it in your IPv4 note, but I need it in English.]

[firejuggler]

it may help :
https://tools.ietf.org/html/rfc5735

[ewmayer]

Originally Posted by firejuggler

it may help :
https://tools.ietf.org/html/rfc5735

Can you condense that manypage spec into 1 or 2 sentences? I don't want ti sound like a Luddite, but I have no interest in becoming a networking expert, and actually would like to get some code written at some point this month! (which has a little over 1 day to go, alas).

Fuck me - had a perfectly good working local-ethernet setup, even with new mobo and network card it should need at most a few file edits and reboot to get this working. Now I'm looking at 20-page "Special Use IPv4 Addresses" specs.

I do see this snip in the spec, though:

192.168.0.0/16 - This block is set aside for use in private networks.
Its intended use is documented in [RFC1918]. As described in that
RFC, addresses within this block do not legitimately appear on the
public Internet. These addresses can be used without any
coordination with IANA or an Internet registry.

Yeah - that's the one I want. Where in the hell did it go? Is it being obfuscated by the 172-one?

[ewmayer]

Signing off for today ... thx again for your generous willingness to help, all.

But if I don't get at least some real (coding) work done today I'm gonna be really annoyed.

[paulunderwood]

To get it back do:

ifconfig eth0 192.168.1.102
ifconfig eth0 up

Now try pinging from the MacBook, please

[ewmayer]

Originally Posted by paulunderwood

To get it back do:

ifconfig eth0 192.168.1.102
ifconfig eth0 up

Now try pinging from the MacBook, please

That works - success at last! Now I just need to fix my dodgy-NIC-ethernet-cable-plug issue ... tried swapping the 2 cable ends, same symptoms, confirming that the problem is with the plug in the ethernet card.

Thanks for all the help, folks!

[paulunderwood]

Originally Posted by ewmayer

That works - success at last! Now I just need to fix my dodgy-NIC-ethernet-cable-plug issue ... tried swapping the 2 cable ends, same symptoms, confirming that the problem is with the plug in the ethernet card.

Thanks for all the help, folks!

You are welcome. I hope it works after a reboot too.

Perhaps a small shim jammed in with the plug would solve the NIC socket problem, as long as you do not prevent contact.