- removed issue_update
Static IP config does not set interface Broadcast address.
With a static network configuration the eth0 interface is not completely set up. In my case the Bcast should be 192.168.255.255. This effects Samba broadcast discovery and may effect other things. All broadcasts from the T3 are to the old BSD broadcast address.
root@beyonwizt3:~# ifconfig eth0 eth0 Link encap:Ethernet HWaddr 00:1E:A0:00:5E:05 inet addr:192.168.255.234 Bcast:0.0.0.0 Mask:255.255.255.0 inet6 addr: fe80::21e:a0ff:fe00:5e05/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2077 errors:0 dropped:784 overruns:0 frame:0 TX packets:1260 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:239174 (233.5 KiB) TX bytes:566447 (553.1 KiB) Interrupt:16
Reproduction steps
Configure a static network configuration. Login to box, "ifconfig eth0". Check Bcast value, will be 0.0.0.0
Comments (10)
-
reporter -
- removed issue_status
The issue was updated with the following change(s):
- The status has been updated, from New to Delegated.
-
reporter /etc/network/interfaces should have "broadcast" and/or "network" entries for static configuration.
i.e. something like this :-
root@beyonwizt3:/media/hdd# cat /etc/network/interfaces # automatically generated by enigma2 # do NOT change manually!
auto lo iface lo inet loopback
auto eth0 iface eth0 inet static hostname $(hostname) address 192.168.255.234 netmask 255.255.255.0 network 192.168.255.0 broadcast 192.168.255.255
-
Account Deleted I got this working today from my T3, Needed to add both network and broadcast and reboot to get it working - needed both.
Needed dns-nameserver to register on network properly
hostname $(hostname) address 192.168.0.160 netmask 255.255.255.0 gateway 192.168.0.254 network 192.168.0.0 broadcast 192.168.0.255 dns-nameservers 192.168.0.254
-
reporter - removed issue_severity
- removed issue_priority
The issue was updated with the following change(s):
- The priority has been updated, from Normal to High.
- The severity has been updated, from Normal to Major.
-
reporter - removed issue_severity
- removed issue_priority
Having the wrong broadcast address with static network configurations is more than just in inconvenience to users.
I have bumped both the Priority and Severity to reflect this.
-
- removed issue_status
The issue was updated with the following change(s):
- The status has been updated, from Delegated to Implemented.
-
- removed issue_status
The issue was updated with the following change(s):
- The status has been updated, from Implemented to Testing.
-
- removed issue_category
The issue was updated with the following change(s):
- The category has been updated, from Not determined to Application / User Interface.
-
- removed issue_resolution
- removed issue_percent
- removed issue_close
- removed issue_status
The issue was updated with the following change(s):
- The status has been updated, from Testing to Closed.
- This issue has been closed
- This issue's progression has been updated to 100 percent completed.
- The resolution has been updated, from Not determined to Fixed.
- Log in to comment
The issue was updated with the following change(s):